Agentic Campaign
Use when: an agent coordinates outreach across channels (email, text, voice, mail) toward one goal. This skill is a design pattern, not an implementation. Channel rules live in agentic-email, agentic-text, agentic-phone, and agentic-postcard; leads live in agentic-leads.
The one rule
One recipient, one active sequence, one goal. Any reply, meeting, or opt-out stops everything immediately.
Six invariants (do not ship without all six)
- Single active sequence. A recipient belongs to at most one sequence at a time, enforced by a shared membership check across channels. Entering a new sequence exits the old one.
- Global stop signals. Reply, meeting booked, opt-out on any channel, or complaint exits all sequences within minutes. The check runs before every send, not once a night.
- Kill-switch per campaign. One control pauses every pending send in a campaign instantly. Pausing is a normal operation (used for copy fixes and incident response), not an emergency-only ritual.
- Caps compose. Per-channel caps still apply inside a campaign, plus a per-recipient cross-channel touch cap. A campaign cannot spend what its channels would refuse.
- Measure verified outcomes. Report on replies, meetings, and deliveries reconciled against provider truth — not on sends, opens, or dashboard vanity. Every claim links to its ledger entries.
- Campaign ledger. Sequence entries and exits, per-touch outcomes, cap blocks, and kill-switch uses append per campaign. A post-mortem reads the ledger, not someone's memory.
Minimal shape
interface SequenceStep { channel: 'email' | 'text' | 'voice' | 'mail'; waitAfter: string; templateVersion: string }
interface Campaign { goal: string; steps: SequenceStep[]; touchCap: number; state: 'active' | 'paused' | 'ended' }
Check membership → check stop signals → check caps → execute step → wait → next step. Any stop signal ⇒ exit all, ledger append.
Anti-patterns
- ❌ Each channel running its own sequence against the same list.
- ❌ Overnight-batch opt-out processing while morning sends go out.
- ❌ A kill-switch that needs a deploy to take effect.
- ❌ Judging the campaign on send volume instead of verified replies.
1---2name: agentic-campaign3description: "Orchestrate multi-channel agent outreach safely — one sequence per recipient, global caps, a kill-switch, and measurement on verified outcomes. Use when an agent coordinates email, text, voice, and mail toward one goal."4metadata:5 source: https://skillmd.com/skills/pooriaarab/agentic-campaign6---78# Agentic Campaign910**Use when:** an agent coordinates outreach across channels (email, text, voice, mail) toward one goal. This skill is a **design pattern**, not an implementation. Channel rules live in `agentic-email`, `agentic-text`, `agentic-phone`, and `agentic-postcard`; leads live in `agentic-leads`.1112## The one rule1314> One recipient, one active sequence, one goal. Any reply, meeting, or opt-out stops everything immediately.1516## Six invariants (do not ship without all six)17181. **Single active sequence.** A recipient belongs to at most one sequence at a time, enforced by a shared membership check across channels. Entering a new sequence exits the old one.192. **Global stop signals.** Reply, meeting booked, opt-out on any channel, or complaint exits all sequences within minutes. The check runs before every send, not once a night.203. **Kill-switch per campaign.** One control pauses every pending send in a campaign instantly. Pausing is a normal operation (used for copy fixes and incident response), not an emergency-only ritual.214. **Caps compose.** Per-channel caps still apply inside a campaign, plus a per-recipient cross-channel touch cap. A campaign cannot spend what its channels would refuse.225. **Measure verified outcomes.** Report on replies, meetings, and deliveries reconciled against provider truth — not on sends, opens, or dashboard vanity. Every claim links to its ledger entries.236. **Campaign ledger.** Sequence entries and exits, per-touch outcomes, cap blocks, and kill-switch uses append per campaign. A post-mortem reads the ledger, not someone's memory.2425## Minimal shape2627```ts28interface SequenceStep { channel: 'email' | 'text' | 'voice' | 'mail'; waitAfter: string; templateVersion: string }29interface Campaign { goal: string; steps: SequenceStep[]; touchCap: number; state: 'active' | 'paused' | 'ended' }30```3132Check membership → check stop signals → check caps → execute step → wait → next step. Any stop signal ⇒ exit all, ledger append.3334## Anti-patterns3536- ❌ Each channel running its own sequence against the same list.37- ❌ Overnight-batch opt-out processing while morning sends go out.38- ❌ A kill-switch that needs a deploy to take effect.39- ❌ Judging the campaign on send volume instead of verified replies.