Running one WhatsApp number across a whole sales team
Two agents answering the same customer, a lead nobody picked up, and no way to tell who promised what. All three come from the same root cause, and it is not a discipline problem.
Short answer. The free WhatsApp Business app's linked devices are not a shared inbox. Every device sees one identical view with no ownership, no assignment, no private notes and no record of who replied. Past two or three people that breaks. A real shared inbox requires the official WhatsApp Business API.
Why linked devices aren't a shared inbox
| Free Business app | Official API + shared inbox | |
|---|---|---|
| People on one number | A few linked devices | Your whole team |
| Assign a chat to one agent | No | Yes |
| See a chat is already taken | No | Yes |
| Internal notes on a conversation | No | Yes |
| Who replied, and when | Not recorded | Recorded |
| Broadcast to an opted-in list | 256 per list, saved contacts only | No cap of that kind |
The free app was built for a shop owner with a phone, and it is good at that. It has no concept of an "agent", so there is nothing to assign to and nothing to attribute. That is a design boundary, not a missing setting.
The three failures, and what causes each
Two agents answer the same customer
Both replies send. The customer gets two answers, sometimes with different prices or dates. Cause: no ownership. Fix: assignment — the conversation belongs to one person and everyone else can see it.
A lead sits unanswered because everyone assumed someone else had it
Cause: the same missing ownership, in the other direction. Fix: assignment plus an unassigned queue, so nothing sits in a state where it is technically everybody's.
Nobody knows what was promised
A customer arrives saying they were quoted a price. Cause: no attribution and no notes. Fix: a shared inbox that records who replied, with internal notes that the customer never sees. In real estate, clinics and anything with a deposit, this is the difference between a dispute and a record.
The other common setup: a number per salesperson
Very common in Dubai, and it creates a different problem. The relationship attaches to the individual, not the business. When that person leaves, the conversations, the history and often the customer go with them. You also cannot broadcast, report, or apply consistent templates across a set of personal numbers — and you have no visibility into what is being said in your company's name.
One business number with proper assignment keeps the relationship with the company while still letting individuals own their conversations.
What you need for this to work
- The official WhatsApp Business API on a number registered to your business — and make sure the WABA is in your name, not your provider's.
- A shared inbox with assignment, internal notes and an unassigned queue.
- Routing rules so new conversations land somewhere specific rather than nowhere.
- Templates for anything sent outside the 24-hour window, so agents are not blocked by the free-form rule.
- An answer for out-of-hours — an auto-reply that sets a real expectation, or a bot that handles the first exchange.
One caveat worth planning for: on an account we run, 11.7% of contacted customers replied, generating 1,392 inbound messages in two months. A shared inbox is only an asset if someone is staffed to answer it.
Adjoltz sets UAE teams up on one business number with a shared inbox, assignment and routing, on Meta's official Cloud API — with the number and WABA registered to your business. From $149/month, zero markup on Meta's rates.
Frequently asked questions
Can multiple people use one WhatsApp Business number?
Yes, but it depends on the product. The free app allows a few linked devices sharing one identical view, with no assignment, notes or attribution. The official API supports a proper shared inbox with assignment and an audit trail. Past two or three people, the API is the only workable option.
What happens if two agents reply to the same chat?
On the free app both replies send and the customer gets two answers, because linked devices share one inbox with no ownership. On a shared inbox built on the API, the conversation is assigned to one agent and others can see it is taken.
Should each salesperson have their own WhatsApp number?
It is common and it costs you. The relationship attaches to the individual, so when they leave the history leaves too, and you cannot broadcast, report or apply consistent templates across personal numbers.
Can I see which agent replied to a customer?
Only on the API with a shared inbox that records it. The free app has no concept of agents, so there is no attribution and no audit trail.