Telegram broadcast message: who gets it and how to send it

A Telegram broadcast message is one message sent by your bot to many people at once. Most guides skip the part that decides your results: who can actually receive it. This one covers Telegram’s rule, the official limits, how to segment by tag and how to schedule without burning your list.

A quick note: this blog belongs to Flow4You, which offers this feature. The steps use our screens, but the rule and the limits apply to any tool. Our app and pricing are in Portuguese and Brazilian reais today, so we mention the original button labels in parentheses.

What a broadcast is, and what it isn’t

The word “broadcast” means two different things on Telegram, and mixing them up causes most of the confusion.

• A broadcast channel is a native Telegram feature. Telegram describes channels as a tool for broadcasting public messages to large audiences, with no limit on subscribers. People join the channel and read your posts.
• A bot broadcast is a message your bot sends privately to each person who has talked to it. Each lead gets it as a one-to-one chat, and can answer it or tap a button. That’s what this article is about.

A broadcast differs from a conversation flow in who starts it. A flow starts when a lead taps a link. A broadcast starts when you send it.

The rule nobody explains: a bot only talks to people who started it

Telegram’s documentation is plain about this: bots can’t start conversations with users. A user must first send the bot a message or add it to a group. In practice, that first message is almost always the Start button, right after tapping the bot’s link.

That changes what “your list” means. A broadcast goes to your bot’s leads. Here’s who is left out:

Who	Gets the broadcast?	Why
Lead who sent /start to your bot	Yes	They started the conversation
Channel member who never opened the bot	No	Being in a channel isn’t talking to the bot
Group member who never opened the bot	No	Same reason
A handle or number from a purchased list	No	No conversation, so the bot can’t reach out
Lead who blocked the bot	No	They closed the door

The most common surprise: someone with 50,000 channel members connects a bot and expects to reach all 50,000. They won’t. The channel talks to the channel. The bot talks to whoever talked to it.

The same goes for imports. Flow4You’s lead base accepts CSV files with each person’s telegram_id, which helps you migrate the list of a bot you already ran on another tool. But importing a name doesn’t create a conversation, and Telegram’s rule still applies.

Moving people from your channel to your bot

There’s no shortcut, and that’s fine: people who opt in respond better. Give them a reason. Post something useful in the channel with a bot deep link in the format t.me/yourbot?start=ref_…. Each Start turns into a lead you can reach later.

Telegram’s sending limits

The official bot FAQ gives the numbers:

• Bulk messages: about 30 messages per second.
• A single chat: avoid more than one message per second.
• A group: up to 20 messages per minute.

Doing the math, 10,000 messages at 30 per second take about five and a half minutes. That’s Telegram’s ceiling, not a speed promise from any tool. It explains why a large broadcast doesn’t land everywhere in the same second. If your offer has a set time, leave some margin.

Telegram also has paid broadcasts, turned on in @BotFather, which raise the limit to 1,000 messages per second. They cost 0.1 Stars per message above 30 per second and require at least 100,000 Stars in balance and 100,000 monthly active users. That’s a Telegram feature for bots at that scale, not a Flow4You option.

How to send a Telegram broadcast message, step by step

In Flow4You, with your bot already connected:

1. Open the broadcast page (“Disparo em massa”) and click “New broadcast” (“Nova Transmissão”). Pick a name you’ll recognize, like “Tuesday live class”.
2. Build the content. It uses the flow editor: messages with text, media and inline buttons, delays and tags.
3. Set the audience (“Público alvo”). Pick the tags and save.
4. Check the preview. It shows how many leads match your filter.
5. Send or schedule. “Send now” (“Enviar agora”) goes right away. The clock icon opens scheduling.
6. Follow it in the history tab (“Histórico”). A progress bar shows progress, with total, sent, errors and remaining.

Until it goes out, the broadcast stays in drafts (“Rascunhos”). Once scheduled, it moves to the scheduled tab (“Agendado”), where you can cancel it. Cancel it and it returns to drafts.

Segmented broadcasts by tag

Sending everything to everyone is the fastest way to get your bot blocked, and blocked bots reach nobody. So broadcasts are filtered by tag.

Tags come from your flows and your live chat:

• Someone who tapped “What’s the price?” gets the tag interested through an Action block.
• An operator applies bought in the chat after confirming a payment.
• A CSV import can mark the new leads it creates with a tag. Leads already in the base don’t get it.

When you set up the broadcast, open the audience panel, add a condition and check the tags. Today, the screen combines checked tags with AND: check interested and live-class, and only leads with both get it.

To reach people with one tag or another, give them a shared tag. Apply offer-list to both groups and filter by that.

The preview is your audience estimate. It updates as you check tags, and it prevents the worst surprise: finding out after sending that your filter matched 40 people, or the whole base.

Filtering works by tag and by bot. There’s no built-in “bought product X” filter, only the tag you applied. If your segments depend on purchases, make sure bought gets applied consistently first. Otherwise the filter will be wrong without warning you.

A practical test for tags: a tag only earns its place if it changes the message. If leads with and without interested would get the same text, you don’t have a segment. You have a label.

Scheduling

Scheduling lets you choose a day and time, up to 30 days ahead, always in Brasília time. The screen shows the broadcast’s name, and you confirm with the schedule button (“Agendar Transmissão”).

If your leads are in another time zone, do the conversion first. There’s no per-lead time zone delivery.

Scheduled broadcasts use the audience saved in the editor. Changed the filter? Save before scheduling.

Example broadcast flow

Here’s a broadcast for leads tagged interested, announcing a live class. Notice how it builds the next segment as it goes:

When…

You send a broadcast

Send Message

Hi {{lead.first_name}}! On Tuesday at 8 pm I'm running a live class on what you asked me about. Want a reminder?Remind meNot now

Action: add tag

Tag "live-class" for whoever tapped Remind me

Smart Delay: 1 day

Send Message

It's tomorrow at 8 pm. The link lands here one hour before.See what we'll cover

Three things to notice:

• The “Not now” button is deliberate. Someone who declines without blocking stays on your list. Without that exit, blocking is the only way out.
• The live-class tag is your next audience. Tuesday’s reminder goes only to people who asked for it.
• The copy reads like a conversation. If it sounds like an ad, it gets treated like one.

One limit: the AI Agent block isn’t available in broadcasts. It works in regular flows, where the lead starts the conversation. If you want AI after a broadcast, add a link button with the address of a flow that has the AI Agent (t.me/yourbot?start=ref_…). The Start flow block doesn’t work for this: what it opens still counts as part of the broadcast, so the agent won’t run.

Common mistakes

• Expecting to reach the whole channel. Broadcasts only go to people who talked to the bot. Plan how you collect leads before you plan the send.
• Skipping segmentation. Check the blocked count in your lead base after each send. If it climbs, your bot block rate is telling you the message didn’t fit that audience.
• Sending with no button. Without a next step, you never learn who was interested.
• Pitching people who already bought. The audience filter includes tags but doesn’t exclude them. Send to an interest tag and remove that tag from people who buy. A repeated offer can cost you more than the sale it’s chasing.
• Sending often with nothing new to say. A broadcast isn’t an alarm clock.
• Not testing first. Create a tag just for yourself, apply it and send. A broken link in a broadcast is broken for everyone.

If a lead replies and needs a person, the broadcast becomes support. See the guide to Telegram bot live chat. And for people who didn’t react, a follow-up sequence usually beats another general send.

Wrapping up

A Telegram bot broadcast works once you accept the rule: your list is whoever pressed Start. Grow that number with good reasons, segment by tag, check the preview and watch your blocks. The rest is a good message at the right time.

If you want to build this, Flow4You has broadcasts alongside flows and live chat. It’s Telegram only, with the app and pricing in Portuguese and Brazilian reais.