One number, twelve people: a shared WhatsApp inbox that doesn't turn into chaos

Ritika Joshi runs operations at a modular-kitchen studio in Pune with twelve people: four designers who sell, three site coordinators, two in accounts, a front desk, a service technician and the owner. Until last month, customers messaged whichever of them they’d met. A carpenter’s measurement photos went to a designer on leave. A UPI payment screenshot sat on the owner’s phone for three days while accounts chased the customer for the same money.

So the studio moved to one business number that everyone answers from. By the end of the first week, two designers had replied to the same customer with different delivery dates, and nobody had replied to a warranty complaint about a sagging hinge because everyone assumed someone else had it.

One number solves the scattering. It doesn’t decide who answers. That part is a set of rules, and here are the ones we’d write down before the first chat arrives.

First, check the app can’t do it

The free WhatsApp Business app lets you use up to 4 linked devices plus the phone. Meta’s paid multi-agent option raises that to 10 devices and adds chat assignment, depending on your Meta Verified or Meta One subscription. Calls ring on every device only when 4 or fewer are linked.

For a team of five that shares a counter, the app with a few linked devices can be enough. For twelve people, it can’t, even on the paid tier. You need the WhatsApp Business Platform, which you reach through a provider, and a shared inbox on top of it. If any of the terms here are new, the WhatsApp Business glossary explains them. If you’re still deciding, our app vs Platform guide covers the trade-offs, and this piece on staff phones covers moving everyone onto one number.

Step 1: build teams around what customers ask

The mistake is copying the org chart. Customers don’t know or care that site coordination reports to the owner. They ask four kinds of question, so Ritika set up four teams:

Team	Takes	Who’s in it
New enquiries	”What does an L-shaped kitchen cost?”, showroom visits	4 designers
Projects	Measurements, drawings, installation dates	3 site coordinators
Accounts	Payment proofs, invoices, balance due	2 accounts staff
Service	Warranty, hinges, channels, after-sales visits	Technician + front desk

The owner sits in no team. She reads everything and owns nothing, which keeps her from becoming the bottleneck the move was meant to remove.

Four teams was right for twelve people. With three staff, you don’t need teams at all. With forty, you’ll want more, but start with fewer than you think and split a team only when its queue is visibly too long.

Step 2: write the assignment rule in two sentences

Every chat needs one owner, and everyone needs to know how the owner is chosen. There are two common patterns.

A dispatcher: one person (usually the front desk) reads each new chat and assigns it to a team or a person. It’s slower by a few minutes, but chats land in the right place and the dispatcher learns what customers actually ask.

First to claim: anyone on the team assigns a new chat to themselves before replying. It’s faster, and it works when team members are equally able to answer. It fails when two people claim at once or when the hard chats are quietly left for someone else.

For teams under about fifteen, we’d start with a dispatcher for new chats and first-to-claim inside each team. Ritika’s rule, pinned in the staff group:

“Front desk assigns every new chat to a team within 15 minutes during office hours. Inside a team, assign it to yourself before you type anything.”

Whatever you choose, the test is the same. At close of day, the Unassigned view should be empty. If it isn’t, the rule isn’t being followed or it’s the wrong rule.

Step 3: give everyone the views they need, and no more

A shared inbox with every chat in one list is just the old chaos on a bigger screen. Each person should open the inbox to a short list that’s theirs.

Ritika’s team uses five views:

• Mine: chats assigned to me. This is where each person starts the day.
• Unassigned: the front desk’s queue, and the owner’s end-of-day check.
• Team queue: one per team, for picking up work when someone is out.
• Mentions: where a colleague has pulled me into a chat.
• Waiting on us: open chats where the customer sent the last message.

The last one matters most. A chat where the customer spoke last is a chat where someone owes a reply, so sort it oldest first. If your inbox can’t filter on who spoke last, the unread count per team is a rough stand-in.

Step 4: notes for the team, replies for the customer

When a designer needs to check a price with the owner, the old habit was to ask in the staff WhatsApp group, with a screenshot of the customer’s message. That splits the conversation across two places and puts customer data in a group chat.

In a shared inbox, internal talk goes in a private note on the chat itself. The customer never sees it, and the next person to open the chat does. Mention the colleague you need, and they get a notification.

Two rules keep notes useful:

1. Any discount, credit or delivery date that isn’t standard goes in a note before it goes in a reply. “Owner approved 8% off on the tall unit, 12 Oct” is the line that settles an argument in March.
2. Read the composer before pressing send. Sending a note meant for a colleague to the customer (“she’s been difficult, go slow on the discount”) is the one inbox mistake customers remember.

Step 5: hand over with a note, not a shrug

Chats change hands for three reasons: a shift ends, someone goes on leave, or someone leaves the company. Each needs the same thing, a short note on the chat before it’s reassigned.

Ritika’s handover note has three lines:

Waiting on: customer’s approval of revised drawing (sent 3 Oct). Promised: installation slot in week of 20 Oct, not yet confirmed with the carpenter. Watch out: second payment is due before material order. Accounts knows.

Then reassign the chat to the new owner, and let the customer know by name. “Hi Mrs Joshi, I’m Rohan from Projects and I’ll be looking after your installation from here” costs nothing and stops her messaging the old designer’s personal number.

When someone resigns, do this for every open chat they own during their notice period, not on their last day.

Step 6: after hours, without a surprise bill

Customers write at 11 pm. That’s fine. The question is when you answer and what it costs.

So a message at 11 pm on Tuesday can be answered at 9.30 am on Wednesday, well inside the window. A message at 10 am on Saturday, answered on Monday, can’t: the window closed on Sunday morning, and your reply now has to be a template. If your office is shut on Sundays, have someone clear the Waiting-on-us view on Saturday evening.

Many teams set an automatic after-hours reply. If you do, keep it to one message that sets a real expectation (“We’re closed now and will reply by 10 am tomorrow”) and send it once per chat, not once per message. It’s a service message like any other, so it counts toward the 1,000 and costs money beyond them.

Step 7: a tag list one person owns

Tags go wrong in a predictable way. Within a month there are “warranty”, “Warranty”, “warrenty” and “service-warranty”, and none of them can be trusted in a report.

Ritika’s rules:

• One person (the front desk lead) owns the tag list. Others ask for new tags; they don’t create them.
• Lowercase, a short prefix for the kind of tag, a hyphen, no spaces: enq-kitchen, enq-wardrobe, svc-warranty, pay-proof-received, src-ad.
• Tags describe the customer’s need or where they came from. Don’t use tags for things the inbox already tracks, such as who owns the chat or whether it’s resolved.
• Twenty tags is plenty. Review the list on the first Monday of each month and delete any tag used fewer than five times.

And resolve chats when nothing is owed to the customer. A resolved chat reopens when the customer writes again. An inbox where nothing is ever resolved has no queue, just an archive.

What to check every Monday

Four numbers, pulled by hand from the inbox in about ten minutes:

Check	What good looks like	If it’s wrong
Chats unassigned at close of day	Zero, every day	The rule isn’t being followed, or the dispatcher is overloaded
Chats where the window closed with the customer waiting	Zero	Weekend or holiday cover is missing
Chats reopened within a week of being resolved	Falling	Chats are being resolved before the customer’s problem is fixed
Service messages sent per number this month	Known, compared to 1,000	Replies are being split into many short messages

The last one is new this month. Take an illustrative team that sends about 4,000 service replies a month from one number. After the first 1,000, the other 3,000 cost ₹0.115 each at Meta’s India rate, about ₹345 before GST. That’s small. But it doubles if every answer is sent as “Hi”, “One sec”, “Checking”, then the reply. Teach the team to send one complete message.

Start with Step 2. Write your assignment rule in two sentences today, pin it where the team will see it, and check the Unassigned view at 7 pm tonight.