Broadcasts

TL;DR:

• Send a message to many users at once — filtered by tags, variables, or subscription status.
• Schedule sends in advance or send immediately.
• Track delivery results (sent, failed, blocked) per broadcast.

What it does

A Broadcast lets you send a message to a group of your bot's subscribers in one action. Instead of waiting for users to start a conversation, you proactively reach out — for announcements, promotions, reminders, or re-engagement campaigns.

You control exactly who receives the message by applying filters (e.g., only users with a specific tag, or users who haven't interacted in 30 days). The broadcast is then queued, delivered at scale, and you can track how many messages were sent or failed.

When to use it

• ✅ Announcements — notify all subscribers about a new feature, event, or change.
• ✅ Promotional campaigns — target users with a specific tag (e.g., vip, cart_abandoned).
• ✅ Re-engagement — reach users who haven't interacted in a while.
• ✅ Scheduled sends — schedule a message to go out at a specific date and time.

When NOT to use it

• ❌ Conversational flows — broadcasts are one-way. For interactive sequences, use a Scenario instead.
• ❌ Real-time triggers — if a message should fire when a user does something, use a Scenario node.
• ❌ Transactional messages — order confirmations, payment receipts, etc. should come from Scenario flows, not broadcasts.

Creating a broadcast

1. Go to CRM → Broadcasts and click New Broadcast.
2. Name your broadcast (internal only — users don't see this).
3. Write your message using the card editor (text, image, buttons — same as the Message node).
4. Set your audience using the filter builder — filter by bot, tags, variables, subscription status, or leave unfiltered to reach everyone.
5. Preview the recipient count before sending.
6. Choose when to send — immediately or at a scheduled date and time.
7. Send (or schedule). You can always cancel a scheduled broadcast before it starts.

Use Edit buttons on a text card to arrange URL buttons in rows of one to four and choose their colors. The saved order, rows, and colors are used for previews and delivery. Existing broadcasts and queued jobs without a saved layout keep their original order with one button per row.

Broadcast statuses

Status	Meaning
Draft	Saved but not yet sent or scheduled.
Scheduled	Queued for a future date/time. Can be cancelled.
Sending	Currently being delivered to recipients.
Done	Delivery completed. Check the stats for results.
Cancelled	Manually cancelled before completion.
Failed	An error prevented delivery from completing.

Delivery results

After a broadcast completes, you'll see per-recipient delivery stats:

Stat	Meaning
Sent	Message delivered to Telegram successfully.
Failed	Telegram returned an error (e.g., user deleted the bot).
Blocked	User has blocked the bot — delivery was skipped.

Tips

• Test first — use the "Send to myself" option before a real send to verify the message looks correct.
• Duplicate for reuse — instead of rebuilding a broadcast from scratch, duplicate an existing one and adjust the content or filters.
• Respect your quota — large broadcasts consume your monthly message quota. Check your plan limits before sending to a large audience.

FAQ

• Q: Can I send a broadcast to users of multiple bots?
  A: Broadcasts are sent per-bot. Create separate broadcasts for each bot, or filter by workspace-level tags if your bots share subscribers.

• Q: Can I cancel a broadcast that is already sending?
  A: Once a broadcast enters Sending status, cancellation is not guaranteed — some messages may already be queued. You can cancel a Scheduled broadcast at any time before it starts.

• Q: Why did some messages fail?
  A: Common reasons: the user blocked the bot, deleted their Telegram account, or Telegram returned a rate-limit error. Failed deliveries do not consume quota.

• Q: Does a broadcast trigger a scenario?
  A: No. Broadcasts send a standalone message directly and do not start any scenario flow.

Related pages

• Telegram Users (CRM) — Manage subscribers, tags, and variables used for filtering.
• Message Node — The node type used inside scenarios for interactive messaging.