The WhatsApp phone on the counter is costing you more than a plan would
Every business that grows past one person hits the same wall: the WhatsApp phone. Two people answer the same customer, or both assume the other did. Nobody can tell what was promised last week. And the person who happens to be holding it becomes the bottleneck for the whole business.
- Every agent signs in as themselves instead of sharing one device and one identity
- Each their own
- A conversation has an assignee and a status, so nobody answers twice
- Owned
- Internal notes and labels mean last week's promise is findable
- On the record
Who it's for
The three-to-ten person business where "the WhatsApp phone" lives on a counter, in a drawer, or in one person's pocket.
The worry it answers
"It works fine, we just talk to each other." It works until someone is off, until two people reply at once, or until a customer says they were promised something nobody can find.
What breaks, specifically
The failures are always the same four, and they get worse in exactly the order a business grows.
- Two people answer the same customer, contradicting each other
- Nobody answers, because each assumed the other had
- The person holding the phone becomes a bottleneck for everyone else
- There is no record of who said what, so a disputed promise cannot be checked
- When that person leaves, the conversation history and the relationships go with the handset
Side by side
| Shared handset | Shared inbox | |
|---|---|---|
| Who can answer | Whoever is holding it | Everyone, from their own login |
| Duplicate replies | Common | Prevented by assignment and status |
| Who handled it | Nobody knows | Recorded per conversation |
| Private team discussion | A separate chat somewhere else | Internal notes with mentions, in the conversation |
| Finding an old promise | Scroll and hope | Search, labels and notes |
| Response times | Not measured | Targets in working hours, with breach reporting |
| Someone leaves | History leaves with the phone | Access is revoked, history stays |
The part that is not about software
A shared inbox does not fix a team that has not agreed how to work. What it does is make the agreement enforceable: if the rule is "assign before you reply", the tool shows you when that did not happen. Statuses, assignment and response targets are the mechanism by which a verbal understanding becomes something you can actually check.
What you keep
You do not give up WhatsApp itself. It is the same number your customers already message, and with coexistence the handset can keep working during the transition. What changes is that the number stops living on one device.
Checked against the product on 2026-08-14. WhatsApp's own rules and charges are set by Meta and can change.
Good to know
Where this feature stops, in plain words — so nothing here surprises you after you buy.
- A shared inbox needs an active plan — any of them.
- Invited team members can enter the shared inbox only. Campaigns, contacts, templates, the flow builder and settings stay with the owner and admins.
- There are two roles, agent and admin. There is no custom permission matrix.
- The web inbox shows the last 7 days of conversations; the mobile app holds the longer history.
- Replies are still bound by WhatsApp's 24-hour window — outside it an approved template is required, whichever tool you use.
Frequently Asked Questions
Can several people really use one WhatsApp number?
Through the API, yes. Each teammate signs in with their own account and works the same inbox, with conversations carrying an assignee and a status.
Do we have to change our number?
No. Coexistence connects the number you already use, and your existing chats come across.
Can I see who replied to a customer?
Yes. Conversations carry an assignee, and internal notes record the team's side of the discussion without the customer seeing it.
What happens when someone leaves the team?
You revoke their access. The conversations, notes and history stay with the account rather than walking out with a handset.
Is this overkill for three people?
Three people sharing one phone is exactly where it starts to hurt. If one person answers everything, you probably do not need it yet.
Take WhatsApp off the counter
Same number, same customers — a team that can actually work it.
See plansThe features behind this
Each one in detail, including its limits.
- Shared InboxEvery conversation on the connected number, with an owner, a status, labels and internal notes. A helpdesk, not a chat mirror.
- Team, Hours & SLAInvite teammates with roles, define business hours with holidays, and measure first-response and resolution targets in working time.
- WhatsApp CoexistenceConnect the WhatsApp Business number you already use, through Meta's own onboarding. Your phone keeps working; automation runs alongside it.
- Mobile AppNot a cut-down viewer. Campaigns, the flow builder, team management and SLA policies are all there, and it works offline.
Other comparisons
The other decisions that come up at the same time.
- App vs APIWhat each one actually gives you, when the app is genuinely enough, and what changes the day you outgrow it.
- Official vs unofficialThe mechanical difference between an official connection and a device-link tool — and what it means for the number your business runs on.
- Build vs buyWhat integrating WhatsApp yourself really costs to maintain — and why moving does not have to mean rewriting.