Telegram inviter

The inviter works with a selected user dataset and an existing Telegram target. Before launch, the panel verifies access and the current permissions of every selected account.

Launch flow

• Select a dataset, accounts, and a target you administer.
• Complete the access and capability-plan check for this launch.
• Start the job and review results, limits, and errors.

Before you launch

• Accounts with proxies. An account without one will not run.
• A dataset of people, not channels: the inviter invites users, so parsed members or commenters are what you want.
• A target your selected accounts can already invite into. The panel does not grant or revoke admin rights — you do that in Telegram itself.
• Readiness for some people in the dataset not to join for reasons outside the panel's control — their privacy settings, for one.

Where to invite

• An existing channel or group — the panel checks your selected accounts' access to that target.
• Create a new channel — the panel creates a real channel from one of your accounts and only uses it after a confirmed result.
• The channel or group can be swapped right up to launch: after a swap the rights check runs again.

The rights check before launch

The check covers every selected account, not a sample. While any account is still unconfirmed the start button stays disabled, so a job never begins on accounts whose rights are unknown. Accounts are checked in waves of a few at a time, so a large selection takes longer. There is no cap on how many accounts the check covers: you wait longer, but nothing is silently trimmed.

Two limits and what you actually get

The total invite limit is the ceiling for the whole job. The per-account limit is the ceiling for one account. Whichever runs out first wins, so the real volume is the smaller of the total limit and per-account limit multiplied by the number of accounts. In the screenshot above the total is set to 240 while five accounts are allowed 20 each, so the plan holds exactly 100 actions, not 240. The panel shows this in the stream allocation before you start, so the gap is visible in advance.

Pace and what to do about FloodWait

• Three presets for the pause between invites: fast, balanced and cautious. The panel prints each one's range in seconds, and any manual value switches the mode to custom.
• The pause always carries jitter: consecutive actions never repeat the same interval.
• When Telegram returns FloodWait there are two responses: wait and continue, or stop that account for the current job. The other accounts keep working.
• An extra pause adds your own minutes on top of the wait Telegram asked for, for when you would rather not come back the moment it expires.

Batching

Batching splits an account's work into parts: it sends a set number of invites, pauses for a number of hours, then continues. That helps when the dataset is large and you want it spread across a day or more. The pause appears in the log as the account reaching its batch size and continuing after the configured pause, so a quiet lane never has to be guessed at.

Run progress

• Every account has its own lane with counters for successes, errors and skips.
• An account paused on FloodWait is marked in the lane list while the other lanes keep going.
• When an account stops, the targets it never reached are handed to another eligible account instead of being lost.
• The log filters by account and by target, so one account's outcome can be traced end to end.
• Pause and stop apply to a single lane without touching the rest.

Reading the results

• Success — the person was added and Telegram confirmed it. People who were already members count here too.
• Skipped — no invite was ever sent: a duplicate in the dataset, an exhausted limit, or a stopped account.
• Blocked — protection stopped the action before it reached Telegram.
• Deferred — Telegram limited the attempt and the target was not closed in this run. Deferrals give the job a partial status even when errors are few.
• Errors — Telegram refused, or membership was not confirmed after the request.

Why someone did not join

• Their privacy settings forbid being added to groups and channels. This is the most common reason and there is no way around it.
• They are already a member. The panel checks that before contacting Telegram, so no limit is spent on them.
• Telegram accepted the request but membership was not confirmed on re-check — that outcome is recorded separately and never passed off as success.
• The account hit FloodWait or an anti-spam warning and stopped for this job.
• The target appeared in the dataset twice: no repeat invite is sent.

Common mistakes

• Launching on accounts that were never warmed up or rested: Telegram restricts fresh sessions fastest.
• Running the rights check on one account and launching on ten: only the confirmed ones will work.
• Setting the total limit by eye without accounting for the per-account limit — the plan comes out half the expected size.
• Judging a dataset from a single run: the share of closed profiles differs wildly between sources.