A WhatsApp shared team inbox that works like a helpdesk
Several agents, one WhatsApp Business number, and no more guessing who is replying to whom. Assign conversations, keep private notes, raise tickets for the work that drags on, and see what your team actually handled.
The problem
One number, five people, no idea who replied
Support on WhatsApp starts simply. One phone, one person, and everything fits in their head. Then a second person joins, and the phone starts moving between desks. Then a third, and you are linking extra devices so everyone can see the same messages — which also means everyone sees every message, nobody owns any of them, and two agents cheerfully answer the same customer within a minute of each other.
The escalations are worse. Someone screenshots a conversation into a staff group, three colleagues weigh in, a decision gets made, and none of it is attached to the customer's thread. A week later the customer asks what was agreed and nobody can find it. What was promised, by whom, and whether it ever happened all live in somebody's memory.
The fix is not more discipline. It is moving the number onto the WhatsApp Business API, where a conversation can be assigned to a person, annotated privately, escalated into something trackable, and closed on purpose rather than by scrolling past it.
What you get
A shared inbox built for more than one person
Multi-agent WhatsApp only works when ownership is explicit. Every part of the inbox is built around answering one question quickly: whose job is this right now?
One inbox, many agents
Every conversation on your WhatsApp Business number lands in a single inbox your whole team works from, instead of on one phone that somebody has to be holding.
Assignment and ownership
Assign a conversation to a specific agent so it has one clear owner. Reassign it when the shift changes or when it needs someone more senior.
Teams and departments
Group agents into teams and departments so sales, support and billing each work their own queue rather than everybody wading through everything.
Private internal notes
Leave notes on a conversation that the customer never sees — what was promised, what you already checked, what the next person should know.
Filters that find the thing
Narrow the inbox by agent, chat status, contact status, contact group, archived state or a date range, or just search for what the customer said.
Archive when it is done
Archive a finished conversation so it leaves the active queue. Nothing is deleted — filter for archived chats whenever you need the history back.
Assign work automatically instead of by hand
Manual assignment works until the day it does not — usually the day volume doubles and the person who normally distributes chats is on leave. Auto-assignment settings let you configure the handover once so incoming conversations arrive with an owner already attached, instead of waiting for somebody to claim them. Your team leads keep the ability to reassign anything by hand when a case needs different eyes.
Canned replies, business hours and away messages
Most support volume is not novel. Save the answers you type twenty times a day as basic replies so agents send them in one keystroke and the wording stays consistent across the team. Set your business hours and an away message so people who write at midnight get a straight answer about when you will reply — which also stops your first-response numbers being quietly ruined by the overnight queue.
Forward a message into the right conversation
Customers send things to the wrong place constantly: the photo of the damaged item goes to sales, the order ID goes to the account manager. You can forward a message from one chat into another, so the evidence ends up in the thread where the work is actually happening rather than being described second-hand.
Helpdesk
Ticketing for the things a chat cannot close
Some issues are answered in two messages. Others need a refund approving, a part shipping or a bug fixing, and they will outlive the conversation that started them. A WhatsApp ticketing system gives that work somewhere to live.
Raise a ticket
Create a ticket for the issues that will not close inside one conversation: a refund waiting on finance, a fault waiting on an engineer, a query that needs a decision.
Ticket categories
Sort tickets into your own categories so you can see what kind of work keeps arriving, not just how much of it there is.
Statuses that move
Update a ticket's status as it progresses, so an issue that is genuinely being worked on looks different from one nobody has touched.
Comments on the thread
Colleagues add comments to the ticket itself. The working-out stays attached to the issue rather than scattered across a staff WhatsApp group.
Typical setup
How a support desk usually comes together
Roughly the order we would suggest. It takes an afternoon, and the first two steps are the ones people regret rushing.
Connect the number and add your people
Bring your business number onto the official WhatsApp Business API and invite your agents as users. From that point the number belongs to the platform, not to a handset in someone's drawer.
Create departments before you create habits
Set up the departments you actually run — sales, support, billing — and build teams inside them. Doing this on day one is far easier than untangling a single shared queue six months later.
Set business hours and an honest away message
Configure your business hours and write an away message that tells people something true: when you will be back and reply. A vague 'we will get back to you shortly' at 11pm helps nobody.
Turn on auto-assignment
Switch on automatic assignment so a new conversation arrives with an owner already attached, rather than sitting in a queue while everyone assumes a colleague has picked it up.
Write the canned replies you already retype daily
Save your standard answers as basic replies — opening hours, where the order tracking link lives, what documents you need. Agents send them in a keystroke and the wording stays consistent.
Agree what becomes a ticket
Decide, in writing, which conversations get escalated into a ticket and which stay in the inbox. Teams that skip this step end up with either no tickets at all or a ticket for every hello.
Reporting
Know what the desk is carrying
Conversation statistics tell you how much is open, how much has been dealt with and how that has moved over a period you choose. Per-agent chat counts tell you how the load is actually distributed, which is usually less even than anyone expects — one person quietly absorbing the difficult cases is a pattern you want to see before they burn out.
None of it replaces reading conversations. But it does turn "support feels busy" into something you can plan a rota around, and it makes the case for another hire in numbers rather than adjectives.
Pair the inbox with campaign reporting and you can see both sides of the number: what you sent out, and what came back for your team to answer.
Where this fits with the rest of ChatSetu
An inbox is only as useful as what sits behind it. Contact history, custom fields and tags come from the contact records your team can see mid-conversation, so an agent opening a chat is not starting from nothing.
In front of the inbox, no-code flows and follow-ups handle the repetitive openings, and an AI assistant trained on your own documents can answer the routine questions and draft replies for agents to check. If you also run Instagram DMs, those conversations reach the same team rather than a second browser tab.
Worth reading before you commit to a setup: how to automate WhatsApp customer support and the differences between the Business app and the API, which is the decision most teams have to make first.
FAQ
Frequently asked questions
The questions teams ask before they move their support number onto the API.
How many agents can work on one WhatsApp number?
On the WhatsApp Business app a number is tied to a phone and a small number of linked devices. On the WhatsApp Business API the number lives on the platform instead, so adding another agent means adding another user account — nobody has to pass a handset around or share a login.
What is the difference between a chat and a ticket?
A chat is the live conversation with the customer and closes when the conversation is resolved. A ticket is for work that outlives the conversation — a refund waiting on finance, a fault waiting on an engineer — and carries its own category, status and internal comments so it can be tracked to completion.
Can customers see internal notes and ticket comments?
No. Notes on a conversation and comments on a ticket are internal to your team. Only messages your agents actually send go out to the customer on WhatsApp.
Does WhatsApp's 24-hour window affect a shared inbox?
Yes, and it is worth building your rota around it. Meta's WhatsApp Business Platform lets you reply freely within 24 hours of the customer's last message; once that service window closes you need an approved message template to reopen the conversation. Teams that answer quickly stay inside the free-form window far more often.
Can I keep using the WhatsApp Business app on the same number?
No. A phone number can be registered to the WhatsApp Business app or to the WhatsApp Business API, but not to both at once. Moving to the API migrates the number across, which is why it is worth reading up on the differences before you switch.
Is ChatSetu AI's team inbox available now?
Yes. The shared inbox, departments and ticketing described here are live in the platform today. Get in touch and we will connect your WhatsApp number for you, including migrating one that is currently on the WhatsApp Business app.
Give your support team one place to work
Tell us what you need and we'll set it up with you, or message us on WhatsApp and we'll help you get your team set up.