Read and report
AgentInspect data, compare periods, find anomalies, and prepare a sourced summary.
Evergreen guide
AI marketing automation approval checklist
Use this boundary before an AI agent receives access to customer data, campaigns, flows, catalogs, budgets, or live sends.
Why this matters nowStart here01
Set the boundary before the prompt.
An agent may have the technical ability to perform an action. That does not give it business authority.
Write down who owns each consequence before connecting the account. The rule should cover five things: the action, the allowed scope, the approval point, the activity record, and the rollback.
Authority levels02
One account. Four levels of authority.
Draft
Agent + reviewPrepare segments, flows, campaign copy, tests, and catalog changes without making them live.
Change
ApprovalEdit an existing segment, flow, template, integration, or catalog only after a person checks the proposed difference.
Send or spend
Named humanA person owns live sends, audiences, suppressions, budgets, publishing, and irreversible account actions.
Record03
Every live change needs an owner and a way back.
Keep the agent name, person approving, account, action, time, affected audience, previous state, and result. A screenshot of a finished screen is weak proof. The activity record should show what actually changed.
Test rollback before the first high-risk action. Know how to pause a flow, restore a template, reverse a segment edit, stop a campaign, and recover suppressed profiles.
The durable rule
The agent prepares. A person owns the consequence.
Automation should remove repetitive work. Authority stays visible wherever the action spends money, contacts customers, changes customer eligibility, or alters commerce.
Have us run it