Skip to main content

Delivery

Once a run has been started, the work moves from building the campaign to watching it land. This section covers what happens after Start: following a run in flight, reading the statuses Outreach reports, and going deeper in the delivery provider's own console.

Where Delivery Is Tracked​

Messages belong to a run, not to the campaign, so delivery is always tracked on a run. Opening a run gives you a progress panel of message counts by status and a messages table listing every recipient, which you can filter, sort, retry from, and export. See Monitoring and Messages.

Status is reported at three levels — the campaign, each run, and each message — and they answer different questions. A campaign is only ever Ready to Run or Run In Progress; the outcome of a send belongs to its run; and the detail of who received what belongs to the individual messages. All three are defined in Campaign and Message Statuses.

When Delivery Looks Wrong​

Most delivery questions resolve to a status definition and a failure reason, both of which are visible in the messages table. A few common ones point elsewhere:

  • Messages are queued rather than sending. Sending capacity is shared, so a run can be In Progress while its messages wait their turn. See Concurrency and Throughput.
  • A run never started and shows Setup Failed. For SMS under Sender Selection, the campaign's sender was unavailable when sending was due to begin. See Unavailable senders.
  • Messages sent but were never confirmed. Not every carrier reports final delivery, which is what Assumed Delivered means. See Timeout rules.
  • You need trends, not one run. Outreach reports per run. Cross-campaign analytics live with the provider — see Provider Reporting.

In This Section​