Skip to main content
Broadcast sends a single message to multiple customer channels simultaneously — product announcements, maintenance windows, event invitations, policy updates. It works across Slack and Microsoft Teams channels linked to your accounts. Broadcast is available to every member of your organization: admins can reach every account’s channels, while members see the accounts assigned to them.

​
When to use it

New features, updates, or changes relevant to many customers at once.
Planned downtime or maintenance windows customers should know about in advance.
Invitations to trainings, roadmap sessions, or conferences.
Terms updates, holiday closures, support-hours changes.
When not to use it: individual customer issues (message the account directly), personalized outreach at scale (that’s a guide’s job or a Motion play), or anything that reads as a sales pitch in a customer channel.

​
Prerequisites

  1. Slack and/or Teams connected — under Integrations.
  2. Accounts with linked channels — an account only appears as a recipient if it has at least one customer channel.

​
Sending a broadcast

1

Open Broadcast

Broadcast in the sidebar.
2

Compose the message

Write once; Thread delivers it to each selected channel in that provider’s format. @here and @channel mentions are supported where the provider honors them. Keep it short, lead with the point, and end with a clear call to action — or “no action needed.”
3

Pick recipients

The recipient list shows your accounts with their channels. Search by account name, filter by provider (Slack or Teams), and select whole accounts or individual channels. Select-all respects your current filters, and deselected filters never sneak channels back in.
4

Preview and send

The preview dialog shows the message and the selected recipient count before anything goes out. Confirm to send.
Broadcasts deliver immediately and cannot be recalled. Read the preview like a customer would before you confirm.

​
Broadcast history

The history panel beside the composer lists past broadcasts — what was sent, when, and to how many channels, including per-channel delivery results, so a channel that failed (archived, bot removed, permissions changed) is visible rather than silent.

​
Good hygiene

Be sparing

Customer channels are high-trust space. Too many broadcasts train customers to ignore them.

Batch related updates

Three small announcements read better as one message than as three pings.

Mind the clock

Mid-week, mid-day lands best for general announcements; avoid late nights and weekends unless it’s urgent.

Preview the recipient list

The most common broadcast mistake is a filter left over from the last send.

​
Troubleshooting

Check the history panel’s per-channel results, then confirm the channel still exists, isn’t archived, and the Thread integration still has permission to post there.
It has no linked customer channel — link a Slack or Teams channel to the account first. Members also only see their assigned accounts; an admin sees everything.
Slack and Teams render formatting differently. Keep formatting simple and check the preview before sending.

​
What’s next?

Slack integration

Connect Slack and link customer channels to accounts.

Microsoft integration

Connect Microsoft Teams channels.