Approvals

Some tool calls pause and ask you to approve before they run. This applies to anything that changes your workspace in a way worth confirming.

​

How approvals work

When Conversion AI needs approval, a card appears in the chat with a short summary of what’s about to happen and two buttons:

• Allow: runs the action.
• Deny: skips it. Conversion AI sees the denial and decides what to do next, usually stopping to ask you for direction.

If several approvals are queued up in a row, you step through them one at a time, with a 1 of 3 style counter showing your progress. Examples of approval messages:

Are you sure you want to create a contact for “alex@acme.com”? Apply your changes to the “Spring Sale” blast? Create campaign “Q2 launch”? Add 47 contacts to audience?

---

​

What requires approval

The general rule: reads don’t, writes do. Anything that lists, gets, or counts runs without prompting. Anything that changes your workspace pauses for approval, in one of two ways.

​

Applying edits to an existing asset

When Conversion AI proposes edits to an existing email, form, audience, or campaign, the edits don’t apply as it works. They’re gathered into a pending list and, at the end of the turn, surfaced for you to approve or reject — one approval per asset, covering all of that asset’s merged changes. Only what you approve is written.

​

Individual write actions

Other changes prompt individually, right before they run:

• Creating contacts and custom fields, audiences, campaigns (and campaign types, statuses, and tokens), and folders.
• Adding contacts to an audience or campaign, importing contacts from a CSV, and duplicating a campaign.
• Moving assets between folders, and renaming a workflow or folder.

​

The exception: new emails, forms, and workflows

Creating a new email, form, or workflow doesn’t prompt. It produces an unpublished draft — nothing is sent, published, or activated — so the safeguard is the manual publish step you control, not an approval. Editing one of those assets later goes through the per-asset edit approval above.

​

Best practices

• Batch related changes in one instruction. A request like “go ahead and rename all of these” still produces an approval per asset, but you step through them together rather than reprompting Conversion AI each time.
• Use Deny when something is wrong. Denying is a clear signal. Conversion AI stops and asks you for direction rather than guessing at a different approach.