RCS CampaignsSupport
Browse all support topics

Understand campaign execution and the delivery funnel

What queued, submitted, sent, delivered, read and failed mean, and how replies, link taps and survey responses are counted.

Every campaign page shows its recipients moving through a funnel. Each recipient is in exactly one state, so the tiles add up to the whole campaign, and each tile's percentage is its share of everyone on it. Knowing the labels tells you whether a campaign is healthy or needs a look.

The states, in order

  • Queued — staged and waiting to be sent. Recipients stay here after a trial batch, after Add audiences, or after a send stopped, until someone sends them. Large campaigns also work through the queue over time; this is normal pacing, not a fault.
  • Submitted — handed to the provider, waiting for its first receipt.
  • Sent — accepted by the provider, no receipt yet. The small print counts everyone the campaign reached (sent, delivered or read).
  • Delivered — confirmed on the phone, not yet opened. Most sends reach Delivered within seconds to a few minutes. A message stuck at Sent for a long time usually means a phone that is off, out of coverage, or a number that no longer has the app. The small print counts everyone ever delivered.
  • Read — the recipient opened it. Some phones hold back read receipts, so Read is a floor: the confirmed seen line under it adds people who replied or tapped without a receipt.
  • Failed — not delivered, with a reason on the recipient's row. The in-app Best Practices page explains every code in plain words. When Meta chose not to deliver some messages, the tile splits Meta declined from genuine failures.

Beside the funnel

  • Tapped a link — appears once someone opens a link from the campaign.
  • Fell back to SMS — RCS campaigns only. WhatsApp has no SMS fallback, so a WhatsApp campaign never shows it.
  • Responded — survey campaigns only: people who completed the survey. See Survey campaigns.
  • Shared with a friend — once someone taps a share button. See Share with a friend.

Stops and retries

Space sends out, on the send step, puts a random pause between messages so a large send reads as a human cadence. A campaign also stops itself after repeated failures (for example, 3 failed deliveries in a row): the rest stay Queued, and the page asks you to Leave them queued or Continue sending…. After a send, Retry N failed sends the failures again. If Meta declined some, it splits into Retry N delivery failures and Retry all N. Re-sending a decline only helps if you have changed the template.

Replies, and which campaign they belong to

Replies land in the Inbox as conversations. Each reply is filed under one campaign: the one whose message it quotes or taps, or else the latest campaign sent to that number before it. Someone in two campaigns who answers the second counts as replied on the second only.

Above the recipient table, Responded filters to anyone who sent something back (an away-message included; on a survey campaign, anyone who completed the survey), Real replies to people who tapped or wrote, and AI paused to threads where the assistant is muted. On each row, the Inbox icon opens that person's conversation showing only this campaign's part, with Show all messages for the whole thread. See the Inbox.

The report

When the campaign settles, an Admin can press Generate report: totals both ways, the funnel with taps, day-by-day activity in your time zone, the most-engaged people by name, replies grouped by what people actually asked about, an AI summary, and a spreadsheet of every message. See the campaign report.

Last reviewed November 9, 2026

Was this page helpful?