Broadcast Responses and Threaded Discussions
A broadcast does not have to be a one-way announcement. Subscribers on real-time delivery can reply to the email, and the reply becomes part of a discussion attached to that broadcast.
How a reply finds its broadcast
Every broadcast email is sent so that a reply comes back to the channel rather than to the sender's personal inbox. The platform recognizes which broadcast the reply belongs to and files it under that broadcast, even when the subject line is changed or the reply arrives days later.
This is why subscribers should use Reply on the broadcast email rather than starting a new message to the channel address. A new message is a fresh community submission, not a response to the existing announcement.
The thread
Responses form a flat thread: every reply is attached to the original broadcast, in the order received. A reply to a reply still belongs to the same thread, so the discussion stays together instead of fragmenting into sub-threads.
The broadcast list shows the number of responses for each broadcast; opening its details shows the thread.
Who can reply
- Real-time subscribers can reply into the thread.
- Digest subscribers cannot: digest emails are read-only summaries. A digest subscriber who wants to contribute should switch to real-time delivery or use the web submission form.
- Channel staff can read and take part from the admin workspace.
How responses are moderated
A response skips the full moderation queue. The platform relies on the mail provider's spam assessment because the sender is already a confirmed subscriber, and a response with a clean assessment is redistributed to the channel without a manual review.
This keeps conversations quick, but it is not the same as editorial review. Channel staff should watch the response list, and can remove abusive or off-topic replies.
A response is stored with the quoted text and signature stripped, so the thread shows what the person wrote rather than the whole email history. Attachments are not part of the discussion record.
Responses versus community submissions
| Broadcast response | Community submission | |
|---|---|---|
| How it starts | Reply to a broadcast email. | Email to the channel address, or the web submission form. |
| Where it goes | Attached to the broadcast's thread. | The moderation queue, as a new broadcast draft. |
| Review | Mail-provider spam assessment; no manual queue. | Automated assessment plus an administrator decision. |
| Audience | The broadcast's thread and, when redistributed, channel subscribers. | Depends on the moderation decision. |
If a reply is really a new announcement, ask the author to submit it as a community post instead.
What subscribers should expect
Replying to a broadcast shares the reply with the channel, not only with the person who sent the broadcast. The admin workspace and the broadcast page both make that clear; subscribers should be told when they join.
Related Content
- Browsing and Searching Archives: Reading a broadcast and its responses.
- Moderating Community Submissions: Reviewing new posts rather than replies.
- Real-Time Broadcasts and Weekly Digests: Why digest subscribers cannot reply.
- Broadcast Lifecycle and Moderation: Where responses sit in the broadcast flow.