Back to features

Telegram CRM

Telegram Broadcast — Server-Side Proxied Sending with Rate Limiting

Send the same message to many Telegram chats from Entergram CRM. API/proxied jobs run server-side so you can close your browser; conservative rate limits stay under Telegram's safety thresholds; templates with variables, attachments, and post-send actions.

Built to stay under Telegram's safety thresholds

Broadcasts are queued server-side and delivered with a per-message delay that scales with the recipient count. One job handles up to 100 recipients; larger lists are split into multiple jobs that run with up to 10 parallel workers. You can pause, cancel, and inspect per-recipient delivery in the Job History panel.

Read the broadcast docs
  • —

    Exact rate-limit tiers

    1–3 recipients = ~6s delay between messages, 4–10 = ~16s, 11–30 = ~31s, 31–50 = ~46s, 51–75 = ~61s, 76–100 = ~91s. So a 50-recipient broadcast takes roughly 38 minutes.

  • —

    Variables for personalization

    Drop {{name}}, {{first_name}}, or {{username}} into your message — Entergram substitutes per recipient. Note: {{username}} only resolves in private chats; groups and channels have no Telegram username.

  • —

    Templates with attachments

    Save reusable messages with full formatting and up to 3 attachments (3 MB each). Insert from the picker — or invoke instantly with a slash command like /intro-message if you've labeled the template.

Frequently asked questions

Frequently asked questions

Why is my broadcast slower than expected?
The delay between messages scales with how many recipients are in the job — 76–100 recipients triggers a ~91-second per-message delay. That's intentional and stays comfortably under Telegram's flood-control thresholds. Splitting one large list into smaller jobs sometimes shortens wall time depending on how Entergram assigns workers.
Why did {{username}} come out empty for some recipients?
{{username}} only resolves in private chats. Group and channel recipients don't have a Telegram username, so the variable comes out empty for them. If your audience mixes private and group chats, use {{name}} or {{first_name}} instead.
Can I close my browser while a broadcast runs?
Yes — broadcasts run as a server-side proxied job. Close the tab, come back later, check status in the Job History panel.
Are broadcasts available on every plan?
Broadcasts require analytics to be connected, and analytics is enabled automatically on the Pro plan (and the 3-day Pro trial). Basic doesn't include broadcasts.
What can I do automatically after a broadcast finishes?
From the broadcast dialog you can configure post-send actions: update a custom column on every recipient (e.g. flip Stage from Lead to Notified) and/or move recipients into a Telegram folder. The actions apply once the job completes.
Start free trial