Skip to main content
A broadcast sends one message to a chosen audience. It is composed, checked, and then run — the three steps are deliberately separate, because a send cannot be recalled.

​
Composing

Name is for you, not the recipients. It is how the broadcast appears in the list afterwards, so name it by what it is rather than when you sent it. Message has a tab per language the tenant has enabled. Each recipient gets the message in their own language, falling back to the assistant’s default when the contact’s language is unknown or has no translation. Basic HTML is supported. The text in your tenant’s base language is required. A recipient with no text in their own language gets the base one, so a broadcast without it would reach nobody; it cannot be saved without text in the base language.
Filling only one language is normal and safe — everyone falls back to it. What is not safe is filling several and leaving one half-written: a contact whose language matches the unfinished tab gets the unfinished text, not the complete one from another tab.

​
Choosing the audience

Three ways, in increasing precision:

​
Reach

As the audience is chosen, Reach shows how many contacts would actually receive the message. It is counted as of now. The audience itself is fixed when the broadcast starts, so the number it is sent to can differ slightly. This is the number to read before sending, and it is not the same as the size of the audience. A contact is counted only if the assistant can still reach them — a segment of five thousand can have a reach far below that if most of those people have blocked the bot or never opened a channel.
A reach of zero means the send would do nothing. That is worth resolving before running it rather than after: the usual causes are an audience that matches nobody, or contacts who exist in the database but have no reachable channel.

​
Sending and cancelling

A broadcast is editable while it is a draft. Once it has started, the message that goes out cannot be revised: the text is read for each recipient as it is delivered, so editing it would change what the rest of the audience receives. Send asks for confirmation, and a send cannot be recalled. Sending twice starts it once: a broadcast that is already running or finished is never started again. A broadcast moves from Draft to Running to Completed. Cancel stops a running broadcast: what was already delivered stays delivered, and the recipients still waiting are skipped. A broadcast that has finished or been cancelled cannot be sent again; compose a new one. Any broadcast that is not running can be deleted, together with its delivery records. A running one has to be cancelled first. A broadcast counts against the tenant’s outbound messages for the period, like any other message. If they run out part-way, the broadcast stops: it becomes Cancelled, the recipients not yet reached are marked Skipped with the reason limit_reached, and nothing more is sent. Starting the same broadcast again after the limit lifts would also reach the people who already received it. Large sends are split into batches and paced, so they cannot delay replies to people in live conversations. How aggressively is a tenant-wide setting; see Settings.