Accounts in one group message each other using built-in everyday scripts with human pauses, so they reach working condition instead of starting from nothing. Below: how it is built, the numbers inside it, and what warm-up does not do.
Updated 20 September 2026
To Telegram, a bought account is a blank page. That is exactly the problem.
A fresh session and one that sat unused for months look identical from the platform's side: no conversations, no history, no incoming messages. And then an account like that suddenly starts writing to dozens of strangers in a row. That is the most recognisable spam pattern there is — far more obvious than anything in the message text.
Warm-up addresses it literally. Before an account touches your list, it exchanges messages with your other accounts following everyday scripts. It ends up with conversations, sent and received messages, and natural intervals between actions. The campaign then starts from something rather than nothing.
The second effect is less obvious and just as useful: a warm-up is a free dress rehearsal. While the accounts talk to each other, the ones with a dead proxy, an unreadable session or an existing restriction drop out. You see them in the table before the campaign rather than halfway through it, when half your messages are already failing.
There is also a hard dependency: without the "Warmed-up account" flag the Checker will not run at all — username verification needs warmed accounts. Warm-up is not an optional extra beside the process, it sits inside the chain of accounts, warm-up, list, campaign.
The Warm-up section in the Automation menu, four steps from a group to the flag.
Warm-up only runs on a group, never on individual accounts. Groups are built in the Accounts section: tick the accounts, hit "Assign group", then pick an existing group or type a new name.
Only accounts with the Active status take part. Frozen, restricted and banned ones are skipped silently.
The system splits the group into pairs and reshuffles them every round, so each account ends up with several correspondents rather than one. "Number of rounds" is set in the launch dialog: 1–50, 10 by default.
The real number of rounds never exceeds the count of active accounts minus one — the system trims it for you. Group size therefore sets the depth of the warm-up directly.
The script holds its own intervals: 45–120 seconds between messages and 30–60 seconds between pairs. That is why one round takes tens of minutes — it is normal, not a hang.
The Forecast block in the launch dialog estimates pairs, rounds and messages. It deliberately overstates: it counts every account in the group and 20 messages per pair, while in reality only the active ones write and only 10 per pair.
The group row refreshes every 5 seconds: "Round X / Y", the message count, how many accounts are warmed, limited and frozen warnings. Expanding the row opens the tiles, the R1, R2… round squares and the accounts table.
When it finishes the badge turns green with "Finished" and the accounts get a flame icon. The Details column is honest about it: "Warmed up (5/5 rounds)" or "Partly warmed up (2/5 rounds)".
The warmed-up flag goes to any account that sent at least one message. To judge the real depth, read the Rounds and Details columns rather than the icon. Every field of the launch dialog and every status is covered in the warm-up guide.
Values that are set in the system, not in a marketing promise.
Warm-up is one of four pillars. Without the other three it only works at half strength.
The sequence that works: proxies, accounts, groups, warm-up, SpamBot check, list building and the checker, then a campaign capped at 3–5 sends a day. Skipping any link usually surfaces on day three as a batch of frozen accounts.
An honest answer instead of a nice number.
There is no single lifespan figure, and any service that quotes one is simply selling you a number. Telegram makes the blocking decision, and it depends on things that live outside the dashboard: where the accounts were bought and how they were registered, how clean your proxies are, what the campaign copy says and — above all — how many people pressed Report.
What you actually control is how quickly an account walks towards a restriction. A warmed account on its own proxy sending 3–5 messages a day with scattered pauses behaves nothing like a fresh session blasting a hundred identical texts in an hour from a shared IP. The difference between those two regimes is set by you, in two fields of the campaign form.
Telegram punishes overheating in different ways. A FloodWait is a temporary "wait N seconds": the account is automatically marked Restricted until the pause ends, its tasks move to other accounts, and afterwards it comes back. A spam block from reports is harsher: the account stops being able to write to strangers and turns Restricted until a date or Frozen indefinitely. In the second case an appeal to @SpamBot is the way out — you write it by hand from the Conversations section and mark "Appeal submitted" in the dashboard.
Spent accounts do not need deleting. The "Retired" status pulls them out of rotation while keeping their statistics in the reports — that shows how many campaigns a batch from a particular seller actually survived. After a couple of purchases this becomes your own lifespan figure rather than somebody else's.
How batches of accounts are usually lost.
What support gets asked most often.
One round takes tens of minutes: the script holds pauses of 45–120 seconds between messages and 30–60 seconds between pairs. At ten rounds, plan for several hours. There is no exact timer in the interface — go by the Round X / Y indicator in the group row, which refreshes every 5 seconds.
The technical minimum is two active accounts in a group, but at that size you get one or two rounds and almost no effect. The working minimum is six to ten: the number of rounds can never exceed the number of active accounts minus one, so the larger the group, the more varied the pairs and the more natural the resulting message history looks.
No, and no service can promise that — Telegram always makes the call. Warm-up lowers the risk: the account has a message history before it ever writes to a stranger. The rest depends on the quality of the accounts themselves, the proxies, the copy in your campaign and how fast you scale the volume. If an account is frozen during the warm-up, the system marks it Frozen (detected during warm-up).
Not on the same group. The extra activity at that moment raises the risk of a freeze and we explicitly advise against it. The correct setup is several account groups: while one is warming up, another works in a campaign. Groups are created in the Accounts section with the Assign group button.
The group and the number of rounds (1–50, 10 by default). The Min/Max delay fields exist in the launch dialog but do not really affect the pauses — the script uses its own values; the server only checks that you stay inside 5–300 and 10–600 seconds. You cannot pick individual accounts, write your own script texts or set the number of messages per pair: the scripts are built in.
So Telegram does not see a batch of accounts coming from one address. Proxies go into the Proxies section before you upload accounts, and then every imported account is automatically placed on the least loaded active proxy. A workable density is 1–3 accounts per proxy. Pairs whose proxy has dropped are simply skipped during a warm-up, so it is worth hitting Check across the pool before you start.
Warm-up, proxies, scraping, the checker and campaigns all sit in one plan. Got a promo code: full access for 7 days, no payment and no card.