Get started
Before you start
Prepare your Telegram account, dedicated proxy, machine, and team permissions before setting up a workspace.
Prepare everything below before opening the add-account flow. This avoids stopping during sign-in to find a password, buy a proxy, or wait for a machine to become ready.
Telegram account and phone
You need a personal Telegram account you are authorized to use. Keep a phone signed in to that account nearby to scan a QR code or receive a sign-in code.
If two-factor authentication is enabled, you need to know the password. The app uses it only during sign-in and does not save it afterward.
You do not need to create an api_id or api_hash to add an account. You also do not need a bot token to connect a personal account.
Signing in to Telegram and signing in to the web app are separate things. Team members sign in to the web with their own identities. They do not all need access to the Telegram account’s phone to work in an authorized inbox.
A dedicated proxy for each account
Each account needs one dedicated, fixed proxy. A proxy cannot be shared by multiple accounts or taken from another workspace.
The system supports:
- SOCKS5.
- HTTP.
- Proxies with or without a username and password.
Prepare the host address, port, and credentials if your provider requires them. Check the actual IP country rather than relying only on the purchased plan’s name.
Do not choose a rotating-IP proxy. Telegram-Auto does not run accounts over a direct connection as a fallback when a proxy is missing or fails.
You can add proxies before you have a machine, but checks must wait for a workspace machine. Connect a machine first for a smoother setup.
Read Proxy concepts and the Add proxies guide.
Choose a Hetzner or Windows machine
The machine holds sessions and performs Telegram work. Closing your browser tab does not stop the machine. Conversely, opening the web app does not make accounts run when their machine is disconnected.
| Option | What you need |
|---|---|
| Hetzner | A Hetzner account, project, and API token with Read & Write permissions |
| Windows | A machine you manage that can run the installer and stay connected to the network when work is needed |
Only the workspace Owner can connect Hetzner. Once connected, the app can create machines and install workers in your project.
For Windows, the in-app installation instructions support Windows 10/11 or Windows Server 2016 and later. The installer runs with standard privileges and does not require Admin. Make sure you can run PowerShell under your machine’s policies.
See Hetzner machines or Windows machines before choosing.
Costs you pay
Hetzner machines belong to your Hetzner account. You pay Hetzner directly for the machines. They are not free machines included with your workspace.
Prices shown when launching a machine help you consider configurations and locations. Do not treat an example price as a fixed-cost commitment.
You also supply and pay for proxies. For Windows, you cover the machine, electricity, network, or Windows VPS costs.
Prepare your team and workspace
Choose a workspace name, working time zone, and primary customer language. The time zone should fit how your team reads schedules and sets operating hours. Accounts also have their own operating-hour settings.
Each member should have their own sign-in identity. Before inviting them, decide what they need:
- Manage infrastructure and accounts: Manager.
- Reply to assigned conversations: Support.
- View overview information and stats without reading messages: Viewer.
Reserve the Owner role for the person actually responsible for the workspace and Hetzner connection.