Sending broadcasts

Broadcast messages allow you to send a message to a targeted audience via Slack, Microsoft Teams, or Email. Use them for alerts, announcements, onboarding nudges, or any internal campaign that needs to reach people fast and at scale.

Think of of them as internal announcements or mini‑campaigns. You compose a message, define an audience, choose one or more channels, and send. Siit personalizes each message with people data and tracks engagement—deliveries, views, reactions, replies, link clicks, and confirmations—so you know what landed.

Broadcasts are great for

• Company announcements and policy updates

• Upcoming events, deadlines, or benefits enrollment

• Time‑sensitive alerts like outages or maintenance

• New‑hire welcomes and day‑1 instructions

• Department‑specific reminders (e.g., expense cutoff, security training)

Key capabilities

• Multi‑channel delivery: Slack DMs, Microsoft Teams messages, and Email

• Personalization: insert people fields (first name, department, start date, manager, etc.) directly in the message

• Targeted audiences: build rules using People attributes and groups (department, location, legal entity, employment type)

• Dynamic or fixed audiences: send to a snapshot right now or keep the rules dynamic for future runs

• Scheduling: send now or at a specific date/time with timezone control

• Optional confirmation: require recipients to acknowledge receipt (and track who confirmed)

• Metrics: sent, delivered, clicked, replied, reacted, confirmed; exportable for reporting

• Send as yourself: connect your personal Slack (and Teams, if enabled) so messages arrive from you for higher engagement

After you send

• Track progress in the Communications tab: see state (Live, Scheduled, Finished), sender, content type, sent count, clicks and engagement.

• Drill into a send to view recipient‑level status and confirmations.

• Resend to non‑viewers or copy the message to create a follow‑up.

Permissions and security

• Role‑based access controls who can create, schedule, and send communications.

• Audience building and personalization respect people field visibility. If a field is hidden from your role, you can’t use it.

• “Send as yourself” requires the user to authorize their Slack/Teams account; they can disconnect anytime.

Best practices

• Keep it short, lead with the action, and link to a request or knowledge article for details.

• Use audiences instead of @channel. It reduces noise and improves relevance.

• Personalize lightly—first name and department are often enough.

• For critical alerts, require confirmation and schedule an automatic follow‑up to non‑responders.

• Time messages with the recipient’s timezone when possible.

Common examples

• Outage alert (IT): audience = All employees; channels = Slack + Email; require confirmation for critical apps.

• Security training reminder: audience = Employees in “Engineering” not yet certified; schedule weekly until completion.

• New‑hire welcome: audience = Dynamic rule “Start date is today”; channel = Slack DM “from manager” via Send as yourself.

• Benefits open enrollment: audience = Legal entity = US; channels = Email + Slack; include deadline and link.