Team Inbox & Escalation
Every conversation has an owner.
The failure mode of a shared inbox is not too many messages. It is a message everyone can see and nobody owns.
The problem
Support on personal phones works until it does not. Nobody can see what a colleague promised, two people answer the same customer differently, and when someone leaves, their conversations leave with them. Moving to a shared inbox solves visibility but introduces a new problem: a queue everybody can see and nobody is responsible for. What makes it work is ownership — every conversation assigned, every escalation deliberate, and the full history attached to the customer rather than to a device.
How it works
Set it up once. Then leave it running.
-
Assign on arrival
New conversations are routed to an agent or a team, so there is always someone specific responsible for a reply.
-
Escalate with context
When something needs a specialist or a manager, it moves with the whole thread and any internal notes attached.
-
Close the loop
Conversations are resolved rather than abandoned, and the history stays against the contact for whoever picks up next time.
Message sequence
What your customer actually receives.
Every step is configurable — change the timing, drop a step, or keep it to a single message.
-
On arrival
Assigned
Thanks for getting in touch — Ravi from our team is picking this up now and will reply shortly.
-
On escalation
Handed over · Optional
I am bringing in a colleague who handles bulk orders — they have everything you have told me, so no need to repeat it.
-
On resolution
Closed
Glad that is sorted. This thread stays here, so just reply if anything else comes up.
Ownership beats visibility
Making a queue visible to everyone is necessary but not sufficient. A conversation that is everybody’s responsibility is nobody’s, and those are the ones that sit unanswered for a day while each agent assumes another has it.
Assignment is the fix, and it is worth being strict about.
Escalate the context, not just the customer
The thing that makes escalation feel bad to a customer is being asked to explain everything again. Moving the thread and the internal notes together removes that entirely, and it is the clearest advantage a shared inbox has over passing a phone across a room.
Conversations outlive people
Staff change. If the history of a customer relationship lives on a departing colleague’s personal phone, it leaves with them — along with whatever was promised. Keeping it against the contact is as much a continuity measure as an operational one.
Works with your store.
Order and cart data flows straight into the conversation.
-
HubSpot
Push contacts and deals to your CRM.
Frequently asked questions
How do we stop two agents replying to the same customer?
Conversations are assigned to one owner, and agents can see when someone else is already typing a reply. That combination removes most duplicate responses, which are the main embarrassment of a shared inbox.
What happens to conversations when an agent leaves?
They stay with the contact rather than on an individual's phone, so they can be reassigned with the full history intact. This is the main reason to move off personal WhatsApp accounts.
Can we add internal notes a customer cannot see?
Yes. Notes and tags are internal to the team and never sent to the customer, which is what lets context travel with an escalation instead of being explained verbally.
How to set this up
The guides and articles behind this use case.
Guide
Assigning and Managing Conversations
How to assign a conversation to an agent, reassign it, and use status and filters so nothing is left unanswered.
Product
Shared Inbox
Give every agent a shared view of every WhatsApp conversation, with assignments, internal notes and status tracking built in.
Guide
Inviting and Managing Team Members
Invite agents to your organisation and control what each of them can access.
Put this to work on your store.
Seven days free. No credit card. Live in minutes.