---
title: "Add an account with a phone number"
locale: en
url: https://tlg.builera.app/en/docs/guides/accounts-add-phone
verified: 2026-10-24
app_version: "2.0"
---

# Add an account with a phone number

Sign in to Telegram with a phone number, verification code, and two-factor authentication password if required.


You can sign in with a phone number when scanning a QR code is inconvenient. Telegram requires a sign-in code and may also require a two-factor authentication password.

## Who can do this

The workspace Owner or Manager.

## Before you start

You must control the Telegram account and have access to where the code is delivered. Have the two-factor authentication password ready if enabled.

The account in the app must have a dedicated proxy and a machine. When adding a new account, choose the proxy, machine, and settings as described in [the QR guide](https://tlg.builera.app/en/docs/guides/accounts-add-qr), then select the phone number method at the sign-in step.

> [!IMPORTANT]
> Do not share sign-in codes or two-factor authentication passwords. Documentation images must completely cover codes, passwords, and phone numbers, even when the interface already masks part of the number.

## Where to start

- New account: **Accounts → Add account**, complete the preparation steps, then continue to **Sign in**.
- Existing account that is not signed in: open the account details and click **Sign in**.

## Steps

1. Select **Phone number**.
2. Enter your number in **Telegram phone number**, including the country code. Masked example: `+84 9•• ••• 101`. When signing in, you must enter your own full number.
3. Click **Send code**.
4. Check the on-screen instructions to see whether the code was sent to the Telegram app or by SMS.

5. Enter the code in **Sign-in code**.
6. Click **Sign in**.
7. If prompted, enter the **2FA password**. This is the password you set for Telegram, not the code you just received.
8. Click **Confirm**.
9. When you see **Signed in successfully**, click **Done**.

### Resend the code or change the number

1. Click **Change number / resend code**. The app returns to **Telegram phone number**, with the previous number still filled in.
2. Edit the number if needed.
3. Click **Send code**. Telegram sends a new code, and the previous sign-in attempt closes automatically.

If Telegram requires a wait before sending a new code, the screen displays the waiting time. Do not keep clicking.

### Cancel sign-in

Click **Cancel** on the sign-in screen. Closing the dialog or switching methods before an attempt finishes also requests cancellation of that attempt.

Cancelling sign-in does not remove the account from the workspace. The record already created may remain in the list so you can sign in again.

## Result

After a successful sign-in, the account connects through the selected machine and proxy. Chats start syncing into Inbox.

The two-factor authentication password is used only for the sign-in attempt and is not saved after completion. Check the limit mode separately. New accounts default to **Free**, not automatically to **Safe**.

## Check

Verify the account you just signed in on its details page. Check **Network & machine**, its status, and **Limits & schedule** before running jobs.

## If something goes wrong

- Incorrect code: read the error beside the input and check the code for the current sign-in attempt.
- Telegram requires a wait: wait as instructed. Do not keep starting new attempts.
- Sign-in job not picked up: check that the machine is connected and check the proxy.
- Forgotten two-factor authentication password: resolve this through Telegram. The app does not skip this step.

See [sign-in troubleshooting](https://tlg.builera.app/en/docs/troubleshooting/telegram-login).

## Do it with the API or MCP

Use [accounts.login_start](https://tlg.builera.app/en/docs/reference/rest/accounts.login_start), [accounts.login_status](https://tlg.builera.app/en/docs/reference/rest/accounts.login_status), and [accounts.login_submit](https://tlg.builera.app/en/docs/reference/rest/accounts.login_submit).

MCP names: `accounts_login_start`, `accounts_login_status`, `accounts_login_submit`. Requests are still subject to the AI connection's permissions and assigned account scope.