Telegram Shared Inbox: How to Give a Team Access Without Sharing the Password

2026-11-06 · 5 min

How a Telegram shared inbox works for teams: per-number permissions, private vs group chats, assigned-only access, data masking and safe offboarding.

Telegram has no built-in shared inbox: one account belongs to one person, and the only way to "share" it natively is to log in on someone else's device, which hands over everything. A Telegram shared inbox solves this by connecting the account to a web panel once, then giving each teammate exactly the access they need — which numbers they see, whether they see private chats or only groups, whether they can reply, and whether customer phone numbers are visible — while the Telegram login itself never leaves the company.

Why "just log in on everyone's laptop" breaks down

Most teams start by logging the business number into Telegram Desktop on three or four computers. It works for a week. Then the problems show up:

Everyone sees everything. Telegram has no permissions inside an account. A new support agent can read the founder's private chats, the saved messages and every group.
Nobody owns a chat. Two people answer the same customer, or nobody does, because each assumes the other will.
Offboarding is risky. When someone leaves, you have to find and terminate their session in Settings → Devices. Telegram also blocks a freshly logged-in session from terminating other sessions for 24 hours (FRESH_RESET_AUTHORISATION_FORBIDDEN), so the timing matters.
The 2FA password spreads. Every new device login needs the code and, if set, the cloud password. Once five people know it, it is no longer a secret.

Most "Telegram shared inbox" tools in the search results (Zoho TeamInbox, Tidio, CallHippo and similar) connect a bot, not your personal number. That is fine for inbound support, but a bot cannot start conversations and customers who already talk to your number will not move to it. If your business lives on real Telegram numbers, you need a shared inbox that connects user accounts. See bot vs user account for the full comparison.

What a shared inbox should control

Here is the permission model we use in Telegramte, and it is a good checklist whatever tool you pick.

Roles

Role	Typical person	What they can do
Owner	Founder, account holder	Full control of the workspace, including billing
Admin	Team lead	Manage members, numbers and settings
Agent	Sales or support rep	Work in the chats they have been given access to

Per-number access

Roles are not enough when you run several numbers. A Turkish-market sales number and a VIP support number need different people. For every member and every number you decide:

Can send — reply and write from this number, or read only (useful for trainees and supervisors).
See private chats — one-to-one conversations with customers.
See groups — groups and channels the number is in.
Only chats assigned to them — the member sees just the conversations where they are the assignee, not the whole number.

A common setup: agents get can send + private chats + only assigned, the team lead gets the full number, and a marketing person gets groups only for a number that runs communities.

Masking customer data

For members without permission, Telegramte masks the customer's phone number and username. The agent can still read and answer the chat, but cannot copy a customer list out of the panel. This matters for outsourced support and for any team where staff turnover is normal.

Accountability

Audit log: who connected a number, changed permissions, or exported data.
Two-factor (TOTP) login for the panel itself, so a stolen panel password is not enough.
First response time reports by number and by member, so you see who is actually answering.

How work flows in a shared inbox

All connected numbers land in one inbox; filter by number, label or stage.
Unassigned chats are handed out — every chat gets an assignee.
Agents leave internal notes (invisible to the customer) so the next person has context.
Templates and quick replies keep answers consistent across the team.
Anything that needs follow-up becomes a reminder or a ticket with status, priority and a due date.

Offboarding without changing the Telegram password

Because the Telegram session lives in the panel, not on employees' devices, offboarding is a panel action:

Disable the member (or switch off their per-number access). They lose access immediately; the number keeps working for everyone else.
Their chats are still there with full history and notes. Reassign them to someone else.
Check the audit log for recent activity such as CSV exports or member changes.
Once in a while, open Settings → Devices on the phone that holds the SIM and terminate any session you don't recognise.

No new SIM, no password reset, no customer notices anything.

Getting started

Connect a number by QR code, by phone number and login code (plus 2FA password if you have one), or by importing a session file of your own account. Then invite your team and set per-number access. There is a free trial without a card; plans are €29 (Basic) and €39 (Pro) per user per month — see pricing.