Campaign planning

Work with the right context

Set the audience rule and delivery window together so the reviewer knows who will receive the message and when. A planned campaign remains separate from accepted provider work. Keep changes visible instead of allowing a revised segment to inherit an unrelated approval.

Keep the next action clear

Scheduling creates a durable intent that the delivery process can reconcile. The delivery team checks current eligibility when each recipient is submitted, because preferences or sender readiness may have changed since approval. Pausing a campaign stops the next eligible dispatch boundary.

Coordinate the workflow

Approve campaign. Email Marketing Manager submits the audience rules, purpose, approved template and schedule. Campaign Approver independently approves that Revision and the AudienceRevision. Changed content, audience or purpose requires fresh review. The scheduled command is rejected if approval no longer matches.

Schedule delivery. Create a durable DispatchKey for the approved campaign version and audience. Preserve the selected delivery window with EndTime after StartTime and reconcile it with ScheduledAt. Scheduling reserves work without claiming that a provider accepted or delivered any message.

Dispatch eligible recipients. Immediately before each provider submission, recheck the subscriber, purpose, list status, global suppression and domain limit under the same dispatch claim. Atomically claim one recipient DispatchKey. Provider acceptance records Sent and the provider message ID; it is separate from Delivered. Unknown outcomes remain reserved for reconciliation instead of blind resend.

Email campaigns. An approved unchanged campaign creates one delivery intent. Reject self-approval or a changed audience using a stale approval.

Audience segmentation. The approved segment resolves to the eligible intended audience. Reject arbitrary query execution and foreign-workspace recipients.

Schedule with a clear delivery state

A scheduled time expresses when dispatch work becomes eligible to begin. It does not establish that a provider has accepted every message or that every recipient has received it. Review the sender domain, recipient eligibility and applicable limits as delivery approaches, then follow the individual send outcomes.

If a campaign is paused, stop unsent work while preserving messages already accepted by the provider. Resume only the eligible remainder after the reason for the pause is resolved. The team should be able to explain which version was approved, when dispatch began, what was paused and what remains unresolved without hiding partial delivery behind a single completed campaign label.