WhatsApp Business Web: Setup, Device Limits, and Where It Breaks for Teams

WhatsApp Business Web is the free browser version of the WhatsApp Business app. It mirrors the account on your phone — every chat, contact, label, and quick reply — inside a desktop browser at web.whatsapp.com after a one-time QR code scan.

It is not a separate product and there is no separate signup. Your phone holds the account; the browser holds a linked session. Since WhatsApp's multi-device update, the linked browser keeps working even when the phone is offline, as long as the phone connects to the internet at least once every 14 days (WhatsApp Help Center).

What you can do from the browser:

• Send and receive messages, images, documents, and voice notes
• Make and take voice and video calls, one-on-one and group, with screen sharing and a Calls tab — added 28 July 2026 and still rolling out
• Insert quick replies by typing / in the message field
• Apply and filter by labels to keep order status and lead stage visible
• View and share your product catalog in chats
• Type on a real keyboard instead of a phone screen — the actual reason most businesses link it

The calling addition is the biggest change to this product in years, and it is the reason the old advice to "install the desktop app if you take calls" is now wrong. Meta's announcement is explicit that browser calls are end-to-end encrypted, with no time limits and at no cost (Meta Newsroom, 28 July 2026).

For a one-person operation answering a few dozen chats a day, this is usually all the desktop tooling needed.

Open web.whatsapp.com in any modern browser, then scan the on-screen QR code with the WhatsApp Business app on your phone via SettingsLinked DevicesLink a Device. The whole process takes under two minutes.

1. Open the browser. Go to web.whatsapp.com in Chrome, Firefox, Edge, or Safari. A QR code appears.
2. Open WhatsApp Business on your phone. Tap Settings (iPhone) or the three-dot menu (Android).
3. Tap Linked Devices, then Link a Device. Your phone may ask for your unlock PIN or biometric.
4. Scan the QR code on your computer screen with the phone camera view that opens.
5. Wait for sync. Chats load in the browser within seconds; older history fills in over the next minutes.

Two setup details worth knowing before you rely on it. First, the session persists — you stay logged in until you log out or the 14-day phone-offline window lapses. Second, the same Linked Devices screen is where you remotely log out a browser session, which matters the day a laptop is lost or an employee leaves.

Less than it used to be, and on Windows almost not at all. Meta rebuilt WhatsApp for Windows as a Microsoft Edge WebView2 wrapper around web.whatsapp.com, replacing the native WinUI app — so the Windows "desktop app" now runs the same web client you get in a browser tab, in its own window. On macOS the app is still a native Mac Catalyst build. Both count as linked devices, exactly like a browser session.

This matters because most WhatsApp Business Web guides still repeat the pre-2025 advice: install the desktop app for native notifications, faster performance and call support. On Windows, two of those three reasons no longer hold.

Which one should you actually run?

On Windows, pick on window management, not capability. The wrapper gives you a taskbar entry, an app icon and a window that survives a browser restart; it costs install rights and noticeably more memory than the old native client, which is the change Windows users complained loudest about through late 2025 and 2026. If you live in the browser anyway, a pinned tab loses you very little now.

On macOS the native app is still a genuine performance and integration upgrade over a tab, so the old advice survives there.

On a locked-down work laptop or a shared machine, the browser is the whole answer — and since July 2026 that includes taking calls, which previously forced an install. Meta called out exactly this case: a work laptop that does not allow app downloads (Meta Newsroom, 28 July 2026).

Whichever you pick, it is a linked session and it consumes a device slot, so running the browser and the app side by side on one machine burns two.

The linking mechanics are identical — both use web.whatsapp.com and the same QR flow. The difference is the account you link: scan with the WhatsApp Business app and the browser shows business tools (labels, quick replies, catalog, business profile); scan with personal WhatsApp and those tools are absent.

There is no separate "business" URL or browser app to find. This confuses a lot of first-time users who search for a dedicated WhatsApp Business Web portal — it does not exist. The web client detects the account type when you scan.

What appears only when a Business account is linked:

• Labels — color-coded tags like New customer or Pending payment, filterable from the chat list
• Quick replies — saved answers inserted with /
• Catalog access — share product cards with prices directly in chat
• Business profile — hours, address, and website visible to customers who tap your name

Greeting and away-message automation is configured on the phone app, not in the browser, but fires regardless of which device you are answering from.

WhatsApp Business Web inherits every limit of the Business App and adds a few of its own: a hard cap on linked devices (4 on the free app), no broadcast sending from the browser, no template messages, no conversation assignment, and no per-agent reporting.

The limits that surprise businesses in practice:

• The linked-device cap. Browser tabs, desktop apps, and tablets all draw from the same pool — 4 on the free WhatsApp Business app. Exceed it and the oldest session gets dropped. Paid Meta Verified subscriptions raise the allowance, but the free app has not moved off 4.
• Broadcasts are mobile-only. Broadcast lists (capped at 256 contacts per list) can only be created and sent from the phone app — the web client cannot send them at all.
• No template messages. Proactive, pre-approved outbound templates exist only on the WhatsApp Business Platform (API), which Meta bills per delivered message since 1 July 2025 (Meta developer docs, pricing).
• The 14-day rule. If the phone holding the account stays offline for 14 days, every linked device disconnects until the phone comes back online.
• One account per phone number. You cannot merge two numbers into one web session or run two accounts in one browser profile.
• No audit trail on the free app. Messages sent from a linked session are indistinguishable from messages sent from the phone — there is no record of who on your team wrote what.

None of these matter for a solo operator. All of them matter the day a second person starts answering during the same hours.

One or two people can make it work. Beyond that, the free app's linked-device model fails in predictable ways: every session shows every chat with no assignment, two agents typing into the same conversation collide, and nobody can measure response time per agent because the free account has no concept of agents.

The failure modes teams report look like this:

• Duplicate replies — two agents answer the same customer within a minute of each other because neither could see the other had it open
• Dropped chats — everyone assumes someone else owns a conversation, and the customer waits hours
• No handover context — there are no internal notes, so shift changes happen over a separate Slack thread or not at all
• Device-slot juggling — agent number five cannot link at all without logging someone else out

What are the three tiers, exactly?

Most guides present this as a binary — free app or API. It is three steps, and the middle one is the part that changed:

1. Free WhatsApp Business app. 4 linked devices, no assignment, no per-agent reporting. Phone-tethered to the 14-day rule.
2. Meta Verified (paid subscription). Meta's own WhatsApp Business site now lists a multi-agent account among the subscription benefits: connect more devices and assign chats to sales agents, alongside the verified badge and prioritised support. Meta does not publish the per-tier device allowance on that page, and its help-centre article is not machine-readable, so check the exact number in the app before planning headcount around it — ToolsMeta Verified shows the tier you are on.
3. WhatsApp Business Platform (Cloud API). No device cap, real routing, and the only way to send proactive template messages. Requires a provider or your own integration.

The distinction that trips people up: the free app and Meta Verified are the same product with a subscription on top. The Platform is a different product with a different billing model. Moving to it means your number leaves the app.

Does the API still make financial sense in late 2026?

Check the date on any cost estimate you were given, because the model is changing twice this year. Meta's developer docs state that from 1 October 2026 service messages — ordinary replies inside the 24-hour customer service window, free since November 2024 — become billable per message, as do utility templates sent in response to users. Separately, from 1 August 2026, Meta Business Agent messages bill per token at $2.00 per million tokens, roughly 4–5 cents per message (Meta developer docs, upcoming pricing updates).

In practice, a support team's WhatsApp bill is about to include the replies it sends, not just the outreach it initiates. If someone modelled your API costs before mid-2026, that model is wrong now. Rebuild it before committing.

The trade-offs between app and API are covered in our WhatsApp Business API vs App comparison, and the channel itself — response-time expectations, the 24-hour service window, setup options — in the guide to WhatsApp customer support.

Solo operators and two-person shops should stay on WhatsApp Business Web and the free app — specifically, if you answer fewer than about 50 conversations a day and never message customers first. At that size, migrating to the WhatsApp Business Platform costs you money and a working setup, and buys you a routing engine nobody will use.

Concretely, do not migrate if all of these are true:

• One or two people answer, and never at the same time. Collisions are the problem assignment solves. No overlap, no problem.
• Customers always message you first. Template messages are the strongest reason to move. If you only ever reply, the free 24-hour window covers you today — though from 1 October 2026 Meta starts charging per message for those replies on the Business Platform, so "we only respond" stops being free there.
• You do not need to prove who said what. Regulated industries and disputed-order businesses need the audit trail. A bakery does not.
• Four devices is enough. One phone, one laptop browser, one tablet — that is three.

The honest failure mode in the other direction is worth naming too. Teams that migrate on the strength of a feature list, without anyone owning the setup, usually end up with a Platform number, a monthly bill, and agents still answering from their phones. The migration is a workflow change; the API is just what makes it possible.

What is the actual trigger to move?

One signal, not a feature list: the first week two people answer the same customer twice. That is the point where the free app's model has run out, and every symptom after it — dropped chats, no handover notes, arguments about who was meant to reply — is downstream of the same missing concept of ownership.

The second trigger is needing to message customers first, because no amount of linked devices unlocks template messages.

Everything else — bigger volume, more channels, wanting reports — is a preference. Those two are structural.

For teams already feeling the collision problem, a unified inbox like Converge connects WhatsApp through the API alongside Messenger, Instagram, Telegram, email, and a website widget, with assignment and per-agent reporting built in, at $49/month flat rate for up to 15 agents.

Almost every WhatsApp Business Web failure traces back to one of three causes: the phone lost its 14-day check-in, the QR scan is failing on screen quality, or the browser session went stale. Each has a two-minute fix.

"Phone not connected" or chats stopped updating

Open WhatsApp Business on the phone and let it sync on Wi-Fi for a minute. If the phone has been offline more than 14 days, all linked devices were disconnected — re-link with a fresh QR scan.

QR code will not scan

Raise the screen brightness, clean the phone camera, and click the refresh arrow on the QR code (it expires after a short period). If it still fails, log out of all linked devices from the phone's Linked Devices screen and start over.

Logged out unexpectedly

Check whether a colleague linked a fifth device — the oldest session gets dropped when the 4-device cap is exceeded. Also check Linked Devices on the phone for sessions you do not recognize, and remove any you cannot account for before re-linking.

Messages send from the browser but customers reply to the phone only

Nothing is wrong. Replies arrive on every linked device; notification settings differ per device, so enable browser notifications and keep the tab open. Installing the desktop app is a weaker fix than it used to be on Windows, where the app is the same web client in a wrapper — on macOS the native app does still deliver more reliable background alerts.