Skip to main content

How do I check if my broadcast text actually sent, or stop one that's still going out?

Open Recent broadcasts to see a per-recipient delivery report, and cancel a broadcast that is still queued or in progress before it reaches everyone.

Every broadcast you have ever sent stays listed under Recent broadcasts, with a running count of what happened and a full per-recipient breakdown if you need it.

Check what happened

  1. On the broadcast page, look under Recent broadcasts. Each row shows how many were sent, failed and skipped out of the total.
  2. Click a row to open its delivery report: one line per recipient, their phone number, and what happened. A text (SMS) row shows "Delivered to carrier" once it hands off; a WhatsApp row shows "Sent to WhatsApp" once Meta accepts it. Either way that means it went out, not that the recipient's phone has confirmed receiving it yet. Otherwise the row shows the reason it did not go out.
  3. Reasons you might see on a text (SMS) row: no phone number, no consent on file, unsubscribed, quiet hours (texts are held back between 9pm and 8am in the recipient's own local time and are not sent later automatically), SMS sending paused for your account, the destination country or US texting registration not being approved yet, we could not check their consent that time, or the texting service did not answer in time (that text is not sent again, so nobody gets it twice). Reasons you might see on a WhatsApp row: no consent on file, unsubscribed, we could not check their consent that time (it is not tried again automatically), the recipient's phone number is already on a conversation with a different contact (merge the two contacts, then send again), or the approved template is not yet available on the WhatsApp number this contact already texts with.
  4. A broadcast can also get refused partway through if your plan no longer includes broadcasts, whether that is because your plan changed or because Peakify support set your account not to allow them. Anyone who already got the message before that point keeps it, and those sends stay counted, only the recipients still waiting in line are not sent. The broadcast's line in Recent broadcasts shows "Not sent. Broadcasts are not included on your current plan."
  5. A text broadcast also stops partway through for a reason that would stop every remaining text the same way: your account running out of credit, reaching your spending limit, or your business name not being set yet (every text has to say who it is from). Anyone already sent keeps their text. The broadcast's line in Recent broadcasts says what stopped it, so you can fix that first.
  6. There is no way to send a stopped broadcast to only the people who did not get it. A new broadcast to the same audience texts everyone in it again, including the people who already got this one, so pick a narrower tag group if you want to avoid that.
  7. If a report shows no rows yet, the broadcast is still being processed. Check back shortly. A broadcast that failed shows why in its report instead, because it will not be processed again. A row that says we could not confirm the text was sent means that one text may have gone out: check that customer's conversation before texting them again. It is never sent a second time automatically.

Cancel a broadcast

  1. A broadcast that is still queued or actively sending shows a Cancel button next to it in the Recent broadcasts list.
  2. Click Cancel, then confirm. This stops the broadcast before its remaining recipients are sent.
  3. Anyone who had already received the message keeps it, canceling never un-sends what already went out. Only the people still waiting in line are skipped.

A broadcast that already finished, or was already canceled, has no Cancel button, there is nothing left to stop.

Was this useful?

More in Campaigns and leads

The other guides people read alongside this one.

Did this not cover it?

Start a chat and the assistant will try first. If it cannot help, it hands you to a person.

Or email support@peakifycx.com. We answer within 1 business day, Mon–Fri.