A list from four sources
Your own list, a folder with one link, the accounts' own chats, or the outcome of an earlier run.
Chat broadcast
One message to sixty groups by hand takes a day: join, wait for the right to write, send, check whether it was deleted. In TeleTraff's «Chat broadcast» it is a single run: you set the chat list, the accounts and the text, and the panel joins, keeps the pauses, posts and records the outcome for every chat.
Your own list, a folder with one link, the accounts' own chats, or the outcome of an earlier run.
The panel shows how many messages one account will send and how many hours the run will take.
«Results» shows where the message was posted, where it was refused and whether it stayed in the chat.
A walkthrough from the TeleTraff YouTube channel: where the chats come from, how the panel splits them between accounts, joining, text variants, pace and the check that the message was not deleted. The video is in Russian.
Everything needed for a launch sits on one screen: accounts, target chats, the message, rounds and protection.

Telegram itself lets you forward a message to several chats at once: you tick the recipients in the forward window. After that everything is manual, and only in chats where you are already a member and allowed to write.
Forwarding works for chats the account is already in. Joining, waiting for permission and checking the result is up to you.
Chat folder: a t.me/addlist link adds a set of groups to another account in one step, but writing in them is still manual.
A bot posts only in chats it was added to and does not join groups itself. According to Telegram, the Bot API allows about 30 messages per second across different chats and no more than 20 per minute to one group.
Forwarding is enough for two or three groups. When there are dozens of groups and several accounts have to write, the parts that manual work cannot carry begin: joining, the restrictions of each chat, pauses and keeping track of results. The Chat broadcast module takes that part.
«Target chats» has four sources. A folder costs one request for its whole contents and is read at the moment of the run. Only groups go to work, channels in the folder are skipped.
| Source | What goes in | Joining |
|---|---|---|
| «List» | A list, a parsing base, a folder or a t.me/addlist link | The panel joins only where writing is otherwise impossible |
| «Account chats» | Groups the selected accounts are already in. Channels and private chats do not count | Not needed |
| «From history: delivered» | Chats where earlier runs delivered a message | Links are taken, membership is not carried over |
| «From history: failed» | Chats where an earlier run did not finish. Only temporary causes are retried: a wait from Telegram, an exhausted join limit, an interrupted run | Links are taken, membership is not carried over |
Collect the chat list: your own list, a parsing base, a folder or a t.me/addlist link. If there is no ready list, it is collected with the chats and groups parser.
Pick the accounts: each chat is written to by one account, and the list is divided between the selected accounts.
Write the message: a chain of steps goes into every chat, the text can take the chat's name and @, and variants are written in curly braces.
In the «Rounds and workload» block set «Passes», chats per account per round and the rest between rounds, choose a protection mode and look at the workload calculation before launching.
Launch the job and watch the «Runs» and «Results» tabs: every chat shows its outcome and the fate of the message.
If the chats are set through the «List» source, the panel joins them by itself, in this order.
210-390 seconds between two joins of one account by default. Every 5-10 joins the account takes a long break, 2-3 times longer than usual.
The account solves the captcha right at joining, because bots remove members on a timer. If the captcha is not passed, the account leaves the chat. The setting «Leave the chat if the captcha was not passed» is on by default and applies only to chats the account joined in this run.
If a bot in the chat demands a subscription to a channel, such a chat is skipped by default. The «Subscribe» mode subscribes the account itself: up to 3 subscriptions per chat by default, 10 at most. Each subscription spends the same join.
The field «First round after, minutes» is 0 by default, meaning write at once, with a ceiling of 1440. The pause runs once, after all joins of the account.
No more than 30 joins per account per run. The rest stays for the next run, which finds the account already joined.
Every action and its outcome is visible in the run results.
Detailed module guideIf the slow mode wait exceeds the run budget, the chat gets the refusal «Slow mode: the wait exceeds the run budget; messages already sent are preserved». The other cases get separate reasons in the panel.
The flag arrives with the chat, and the panel requests the interval once per group and only where the flag is set. If the wait does not fit into the pause, the tail of the chain is postponed: the account posts to other chats and returns after the pass. The panel remembers its own sends, so later rounds do not run into the same slow mode.
In the results the chat carries the reason «Only administrators can post in this group».
Separate reasons: «The topic is closed: messages cannot be sent to it», «Plain text messages are forbidden in this chat», «Sending photos is forbidden in this chat».
If a chat admits only by request, the target gets the reason «The target is waiting for the request to be approved: the chat admits only by one».
Each chat is written to by one account: the list is divided between the selected accounts. In a round an account writes to the set number of chats, the next round takes the next ones, and the list goes around in a ring.
| Example | Accounts | Chats per account per round | Passes | What you get |
|---|---|---|---|---|
| 60 groups for an arbitrage course | 4 | 5 | 3 | 20 chats per round, all 60 in three passes, up to 15 messages from one account |
| The same 60 groups, too few passes | 4 | 5 | 2 | 40 of 60 chats get the message, the other 20 are marked «Not taken up: it didn't fit into this run's rounds» |
| The same 60 groups, the field set to «0» | 4 | 0, all chats | 1 | 15 chats per account in one round |
Before the launch the panel counts the workload out loud. For four accounts, three chats per round and two passes it writes: «4 × 3 = up to 12 chats per round. Up to 6 messages will go out from one account: 3 per round × 2 rounds». Next to it comes a time estimate, about 30 minutes of work per round plus the breaks.
Field bounds: passes from 1 to 48, rest between rounds from 1 to 1440 minutes, 60-120 by default. Chats per account per round at most 500: that is how many groups and channels Telegram lets one account join without Premium, up to 1000 with Premium.
A chain of several steps goes into every chat, not a single message. The «Add step» button adds one. Step types: text, photo, video, GIF, sticker, voice, round video, album, file, audio and a «Repost» of a channel post. Between steps inside one chat the pause is 60 seconds by default and never faster than the chosen band. Chat broadcast posts in public rooms, where every member sees the message, so its bands are higher than those of a mailing to private chats.
| Protection mode | Pause between groups |
|---|---|
| «Fast» | 30-45 s |
| «Balanced» (default) | 60-90 s |
| «Careful» | 150-210 s |
A plan opens the whole panel, not only chat broadcast: you get the same number of streams in private mailing, warm-up, inviting and every other module. A stream is one account working in a module at the same time as others. Accounts and proxies are paid separately, current prices are on the pricing page.
| Plan | Price | Streams per module |
|---|---|---|
| Trial | $0, 3 days, no card | 3 |
| Starter | $29 for 30 days | 10 |
| Pro | $59 for 30 days | 50 |
| Team | $99 for 30 days | 150 |
«Runs»: the progress of the job by account.
«Results»: the chats that were written to and the fate of each message: whether it stayed in the chat or was removed.
«Skip recent»: a chat that was already written to is skipped. Off by default, the window «How many days to remember» is 30 by default.
«Chat blacklist»: a chat gets there if several different accounts could not write in it. The threshold is 2 by default, from 1 to 10. Reasons: «Deletes messages», «Nobody can post», «Charges Stars per message», «Group not found».
The blacklist is one for all runs of the workspace, and there is no whitelist. If you stop a run and continue it, chats already written to in this round do not get the message again.
How to find chats with a parser, prepare accounts and write text variants: mailing to chats, the breakdown.
Every field of the module and the skip reasons: the guide Chat broadcast module: setup and limits.
How to collect the list of groups for a mailing: parsing chats and groups.
Yes, if the chats are set through the «List» source: the panel joins by itself where writing is otherwise impossible. The default pause between joins is 210-390 seconds, with at most 30 joins per account per run.
The number of accounts multiplied by «Chats per account per round» and by «Passes» (up to 48). If the list has more chats, the extra ones are marked as not fitting into the rounds, and the next run can take them.
Nothing. The panel learns the interval itself and, if the wait does not fit into the pause, postpones the tail of the chain while the account posts to other chats. If the wait exceeds the run budget, it shows as a separate reason in the results.
In «Results» the chat shows «The message was removed after sending». If it repeats from different accounts, the chat goes to the «Chat blacklist» with the reason «Deletes messages».
Within one run a chat is written to by one account. If Telegram refused an account in a chat, on later runs it does not write there, while other accounts can still use the chat.
The text can take the chat's name and @, and variants are written in curly braces. For the first step you can pick «AI for each chat» and describe what to write about.
In the «Mandatory subscription» block you choose «Skip such chats» (the default) or «Subscribe». In the second case the account subscribes to the channel, up to 3 times per chat by default, and each subscription spends a join.
Forwarding works only in chats the account is already in and allowed to write to, and everything else is manual. The module joins by itself, keeps the pauses, splits the list between accounts and records the outcome for every chat.
The module is included in every plan together with the rest of the panel, and the plans differ in the number of streams. The prices are counted in the table above, current ones are on the pricing page. Accounts and proxies are paid separately.
It depends on the protection mode: «Fast» 30-45 seconds, «Balanced» 60-90 seconds (the default), «Careful» 150-210 seconds. Between steps inside one chat it is 60 seconds by default, and never faster than the chosen band.
No, only to groups. Channels in folders are skipped, and the «Account chats» source does not include channels or private chats. Private messages have a separate mailing to private chats.
The module does not add link buttons. For a link with a button there is the «Repost» step: a channel post is forwarded whole, with the source header, and the sending account must have access to that channel.
Ready lists of channels and chats by topic: how many a section holds, how active they are and the top 20 by subscribers.
Works together with
The free Trial plan covers the whole workflow: connect accounts, configure a launch and see the results with your own eyes.
TeleTraff editorial teamUpdated: