Campaign approval loop (ABM / RevOps)

Runtime flow

| Stage | In this pattern | | --- | --- | | Provider | LLM generates sequence copy, subject lines, and personalization tokens from account research | | Loop + Guards | campaign.launch — brand voice guard, compliance keyword blocklist, evidence-required | | Channel | Slack — marketing ops + legal review in #campaign-approvals | | Integration | MAP/SEP (e.g. Outreach, Marketo webhook) — schedule sends only after APPROVED | | Evidence + learning | Copy hash, guard outcomes, approval latency; learning on reply-rate vs predicted |

Operational scenario

1. ABM operator opens loop for target account list segment.
2. Provider produces draft sequences per persona — no sends yet.
3. Guards block transitions containing forbidden claims or missing disclaimers.
4. Channel collects approve / revise / reject from brand and legal roles.
5. Integration activates campaign in marketing platform with approved artifact id.
6. Evidence supports regulatory review (“who approved this copy, when, with what model”).

Deterministic boundaries

• Prompt instructions cannot bypass compliance guards.
• Slack reactions are not sends — MAP activation is post-governance Integration.

Related

• SDR qualification loop
• Runtime Taxonomy — Providers
• Human approval gates