A shared WhatsApp inbox, without sharing a phone
Every growing business hits the same wall: one WhatsApp number, several people who need to answer it, and a phone that can only be in one pocket. The usual workarounds all break in the same place. Here is what actually has to happen.
Every business that grows on WhatsApp hits the same wall at the same size. One number that customers know, three or four people who need to answer it, and a phone that can only be in one pocket at a time.
What follows is a tour of the workarounds, why each one fails, and what a system has to get right to actually solve it.
The four workarounds, and how each ends
Passing the phone around
Works for two people in one room. Fails the first time somebody takes it home, and takes the entire customer history with them.
WhatsApp Web on four laptops
Better, and the most common answer. Everybody sees everything, which sounds like the goal and is the problem: every message interrupts four people, two of them start typing the same reply, and the customer gets both. There is no record of who handled what and no way to hand a conversation over other than shouting across the room.
A WhatsApp group that the team forwards into
Now the conversation and the discussion about the conversation are in different places, and replies have to be copied back by hand. Something always gets missed, usually the thing somebody promised to check.
WhatsApp Business with labels
Genuinely useful for one person. It is a single-device product with a labelling system, not a shared inbox, and no amount of labelling makes a second person able to answer.
All four fail in the same place: WhatsApp has an idea of an account, and no idea of a team. Nothing you arrange on top of the app supplies the missing concept — assignment.
What a real shared inbox has to do
Reach everybody, then stop
A new message should reach everyone who might answer it. The moment one of them does, the others should stop receiving it — that is what assignment means, and a system that keeps ringing the whole team after somebody has picked up is a group chat with extra steps.
The others do need to be told. Silence after a claim reads exactly like a message nobody answered, and somebody will double-check it. “Sone is handling this” costs one line and saves the duplicate reply.
Survive two people answering at once
On a busy morning this is not an edge case, it is Tuesday. Two people open the same message and both start typing. Exactly one of them must end up owning it, decided at the moment the first reply lands rather than by who finished typing first.
Let a conversation be handed over
Someone takes a chat, discovers it is about a refund, and needs the person who handles refunds. Without a transfer the options are to muddle through or to abandon it, and a transfer that only exists as a message to a colleague is not a transfer — the customer is still waiting on somebody who has mentally moved on.
Two details make the difference. The customer should be told — being passed between people invisibly is how a conversation gets repeated from the start. And the person receiving it needs enough to pick it up cold.
Name who is speaking
A shop where replies come from a named colleague is a different experience from one where they arrive from the shop itself. It also matters internally: when a customer says “somebody told me it would arrive Tuesday”, you want to know who.
Work where the team already is
This is the one that decides adoption. A shared inbox that requires everybody to sit in a web console is a shared inbox your team routes around by opening WhatsApp Web anyway — and then you have two systems disagreeing.
The systems that survive contact with a real team let people answer from their own WhatsApp, on the phone already in their hand, and do the routing invisibly behind that.
What to look for
| Question | Why it matters |
|---|---|
| Does the team answer from their own phones? | Decides whether it is adopted or worked around |
| Does a claim stop the others being notified? | Otherwise it is a group chat |
| Can two people claim the same chat? | A race on a busy morning, not an edge case |
| Can a chat be transferred, and is the customer told? | Refunds, escalations, shift changes |
| Does the customer see who is speaking? | The difference between a shop and a switchboard |
| Do groups work as recipients? | Most teams already have the group |
| What happens when somebody leaves? | Their open chats must not leave with them |
How WaveSenda does it
A widget message, or a customer message, goes to everybody on the rota — people or a team group, whichever you list. The first reply claims it, everyone else stops receiving it and is told who took it, and replies carry that person’s name to the customer.
Handing over is /transfer Ada in the reply, typed on the phone the operator is already holding; /take grabs a chat somebody left. Both sides are told. Removing somebody from the rota returns their open chats to it rather than letting the conversations leave with them.
It pairs with the website widget, which is where most of these conversations start.
Common questions
Can several people use one WhatsApp number at the same time?
Not in the app beyond WhatsApp Web sessions on the same account, which show everyone everything and assign nothing. Answering as a team requires software in front of the number that decides who handles what — WhatsApp itself has no concept of assignment.
Does a shared inbox need the official Business API?
No. The API is one route and it removes the number from the app entirely, meaning nobody answers from a handset. A shared inbox over a connected number keeps people on their own phones, which is usually what makes a team actually use it.
What stops two people replying to the same customer?
Assignment on first reply. The first person to answer owns the conversation and the others stop receiving it. Without that you have a group chat, and duplicate replies are guaranteed rather than unlikely.
Can a WhatsApp group be one of the recipients?
It should be able to be. Most teams already have a group, and WhatsApp names the participant who sent a group message — so somebody answering from the team group can still be identified and still claim the chat as themselves.
What happens to open chats when somebody leaves the team?
They should return to the rota so anybody can pick them up. A conversation owned by an account that no longer exists is a customer waiting on nobody, and it is the failure mode nobody tests for until it happens.