# Telegram chat broadcast: the Chat broadcast module > A chain of messages goes into Telegram groups from several accounts. Where the chats come from, how rounds run, and what the module does with chats that remove messages. TeleTraff editorial team · October 21, 2026 · 3 min read - A message chain into every chat, with AI writing the first message per chat - Rounds with breaks and a workload estimate before launch - A chat blocklist the module fills in itself TeleTraff sends messages to Telegram chats with the Chat broadcast module: it delivers a chain of messages into groups from several accounts. Chats come from your list, from the groups the accounts already belong to, or from the history of earlier runs. Chats that remove messages or refuse posts go onto a blocklist by themselves, and the module stops going there. ## How to run a broadcast into Telegram groups - Pick the accounts and the chat source: "List" (the base can be built with [parsers](/en/modules/parsers)), "Account chats" or the history of earlier runs. - Build the message chain and set the passes, the rest between them and the protection. - Launch the task and follow it in the "Runs" and "Results" tabs. ## Where does the module take chats from? - "List": your list, a parsing base, a folder or a t.me/addlist link. The module joins only where Telegram would not let it write otherwise. - "Account chats": send only to groups the selected accounts already belong to. The list is ignored and nothing is joined. - "From history: delivered": chats from earlier runs where the message stayed. - "From history: failed": chats where sending failed. Blocklisted chats do not get here. Chats that failed for a temporary reason are retried: flood wait, join budget, an interrupted run. A folder costs one request for its whole contents, and its chats are read at launch. Only groups from the folder are used; channels are skipped. For "Account chats" the panel shows a preliminary group count from saved dialogs beforehand: channels and private chats are not in it, and at launch membership is checked again and duplicates are dropped. If the number looks short, "Recount" refreshes it. ![Chat broadcast setup screen](https://teletraff.com/modules/shots/en/chat-broadcast-setup.webp) *Settings: accounts and target chats on top, below them the message with placeholders and the Rounds and workload block with passes, chats per account and rest.* ## What goes into the chat? Every chat gets a chain of several steps, not a single message. Steps are added with "Add step"; the default pause between them is sixty seconds, never faster than the protection band. The "How the chat will see it" preview shows how it looks in a group. - Step types: "Text", "Photo", "Video", "GIF", "Sticker", "Voice", "Video note", "Album", "File", "Audio". - "Repost": you give a "Post link" and the post is forwarded whole, with its source header. The sending account needs access to the source channel. - The chain has no link button. If you need one, make a post with it in your own channel and send that post as a "Repost" step. On every pass the panel checks whether the first message of the chain stayed in the chat. ## Can AI write the first message for each chat? Yes. In "Who writes the first message" choose "AI for each chat" instead of "My text" and briefly describe in "What to write about" what you offer: for example, analytics for Telegram channels or a free week of access to a service. AI uses your brief, the chat name and its @; it does not read the chat feed. Only the first step is replaced: the rest go as written. If AI is unavailable, the first step's text is sent and the outcome shows in the journal. AI cannot replace a repost. ## How do rounds and rest work? - "Passes": how many times to go through the list, from one to forty-eight. - "Chats per account per round": how many chats an account takes in one round. Zero means all of its chats. - "Rest from, min" and "Rest to, min": the pause between rounds, sixty to one hundred twenty minutes by default. With a single pass the fields are inactive. - The target list is split between the selected accounts. After a restart, messages already sent are not repeated. Before launch the panel estimates the workload: how many messages one account will send (per round and over all passes) and how long the run takes. For time it assumes about thirty minutes of work per round plus the breaks. A run longer than a day holds one stream of your plan the whole time. How to work out sending to a list of chats is shown on the page about [sending to multiple groups](/en/telegram-automation/send-to-multiple-groups). ## What about chats that demand a subscription? In promo chats a bot often deletes the message and asks you to subscribe to a channel or start a bot. The "Mandatory subscription" block offers two ways: "Skip such chats" (the default) or "Subscribe". With the second, the account subscribes itself, starts the bot, taps "I subscribed" if the bot offers it, and sends the message again. "Subscriptions per chat, at most": three by default, ten at most. If a chat asks for more, it is skipped and the account does nothing. Every subscription is a join: it spends the account's join limit (thirty per run on screen) and follows the same pause. Subscriptions stay on the account. With the option off, the journal shows exactly what the bot demanded. ## What does the module do with chats that remove messages? The "Chat reputation" card keeps one "Block list" across all runs of the workspace, not per run. This module has no allow list. The list fills in by itself when a chat refuses or removes messages, and every entry shows its reason. - Reasons in the list: "Deletes messages", "Nobody can post", "Charges Stars per message", "Group not found", "Restricted the account for longer than the run", "Added manually". - The "Blacklist a chat if posting there failed for" line: how many different accounts must fail before a chat enters the list, from one to ten (two by default). One account may have stumbled on its own; several different ones mean the chat is the problem. - "Add your own list": chats as @ or t.me, one per line or comma-separated. "Upload" and "Export" move the list as a file. - "Skip recent": off by default. Turn it on and set how many days to remember (thirty by default): chats written to within that period are skipped. ## Can I reply to incoming private messages? Yes, with the "Private conversations" block. "Do not reply" is selected by default. Choose "Dialogs reply" and [Dialogs](/en/modules/dialogs) answers the private messages. You can also take the settings from a Dialogs campaign: "By campaign". Then the prompt, memory and limits come from there, and only the reply window stays on the card. Replies go out in the breaks between rounds and after the last one: during the broadcast itself the account is busy. The window is set by "After the pass, min" (one hundred twenty by default), and the conversation cap per account by "Conversations per account" (six by default). When the cap is reached, new contacts wait for a free slot. ## What can I see during a run? - "Runs": the task's progress by account. A run has an action that opens its incoming messages. - "Results": the chats written to and what became of each message: whether it stayed in the chat or was removed. - The journal: the reason for every refusal and the outcome of AI text. > **Member mentions** > > Mentions are off by default. If you turn on "Mention members", chat members are mentioned in a hidden way at the end of the message, and the notification can reach them even when the chat is muted. Admins, bots and your own accounts are not mentioned; if the member list is unavailable, the message goes out without mentions. The panel warns that mentions raise the risk of reports and account restrictions. ## FAQ **Which chats can I write to?** Groups. Channels in folders are skipped, and "Account chats" counts only groups the accounts already belong to: channels and private conversations are not included. **Do I have to join the chats beforehand?** No. With the "List" source the module joins only where Telegram would not let it write otherwise. If the accounts are already in the groups, use "Account chats": no joins at all. **How many messages will one account send?** The panel counts it before launch: messages per round times the number of passes. The expected duration in hours is shown right there. **What happens if I stop the run and start it again?** Messages already sent are not sent again. The target list is split between the selected accounts and the remainder is worked through. **How do I know a message stayed in the chat?** Open the "Results" tab: it marks for every chat whether the message stayed or was removed. On every pass the panel also checks the first message of the chain. **How is this different from mailing to private messages?** ["Mailing"](/en/modules/mailing) writes to people in private messages; "Chat broadcast" writes into groups. Chats have their own mechanics: mandatory subscription, removed messages, chat reputation. **Why does chat reputation count failed accounts?** So a chat is not punished for one account's mistake. A chat enters the block list only when several different accounts failed to write in it. You choose how many.