How to Use One WhatsApp Number Across a Team (Without Passing a Phone Around)

The blocker is simple: a WhatsApp account is tied to one phone number, and that number is tied to one primary device. Everything people try — linked devices, shared phones, passed-around logins — is a workaround for that, and each breaks in a different place.

Option 1: linked devices#

Link the same account to a laptop, a tablet and another phone. Each linked device can send and receive.

Works for: one person working across their own devices. A founder answering from a laptop during the day and a phone in the evening.

Breaks for teams:

• Everyone sees every conversation. There is no way to give sales access to sales chats only.
• No assignment. Two agents open the same chat and both reply.
• No ownership or audit trail. "Who promised that discount?" is unanswerable.
• Sessions expire, drop when the limit is reached, and depend on the primary phone staying reachable — see WhatsApp Web not working.
• No reporting. No response time, no volume per agent, nothing.

Option 2: passing the phone or sharing a login#

Common, and worse than it looks.

• The number lives on someone's personal device. When they are on leave, the channel is on leave.
• Chat history walks out with the phone. If they leave the company, so does the customer relationship — the problem covered in exporting chat history.
• Anyone with the login can read every past conversation, including HR-sensitive and payment-related ones.
• There is no way to prove who said what.

If you already run this way, the migration section below matters more than the comparison.

Option 3: the WhatsApp Business Platform with a shared inbox#

Registering the number on the Business Platform separates the number from any phone. Messages arrive over the API into an inbox where each agent has their own account.

What that buys:

• Assignment. A conversation belongs to one agent. Everyone can see who is handling what.
• Internal notes. Context stays attached to the customer, not in someone's memory.
• Access control. Agents see their queues; managers see everything.
• History that belongs to the business. Nothing is lost when a person leaves.
• Reporting. First-response time, volume by agent, conversations by stage.
• Templates and campaigns, with delivery states per message.

The trade-offs, stated plainly: messages sent outside the customer-initiated window cost money per template message, the number must be registered on the platform, and the WhatsApp consumer app can no longer be used with that number.

Compared across the seven things teams actually need#

Migrating an existing number without losing customers#

This is the part people fear, and the fear is mostly about chat history.

1. Export what you need first. Business-critical threads should be exported before migration — history from the app does not carry into the platform.
2. Register the number on the Business Platform. The number must be removed from the consumer or Business app account during registration. Plan for a short window where it is unavailable, and do it outside business hours.
3. Have templates approved in advance. Anything you need to send proactively on day one — order updates, appointment reminders — should already be approved. See templates that get approved.
4. Set up routing before you switch, not after. Decide who answers what, and what the greeting says outside hours.
5. Tell customers nothing. From their side the number is unchanged; the thread continues. That is the point.

What does not carry over: existing chat history, labels, and the WhatsApp Business app's own automation settings. Plan to rebuild labels as tags in a CRM, which is an upgrade rather than a loss.

Choosing#

• One person, several devices → linked devices.
• Two people, low volume, no compliance concerns → shared login will work until it does not.
• Three or more people, or anything where "who handled this" matters → shared inbox on the Business Platform.

Start a free AR-Inbox workspace and put your existing WhatsApp number in front of your whole team, with assignment, notes and reporting.

Related: what happens when the browser session keeps dropping · organising contacts past the point labels break.