Broadcasts

Multi-channel messaging broadcasts — one message to a contact segment over a messaging channel (WhatsApp / Telegram / Messenger / Instagram), honouring each platform's proactive-messaging rules.

📄️List messaging broadcasts (channel manager only)

Recent broadcasts, newest first, with their per-recipient delivery counters.

📄️Create + queue a messaging broadcast (channel manager only)

Sends one message to the chosen contact segment over a single messaging channel, honouring each platform's proactive-messaging rules (WhatsApp needs an approved template outside the 24h window; Messenger / Instagram attach a message tag; Telegram is free text). Queued or scheduled. 422 on an unsupported channel, a missing template, or an empty audience.

📄️List broadcast-capable connected channels (channel manager only)

The connected WhatsApp / Telegram / Messenger / Instagram channels a broadcast can be sent on.

📄️Preview the audience size for a broadcast segment (channel manager only)

How many contacts the segment resolves to on the chosen channel (contacts who already have an identity on that channel, not blocked).

📄️Get a messaging broadcast (channel manager only)

Get a messaging broadcast (channel manager only)

📄️Get a broadcast's campaign report (channel manager only)

Funnel aggregates (targeted → queued → sent → delivered → read plus the failure split), the most frequent delivery-failure reasons in the reader's language, and the day-by-day timeline a drip spreads the send over. Aggregates read the stored counters kept fresh by status webhooks and reconciled daily.

📄️Export a broadcast's per-recipient outcomes as CSV (channel manager only)

The full per-contact status list (contact, channel id, queue status, delivery status, error, sent time) as a streamed CSV download.

📄️List a broadcast's recipients (channel manager only)

The per-recipient delivery breakdown (status + error + contact), newest first, paginated.

📄️Resume a halted broadcast (channel manager only)

Restart a campaign that was HALTED because Meta paused, disabled or rejected the template it is built on. The pending recipients were never skipped, so it picks up where it stopped. Resuming is deliberately a decision rather than something that happens by itself when the template is approved again: the template usually stopped working because of what it says, and the queued messages say exactly that. 422 in any other state.

📄️Cancel a broadcast (channel manager only)

Stop a queued, scheduled or sending broadcast — every still-pending recipient is skipped. 422 if it is already in a terminal state.