A shared inbox or employees' personal numbers? The decision that sets the quality of WhatsApp customer service
A plain comparison between a WhatsApp number per employee and a shared inbox on one number: who owns the customer, what can and cannot be measured, bot, routing and permissions, the cost of moving, and when a personal number is enough.
The ArabyBot teamOfficial Meta partner · written from our own platform dataOn this page 5
The short answer
One business number and a shared inbox, always, once more than one person replies. A personal number leaves with the employee, with their customers and conversations; nobody knows how many messages sit unanswered; and no bot can answer a personal number. A shared inbox gives every conversation an owner, every role its permissions, and measures reply time — this page compares the two line by line and says when a personal number is acceptable.
Also asked as: «الموظفين بيردوا من ارقامهم الشخصية» · «صندوق وارد مشترك للفريق واتساب» · «كيف أوقف الرد من جوالات الموظفين» · «رقم واحد للشركة بدل أرقام الموظفين»
The first question: who owns the customer?
On a personal number the employee owns the customer: their number is saved under their name, the conversation is on their phone, and when they leave — and they do leave — a relationship the business built and paid for in ads leaves with them. On a shared number the business owns the customer: one number that never changes, every conversation in a record that outlives every employee, and whoever takes the thread tomorrow reads what was said yesterday.
The comparison, line by line
| Item | A personal number per agent | One number, shared inbox |
|---|---|---|
| Who owns the conversations | The agent | The business |
| How many messages are unanswered right now? | Nobody knows | A number on the screen |
| First-reply time | Not measured | Measured per agent |
| An owner per conversation | — | ✓ |
| A bot answering outside hours | — | ✓ |
| Permissions by role | — | ✓ |
| Broadcasts on approved templates | Ban risk | ✓ |
| Automatic routing | — | ✓ |
| Instagram and Messenger on the same screen | — | ✓ |
| Works from a phone | ✓ | ✓ |
| Monthly cost | Nothing | The platform subscription |
What cannot be measured cannot be fixed
The real problem with personal numbers is not chaos but blindness. A manager asking "how many customers went unanswered yesterday?" across five phones gets five answers and can verify none of them. In a shared inbox the same question is one number, with who was late and why. The difference between the two is the difference between managing a team and taking its word.
Bulk messages from a personal number are the commonest reason numbers get banned in this market. A shared number on the official API broadcasts on approved templates to people who opted in — the difference between a campaign and a locked number. Details in the ban guide.
Moving in four steps, without losing a customer
- Choose the number that stays
The advertised business number, or the busiest agent's number if customers know it — moved to the official API in coexistence mode, keeping its chats. The number sits under the company in Meta Business Manager, not under an employee.
- Create an account per agent and set permissions
Who sees what, who replies, who assigns, who exports. The supervisor sees everything. A new agent is added in a minute; a leaver is closed the same moment.
- Tell customers once
One message from the old numbers: "from today we are on [new number], please save it". Then an auto-reply on the old ones redirects for a month. Do not shut the old ones off abruptly.
- Switch on the bot and the numbers from day one
The agent answers the recurring and the off-hours, and the inbox measures reply time and the unanswered. Review both numbers weekly with the team — the first week sets the habit.
Frequently asked questions
Can several employees reply from one WhatsApp number?
Yes, through the WhatsApp Business API: one number, conversations in a shared inbox on web and app, and an account with permissions per agent. The free WhatsApp Business app allows a few linked devices with no routing, no permissions and no bot — that is its limit.
What happens to the customers of an agent who left?
On a personal number: they leave with them, literally; the conversations are on their phone and the customer knows their number. On a shared number: their threads are reassigned to the team in one tap with the full history, their account is closed at the same moment, and the customer notices nothing.
Does every agent see every conversation?
As you decide. Permissions set who sees a channel, who replies, who assigns and who exports. A sales agent sees WhatsApp and not Facebook comments if you wish; the supervisor sees everything and reads the numbers.
And the employee working from their phone in the field?
The same app carries the whole inbox: they reply from their phone on the shared number, under their own account, and the thread stays in the record. Mobility does not require a personal number.
When is a personal number acceptable?
When the responder is one person who will not change, the volume is small, and there is no need for a bot or measurement. A shop owner answering ten messages a day personally does not need an inbox. The day a second person replies is the day to move.
How we write these guides Figures come from our platform and Meta's actual invoices, dated with their sample; we describe what works today, not what we plan, and say what we do not do and when someone else is the better choice. Reviewed by the ArabyBot team on 23 September 2026.
Read next
One number for your whole team — try it on our agent first
The agent that will answer your customers is the one answering you now: ask it from the chat button here or on WhatsApp. Your account is free with no credit card, and the free trial on your own number or page is activated after you contact our team on customer-service WhatsApp.