Account and data security
What the panel does
Section titled “What the panel does”Spread pauses. The pace profile sets the gaps between actions, and every pause differs slightly from the previous one — consecutive actions never repeat the same interval.
FloodWait handling. If Telegram asks to wait, the thread pauses instead of pushing the account further. In inviting there is a choice: wait out the delay and continue, or stop that account for the current job.
Daily limits and a night break. Configured separately from pace.
Stopping before sending. Some actions are stopped by protection before Telegram is contacted — in the results this appears as a skip rather than an error.
Thread isolation. Pause and stop apply to a single account; the neighbours keep working.
What depends on the operator
Section titled “What depends on the operator”- A proxy on every account — before the first action in Telegram, not after.
- Warmup before working tasks — duration matched to the account’s age.
- Sensible volume — putting the whole limit on one account instead of spreading it across the fleet remains the most common cause of problems.
- A filled-in profile — the panel does not set the name, avatar and bio for you.
- Varied text — an identical message from every account is obvious to readers and anti-spam alike.
Data in this documentation
Section titled “Data in this documentation”The screenshots in this knowledge base were taken on demonstration data: there are no real phone numbers, sessions, proxy credentials or client usernames in frame.
What warmup does not do
Section titled “What warmup does not do”Warmup does not lift restrictions already imposed and does not unblock an account. An account under restriction has to be checked and recovered first — see the warmup guide.