Broadcasts

Broadcasts deliver the same message to many chats with rate limiting designed to stay below Telegram’s safety thresholds.

How sending works

Broadcasts use the API (proxied) send mode: a server job queues your messages and sends them in the background, so you can close your browser and come back later. Job history shows progress and per-recipient status.

This mode requires analytics, which is enabled automatically on the Pro plan — so broadcasts work out of the box on Pro and the trial. (Basic doesn’t include broadcasts.)

Exact rate-limit tiers

Entergram enforces a per-message delay that scales with the recipient count:

Recipients	Delay between messages
1–3	~6 seconds
4–10	~16 seconds
11–30	~31 seconds
31–50	~46 seconds
51–75	~61 seconds
76–100	~91 seconds

So a 50-recipient broadcast takes roughly 50 × 46 s ≈ 38 minutes.

Max per job and splitting

• One job handles up to 100 recipients
• For more than 100 recipients, the broadcast is split into multiple jobs run with up to 10 parallel workers
• Each job has its own progress row in the job history panel

Composing the broadcast

1. Open the broadcast dialog from the chat selection toolbar (or the Broadcasts button)
2. Confirm the recipient list (filterable by tag, folder, type, or account)
3. Choose a template or write a new message
4. Use variables for personalization: {{name}}, {{first_name}}, {{username}}. Note that {{username}} only resolves for private chats — group and channel recipients have no username, so the variable comes out empty for them. Stick to {{name}} and {{first_name}} if your audience mixes private and group chats.
5. Attach files (10-attachment / 50 MB rules apply)
6. Review the live ETA and the message preview
7. Send

Post-send actions

Optionally apply changes to every recipient after the send:

• Update a custom column — set, add, or remove a value
• Move recipients into a Telegram folder

For example: broadcast a launch announcement, then automatically flip every recipient’s Stage column from Lead to Notified in one go.

Progress and history

The Job History panel shows status (pending / in progress / completed / failed), per-recipient delivery results, and an expandable recipient list. You can re-open completed jobs to review who was sent to and who failed, and delete old jobs from history.

Example: launch blast

• Target: 280 leads tagged trial-user in the workspace
• Composition: load the “Launch v4” template (content + product screenshot)
• Submit — the broadcast queues server-side, you can close the tab
• Result: 3 jobs of 100/100/80 recipients run in parallel; total elapsed ~90 minutes at the 76–100 tier; per-recipient delivery visible in the history panel