Short answer. Telegram mass DM means sending unsolicited direct messages to people who never contacted you, and no Telegram bot can do it. Telegram's developer documentation states that bots cannot start conversations. Mass DM therefore runs on ordinary user accounts driven by unofficial clients, which Telegram's terms prohibit, and the accounts that get restricted are the sending accounts rather than the buyer's.
Search for this and the results split cleanly in two. One half is Python scripts and forum threads. The other half is service pages quoting a price per thousand messages. Not one page in either half links to a Telegram document, and the daily sending limit they all cite does not appear in any Telegram document at all.
This guide is written the other way round: every platform figure below is quoted from Telegram's own pages, and where Telegram publishes nothing, that is stated instead of filled in.
What is Telegram mass DM?
Telegram mass DM is the practice of sending the same private message to a large list of Telegram users who have not opted in, usually after collecting their usernames from public groups. It is distinct from broadcasting, where messages go only to people who started a bot or joined a channel. The distinction is technical, not rhetorical: the two run on different Telegram interfaces with different rules.
Queries for mass dm telegram and telegram mass dm return the same two categories of result — open-source scripts built on user-account libraries, and vendors selling message volume by the thousand. Both categories describe the same pipeline, and neither describes the interface Telegram supports for reaching an audience at scale, which is opt-in broadcast on the Bot API.
There are two ways to drive Telegram programmatically, and almost every misunderstanding in this topic comes from conflating them.
| Interface | Bot API | User account (MTProto) |
|---|---|---|
| What drives it | A bot created in @BotFather | A phone-verified personal account |
| Can message a stranger | No — documented as impossible | Technically yes |
| Rate limits | Published in the Bots FAQ | Error 420 FLOOD_WAIT_X, no published thresholds |
| Terms position | Supported, with a consent requirement | Automation for unsolicited messaging breaches the ToS |
| What gets restricted | The bot's throughput | The account, and the phone number behind it |
Can a Telegram mass DM bot message strangers?
No. A Telegram mass DM bot, in the sense of a bot that opens conversations with people who have never interacted with it, cannot exist on the Bot API. Telegram's developer introduction states the constraint in one sentence: "Bots can't start conversations with users. A user must either add them to a group or send them a message first." No API key, price tier or configuration changes that.
"Bots can't start conversations with users. A user must either add them to a group or send them a message first."Telegram, Bot Platform introduction, core.telegram.org/bots
This single line invalidates most briefs that arrive with the phrase "mass DM bot" in them. What the tools sold under that name actually automate is a personal account, using a library that speaks Telegram's MTProto protocol directly instead of the HTTP Bot API. The product is a script wearing the word "bot", and the compliance position of the two is not comparable.
Telegram's Bot Platform developer terms make the consent requirement explicit rather than implied. The broadcast allowance is written as permission to "broadcast up to 30 messages per second to users who have granted permission to contact them", and a separate clause states that a third-party application "must not harass or spam users with unsolicited messages".
What a Telegram mass DM service is selling
A Telegram mass DM service sells three things bundled together: a target list collected from public group membership, a fleet of phone-verified user accounts, and message volume delivered through those accounts. The buyer pays for messages sent. The accounts carry the enforcement risk, and those accounts belong to the vendor, which is what makes the pricing look cheap relative to the exposure.
Understanding the shape of that pipeline matters for one reason: it is how you recognise what a proposal is actually proposing, whichever word it uses on the order form.
Inside a Telegram bulk message sender bot
A telegram bulk message sender bot, and the desktop and browser tools marketed as a telegram bulk message sender, are wrappers around the same three stages — collect identifiers from public groups, filter the list, then send from multiple user accounts with varied message text. Every stage after the first depends on the account fleet, which is why these tools ship with account-management features rather than deliverability features.
Telegram's Terms of Service address the output of that pipeline directly. The prohibited-use list includes "Use our service to send spam or scam users", and Telegram's stated consequence is that failure to comply with the Terms "may result in a temporary or a permanent ban from Telegram or some of its services". There is no volume at which that clause stops applying.
What Telegram publishes about send limits
Telegram publishes exactly four send figures for bots, all in its Bots FAQ, and the wording of each one differs in a way that matters. One is advice, one is a stated cap, one is explicitly approximate, and one is a paid ceiling with entry requirements attached. Flattening all four into "the limit is 30 per second" loses the part that determines queue design.
| Scope | Figure | How Telegram words it |
|---|---|---|
| One chat | 1 / sec | Advice — "avoid sending more than one message per second" |
| One group | 20 / min | Cap — "bots are not be able to send more than 20 messages per minute" |
| Bulk notifications | ~30 / sec | Approximate — "not able to broadcast more than about 30 messages per second" |
| Paid Broadcasts | 1,000 / sec | "up to 1000 messages per second", at 0.1 Stars per message above the free 30 |
Paid Broadcasts is gated, not merely priced. Telegram requires a bot to hold at least 100,000 Telegram Stars on its balance and to have at least 100,000 monthly active users before the feature is enabled, which puts it out of reach of every programme that is still building a subscriber base.
Telegram also publishes its own advice for staying under the free ceiling, and it is a scheduling instruction rather than a technical one: spread broadcasts "over longer intervals (e.g. 8-12 hours)". When the platform's own guidance is to slow down, a product promising an instant blast to an entire list is promising something the platform documents against.
The documented free tier delivers 30 messages per second to opted-in subscribers — 108,000 messages per hour. At the 50-messages-per-account-per-day figure the mass-DM vendors quote themselves, reaching 100,000 people needs 2,000 account-days of sending.Arithmetic from Telegram's published bulk-notification rate and vendor-stated daily figures
The comparison is worth sitting with, because it inverts the usual assumption. The compliant interface is not the slow one. It is roughly three orders of magnitude faster per day than an account fleet, and it does not consume a phone number per 50 recipients. What the compliant interface requires instead is a list of people who pressed start, which is acquisition work rather than sending work.
What Telegram does not publish
Telegram publishes nothing about daily direct-message volume from user accounts. There is no threshold table, no restriction schedule, and no criteria for appeals. This absence is the single most important fact in the topic, because the entire market has filled it in with numbers, and the numbers disagree with each other.
Four specific things are undocumented. There is no per-day DM figure in the Bots FAQ, the spam FAQ or the Terms. There is no published sequence of consequences for repeated reports. The error identifier PEER_FLOOD, which the bulk-sending tools all reference, does not appear in Telegram's own API error list — that page documents error class 420 as "The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded", with FLOOD_WAIT_X as its named example. And the criteria @SpamBot applies to an appeal are not stated anywhere.
| Daily figure claimed | In Telegram's docs? |
|---|---|
| Under 20 per day, new account | Not published |
| 30 to 50 per day | Not published |
| 40 to 50 per day, fresh account | Not published |
| 40 to 80 per day, aged account | Not published |
| 50 per account per day | Not published |
| 80 to 100 per day, warmed account | Not published |
| 5 to 7 reports in 24 hours triggers a block | Not published |
Across eight vendor and guide pages ranking for this keyword in July 2026, seven distinct "safe" daily figures were stated as fact. None named a source. None of the eight pages linked to a single Telegram document.Sendhaus review of the telegram mass dm search results, July 2026
A number that six vendors state differently is not a threshold. It is an estimate derived from each vendor's own campaigns, presented without the sample size, the account histories or the failure rate that would make it interpretable. Building a plan on it means building on someone else's undisclosed data.
What happens to a reported account
Telegram's spam FAQ describes a moderation process driven by recipient reports rather than by volume counters. Its wording: "When users press the 'Report spam' button in a chat, they forward these messages to our team of moderators for review. If the moderators decide that the messages deserved this, the account becomes limited temporarily." The trigger is human judgement on reported content, which is why volume tuning does not reliably prevent it.
What a limited account can still do is narrower than most descriptions suggest, and Telegram states it precisely: "Limited accounts can send messages to people who have their number saved as a contact. You can also always reply to anyone who messages you first." Inbound conversations continue. Outbound contact with strangers, which is the entire function of a mass DM account, stops.
On duration, Telegram commits to very little: for a first occurrence and an account that is "not an industrial scale spammer", the account "will most likely be limited for a few days or so". Telegram names @SpamBot as the appeal route and publishes no criteria for how appeals are decided, so the outcome of an appeal is not something any vendor can honestly forecast.
Telegram's spam FAQ also names the reportable behaviours, and the list maps onto a cold outreach campaign almost exactly: unsolicited advertisements, links, and invite links to groups or channels, sent to people the sender does not know.
The consent rules above Telegram's rules
Platform permission is not the only constraint on unsolicited commercial messaging. In the European Union, the ePrivacy Directive requires prior consent for direct marketing sent by automated means, and that obligation applies whatever an individual platform's terms allow. A campaign can be inside a platform's rules and still be unlawful in the recipient's jurisdiction.
Article 13(1) of Directive 2002/58/EC states that "the use of automated calling systems without human intervention (automatic calling machines), facsimile machines (fax) or electronic mail for the purposes of direct marketing may only be allowed in respect of subscribers who have given their prior consent." National regulators have applied the prior-consent principle to electronic messaging broadly, and the narrow exception in Article 13(2) covers existing customers being marketed similar products, with an opt-out offered at collection and in every message.
How strictly regulators read consent is visible in the enforcement record. France's CNIL fined the retailer Brico Privé €500,000 on 17 June 2021, of which €200,000 related to unsolicited commercial communications and cookies, and the decision turned on a narrow point: creating an account without making a purchase was not a sufficient basis to send marketing without prior consent. A scraped group-membership list is a considerably weaker basis than an unconverted account registration.
How to send a Telegram bulk message at scale
Sending a telegram bulk message to a large audience within Telegram's rules means building a subscriber base first and then broadcasting to it on the Bot API. There is no import path from a phone list, an email list or a scraped username list — the recipient has to press start on the bot or join the channel. That acquisition step is the whole difference between the two approaches, and it is the step the mass-DM market exists to skip.
-
Create the bot and the consent record
Register the bot in
@BotFatherand publish start links carrying a deep-link parameter, so every subscriber arrives with a recorded origin. Telegram allows up to 64 characters in that parameter, which is enough for a real campaign identifier. -
Acquire subscribers deliberately
Official Telegram Ads, channel cross-promotion, existing owned channels and website placement each produce subscribers who chose to arrive. Volume here is slower than a purchased list and it is the only volume that is addressable at all.
-
Queue below the published rates
Hold one message per second per chat and stay under the approximate 30 per second aggregate. Where a limit is exceeded the Bot API returns an error carrying an optional
parametersobject with aretry_aftervalue; Telegram's API reference describes that object as information that "can help to automatically handle the error". Honouring it converts a brief throttle into a brief throttle. Retrying immediately does not. -
Segment before increasing volume
Every irrelevant broadcast produces blocks, and a block on Telegram is closer to permanent than an email unsubscribe — the chat is gone and there is no re-permission flow. Sending less to a narrower segment protects the base that took months to build.
-
Report states rather than sends
Queued, sent, delivered, blocked and opted out, with the reachable base as the denominator. A "messages sent" figure cannot fail, which is exactly why it is the number bulk tools display.
The engineering behind steps three to five is ordinary bot and queue work rather than anything exotic. What makes programmes fail is usually step two being skipped.
When bulk messaging will not work
Broadcast on Telegram is the wrong tool in four situations, and each is worth checking before any budget is committed. None of the four is fixable by choosing a different vendor, because all four are properties of the audience or the platform rather than of the tooling.
The first is having a contact list rather than subscribers. A CSV of phone numbers or email addresses cannot be converted into Telegram recipients by any method — the person has to press start. The second is an audience that is not on Telegram: penetration varies enormously by country and community, and a technically flawless broadcast to a base that does not exist has no commercial outcome.
The third is needing genuine two-way conversation at volume, which is a routing and handover build rather than a broadcast one. The fourth is a regulated vertical — financial products, health claims, gambling and adult content each carry disclosure and consent obligations that sit on top of both Telegram's rules and general consent law, and in several of them a messaging channel is the wrong medium regardless of compliance.
Frequently asked questions
Is Telegram mass DM against Telegram's rules?
Yes. Telegram's Terms of Service prohibit using the service to send spam or scam users, and the Bot Platform developer terms state that a third-party application must not harass or spam users with unsolicited messages. Telegram's own wording on enforcement is that failure to comply may result in a temporary or a permanent ban from Telegram or some of its services. Cold-messaging people who never contacted you is the case those clauses describe.
How many DMs can you send on Telegram in a day?
Telegram does not publish a per-day direct-message figure anywhere in its documentation. The Bots FAQ publishes per-second and per-minute send rates for bots, and the spam FAQ describes a report-driven moderation process with no numeric threshold attached. Every daily figure in circulation — 20, 40, 50, 80, 100 — comes from a vendor page rather than from Telegram, and those pages disagree with each other.
Does using multiple accounts and proxies make mass DM safe?
No, because the mechanism that restricts an account is recipient reports, not connection fingerprints. Telegram's spam FAQ states that when users press the report spam button, moderators review the messages, and if the moderators decide the messages deserved it the account becomes limited. Spreading the same unsolicited campaign across more accounts multiplies the number of accounts exposed to that review. It also does not address the Terms of Service clause the campaign already breaches.
What happens if a Telegram account gets limited for spam?
Telegram's spam FAQ states that limited accounts can send messages to people who have their number saved as a contact, and that you can always reply to anyone who messages you first. Outbound contact with strangers is what stops. For a first occurrence Telegram says the account will most likely be limited for a few days or so, appeals go through @SpamBot, and Telegram publishes no criteria for how those appeals are decided.
Sources
- Telegram Bot Platform introduction — bots cannot start conversations.
- Telegram Bots FAQ — per-chat, per-group and bulk send rates, Paid Broadcasts pricing and entry requirements.
- Telegram Bot API reference — error responses and the
retry_afterparameter. - Telegram API error reference — error class 420 and
FLOOD_WAIT_X. - Telegram Terms of Service and Bot Platform developer terms — spam prohibitions and the consent wording on broadcasting.
- Telegram spam and limitation FAQ — how accounts become limited, what limited accounts can do, appeals.
- Directive 2002/58/EC, Article 13 — prior consent for direct marketing by automated means.
- CNIL — decision SAN-2021-008 against Brico Privé, 17 June 2021.
Have a mass DM proposal on your desk?
Send it over with the current setup. You get a written read on what is reachable inside Telegram's rules, what will be rate-limited, and which parts of the proposal describe something the API cannot do.
Related guides
- Broadcast & bulk messaging — the queue design, opt-out handling and delivery-state reporting behind the supported path.
- Growth & marketing — how a subscriber base gets built when there is no list to import.
- Bots & automation — what the Bot API can do, what it structurally cannot, and the first-year running cost.