> ## Documentation Index
> Fetch the complete documentation index at: https://www.plain.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Broadcast reports

> Read the delivery counts, per-channel statuses, reactions, and reply threads a send produces.

Once a broadcast starts sending, its page becomes a report that updates live while the send is running. The report has four parts: delivery counts, the recipient list, reactions, and the threads customers started by replying.

## Delivery

Four counts, taken from one snapshot so they always add up:

* **Recipients**: total channels this send targeted

* **Delivered**: messages Slack confirmed

* **Pending**: waiting to be posted, or mid-post

* **Failed**: will not arrive

A send that reaches some channels and not others finishes as **Partially sent**, which is deliberately distinct from **Sent**.

## Recipients

Every channel the send targeted, with a status icon each. The list keeps the name each channel had when the send resolved, so renaming a channel afterwards doesn't rewrite the record of where a message went.

Hover a failed channel to see why. Plain reports these reasons:

| Reason shown                                                              | What to do                                                     |
| ------------------------------------------------------------------------- | -------------------------------------------------------------- |
| Plain is not connected to this channel                                    | Reconnect the channel, or remove it from the audience.         |
| Plain's Slack app is missing a permission it needs to post                | Reconnect the Slack integration.                               |
| Slack rejected this message's formatting                                  | Simplify the message content and send again.                   |
| Slack rate limited this channel's workspace for longer than we could wait | Retry in a new broadcast; Slack was throttling that workspace. |
| The Broadcast has no sender set / no notification title                   | Fix the broadcast and send again.                              |

Failures shown here are final. Anything worth retrying was already retried automatically before it landed in this list.

## Reactions

Emoji reactions on the messages this broadcast posted, totaled across every channel. The count keeps updating after the send finishes. It's a readout only, so you can't react from here.

## Threads

Every Plain thread created when someone replied to one of this broadcast's messages, newest first. These behave like any other thread: assign them, label them, reply to them. A broadcast creates a thread only when someone replies, not one per customer.

## Resources

* [Broadcasts](/docs/product/broadcasts): the four states a broadcast can be in
* [Send and schedule a broadcast](/docs/product/broadcasts/send-and-schedule): what happens before a report exists
* [Slack](/docs/product/channels/slack): the integration and customer channels a send depends on