Features / Campaign runs

Turn a draft into a send your team can follow from one screen.

Keep the message, audience, variables, provider connection, and run status together. Once a campaign starts, its draft is locked for every recipient being queued.

September product briefing

Example campaign workspace

Ready to queue

Operation

  1. Audience2,416 eligible01
  2. ContentVersion 602
  3. Review2 approvals03
  4. QueueReady04

Audience snapshot

2,416

eligible recipients

Consent and suppressions resolved in Knownry

Provider handoff

Configured

SenderVerified

TemplateRendered

TrackingExplicit

Queue with full contextAudience, content, approvals, provider

In practice

Follow one send from start to finish.

  1. 01

    Review the whole send

    Confirm the template, subject, required variables, consent class, audience, and active provider before launch.

  2. 02

    Start one fixed run

    PostDesk snapshots the audience rules and marks the campaign as sending before fan-out begins.

  3. 03

    Work the exceptions

    Queued messages keep their own status and attempt history, so the rest of the run stays clear when one fails.

During a live run

One provider error stays one error.

Each prepared recipient has an independent queue state and attempt history. An operator can isolate a failed handoff, understand what was already accepted, and retry only where the run still permits it.

Run state
Sending
Queue
Per-recipient status
Exception
One failed handoff

The retained record

What stays with the run

  • The campaign and template selected at launch
  • The audience filters and consent class used for the run
  • Each recipient queue item and its current status
  • The provider connection used to hand off each message

Why keep it

A campaign still has to operate after the design is done. Keeping its preflight decision and queue together gives support and operations teams a concrete place to investigate a partial send.

What you can rely on

PostDesk prepares and queues each message for your provider, and cancelling a run stops every message still in the queue.