How to avoid Telegram restrictions
AISAR offers two ways to connect Telegram: a personal account that plays by the same rules as Telegram Desktop, and a separate Bot API with its own limits on who a bot may message first. Each carries a different kind of restriction risk — here's both.
What you need to know
- Telegram (personal account) connects as one more linked device — like Telegram Desktop or Telegram Web. Restrictions come from Telegram itself, and AISAR has no say in that decision.
- Telegram Bot runs on the official Bot API — it doesn't carry the same volume-based ban risk, but it has its own rule, built into Telegram itself: only the user can message first.
A personal Telegram account
Just like with regular WhatsApp, broadcasts from a personal Telegram account in AISAR run under a rate limit by default, not all at once:
| Mechanism | Default |
|---|---|
| Messages per minute | 20 |
| Random delay between messages (jitter) | 5-15 seconds |
| Daily limit | None by default — can be turned on manually in the broadcast settings. |
As with WhatsApp, these values are a recommendation: the broadcast wizard warns if the rate is raised or the delay lowered past the recommended values ("the channel can get blocked"). Replying "stop", "/stop", "unsubscribe" or its Russian equivalent to an AISAR message opts the contact out of broadcasts across every one of their channels, Telegram included.
- Avoid a mass first-contact broadcast to strangers — as with WhatsApp, recipient spam reports are the main reason Telegram can restrict an account.
- Don't add a sudden large batch of new contacts or launch a big broadcast right after connecting a fresh account — give it some ordinary use first.
Telegram Bot
The Bot API is Telegram's official interface, so AISAR doesn't layer its own rate limit on top the way it does for a personal account. But bots carry a rule built into the platform itself: a bot can only message a user first after that user has messaged the bot first (or followed a special deep link). This is Telegram's own limit, not AISAR's, and no broadcast setting works around it.
- A bot broadcast actually reaches only people who have messaged the bot at least once — build the broadcast audience segment with that in mind.
- Giving the user a reason to message the bot first (a button, a t.me/bot_name link, a QR code) is the usual way to start a conversation the bot can then reply into and broadcast to.
Common issues
| Symptom | Cause and what to do |
|---|---|
| The broadcast wizard warns the channel can get blocked | Bring messages per minute and delay back to (or below) the defaults (20/min, 5-15s for a personal account). |
| The bot does not reply to some users | Expected if that user hasn't messaged the bot first yet — Telegram's own platform rule, not an AISAR error. |
| A bot broadcast reaches far fewer people than expected | A bot can only message people who already started a conversation with it — check that the chosen segment is actually people who have messaged the bot. |
| A personal Telegram account disconnected after a broadcast | In Telegram, open Settings → Devices and check the AISAR session is still there. If the account is restricted by Telegram itself, only Telegram can lift that — reconnecting will work again once it does. |
See also
For the connection walkthrough for each method, see Connecting Telegram and Connecting Telegram Bot. For the same logic on a different channel, see How to avoid a WhatsApp ban.