Auto Registration

Auto Registration creates new Telegram accounts: it rents a number from an SMS service (or takes one you entered), passes the captcha, confirms an email if needed, receives the SMS code, creates the account with a generated name, saves the session files and writes the account to the accounts database.

How the task works

When you create a task for Auto Registration, the window asks:

• Accounts to register — the task stops once this many accounts are created. Empty — it registers until you stop the task.
• Save to table — which table of the accounts database to write the new accounts to.
• Threads — how many registrations run at the same time.

Each thread makes one attempt at registration. A successful attempt adds an account; a failed one releases the number and names the reason — and the next attempt starts right away, until the goal is reached. Failures don't stop the task, except for setup errors that repeating won't fix: a wrong service key, an unsuitable country, an empty email list and so on.

Quick setup

The other settings default to Auto: device, language, time zone and names are matched to the number's country.

Phone number

Manual entry. No service or key needed: during the task the application asks you to enter a number, and then the SMS code. Suitable for registering an account on your own number.

Custom service. For an SMS service that isn't on the list, you set up HTTP requests: Request: rent a number, Path to the phone number, Path to the activation id, Request: read the code, Path to the code, Request: release the number, Request: close the order. The requests can use [[smsActivationId]] and [[smsPhone]]. If the path to the code is left empty, the first number of 5–6 digits in the response is taken.

Captcha

Telegram may ask for a captcha when the code is sent. Captcha service:

• Built-in solver — solves the captcha by itself, nothing to set up;
• NextCaptcha — through the NextCaptcha service, needs a NextCaptcha API key.

Email verification

Sometimes Telegram asks to confirm an email instead of an SMS or before it.

Temp-mail service:

My own emails — a list of email:password, one per line. Each registration takes the next email from the list, and the code is read over IMAP: IMAP host (imap.firstmail.ltd by default), IMAP port (993), Use SSL/TLS. You need the mailbox password or an app password.

Manual entry — the application asks you to enter the address, and then the code from the email.

Device and region

The defaults are the best choice: every account gets a real device of its own, and the language, time zone and name agree with the number's country, as for a real user.

Proxies

Assign proxy on creation (on by default) and Proxy selection — proxies from your database. Each attempt takes a random one of the ticked proxies, and the registration goes through it. This proxy is saved on the new account.

Without proxies every registration goes from your IP — for a series that means almost guaranteed bans.

Additional options

2FA password pattern — the tokens <UpperLetter>, <LowerLetter>, <Letter>, <Digit>, <Number>, <Symbol> (one of !@#$%^&*-_=+), <Hex>; any other text goes into the password as is. Variants {a|b} don't work here. A pattern without tokens gives a password of 10 random characters.

Timeouts, retries and pauses

The Configure timeouts button. The default values suit most services.

How a registration goes

The log shows every stage:

1. "Taking a number: service, country (balance: …)" → "Took number: +…". If there are no numbers — "No numbers … waiting for some to appear". If the money has run out — "Insufficient balance … waiting for funds": the task doesn't stop and continues when the balance grows.
2. Captcha — "Solving the captcha" → "Captcha passed" or "No captcha required".
3. Email, if Telegram requires it: "Taking an email: …" → "Waiting for the confirmation code by email" → "Got the code".
4. SMS code: "Waiting for the SMS code" → "Got the SMS code".
5. Creating the account: "Creating account: First Last" → "Account registered: +…" with the progress.
6. Saving: the .session and .json files go to the sessions folder, the row goes to the selected database table. The order at the SMS service is closed as used.
7. Pause before the next registration. When the goal is reached — "Goal reached — no new registrations".

The new account appears in the database with the Unchecked status, with a name, country, 2FA password (if enabled) and the proxy it registered through.

Refunds for numbers

If a registration failed, the number is released at the SMS service as a separate job after the Cooldown before releasing a number — the money goes back to the service balance. In the log: "Number … will be released … in … s" and then "Number … released — money refunded".

• If an SMS has already arrived on the number, it can't be released — the service considers the number used.
• Some services have no release: the number expires by itself, and the money comes back by the service's rules.

Why a registration failed

The reason is written after "Registration failed:".

The whole task stops if: the SMS service rejected the API key, the service doesn't sell numbers of the selected country or no country is selected, there is no NextCaptcha key or no money on it, your own email list is empty or there is no password for IMAP, the sessions folder could not be created. The log shows "Stopping the task: reason" — fix the setting and start again.

Recommendations

• First run — one thread and 1–2 accounts. Check the key, proxies, email and folder without spending dozens of numbers on one mistake.
• Quality beats quantity. Success is decided by numbers and proxies: cheap numbers of mass-market countries are often "burnt", and Telegram doesn't like server proxies. Mobile and residential proxies give noticeably better results.
• Everything on Auto. Device, language, time zone and name matching the number's country — a +7 number with the English language and the New York time zone looks implausible.
• Few threads. Several registrations at once from neighboring IPs are more dangerous than a slow series.
• A separate table for fresh accounts — this makes them easy to tell apart and keeps them off mailings at first.
• Warmup. A fresh account is very fragile: the first days — only calm activity, no mailings or inviting.

Common questions

How many accounts are created per run?

As many as set in Accounts to register. An empty field — registration goes on until you stop the task.

Will I get the money back for a failed registration?

Yes, if no SMS arrived on the number: the number is released after a couple of minutes, and the service refunds the money. If the code has already arrived, the number counts as used.

What happens if the money on the SMS service runs out?

The task doesn't stop: it waits until the balance grows — from refunds for released numbers or a top-up — and continues.

Can I register an account on my own number?

Yes: SMS service → Manual entry (during the run). The application asks for the number, and then the code.

Which email service should I choose?

To start — Mail.tm: free and without a key. If Telegram rejects its domains, use the paid Qeex or AnyMessage with domains of large email providers.

Where do I find the created accounts?

On the Accounts tab, in the table chosen when creating the task, and in the Sessions save folder.

Why does a new account have the "Unchecked" status?

Every new account is marked this way. Run the Check accounts mass action — the status becomes Active.

Updated October 3, 2026