Personalized campaigns and approval

Choose a review mode for each campaign

• ColdPegion: open Review and approval, inspect recipients and rendered emails, select reviewed messages, then approve. Your MCP client cannot approve in this mode.
• MCP client: the client shows the exact recipient, subject and message and asks your approval there. It then submits those email revisions with the review epoch.
• Auto: emails need no review approval after campaign launch. Sender permissions, schedules, verification holds, suppression and plan limits still apply.

A complete MCP workflow

1. 1create_campaign creates a draft, offer and audience from a brief. Choose reviewMode and reuse requestId on retries.
2. 2import_leads adds people to the returned listId; get_campaign_contacts pages through their facts and verification states.
3. 3configure_agent chooses senderEmails, cadence and schedule. Do this before approval because configuration changes invalidate reviews.
4. 4Write a unique subject and safe HTML body for each person. prepare_emails stores each prospectEmail and step, without another platform AI call. Follow-up step numbers must be contiguous from zero.
5. 5get_campaign_review returns exact messages, revisions and reviewEpoch. Respect pagination and the selected review policy. approve_campaign_emails is only for MCP_CLIENT and only after the human's explicit review.
6. 6launch_agent starts sending after all required approvals. pause_agent stops further queued sends; an email already being transmitted may finish.

Changes and retries

Editing an email removes its approval. Changing campaign settings invalidates earlier approvals. Already sending or sent emails cannot be overwritten. Repeating prepare_emails with identical content leaves the current revision intact.

Failed prepared deliveries are held for inspection to avoid duplicate sends on ambiguous provider timeouts. Check provider history before arranging a new send.