Using one WhatsApp business number on more than one device

One WhatsApp Business app number can be answered from more than one device, and the limit is small. Meta states it clearest in documentation written for API partners, and prints a larger number elsewhere with a different framing. The browser client is one of those devices rather than an account of its own. On the Cloud API the question changes shape: the number is registered to an account rather than installed on a phone, so how many people answer at once is a property of the software you connect, not a device count Meta publishes.

Where Meta prints a device count

It appears in the feature comparison table of Meta’s page on onboarding WhatsApp Business app users, in the row for linked devices:

Businesses can link up to four WhatsApp “companion” clients to their WhatsApp Business app account on other devices

Two things there are easy to miss. It sits on a developer page addressed to Solution Partners rather than on either Business app product page, and it points at WhatsApp’s Help Center for the term the app uses, which is where this article runs out of citable ground.

A different Meta page markets a larger number. The WhatsApp Business App Features page, in its Meta Verified section, under the heading “Grow efficiently with multiple agents”, says you can “Handle more orders and respond to more customers by linking up to 10 devices and agents to your account”.

Neither page offers a reconciliation and we will not invent one. Neither defines whether a “device or agent” counts the same way as a companion client, and the larger figure is published as a benefit of a paid verification product. Any roundup handing you one number as the app’s device limit has quietly chosen which of Meta’s two pages to believe.

Where Meta prints a count	What that page documents
Onboard WhatsApp Business app users, linked devices row	Four companion clients, linked to the app account on other devices
WhatsApp Business App Features, Meta Verified section	“linking up to 10 devices and agents to your account”

The same page says which clients stop counting: once a number is onboarded to Cloud API alongside the app, Meta excludes WhatsApp for Windows and WhatsApp for WearOS from the supported companion clients, and supports the rest.

The consumer rule underneath, and where the browser sits in it

WhatsApp’s own features page states the arrangement in three sentences, for personal accounts rather than for the Business app:

Linked devices provide a reliable, secure way to access WhatsApp from any of your devices. You can stay connected by linking up to four devices at a time to your primary phone. You’ll still need your primary phone to register your WhatsApp account and link new devices.

Read the last sentence twice. The primary phone is not the most convenient device, it is the one that holds the registration. Everything else is a companion to it, which is the word Meta’s developer documentation uses on a business account.

The browser is one of those companions. WhatsApp’s download page files it under signing in rather than installing, under the heading “Log in from your browser”, and offers it in the same breath as an unsupported device: “Don’t see your device supported?”, then “Use WhatsApp on your browser.” Take the phone out of the arrangement and the browser has nothing to show.

What it does, it does properly. The features page puts calling on the web alongside the phone platforms, “across iOS, Android and web”, and says you can “Make calls on WhatsApp with the device you want by downloading our apps or right from your web browser”. For reading a customer’s message and typing a reply on a keyboard it is a real answer, free and needing no API.

What it cannot be is an account. No page cited here offers a route from a browser to a registered WhatsApp number, because registration is what the primary phone does. Nor is it where the Business app’s own tools are documented: neither Business app page we read names a web or desktop client among the features it lists, and the away message entry offers one link for iPhone, one for Android, and none for a browser. Driving that session with a script rather than sitting in front of it is a different subject, quoted in unofficial WhatsApp APIs.

Can two people answer at once

On the app, Meta’s own framing is that they can: the features page sells multiple agents as a reason to subscribe to Meta Verified. The behaviour underneath is undescribed on the pages we fetched: nothing we read says what happens when two agents open the same chat, how an incoming message is routed, or whether one agent can see that another has already replied.

The page that does document linked devices for the app in detail is WhatsApp’s Help Center, on faq.whatsapp.com. That site delivers its body inside a script payload, so a saved copy extracts to under sixty characters of text and verifies nothing, a measurement of ours declared in the frontmatter. We cannot store a copy we can stand behind, so we will not quote it or print the device numbers it carries. Whether the browser client lets you edit a business profile, apply labels, send a catalog or change the greeting and away messages is the same kind of Help Center subject, so open the browser and look.

What the citable pages do establish is that one device is not like the others. Listing why an onboarded account gets disconnected, Meta’s onboarding page includes both “companion device inactive for approximately 30 days” and “primary device inactive for approximately 14 days”. Those reasons are documented for a number running on the platform alongside the app, so read them as behaviour for that setup rather than as a general app rule. They still give the shape of the thing: a primary device holds the account, and companions hang off it, each with its own inactivity window.

What happens to the chat history

For the app alone, the pages cited here do not say what a newly linked companion client shows of past conversations. That answer is in the Help Center we just declined to quote.

Where Meta does document history is the crossover between the app and the Cloud API. On its onboarding page: “Messages sent and received are mirrored between the Cloud API and WhatsApp Business app”, and messages sent from the app afterwards keep flowing to the connected software, because each one “triggers an smb_message_echoes webhook”.

Getting to that state is where history can be destroyed. Meta’s migration page gives two routes and only one of them is safe:

If you delete your WhatsApp Business app phone number and then register it for use with Cloud API using the steps below, your existing messaging history will be lost, and you will be unable to use that number with the WhatsApp Business app again, unless you deregister the number from Cloud API.

The other route keeps both sides alive. On the same page: “you will be able to use both the WhatsApp Business app and the partner’s app concurrently, and your messaging history will be preserved.”

What onboarding does to the devices you already have

Two consequences Meta publishes, both about the companions rather than the number. Its wording, then ours.

Meta, Onboard WhatsApp Business app users	What it means for you
“all companion apps will be unlinked from the account, and the business can then re-link any supported companion apps”	One forced sign-out of every linked device, then you relink by hand.
“Messages sent from an onboarded business (by any means) that are viewed in an unsupported companion device will appear with placeholder text”	Your outbound message can land somewhere it cannot be read.

A change of phone resets the arrangement too. Meta’s coexistence documentation is direct about a re-registration: “When a client onboarded via coexistence changes devices or re-registers their WhatsApp Business app, their Cloud API companion is automatically offboarded.” None of that is a reason to avoid the API. It is a reason to know that a browser session and the API are two views of one number, not two workers.

On the Cloud API there is no device to count

Meta’s business phone numbers page states that “A valid business phone number must be registered before it can be used to send and receive messages via Cloud API”, and that a registered number “cannot be used with WhatsApp Messenger”. Incoming messages arrive at software you run rather than at a handset: the platform overview says “the contents of any message sent from a WhatsApp user to your business phone number is communicated via webhook”.

So there is no companion client limit on that side, and no linked-device screen. How many people answer at once is decided by whatever inbox you point the webhook at, so the seat count is a question for that vendor rather than Meta. The one ceiling Meta does document for a number running both ways is throughput: business phone numbers in use with the app and Cloud API together have a “fixed throughput of 20 mps”.

The honest summary

If two or three people need to answer the same number on the app, you are working inside a small companion-client allowance that Meta states plainly in one place and markets differently in another, and the browser is one of those companions rather than a way around them. Verify the current number in the Help Center before planning staffing around it, because that is the page Meta keeps current and the page we cannot cite.

If the number of people answering is the reason you are reading this, the app’s device list is the wrong lever. Moving to the platform replaces a device count with a software choice, and choosing that software is the same exercise as picking review management software: judge it on what its documentation commits to.