Read a broadcast's results

Delivery, reads, clicks and every skipped person, per number, once a broadcast has run.

Quick start

  1. Open Broadcasts, click a broadcast that has sent or is sending, then click View Report.
  2. Read the tiles: Audience, Sent, Delivered, Read, Failed, Skipped.
  3. Scroll to Recipients and search for one person by name or number.
  4. Read the Detail beside a failed row for its reason.
  5. Wait for Completed or Failed. Read Detail and check the retry or resume controls.

Watch out

  • Skipped is not a failure. It is usually consent, or a missing phone number.
  • Retry failed withholds message ids and known unknown outcomes. Older errors remain unclassified; retrying an unknown outcome can send twice.
The report tiles: Audience, Sent, Delivered, Read, Failed, Skipped.
Recipients: Contact, Phone, Status and Detail, including a failed and a skipped row.
Details

Getting here

Broadcasts → click a row to open its drawer → View Report. A draft's drawer offers Continue Editing instead; a scheduled broadcast's offers Cancel Broadcast.

Before you start

  • Only an owner or an admin can open Broadcasts at all.
  • A broadcast that is still sending shows live counts, and the totals settle when it finishes.
  • Retry failed and Resume need an owner or admin and a plan that allows broadcasts.

Fields

Scheduled
The time it goes out, or Next tick when it has no set time.
Limits: Shown while it is scheduled.
Audience
How many people it was published for.
Sent
Messages handed to WhatsApp.
Delivered
Receipts saying it arrived, including those since read.
Limits: Shown once anything has been sent.
Read
Receipts saying it was opened.
Failed
Failed sends, unknown outcomes, or checks that stopped sending.
Skipped
People in the list who were not sent to.
No consent
People the segment matched who had no active consent.
Limits: Shown only when it stopped somebody.
Clicked / Click rate
People who clicked a tracked link, and that as a share of Sent.
Limits: Shown only when the message carried a tracked link.

How it works

  • Audience, Sent, Failed and Skipped are the broadcast's own totals. While it is still sending they are counted live from the whole list, so they move as it goes; once it finishes they are the totals it finished with. Delivered and Read are counted across the whole list, not only the rows on screen.
  • Delivered counts everybody whose message arrived, including those who then read it, so Read is a smaller number inside it.
  • By channel appears when each contact was reached on the number they last used. It lists Channel, Template and Recipients, with a reminder above them: “Each contact was sent on the number they last messaged, with that number's template.”
  • While a broadcast is still sending, those rows carry a note: “Still sending: these counts are live.”
  • Recipients lists each person with Contact, Phone, Status and Detail, and it can be searched, sorted, filtered and grouped like any other list here.
  • A status is pending, sending, sent, delivered, read, failed or skipped.
  • Detail shows the time it went out for anything sent, and the reason for anything that failed. A failure with no reason on record says so rather than showing nothing.
  • A skipped person's row explains why: no phone on file, marketing consent not active, a marketing opt-out on record, or no longer matches the segment at send time.
  • Other skip reasons are contact is blocked, contact completed a data-deletion request, contact no longer available, contact identity changed or erased and contact phone changed. Changing the saved number can therefore skip that recipient.
  • No consent is not part of Audience and not a subset of Skipped. It counts people the segment matched before publishing, who never became recipients at all.
  • Before each person's send, their current contact, number, blocking and consent are checked again. Any broadcast may reach fewer people than its published Audience.
  • Failed rows with a message id retain the provider reference and are never re-sent by Retry failed. The id alone does not prove delivery; the button shows how many rows it leaves alone.
  • Completed and Failed broadcasts show recovery controls. Retry counts eligible failed rows without a message id or a known unknown-outcome marker. Resume counts existing pending rows; a combined control shows both counts.
  • A zero eligible-and-pending count leaves the retry control disabled. If recovery counts are unavailable, a warning replaces the control; refresh before retrying.
  • Click the recovery control, then confirm it. Queuing means the existing rows await processing and sending checks; it does not guarantee provider delivery.
  • Reschedule appears while it is scheduled, or on a row cancelled by an older version of the product.
  • Cancel broadcast appears while it is scheduled, asks Confirm cancel, and returns the broadcast to a draft with its scheduled time cleared.
  • When WhatsApp is slowing one of your numbers, a banner says since when and roughly when it resumes. The send is paused, not broken, and it carries on by itself.
  • When one of your numbers has used its WhatsApp daily limit, a banner names the number, how much of the limit is used, and the latest time sending should resume. The rest of the broadcast waits and carries on by itself; nobody is dropped. Workflow and API template sends on that number use the same limit.
  • A broadcast whose last people went out just as the number reached its limit still finishes: it does not wait for the limit when there is nobody left to send to.

When it fails

  • A retry can reset failed rows to pending before counting or restarting the broadcast fails. The page refreshes automatically after a failed response. Check its current recovery controls.
  • If Resume now shows pending rows, click it and confirm again to restart processing. A general queuing error alone does not confirm that any rows were reset.
  • A broadcast stopped by a failed channel, credential or plan check may also have pending rows. Resume runs the sending checks again; it does not repair configuration.
  • Fix the prerequisites first. Otherwise the broadcast may fail again and stays failed until another explicit recovery click; the sender does not automatically resume it each minute.
  • Nothing matches the search or the filters on the list: No recipients match the current filters.
  • A number the report cannot name: Unnamed channel. A recipient with no number on the row: No channel assigned.
  • Retry failed on a page opened before the broadcast started sending again: it says how many people are still waiting, for example “2 recipients are still waiting to be sent. Retry the failed ones after they have gone out.”
  • Cancel on anything that is not scheduled: Only scheduled broadcasts can be canceled.
  • A whole number being slowed down shows the banner rather than a pile of failures.
  • A segment with Time Since Last Outgoing Message is checked before each batch and each person's send, using the complete rules saved at publishing. Other segments keep their published audience rules.
  • An unavailable check holds the unattempted batch or person for a later tick, about a minute later. A held person's row returns to pending without a failure reason.
  • When the failure counter is available, failed checks count once per broadcast per tick, across its people and channels. On the tenth failing tick within an hour, a batch check fails still-pending rows with segment could not be re-checked at send time.
  • A person's unavailable check at that limit fails their still-owned row with recipient could not be re-checked at send time. Retry failed checks them again; another failed check in that same hour gives up immediately.
  • Before each send, the channel and the workspace are checked again, reusing an answer for up to two seconds. If that check cannot be read, the unsent rows return to pending and the tick counts toward the same limit.
  • On the tenth such tick within an hour, the still-pending rows fail with channel or workspace could not be checked at send time — not sent. Retry failed sends them again; another failed check in that same hour gives up immediately.

Limits

  • Pending means waiting for processing, not provider acceptance or delivery. Resume queues existing rows for validation and does not create a new audience.
  • The finish time belongs to the current attempt. Restarting clears it and schedules another attempt; it is not a history of earlier attempts.
  • Recipients lists the first five hundred rows. The heading says Recipients (first 500) when it is capped, and the tiles above still count everybody.
  • Read is only reported where the channel reports it. A missing read is not proof nobody read it.
  • Skipped is not a failure. It means the person was in the list and was deliberately not sent to.
  • The report does not attribute revenue. Clicked counts people who clicked a tracked link and nothing further.
  • Clicked counts people, not clicks, so one enthusiastic reader is one.
  • Retry failed withholds failed rows with a message id or the exact known unknown-outcome marker. A message id alone does not prove delivery.
  • A transport-ambiguous or thrown send now says send outcome unknown — provider acceptance could not be confirmed. An expired claim on a send that was attempted says send outcome unknown — claim expired; a claimed row that was never handed to WhatsApp goes back to pending and is sent later. Both are withheld from automatic and manual retry, even without a message id.
  • Older raw errors and variable unknown-outcome details have not been fully classified and can still be manually retried without a message id. A missing id does not prove WhatsApp refused it; retrying such an unknown outcome can send twice.
  • A sending broadcast cannot be cancelled. Only a scheduled one can.

Best practices

  • Read Skipped before Failed. A large Skipped usually means consent, not a technical problem.
  • Search the Recipients list for the customer who says they got nothing, and read their Detail.
  • Wait for Completed before judging Delivered and Read. Receipts arrive after the send.
  • Put a tracked link in the template when the point of the campaign is a click. Without one there is nothing to measure.
  • Fix channel, credential and plan problems before retrying or resuming. Recreate the broadcast if its configured target cannot be repaired.

Use cases

  • A campaign finished and you want the delivery rate: compare Delivered against Sent.
  • Sarah Chen says she got nothing: search her in Recipients and read her Detail.
  • A number is slow today: the banner tells you when it resumes, so nobody has to guess.
  • Twelve eligible rows failed: read Detail, fix the cause, then confirm Retry. Check the recovery controls if queuing fails.

FAQ and troubleshooting

Sent and Delivered are different. Is something broken?
No. Sent is what went to WhatsApp; Delivered is what arrived. Receipts come back over the following minutes.
Why is Read lower than Delivered?
Read receipts are only reported where the channel reports them, and a customer may simply not have opened it yet.
What is the difference between Skipped and Failed?
Skipped means the send was deliberately not attempted. Failed can mean a send failed, its outcome is unknown, or repeated checks stopped it before sending. Read Detail.
Can I resend to somebody who never received it?
After completion, Retry queues eligible failed rows and Resume queues existing pending rows for validation. Neither proves delivery. Rows with an id or a known unknown-outcome marker stay put. Older errors remain unclassified; retrying an unknown outcome can send twice.
Only five hundred recipients are listed. Where are the rest?
The list shows the first five hundred rows. The tiles above count everybody, and the heading says when the list is capped.
Can I still cancel?
Only while it is Scheduled. Cancelling returns it to a draft and clears its time, so choose the timing again before you republish.

Reading this with an AI assistant? Plain Markdown version.