How to message Telegram bot users with offers without getting blocked
Telegram bots can broadcast about 30 messages a second for free, but blocks are the real limit. Telegram's rules, how often to send, and how to measure blocks.
How do you message your Telegram bot users with offers without getting blocked?
By Andrej Ruckij · November 14, 2026 · Telegram’s bot limits and developer terms checked the same day
TL;DR: A bot can only message people who pressed Start, and Telegram’s free limit is about 30 messages a second, so a list of 100,000 takes about an hour. The limit you’ll hit first isn’t technical, it’s the block button: once a user blocks you, you can’t reach them unless they unblock. Telegram’s developer terms ban “unsolicited messages”, so send only what people asked for or would expect. In practice: say in the welcome how often you’ll write, send in the user’s waking hours, one planned message a week at most, the value in the first line, a
/settingsor opt-out command, and a list cleaned of everyone who blocked you. Measure blocks against a group that got no offer, or you’ll blame every block on the message.
We build and run these follow-ups for clients after their Telegram ads: Telegram ads at Primores.
Who you’re allowed to message
Only people who started your bot. “Bots can’t start conversations with users. A user must either add them to a group or send them a message first” (Telegram). So every user who came from an ad and pressed Start is someone you can write to again. That’s the point of sending ad traffic to a bot.
But “can” isn’t “should”. Telegram’s developer terms say your bot “must not harass or spam users with unsolicited messages”, and describe free broadcasts as going “to users who have granted permission to contact them” (Telegram). Breaking the terms can end with Telegram terminating “your TPA, your account, or both”. Someone who pressed Start for a free price list didn’t necessarily agree to a daily stream of promotions.
The technical limits
From Telegram’s bots FAQ (Telegram):
| Limit | What Telegram says |
|---|---|
| One chat | ”avoid sending more than one message per second” |
| Groups | no more than 20 messages per minute |
| Broadcast, free | ”not able to broadcast more than about 30 messages per second” |
| Broadcast, paid | ”up to 1000 messages per second”, at 0.1 Stars for each message over the free 30 a second |
| Who can use paid | bots with “at least 100,000 Stars on its balance and at least 100,000 monthly active users” |
Most advertiser bots won’t qualify for paid broadcasts, so plan around 30 a second. Telegram’s own advice: “consider spreading them over longer intervals (e.g. 8-12 hours) to avoid hitting the limit.” At 30 a second, 10,000 users take under six minutes and 100,000 take about an hour.
If you go over, Telegram answers with error 429 and a retry_after value, “the number of seconds left to wait before the request can be repeated” (Bot API). The grammY bot framework’s docs put it simply: “hitting rate limits does not lead to bans. Ignoring them does” (grammY).
What gets you blocked
Telegram tells users exactly how to get rid of you: “If you don’t want a bot to send you messages, feel free to block it – same as you would block a human user” (Telegram FAQ). Some apps also have a “Stop Bot” button. Telegram’s spam FAQ, written about user accounts, says what people mind: “unsolicited advertisements, links, invite links to groups or channels, random photos and, above all, anything related to commerce” (Telegram).
I couldn’t find a published threshold for how many blocks or reports get a bot restricted, in Telegram’s docs or anywhere reliable.
The advice below is from vendors who sell bot and broadcast tools, so it’s opinion, not measurement:
- Send less. “The most effective rate-limit strategy is having less to send” (JustRunMy.App). Their line on blocks: “Bots get blocked for being noisy far more often than for being useless.”
- One planned message a week, at most. “A safe default is one planned broadcast per week, plus event driven messages people asked for” (TeleMinute). JustRunMy.App goes further: “One monthly note lands better than four weekly ones”.
- Local waking hours. “A 03:00 notification is the fastest way to get blocked” (TeleMinute). Telegram gives the bot the user’s language, not their time zone, so my suggestion is to use the country of the ad they came from.
- Value in the first line. The notification preview shows very little. That line decides whether the message gets opened or the bot gets blocked.
- Segment before you widen. A message to the 2,000 people it fits beats one to 20,000 who don’t care, “including how many of them block you afterwards” (JustRunMy.App).
- Give an exit that isn’t the block button. Telegram lists
/settingsas a standard command (Telegram). Put a notifications off switch there. A user who muted you can still buy later. One who blocked you can’t, unless they unblock.
Offers that people don’t mind
No one has published measured Telegram data on follow-up sequences, so treat these as starting points. TeleMinute suggests:
| Message | When | To whom |
|---|---|---|
| Follow-up on interest | once per person per campaign, 24 to 72 hours later | people active in the last 7 days |
| Limited-time offer | about once a month, plus one closing reminder | people active in the last 90 days |
| Come back | about once a quarter | people inactive for 60 days or more |
Two things I’d add. Set the expectation in the welcome (“one update a week, switch it off in /settings”), then keep to it. And stop the sequence for anyone who replied, bought, or no longer fits.
How to measure blocks properly
When a user blocks or unblocks your bot, Telegram sends the bot an update (Bot API). Sending to a user who blocked you fails with a 403 “bot was blocked by the user” error (grammY). So you can count blocks per message.
The trap is blaming every block on the message. People leave bots anyway, offer or not. So hold back a random slice of users from each offer and compare: the blocks above that group’s rate are the ones the offer caused. If an offer pushes blocks well above the holdout, stop it before it reaches everyone.
How to do it
What I’d set up before the first broadcast:
- Welcome promise. One line in the welcome on how often you’ll write and how to turn it off.
- Opt-out. A
/settingscommand with notifications on and off, and respect it. - A send table. Every send is a row: user, message, status. A broadcast that crashes halfway resumes from the pending rows.
- Rate and retries. Send at about 30 a second or less. On a 429, wait exactly
retry_afterseconds and retry the same user. Answer live user messages before broadcast sends. - Clean as you go. A 403 “blocked” error means stop sending to that user; mark them at send time. Listen for the block and unblock update, so someone who unblocks comes back on the list.
- Segment. By the ad they came from, what they did in the bot, and when they were last active. Write the message for the segment.
- Holdout. Keep a slice of each segment without the offer; we’d use about 10%, which is our choice, not a rule. Compare blocks and sales against it.
- Time zone. Schedule by the country of the ad they came from, in waking hours.
- One planned message a week, at most, and read the block rate after each before sending the next.
Where these users come from: Telegram bot marketing for the funnel, how to find channels to advertise in for the traffic, and the guide to advertising on Telegram for the whole picture.
Sources
- Telegram: Bots: bots can’t message first
- Telegram: Bots FAQ: rate limits, paid broadcasts
- Telegram Bot API: retry_after, block updates
- Telegram: Bot features: standard commands
- Telegram: Bot Platform Developer Terms: unsolicited messages, permission, termination
- Telegram FAQ and Telegram spam FAQ: blocking, what users count as spam
- grammY: flood limits and grammY FAQ (bot framework): retries, blocked-user error
- JustRunMy.App (hosting vendor): send less, opt-out
- TeleMinute (bot-builder vendor): frequency, timing, cadence