Most growing businesses in India end up in the same place: customers message one WhatsApp number, and that one number now has to serve sales, support, accounts and three different service lines. The question stops being "how do we reply on WhatsApp?" and becomes "who replies to which chat — and how does everyone else know?"
This guide covers how to run a WhatsApp team inbox properly: what you need, how to route chats to the right department, how to hand them over without losing context, and the WhatsApp rules you have to design around.
The short answer
To let several people answer customers from one WhatsApp number, move the number to the WhatsApp Business Platform (Cloud API) and connect it to a WhatsApp CRM that supports chat assignment. Then:
- Give each team member their own login.
- Route each new chat to a department automatically, based on what the customer asks for.
- Let each person see only their own chats plus unassigned ones.
- Let anyone hand a chat to another department, and record who did it.
- Put the inbox on everyone's phone, with alerts only for the chats they own.
The rest of this article explains each step and the traps to avoid.
Why a shared phone stops working
The WhatsApp Business app is built around one phone. Linked devices help a little, but everyone still sees every chat, nobody owns anything, and there is no record of who said what. As soon as a second department joins, three problems appear:
- Missed replies. Everyone assumes someone else is answering.
- Double replies. Two people answer the same customer, sometimes with different prices.
- No accountability. When a customer says "but your team promised…", there is no way to see who.
A team inbox fixes this by giving every chat an owner.
Step 1: Move to the WhatsApp Business Platform
The WhatsApp Business Platform (often called the WhatsApp Business API or Cloud API) is Meta's way for businesses to send and receive WhatsApp messages from software instead of a phone. Your number then lives in a CRM, and any number of team members can work on it from their own accounts.
Two things change when you make this move:
- Your number is no longer tied to a phone. Nobody's personal WhatsApp is involved.
- You follow the platform's messaging rules, most importantly the 24-hour window (covered below) and approved message templates.
Step 2: Route new chats to the right department
Routing is where most setups fail. If someone has to assign every new chat by hand, the inbox becomes a queue that only one person manages.
The reliable way is to let the customer choose, then let automation assign:
- Send new customers a welcome message with buttons or a list: Studio bookings, School software, Accounts, and so on.
- When the customer taps an option, tag the chat (for example,
New Studio). - Add one automation per department: when the tag "New Studio" is added, assign the conversation to the Studio lead.
Now a new enquiry reaches the right person within seconds, with no one in the middle.
What about chats nobody claims?
Some chats will always arrive unassigned: a customer who ignores the buttons, or a message outside working hours. Treat unassigned chats as a shared pool:
- Everyone can see them.
- Decide who gets alerted: every agent, only admins, or nobody.
- The first person who replies becomes the owner. This one rule, often called claim on reply, is what prevents two people answering the same customer.
Step 3: Show each person only their own chats
Once chats have owners, visibility should follow ownership:
| Role | Sees |
|---|---|
| Agent | Chats assigned to them, plus unassigned chats |
| Admin / Owner | Every chat |
This keeps each department focused and keeps customer conversations private between teams that have no reason to read them. Make sure the rule is enforced by the system itself, not just hidden in the interface. Otherwise anyone with a direct link can still open another department's chat.
Step 4: Hand over chats with a record
Customers do not stay in one department. A studio client books a shoot, then asks about an invoice; a parent asks about admissions, then about the school bus. The chat needs to move, and the move needs to be visible.
A good handoff has three parts:
- Anyone who can see the chat can move it, not only admins. If a chat lands with the wrong department, they fix it themselves.
- The new owner is alerted immediately, ideally on their phone.
- The chat keeps a record such as "Manas handed this chat to Mehaveen · 4:40 pm", so anyone reading later understands what happened.
What if a customer asks two departments at once?
A customer has one WhatsApp conversation with your business, and it can only have one owner at a time. Decide your rule upfront:
- Latest enquiry wins: the chat moves to the department the customer just asked for. This matches what the customer wants now, but the previous department loses sight of it.
- First owner keeps it: the chat stays put, and the owner hands it over when needed. Nothing moves unexpectedly, but the customer may wait.
Whichever you choose, the handoff record means nobody loses track of the history.
Step 5: Put the inbox on everyone's phone
A team inbox that lives only in a browser tab works for people at desks. Studio crews, field technicians, teachers and doctors are rarely at one. For them, the inbox has to be on the phone, and the alerts have to be selective:
- Alerts only for your own chats, plus unassigned ones if your team handles those.
- Quiet hours so the phone stays silent at night while alerts still collect.
- Lock-screen privacy, so customers' messages are not shown to anyone glancing at a phone.
The WhatsApp 24-hour rule
On the WhatsApp Business Platform, you can reply freely for 24 hours after the customer's last message. After that, you can only send an approved template message until the customer writes again.
Design around it:
- Show your team how much of the window is left on every chat.
- Handle urgent chats before the window closes.
- Prepare templates for common follow-ups (payment reminders, booking confirmations) so reopening a conversation is quick.
Show who replied
When several people reply from one number, the customer sees only the business. Internally, though, every reply should show which team member sent it. It settles "who told the customer that?" in seconds, it helps new team members learn from each other, and it makes handoffs smoother because the next person can see exactly what was promised.
A checklist for your WhatsApp team inbox
- Number on the WhatsApp Business Platform, connected to a CRM
- One login per person, with roles (owner, admin, agent)
- Welcome message that asks customers what they need
- One automation per department that assigns tagged chats
- Agents see their own and unassigned chats; admins see all
- First reply claims an unassigned chat
- Anyone can hand a chat over; the new owner is alerted; the chat records it
- Mobile app with alerts only for your own chats, quiet hours and lock-screen privacy
- The 24-hour window visible on every chat, with templates ready
- Every reply shows who sent it
How Pocket CRM does this
We built Pocket CRM to put this whole workflow on Android phones. It connects to a WhatsApp CRM and gives each team member alerts for their own chats, full conversations with photos, videos, voice notes and documents, replies within the 24-hour window, department-wise visibility, claim on reply, and two-tap handoffs recorded in the chat. It is free to download and live on Google Play. Message us on WhatsApp to set it up for your business.
Frequently asked questions
Can several people use the same WhatsApp business number?
Yes, on the WhatsApp Business Platform. The number is connected to a CRM, and each team member works from their own account.
Can I assign WhatsApp chats to specific team members?
Yes, with a WhatsApp CRM that supports assignment. Chats can be assigned by hand, automatically by department, or claimed by the first person who replies.
Do customers see which team member replied?
No. Customers see your business name. Internally, a good team inbox labels every reply with the team member who sent it.
What happens after 24 hours without a customer message?
You can no longer send free-form replies. You send an approved template message instead, and normal replies resume once the customer writes back.