Skip to main content
Broadcast Notifications let you send one message to dozens or hundreds of Telegram groups in a single action. Target groups by tags, schedule the send time, track which groups have acknowledged, remind the ones that haven’t, and collect information (emails, phone numbers, form responses) back from every group — all from one dashboard. Typical uses: release announcements, maintenance notices, policy updates, deadline reminders, and collecting details from a fleet of customer or project groups.
Broadcast Notifications is a beta feature and requires an active subscription. Find it in the web app under More → TG Notification, or go directly to Dashboard → Broadcast Notification.

Before You Start

Broadcasts are delivered by your intern’s Telegram bot, so two things must be in place first:
  1. Connect Telegram — your bot must be set up under Settings → Integrations → Platforms → Telegram.
  2. Add and tag your groups — every group you want to reach must be added under Telegram → Groups (the Telegram Groups button on the Broadcast page takes you straight there), and the bot must be a member of each group.

Tag your groups

Targeting is entirely tag-based, so tagging is the foundation of the whole feature. Each group carries tags organized into tag groups — for example a Type tag group (Customer Support, Notification) and a Batch tag group (15). Tag groups marked with * are required; groups missing required tags are flagged with a Missing Required Tags warning in the group list.
Design your tag groups around how you’ll want to slice your audience: one tag group for the kind of group (support, announcements, internal), another for cohort/batch/region. You can then target any combination.

How Targeting Works

When creating a notification you pick Target Tags. The matching rule is:
  • OR within the same tag group — selecting Batch 2 and Batch 3 targets groups in either batch.
  • AND across tag groups — selecting Batch 2 and Customer Support targets groups that are in Batch 2 and tagged Customer Support.
  • Exclusion tags — groups carrying any exclusion tag are removed from the audience.
If no tags are selected, the notification is not sent to any group — there is no implicit “send to everyone.” You can also set separate Reminder Target Tags to narrow where reminders go. If you leave them empty, reminders go to the same groups as the initial notification.

Create a Notification

Click Create Notification on the Broadcast page and fill in: To attach images, create the notification first, then open it with Edit — the edit drawer lets you upload images (with captions) that are delivered alongside the message.

Approve and Send

A newly created notification is a draft — nothing is sent until you approve it. This gives you a review step between writing and delivery.
  1. Review the draft card (content, send time, targeted tags).
  2. Click Approve. A notification without any target tags cannot be approved.
  3. At the scheduled send time, the message is delivered to every targeted group. If the send time is already in the past, delivery starts right away.
Each notification card shows its status:

Track Delivery and Acknowledgments

Open any notification with View and switch to the Tags & Delivery Status tab. You’ll see a per-group breakdown with a summary line like “1 acknowledged • 7 sent • 7 total”. For each group you can see:
  • Sent / Pending ACK / Acknowledged status with timestamps
  • Who acknowledged — the Telegram user who tapped the button, with a link to their profile
  • How many times the message has been sent (initial send + reminders)
Per-group actions let you send a reminder now, retract the message from that group, or open the group in Telegram Web. You can also refresh all delivery statuses and export the delivery status as CSV for reporting, in either grid or table view.

What recipients see

The message arrives in the group from your intern’s bot, with the acknowledgment button attached (if enabled). Any member taps the button to acknowledge on behalf of the group — the button disappears and the dashboard records who acknowledged and when.

Reminders

Reminders are sent automatically on your configured frequency, only to groups that haven’t acknowledged yet, and stop after the configured number of reminders. When every targeted group has acknowledged, the notification is automatically marked Completed.

Collect Information

Beyond acknowledgments, a notification can carry a collection request — a prompt for each group to submit a piece of information (a phone number, an email, a form link response).
  1. Open the notification and go to the Collect Request tab.
  2. Click Create Collection Request and enter the request text, e.g. “Please enter Phone Number”.
  3. The request is sent together with the notification (and its reminders) — use the Send/Remind actions in the Tags & Delivery Status tab to deliver it.
Group members reply in the group, and your intern records each group’s response. The Collect Request tab shows a live table of every targeted group and its collected response, exportable as CSV.

Templates

For recurring announcements, use the Templates tab:
  • Save as Template — turn any existing notification into a reusable template (from the notification detail view).
  • Create Template — build one from scratch.
  • Generate from template — pick a template and give the AI a short prompt (e.g. “v2.3 release, adds SSO support, maintenance window Friday 9pm UTC”); it writes the notification content in the template’s structure and creates a ready-to-review draft.
Templates keep their tags, reminder settings, and acknowledgment options, so a generated notification only needs a content review, send time, and approval.

Other Actions

From the notification detail view:
  • Retract — delete the delivered messages from Telegram, either from all groups or selectively by tags. This cannot be undone.
  • Manual Complete — stop reminders and mark the notification done even if some groups haven’t acknowledged.
  • Copy share link — every notification has a public, read-only status page you can share with stakeholders who don’t have dashboard access. Regenerate share link invalidates the old link.
  • Learn — add the notification’s content to your intern’s knowledge base, so it can answer follow-up questions about the announcement in any conversation.
  • Delete — remove the notification record entirely.

Agent Cases

If group members reply to a broadcast with questions or issues, your intern can open Agent Cases to track the follow-up. The Agent Cases tab on each notification shows cases generated from that broadcast, and the Agent Cases button on the Broadcast page opens the full case dashboard.

GitHub releases

The Releases on GitHub button links to the GitHub integration. With the GitHub App installed, your intern can turn release notes into broadcast drafts — handy for announcing new versions to all customer groups.

Manage Broadcasts by Chatting

You don’t have to use the dashboard — your intern has broadcast tools built in. In any chat with your intern (web or Telegram), try:
Notifications created by chat are also drafts — they still require your approval in the dashboard before anything is sent.
A good rhythm: draft by chat while the details are fresh, then approve from the dashboard after a quick review of content and targeting.