Telegram account warmup

Warmup runs the actions defined by a profile for selected accounts. The operator sees the plan, job progress, and actual statuses instead of a promise that an account is ready.

Launch flow

• Select accounts and a warmup profile.
• Review the launch preview and eligible accounts.
• Start the job and monitor results and restrictions.

Before you launch

• Accounts with proxies — an account without one will not run.
• Accounts free of other jobs: they cannot be used in working modules while warmup runs.
• A sense of how long you can wait: from half an hour to a week.

Warmup duration

• Short presets — 30 minutes, one, two or three hours: a quick warm-up before a job.
• One day — the baseline for accounts that already worked somewhere.
• Three days and a week — for fresh accounts, where rushing costs the most. A week is the longest warmup there is.
• Your plan caps the maximum duration.

What the account does during warmup

Warmup does not keep an account online for days. It splits the work into short micro-sessions: the account signs in, reads something, leaves a reaction, subscribes to a channel, saves a post — and leaves. Sessions are spaced from about ninety minutes to four hours apart, and in between the account is offline, like a real person. The plan for the chosen duration is visible before launch: how many micro-sessions, how many actions in total and what they consist of.

What the cycle plan shows

• Micro-sessions and total actions as a range, not an exact figure: the real number depends on the account.
• The interval between cycles in minutes.
• Phases by day: day one is the quietest, then activity ramps up gradually.
• The action mix: the share of reading, reactions, subscriptions and saves.

Run progress and results

• The warmup day and how many actions each account has completed.
• Current state: a micro-session is running, or the account is on a break.
• An event log per account.
• Warmup can be stopped at any moment — completed actions stay.

Why an action may not happen

• Telegram asked to wait (FloodWait) — the account pauses and continues later.
• The action is unavailable to this account: no suitable channels to subscribe to, for example.
• The operator stopped the run.
• The account picked up a restriction — visible in its status.

What warmup does not do

• It does not lift restrictions the account already has and does not unblock it.
• It does not guarantee that any module will then run without refusals.
• It does not replace a proxy or a filled-in profile: name, avatar and bio are on you.

Common mistakes

• Expecting warmup to heal an account that already has a restriction.
• Warming up with no proxy, or with one that keeps dropping.
• Duration that ignores account age: half an hour is far too little for an account registered days ago — it needs a day or more, while an account older than a month is usually fine with a short preset.