WhatsApp Business Multiple Users: How to Share One Number With Your Team

Short answer: Yes, multiple people can use one WhatsApp Business account, but only in a limited way. The free WhatsApp Business app supports one primary phone plus up to four linked devices, and every linked device sees every conversation. There are no agent seats, no chat assignment, and no roles. For a real team inbox, where conversations are routed to owners and nothing gets answered twice, you need the WhatsApp Business Platform, Meta's Cloud API.

This is the question every growing business hits about six months into using WhatsApp seriously. One person started answering customers from their phone. Now three people need to, the owner wants visibility, and somebody just replied to a customer who had already been helped an hour earlier.

How many devices can use one WhatsApp Business account?

The WhatsApp Business app allows one primary phone and up to four additional linked devices, so five in total. Linked devices can be a computer through WhatsApp Web or the desktop app, a tablet, or a second phone. They work independently, meaning the primary phone does not need to stay online for a linked device to send and receive.

That sounds like a team solution until you use it. Every linked device sees the same single inbox. There is no way to say this conversation belongs to Maria and that one belongs to Chris. There is no read or unread state per person, no internal notes, and no record of who said what to whom. Two people can start typing a reply to the same customer at the same time, and neither knows the other is doing it.

It also means access is all or nothing. A new hire who links a device can scroll the entire message history with every customer. When they leave, you had better remember to unlink them.

Can two people use the same WhatsApp Business number?

Two people can use the same number by linking a second device to the account. Both will see the full inbox and both can reply. What they cannot do is work as a team: no assignment, no routing rules, no visibility into who handled which conversation. For two people who sit near each other and talk, that is often fine. For anything larger, it breaks down fast.

The other constraint is that a phone number can only live in one place. A number registered to the WhatsApp Business app cannot simultaneously run on the API, and once you move a number to the Cloud API, its messages stop appearing in the app entirely. Plan that migration deliberately rather than discovering it on a Monday morning.

App versus API: what changes for a team

What is a WhatsApp shared inbox?

A shared inbox is a single view of one WhatsApp business number that a whole team works from, where each conversation has an owner. An incoming message gets routed to a person or a queue, that person replies, teammates can leave internal notes, and a manager can see response times and who is handling what. It is the same idea as a shared email inbox for support, applied to WhatsApp.

Shared inboxes run on the Cloud API rather than the app, because the app has no concept of separate users. When a message arrives, Meta sends it to a webhook, your platform stores it, assigns it, and shows it to the right agent. Replies go back out through the API on the same business number, so the customer sees one consistent identity no matter who answers.

Teams that already run structured support operations for email and phone will recognize the pattern immediately, because a WhatsApp shared inbox is simply that discipline extended to the channel customers actually prefer.

Can I assign WhatsApp chats to different agents?

Not in the free app. Assignment requires the WhatsApp Business Platform. Once your number runs on the Cloud API through a platform like WaBulkSend, you can auto-assign by keyword, by business hours, by round robin, or by which rep already owns the contact in your CRM. Anything an automation cannot resolve gets handed to a human with the full conversation history attached.

That last part matters more than the routing itself. The reason customers hate being passed around is repeating themselves. When the thread and the CRM record travel with the assignment, the next person opens the conversation already knowing what happened.

How do I add users to WhatsApp Business?

In the free app, open WhatsApp Business on the primary phone, go to Settings, choose Linked Devices, tap Link a Device, and scan the QR code shown on the other device's screen. Repeat for up to four devices. There is nothing else to configure, because there are no user accounts to create.

On the API, you do not add users to WhatsApp. You add them to the platform that holds your inbox. Each agent gets their own login, their own permissions, and their own assigned conversations, while WhatsApp only ever sees one business number. That separation is exactly what lets you scale past five people without anyone sharing a phone.

The migration path most teams actually take

Very few businesses start on the API. The realistic sequence looks like this. You begin on the free app with one phone. You link a laptop so someone can type properly. You add a second person, then a third, and the cracks appear: duplicate replies, missed messages overnight, no idea which rep promised what.

At that point you register a dedicated number on the Cloud API. Note the word dedicated. Do not migrate the number your staff answer by hand or the one printed on your storefront window, because once it moves to the API it leaves the app. Set up the WhatsApp Business Account, verify the business in Meta Business Manager, and connect the number to a shared inbox. Then wire it into your CRM so the conversation lands on the contact record and your automations can act on it.

Verification is worth doing early. An unverified business is capped at 250 unique customers per rolling 24 hours, which is a ceiling you will hit the first time you send anything at scale. Verification lifts it.

What this costs

The Cloud API itself is free to call. Since Meta moved to per-message pricing on July 1, 2025, you pay when a template message is delivered, priced by the template's category. Replies you send inside the 24-hour customer service window, after a customer messages you first, cost nothing at all. For a support team, which spends most of its time answering inbound messages, the running cost of a shared inbox is close to zero.

One US-specific point. Meta paused delivery of marketing category template messages to US phone numbers on April 1, 2025, and it has not resumed. Utility templates for orders, appointments, and quotes still deliver, authentication templates still deliver, and inbound conversations are unaffected. A shared inbox is about answering customers, so the pause does not get in your way. See our WhatsApp Business API pricing breakdown for the full picture.

Where to go next

If your problem is simply that two people need to type, link a device and move on. If your problem is that nobody knows who owns a conversation, you have outgrown the app, and no amount of linked devices will fix it.

The step that pays for itself is connecting the number to your CRM, because a shared inbox without a customer record is just a nicer chat window. Our guide to WhatsApp CRM integration walks through the webhook, the credentials, and what actually syncs. If you run HubSpot, the HubSpot WhatsApp integration page covers the native channel, the tier it requires, and the 1,000 template per month allowance that catches teams by surprise. And if you are still deciding between the app and the platform, start with the WhatsApp Business API.