Guides
Telegram voice calls in the browser
Place and answer 1:1 Telegram voice calls right in the browser with a connected account; the account needs a SOCKS5 proxy that carries UDP.
You call a person straight from the Inbox, with the very Telegram account you chat with them from, and answer the calls they place to it. Audio travels from your microphone to the worker, through the account's own proxy, to Telegram. The app does not record and stores no audio; it keeps only the time, the duration and why the call ended.
Calls are 1:1 voice only. Video calls, group calls and screen sharing are not available.
Who can do this
Owners, managers and support agents (for the accounts assigned to them) place, answer, decline and hang up calls. Viewers cannot call.
Before you start
- The account is logged in, not paused, not restricted by Telegram, and its worker is online on version 1.0.49 or later.
- The account's proxy is a SOCKS5 proxy with UDP support labelled Voice calls. See Proxies.
- Chrome or Edge (or a recent Safari or Firefox), the app opened over
https, and microphone access allowed. - An existing private chat between the account and that person. Groups, channels, bots and yourself cannot be called.
- Headphones help, so the other person does not hear their own voice back.
Where to start
Open Inbox and pick the private chat with the person to call. The Voice call phone button sits at the top of the chat. When the button is greyed out, hover it to see why.
Steps
Place a call
- Click Voice call. The first time, the browser asks for the microphone: choose Allow.
- The Call panel opens in the corner and shows Calling… while the other phone rings.
- When the other person picks up, the panel shows Connecting… and then starts counting.
- Compare the Verification code with the other person: seeing the same 4 emoji on both sides means the call is end-to-end encrypted.
- Click Mute / Unmute as needed. Switch microphones in Call settings. Click Minimize to keep working without hanging up.
- Click Hang up to end the call.
Answer a call
- When someone calls an account, an incoming-call card appears in every tab of the people allowed to use that account.
- Click the green button to answer, or the red one to decline.
- The first person to answer keeps the call; other tabs show Answered elsewhere.
When the account cannot answer yet (for example an HTTP proxy), the card shows the reason instead of the account name. A call nobody answers becomes Missed call. While the account is in a call, a second call is declined as busy.
Limits and safety
- Free accounts: no limit on calls.
- Safe accounts: at most 10 outgoing calls a day, at least 60 seconds apart.
- Answering, declining and hanging up never count.
- People who asked not to be contacted cannot be called.
- Each worker carries at most 4 calls at a time.
Result
The call appears as a line in the chat with its duration or why it ended (missed, declined, busy, could not connect…).
Check
Once the other person answers, ask them to say a few words and reply. The Quality bars in the call panel show the connection; audio lost, reconnecting means audio packets are being dropped.
When something goes wrong
| You see | It means | What to do |
|---|---|---|
| The proxy cannot carry call audio | The proxy is HTTP, or a SOCKS5 proxy has not confirmed UDP | Assign a SOCKS5 proxy with UDP, then click Recheck on the Proxies page |
| The account is not ready to call | Not logged in, paused, proxy failing or worker off | Fix the account / machine first |
| The worker needs an update | The worker is older than 1.0.49 | Wait for it to update itself |
| Calls work only in private chats | A group, channel, bot or yourself is open | Open the private chat with the person |
| This person asked not to be contacted | The person opted out | Do not call |
| The account is already in another call | One call per account | Hang up the other call first |
| The worker already carries its maximum calls | The machine has 4 calls | Try again later |
| Calling is switched off for now | The operators switched calls off system-wide | Wait until it is back |
| Stuck on Connecting…, then the call ends | Audio could not get through the proxy route | Check the proxy again; if it keeps failing, report it to support with the call time |
| The microphone does not open | The browser blocks the microphone or the page is not https |
Open the microphone help from the call panel, allow the microphone, call again |
Do it with the API or MCP
Use calls.readiness to see whether a chat can call, calls.start, calls.answer, calls.decline, calls.hangup, and calls.list / calls.get for history.
An AI assistant carries no audio: the audio plays in a browser tab with Ready for calls placed by an agent switched on (in Call settings, or on the AI connections page). The assistant always has to ask you before dialling. See Voice calls through an assistant.