People searching for WhatsApp coexistence and WhatsApp Web want to know whether the computer keeps working once a WhatsApp Business app number is connected to the official WhatsApp Business API. It does: WhatsApp Web comes back after you link it again, with two exceptions.
What changes is the routine around the primary phone. This guide covers which devices are supported, how to reconnect, the 14-day rule, changing phones, splitting work with the platform, and account security.
Key Takeaways
- WhatsApp Web is unlinked at activation and can be linked again: up to four devices, except WhatsApp for Windows and Wear OS.
- The primary phone is in charge: about 14 days without use drops the API, and a phone change reconnects the API but not WhatsApp Web.
- Multiple agents, AI agents, and templates call for the API team inbox; security starts with who holds the phone.
WhatsApp Coexistence and WhatsApp Web: What Stays and What Changes
Under coexistence, WhatsApp Web keeps working as a device linked to the WhatsApp Business app, while the Cloud API serves the same number. WhatsApp coexistence is a Meta feature that ConverZAP, a Meta-verified Tech Provider, turns on inside its own app since October 2026.
What Keeps Working on the Computer
Once linked again, WhatsApp Web shows the account’s one-on-one chats and lets you reply from the keyboard, as before. According to Meta’s coexistence documentation, the business keeps using the app and supported linked devices to send and receive messages.
Every message sent from the app or a supported device triggers an echo event, called smb_message_echoes, to the partner’s platform. This way, the platform can log what the team replies from the computer, depending on each partner’s integration.
What Changes in Chats
Activation changes some features in every one-on-one chat, and the computer follows those changes. Disappearing messages, view once, and live location are turned off, and broadcast lists become read-only.
Part of this already applied to WhatsApp Web before coexistence. The WhatsApp Help Center states that linked devices do not show live location or create broadcast lists. Groups and calls stay in the app but off the API, as the guide to WhatsApp coexistence groups explains.
Linked Devices Under Coexistence: How Many and Which Ones
Under coexistence, the business can link up to four devices to the WhatsApp Business app, and all of them are supported except WhatsApp for Windows and WhatsApp for Wear OS. The rule comes from Meta’s documentation as of October 2026.
Up to Four Devices, With Two Exceptions
The limit of four is the same as for any WhatsApp account. The Help Center lists WhatsApp Web, the desktop app, tablets, additional phones, and glasses with Meta AI as linked devices, all tied to a primary phone.
Under coexistence, the account gains one more participant: the Cloud API itself, which Meta calls the “Cloud API companion” in its reconnection documentation. Like the others, it depends on the primary device, as the next sections show.
Device-by-Device Table
The table below applies Meta’s rule to each device type. The last column gives practical guidance, based on the documentation and the Help Center as of October 2026.
| Device | Under coexistence | Practical guidance |
|---|---|---|
| WhatsApp Web (browser) | Supported | Link again after activation |
| WhatsApp for Mac | Supported under the general rule | Link again after activation |
| WhatsApp for Windows | Not supported | Use WhatsApp Web in the browser |
| Linked tablet or iPad | Supported under the general rule | Check that it appears in the device list |
| Additional linked phone | Supported under the general rule | Keep it with a trusted person only |
| Wear OS watch | Not supported | Read messages on the phone |
For teams on Windows computers, the way forward is WhatsApp Web in the browser, not the installed app. Messages viewed on an unsupported device show placeholder text that tells the person to open the primary phone.
Why Activation Logs Out WhatsApp Web
Turning on coexistence unlinks every linked device on the account, including WhatsApp Web, and the business needs to link them again. This is expected behavior documented by Meta, not a failure of the partner or the computer.
What Happens at Connection Time
When the business finishes the connection flow, the WhatsApp Business app updates on its own and shows that the number is connected to the API. At the same moment, every linked device leaves the account and stops showing chats.
The documentation does not explain the technical reason for the logout; it only describes the effect and allows supported devices to be linked again. That is why it pays to schedule activation for a quiet time of day, with the primary phone at hand.
How to Reconnect WhatsApp Web Step by Step
Reconnection follows the same path as any account, described on the Help Center page how to link a device. The whole process starts from the primary phone, which must be unlocked and running an updated WhatsApp Business app.
- On the computer, open WhatsApp Web in the browser.
- On the primary phone, tap the more options icon (three dots, on Android) and then Linked devices.
- Choose the option to link a device and scan the QR code shown on the computer, or link with your phone number instead.
- Wait for chats to load and repeat on the other devices, up to the limit of four.
After linking, ask someone to send a test message and check that it shows up on the computer and on the platform. This test confirms both sides are receiving before the team gets back to its normal pace.
The Primary Phone and the 14-Day Rule
Under coexistence, the primary phone needs regular use: after about 14 days of inactivity, the system removes the connection to the partner and the Cloud API. The same device keeps every linked device running.
Why the Primary Device Is in Charge
The primary phone is where the WhatsApp Business app account is registered, and only it can link new devices. According to the Help Center, computers, browsers, iPads, and wearables cannot be used as the account’s primary device.
Under coexistence, this role grows. The phone is where the business confirms the connection with the partner, approves sharing chat history, and, if it wants, disconnects the platform. Without the device, the business loses control of its own connection.
14 Days, 30 Days, and What Drops in Each Case
There are two different periods, from two official sources, and they are easy to mix up. The table sums up what the account_update webhook reference and the Help Center say about inactivity, as of October 2026.
| Situation | Approximate period | What happens |
|---|---|---|
| Primary phone unused (coexistence) | About 14 days | The system removes the connection to the partner and the API (reason PRIMARY_INACTIVITY) |
| Primary phone unused (devices) | More than 14 days | Linked devices, such as WhatsApp Web, are logged out |
| Linked device unused | 30 days | WhatsApp logs out the device; the API reference also lists the reason COMPANION_INACTIVITY (about 30 days) |
Meta does not set a fixed interval for opening the app. A weekly routine on the primary phone, with the app open and a few chats answered from it, leaves a safe margin. Messages sent only through the platform should not be treated as a substitute.
Changing Phones Under Coexistence
When you change phones or reinstall the WhatsApp Business app, the Cloud API connection drops and comes back on its own within a few minutes, but WhatsApp Web must be linked again by hand. Meta describes the process on a dedicated page.
What Happens When You Switch or Reinstall
According to Meta’s reconnection documentation, a device change, a reinstall, or a new registration of the number automatically disconnects the Cloud API companion. On the new phone, registration shows a pre-checked option with the products that were connected.
If the business leaves the option checked, reconnection usually finishes within a few minutes. During that gap, the API is paused, the app is briefly unavailable, and history from that period does not sync. If another partner connects the account, reconnection fails.
A Checklist for a Smooth Switch
A phone change goes smoothly when it is planned. The list below is practical guidance, built from Meta’s documentation and the Help Center, not an official procedure:
- Tell the partner and the team when the switch will happen, ideally outside peak hours.
- Keep the same number and finish registration on the new phone without unchecking the connected products.
- Check on the platform that messages are arriving through the API again.
- Link WhatsApp Web and the other devices again.
- Wipe the old device before giving it away or selling it.
The Help Center page on changing phones recommends backing up chats and erasing the old device. Under coexistence, the app backup still matters, because groups do not go to the API and older media reaches the platform without the file.
Keep your number and add the official API
ConverZAP, a Meta-verified Tech Provider, connects your WhatsApp Business app number through coexistence. The phone keeps working, and the AI agent and team inbox run on the official API.
Try it free with your own numberSee how it worksWhatsApp Web With the Official API: Who Answers Where
WhatsApp Web with the official API splits the work across two screens: WhatsApp Web mirrors the phone, and the platform’s team inbox organizes the team through the Cloud API. Under coexistence, both run on the same number.
What Each Screen Does Well
WhatsApp Web repeats the phone on the computer. Every linked device sees the same chats at the same time, with no owner per conversation, no queue, and no per-person reports. It works well for the owner and for very small teams.
The API team inbox is built for teams. It distributes chats, records who replied, and supports multiple agents and AI agents on the same number. Templates go out only through the API, according to Meta’s official PDF guide.
WhatsApp Web vs the Team Inbox
The comparison below assumes a coexistence number with WhatsApp Web linked and a platform connected to the Cloud API. The criteria are the ones that matter most when more than one person handles customers.
| Criterion | WhatsApp Web (linked device) | Team inbox on the API |
|---|---|---|
| How many people | Up to four devices on the account | Depends on the platform, with individual logins |
| Splitting chats | Manual: everyone sees everything | Assignment to agents and queues |
| AI agent | No | Yes, through the Cloud API |
| Templates and campaigns | No | Yes, with approved templates |
| Groups | Yes | Not on coexistence |
| Meta cost | Outside the Cloud API (app messages are free) | Cloud API pricing |
In practice, the two screens complement each other. The team inbox help page shows how the shared inbox works, and the guide to human and AI customer service explains how the AI hands a conversation over to a person.
WhatsApp Business App and API on the Computer: The Team Routine
Using the WhatsApp Business app and the API on the computer at the same time takes simple rules about who answers what. Without them, the customer gets two replies, and nobody knows who took over the conversation.
Splitting Roles Between the App and the Platform
A common setup leaves the phone and WhatsApp Web with the owner or manager, who handles groups, calls, and long-standing customers. The team and the AI agent work through the platform, where the queue and history live.
App tools, such as automatic greeting and away messages, quick replies, and labels, keep working but are not supported by the API. An away message from the app can reach a customer who is already chatting with the AI, so review them.
The split also affects cost. According to Meta, messages sent from the app remain free, while messages sent through the API follow Cloud API pricing, explained in the WhatsApp coexistence pricing guide.
From October 1, 2026, Meta charges for service messages and for utility messages inside the 24-hour window, with 1,000 free service messages per phone number each month, according to the official non-template message pricing page.
How to Avoid Duplicate Replies
Duplicate replies are the natural risk of answering from the app and the platform at the same time. A few simple rules, agreed with the team and reviewed often, prevent most conflicts:
- Define in writing which chats stay on the phone and which stay on the platform.
- Set the AI agent to stop when a person replies from the app.
- Review the app’s greeting and away messages before turning on the AI.
- Use the platform for internal notes instead of messages in the chat itself.
- Review the rules every month, along with customer service numbers.
The technical piece that makes this possible is the echo. Because the platform receives every message sent from the app or WhatsApp Web, the AI can detect that a person has taken over and step out of the conversation, if the platform uses that event.
Security: Who Has Access to the Primary Phone
Under coexistence, whoever holds the primary phone controls the account: they can link devices, disconnect the platform, and register the number on another device. That is why security starts with deciding who keeps that phone.
The Phone Is the Key to the Account
With the device in hand, anyone can open Settings > Account > Business Platform and disconnect the partner, which ends the Cloud API integration. They can also link an unknown computer and read the business’s one-on-one chats.
The Help Center advises never sharing the six-digit registration code or the PIN and offers two-step verification as an extra layer. Turning on that feature for the business number makes it harder to register the account on another device.
Access Best Practices
A few practices reduce risk without slowing customer service. Most come from the Help Center’s recommendations for linked devices, adapted to a business with several employees:
- Keep the primary phone with one or two responsible people, with a screen lock.
- Turn on push notifications on the phone, which let you block unknown devices from linking.
- Check the list of linked devices every week and remove unknown ones.
- Log out the devices of anyone who leaves the company the same day.
- Give the team access through the platform, with individual logins, instead of linking more computers.
- Do not use unofficial extensions, websites, or apps to extend WhatsApp Web.
The last item deserves attention. The Help Center warns that connecting the account to unofficial apps or websites can lead to a temporary or permanent ban. The guide to the unofficial WhatsApp API and the one on a banned WhatsApp number explain those risks.
To remove a device, the Help Center page how to log out of a linked device shows the path from the phone, under Linked devices, or from the linked device itself. If a computer was lost or ended up in the wrong hands, that is the first step.
Common Device-Related Errors Under Coexistence
The device problems Meta describes under coexistence have known causes: an unsupported device, an idle phone, a device change, or a new registration of the number. The table below links each symptom to its cause and the fix.
Symptoms, Causes, and Fixes
The symptoms below are compiled from Meta’s documentation and the Help Center as of October 2026. Activation and signup codes are covered in the guide to WhatsApp coexistence errors, with the official fix for each one.
| Symptom | Likely cause | What to do |
|---|---|---|
| WhatsApp Web logged out right after activation | Expected unlinking at connection time | Link it again from the phone |
| Placeholder text on the computer | Unsupported device, such as WhatsApp for Windows | Use WhatsApp Web or the phone |
| The platform receives error 131060 | A customer’s first contact or an unsupported device | Check the message in the app; on first contact, it usually resolves within seconds |
| The integration dropped with nobody touching it | Primary phone idle for about 14 days (PRIMARY_INACTIVITY) | Use the phone again and ask the partner to redo the connection |
| The integration dropped after changing phones | New registration of the number | Do not uncheck the connected products, and link WhatsApp Web again |
| The integration dropped after using the number on regular WhatsApp | Registration on the consumer app (BUSINESS_DOWNGRADE) | Talk to the partner before any new registration |
When to Call the Partner
If the symptom involves only the computer, the business can fix it by linking the device again. When the platform stops receiving messages, the partner needs to step in, because it is the one that receives Meta’s disconnection notices.
Agree with the partner on an alert for disconnection events, such as PARTNER_REMOVED and ACCOUNT_OFFBOARDED. The WhatsApp API glossary explains the technical terms, and error 131060 is common with click-to-WhatsApp ads.
How to Keep the Computer and Start on the Official API
Coexistence lets the business add the official API without giving up the phone or WhatsApp Web, as long as it follows the primary phone rules. In ConverZAP, it is turned on inside the app through Meta’s Embedded Signup, and WhatsApp Web works again once linked.
Coexistence or a Dedicated Number
For businesses that work only through the platform, a dedicated number on the Cloud API can be simpler: no phone to keep active and no devices to link. The comparison WhatsApp coexistence vs Cloud API breaks down the choice by scenario.
Under coexistence, the number in use stays on the app and gains the API. High-volume senders should also factor in the fixed limit of 20 messages per second, according to Meta’s throughput documentation as of October 2026.
Official API With AI Agents and a Team Inbox
ConverZAP, a Meta-verified Tech Provider, connects your WhatsApp Business app number through coexistence and runs on the official WhatsApp API: AI agents that take action in the CRM and database, a team inbox for multiple agents, and bulk messaging with approved templates, opt-in, and unsubscribe. Recent one-on-one history (up to 6 months) can be imported in the first 24 hours.
Messages you send from the phone show up in the ConverZAP inbox as “Sent from phone”, and the AI agent pauses so it doesn’t reply over you. The computer stays the team’s desk; what changes is what runs on it. The coexistence setup guide shows activation, you can try it free with your own number, and the pricing page lists every plan.
FAQ About WhatsApp Web Under Coexistence
Yes, for a while. According to the Help Center, linked devices work even with the phone offline, but they are logged out if the app is inactive for more than 14 days. Under coexistence, a similar period drops the API connection.
No. According to the Help Center, the phone sends the linked device an encrypted copy of the most recent messages, and WhatsApp Web syncs fewer messages than the desktop app. The full history stays on the primary phone.
The supported browsers page says WhatsApp Web works on Windows, Linux, and macOS and that calls work best on Chrome, Edge, Firefox, Safari, and Opera. The page also lists minimum browser versions.
Voice and video calls stay in the WhatsApp Business app but do not go through the API. Since WhatsApp for Windows is not supported with coexistence, test calls on the computer using the Mac app or the browser.
Yes. The official reference lists a number change (CHANGE_NUMBER) among the reasons the partner gets disconnected. Plan the change with the partner in advance, so the connection can be redone with the new number.
Meta states that messages sent from the WhatsApp Business app remain free under coexistence. WhatsApp Web is a device linked to the app, and its messages count as app messages; charges apply to what goes out through the Cloud API.
Yes. Activation in ConverZAP logs out WhatsApp Web, as with any coexistence connection, and the business links it again from the primary phone. After that, the number keeps working in the app and on the computer, and ConverZAP serves customers through the official API on the same number.
