Supporting asset
Guided pilot
Campaign Hub
Prepare permissioned outreach with an exact audience, visible compliance checks, and separate review, approval, execution, and outcome evidence.
A controlled campaign path
The operator sees what is ready, what is blocked, and what each state actually proves.Campaign Hub workflow
Draft to exact outcome—without hidden sends
Each boundary is workspace-scoped, reviewable, and invalidated when material inputs change.Step 1
Draft
Review exact content and channel intent.Step 2
Resolve audience
Bind permission and contactability evidence.Step 3
Run preflight
Check provider, suppression, quota, and cost truth.Step 4
Review and approve
Record review, then approve separately.Step 5
Verify outcome
Read acceptance, events, recovery, cost, and attribution.Exact inputs
Campaign, audience, provider, authorization, and recipient fingerprints.Compliance at execution
Consent, unsubscribe, suppression, DNC, and contactability are checked again.Honest outcomes
Acceptance is not delivery; delivery is not reply or conversion.What the current product boundary supports
Draft and exact audience review
Start from server-owned templates, enroll workspace contacts, and inspect the exact campaign audience before any execution decision.Consent and suppression checks
Review durable email authorization or SMS consent together with opt-out, DNC, suppression, contactability, provider, and quota state.Durable approval boundary
Record what was reviewed, bind approval to exact audience and provider fingerprints, and make content or audience changes invalidate stale approval.Outcome evidence without shortcuts
Keep provider acceptance, delivery, reply, bounce, unsubscribe, business outcome, cost, and recovery as separate states.Live boundary
Provider setup is evidence, not a checkbox
Credentials or a sender address alone do not make a campaign eligible. Before one live test, the final packet must name the sender, recipient, content, IDs, maximum cost, quota reservation, callback, timeout, cleanup, and forbidden effects.- A verified sender and eligible provider account
- One owner-controlled recipient with exact authorization evidence
- A provider-authoritative quote, quota reservation, and maximum cost
- A public callback with provider signature verification
- A separate exact owner approval naming the final packet