Search for a telegram shill bot and most of what comes back is code on GitHub, forum listings and research into crypto scams. The tools promise loops across many groups and claim they never get banned. The research describes groups where bots mostly talk to other bots. Very little of it explains what the posting actually does inside one group, or what the people reading it can see.
We sell a module that does this, so this page is not neutral. It is written to be accurate. Where a figure comes from Telegram it is linked, where it comes from our own module's settings it says so, and where nobody has published a number we do not invent one.
What are Telegram shill bots, and what makes a drip bot different?
A telegram shilling bot is not a bot in Telegram's sense. Bot API bots cannot join a group by themselves, and they appear with a bot label, so anything that has to look like a member runs on ordinary user accounts through their sessions. That split between software built on a bot and software built on an account decides what any telegram shill software can do. Here it means every message comes from a phone-number account, and each one carries that account's risk.
The classic telegram shill bot software works like a broadcaster. It loops a text, or a handful of texts, through as many groups as it can reach. A blaster that posts one message into many groups is the honest name for that job. A telegram drip bot, sold as a telegram group drip bot, points the other way. It targets one group, gives each account a different line, and spaces the accounts out so the messages arrive the way new members would.
The labels sold around this, telegram group hype bot, telegram group chatter bot or telegram group seeding bot, all describe the same mechanism with a different goal in mind. Hype pushes a launch or a token. Chatter fills silence. Seeding puts the first questions in a new group so real members are not the first to speak. The mechanics are identical, and so is what a careful reader can spot. The difference is whether the accounts are real people saying what they think or invented personas posing as satisfied users.
Why ten new accounts posting at once reads as a raid
Groups are watched more closely than private chats. An admin sees joins, a moderation bot logs them, and members notice when strangers arrive in a cluster and agree with each other. A burst from fresh accounts is the shape most anti-spam setups are built to catch, and it is also what a spam raid looks like. A telegram group drip exists because of that. It changes the timing, not the content.
Telegram gives admins tools that work against bursts directly. Slow mode limits each member to one message per interval the admin picks, and a member who writes sooner gets an error back rather than a post. Since December 2022, admins of groups with over 200 members can switch on Telegram's aggressive anti-spam, which removes messages its own system flags. Many groups also run third-party bots that check new joiners against shared spam lists, demand a captcha, or delete links from accounts that joined minutes ago.
Pacing changes the timing, not the accounts
A drip run spreads joins over an hour or more, so slow mode rarely triggers, because each account writes once anyway. It does nothing about a filter that deletes the message after it lands, or an admin who reads the thread and recognises a staged exchange. Finding groups is a separate task. Searching for public groups worth joining covers how Telegram's search ranks them, and the rules for public usernames in search explain why the @name you paste must resolve before any account can join.
The accounts themselves matter as much as the pacing. A session that was registered last week, has no photo and no history, and joins a group only to post one enthusiastic line is easy to read, however slowly it arrives. No timing setting changes that.
How the Group Drip module runs one message per account
Group Drip is module 32 in Telegram Solutions, a Windows desktop suite that runs many accounts from their sessions. It does one thing: the accounts you select visit one group, each posts its own message from your list, and each leaves again. The walkthrough below shows a full run in the panel, from pasting the list to reading the results table.
Setting it up takes a few fields. The defaults quoted here are the module's own settings, not limits Telegram publishes.
- Select the accounts. They load from session files or a desktop install's data, the same TDATA folder a Telegram Desktop copy keeps, and each one uses its own proxy if it has one.
- Paste the group: a public @username, a t.me link, a private invite link or a t.me/c/ address.
- Write the messages, separated by a line that holds only
--. Account 1 posts message 1, account 2 posts message 2, and nobody posts the same text. A message can run over several lines, and it is sent exactly as typed. - Choose the order, in-order or shuffled once, and what happens when the list runs out: skip the remaining accounts, or start again from the top.
- Set the timing. Each account reads the group for 15 to 45 seconds, shows the typing indicator for 3 to 9 seconds, stays 20 to 60 seconds after posting, and the next account waits 90 to 240 seconds. Every wait is picked at random inside its range.
- Choose how many accounts run at the same time. The default is one, and the most is 20.
Leaving the group and checking the post survived
Two behaviour switches sit underneath. Leave the group after posting is on by default, but an account that was already a member before the run never leaves, because that membership is real. Verify the message stayed reads the post back a few seconds later, so a message deleted by the group's anti-spam bot is reported as failed instead of delivered. That check is the honest answer to whether anything reached the group, and the results table lists every account as sent, failed, skipped or stopped.
The accounts do not need each other as contacts, and nothing in the run adds anyone. Saving another account as a contact is a separate step none of this needs.
Can a telegram group conversation generator make an exchange read naturally?
It can make it read in order. Whether it reads naturally depends on what you write. With Reply to the previous message switched on, each account answers the line the account before it posted, so the group shows a thread instead of separate posts. The module then runs one account at a time, because a reply needs the earlier message to exist. With several accounts in parallel and in-order selected, each account still gets its own line, but the lines can land out of order, and the log warns about it.
That is the whole of the telegram group conversation generator part. The module writes nothing. It posts your lines, so the quality of the exchange is the quality of the script. A telegram fake conversation bot that only rotates "this is great" and "agreed" teaches readers to ignore it within a day. Lines that ask real questions get real replies, and a real reply is worth more than ten staged ones.
Three things give a scripted thread away, and none of them is the software. The first is accounts that join, post and leave inside a few minutes, every time. The second is strangers who agree perfectly and never ask anything awkward. The third is profiles that look alike. Any member can open an account's profile, see the groups they share, and draw a conclusion. What a scraper can see of a group's members is the same view an admin has of yours.
If you run your own accounts, how many accounts one Telegram app holds is the first limit you meet. Past it, accounts go into a session manager, which is where this module reads them from.
What stops a run: the errors Telegram and the group send back
Every request in a run can come back with an error, and a drip run is mostly about reacting to them correctly. Telegram documents these identifiers in its reference for sending a message. What each means, and what the module does with it, follows.
FLOOD_WAIT_X tells the account to wait X seconds before repeating the action. The module waits out short ones. A wait above 300 seconds, on joining or on sending, stops that account and moves to the next, rather than leaving the run asleep for hours. SLOWMODE_WAIT_X means the group's slow mode is on and this account wrote too soon, which in a one-post visit usually means the account had already written there.
CHAT_WRITE_FORBIDDEN means the account cannot write in this chat, for example in a channel or a group where members are muted. CHAT_GUEST_SEND_FORBIDDEN means the account has to join the discussion group before it can comment, which is why the module joins first. PEER_FLOOD is different in kind. It is Telegram's signal that this account has been limited for sending too much, and the module stops that account and marks it in the results table instead of retrying. An account in that state belongs in a spam check, not in the next run.
When the module stops the whole run
Some failures are about the run, not one account. If three accounts in a row hit a dead link, the module stops the whole run, because the link is wrong. Three in a row that cannot write stop it as well, because the group does not let new members post. A third trigger is three flood limits in a row. Sessions that turn out to be dead or banned are marked as such. The Stop button answers within seconds even during a four-minute wait. Clearing up afterwards is a separate job: removing your messages in bulk and leaving dozens of groups in one pass both have their own limits.
Is shilling in a Telegram group allowed?
Telegram's terms of service say users agree not to use the service to send spam or scam users. They publish no threshold for spam. In practice the group decides first: its admins can remove a member, ban one, or report the messages, and reports feed Telegram's own moderation. A run that posts into a group whose rules forbid promotion is breaking that group's rules regardless of pacing.
The law is more specific than most pages admit. In the United States, the FTC's rule on consumer reviews and testimonials, 16 CFR Part 465, has a section on fake indicators of social media influence. It defines those as indicators generated by bots, by accounts not associated with a real individual, or by hijacked accounts, and it bars selling or buying them where the buyer knows or should know they are fake and uses them to misrepresent influence for a commercial purpose. The rule took effect in October 2024. Whether a staged group thread counts as such an indicator is a question for a lawyer, but persona accounts praising your product sit close to the line it draws.
Disclosed team accounts versus invented personas
The FTC's separate endorsement guides cover the simpler case. When someone praising a product has a connection to the seller that readers would not expect, such as being on its staff or being paid, that connection has to be disclosed. Team members writing in a launch group as themselves, with their role visible, are fine under that idea. The same people posting as invented happy customers are not.
Crypto groups are where shilling meets fraud. Using fake accounts to pump a token so others buy is market manipulation in many jurisdictions, and it is the use most research on telegram shill bots documents. We do not support it, and no setting in the module makes it safer. The disclosure rules and scam patterns around paid promotion are covered in how crypto projects market through Telegram groups and bots.
Where seeding software helps, and where it does not
Used plainly, telegram group seeding software is a scheduling tool for your own accounts. It suits a new community where staff accounts post the first real questions, an announcement that several team members should acknowledge without arriving in the same second, or an admin testing whether their own group's slow mode, join rules and anti-spam bot catch what they should. In each case the accounts are what they appear to be.
It does not create members. Nobody is added to the group, which is a different mechanism with a hard cap. Adding members to a group in bulk and the limits that stop member-add bots cover that side. It does not reach anyone outside the group either. Writing to someone without saving their number and looking a person up by phone number are direct-message problems with their own rules.
Engagement that outlasts the script
It also does not fix a group that has nothing to say. A telegram group engagement bot or telegram group engagement tool can start a thread, but members stay for answers, moderation and a reason to come back. Most products sold as telegram engagement software are Bot API helpers for welcome messages, polls and moderation, which is the more durable kind of engagement. If the group is a project you may hand over later, keep ownership on an account that never runs automation. Passing ownership of a channel or group to another account has conditions that a flagged account can fail.
No software raises Telegram's limits or keeps an account from being restricted.
A drip run controls pace, order and honesty about delivery. The rest is the content and the accounts, and both are the operator's responsibility.