A shared inbox fails in two directions: the same customer gets three answers, or gets none because everyone assumed someone else had it. Both come from the same missing thing — explicit ownership.
Assignment is not optional
Every conversation should have exactly one owner at any moment. Not a team, a person. Unowned conversations are the ones that go unanswered, and shared responsibility reliably becomes nobody's responsibility.
Automatic assignment on arrival — round-robin, by keyword, or by segment — beats a queue people pick from, because picking favours the easy conversations and leaves the difficult ones circling.
Statuses that mean something
- Unassigned — arrived, nobody owns it. Should be near zero during working hours.
- Open — owned, awaiting your reply. This is the working queue.
- Waiting on customer — you replied, ball in their court. Keep separate from Open or your queue lies to you.
- Snoozed — legitimately deferred, with a wake time.
- Closed — resolved.
The distinction between Open and Waiting on customer is the one that makes a queue count trustworthy. Without it, an inbox of 60 looks like a crisis when 50 are waiting on someone else.
Close conversations deliberately
Teams that never close anything lose the ability to see what is actually outstanding. If a conversation is resolved, close it. WhatsApp is a continuous thread, so it will reopen naturally when the customer writes again.
Internal notes, not internal messages
Everything typed in the composer reaches a real person's phone. Discussion between agents belongs in internal notes attached to the conversation. This sounds obvious and is nonetheless the most common embarrassing incident on shared inboxes — an internal remark sent to the customer.
Handovers at shift change
- Nothing is left Open under a departing agent's name.
- Anything unresolved is reassigned to a named person on the next shift.
- An internal note records where it got to and what is expected next.
- Anything promised a reply "today" is either delivered or the customer is told it will be tomorrow.
That last point matters disproportionately. A customer who is told about a delay is far more patient than one who is simply left waiting.
Watch the 24-hour window
You can reply freely for 24 hours after the customer's last message. After that you need a template. A conversation left overnight can drift past that boundary, at which point the natural reply becomes impossible and the agent has to fall back to a template that may not fit.
Surfacing time-remaining on each conversation, and prioritising those closest to expiry, prevents a whole class of awkward interactions.
Agree on tone
Six agents on one number will sound like six businesses unless someone decides otherwise. Write down whether you use the customer's first name, whether emoji are acceptable, how formal to be, and how to apologise. One page is enough, and it makes a shared number feel like a single coherent business.