setscale

WhatsApp coexistence for agencies: limits and verdict

September 14, 2026·16 min read
Man around thirty with dark hair and a two day beard, wearing an olive green overshirt, leaning on a tall walnut counter in a warm agency kitchen, holding a smartphone next to an open laptop, soft warm light on his face and a cool blue tone in the background

WhatsApp coexistence lets a client keep using the WhatsApp Business app on their phone while the same number is connected to the Cloud API, which is the version of WhatsApp that software and teams work through. For an agency, that is the difference between onboarding the number your client's leads already know and asking the client to give up the app they sell from.

The verdict, before the detail: coexistence is a good fit when the client keeps answering some conversations personally and volume stays at conversation scale. It is the wrong fit when your team needs the number to be one auditable workspace, because the phone stays in the loop and brings its own blind spots. This review is based on Meta's developer documentation, consulted on 14 September 2026 and linked at each point, not on a vendor's summary.

TL;DR

  • Coexistence connects an existing WhatsApp Business app number to the Cloud API through a partner, without deleting the app or the history.
  • The client keeps one to one chats on the phone. Broadcast lists become read only, and disappearing messages, view once and live location are switched off.
  • Chat history from the last six months can be synchronized, once, within 24 hours of onboarding, and only if the client agrees.
  • Messages sent from the app are free and ignore the 24 hour window. Messages sent through the API follow Cloud API pricing and the window.
  • The client's phone becomes infrastructure: an inactive phone or a new device can disconnect the number from your tools.

Table of contents

What WhatsApp coexistence actually is

Meta's documentation page is titled Onboard WhatsApp Business app users, and it says plainly where the popular name comes from: "This feature is sometimes referred to as "Coexistence" in support channels and Partner documentation." The mechanism: a business that already uses the WhatsApp Business app connects that same account and number to the Cloud API, then keeps sending one to one messages from the app while a partner tool handles volume, with history kept in sync between the two.

Three terms need unpacking before the rest makes sense. The Cloud API is the programmable side of the WhatsApp Business Platform, the one a shared inbox or an AI setter plugs into. A partner is the company whose product you connect through, and Meta requires it to be a Solution Partner or Tech Provider using its Embedded Signup flow, which is the connection window the client clicks through. And the client needs a recent app: "The business customer must use WhatsApp Business app version 2.24.17 or higher."

Verdict for this section: coexistence is not a workaround or a grey area. It is a documented onboarding path, and it only exists through a partner product, not as a switch in the app.

How a client connects an existing number

The connection starts in the partner's signup window, not in the app. According to Meta's page, the client is given the option to connect their existing WhatsApp Business app account to Cloud API, enters the phone number, and receives a verification code. Inside the app, a message arrives from the official Facebook Business Account, the client taps through to connect to the Business Platform, then taps Confirm to decide whether their chat history is shared.

Two details belong in your onboarding document because either one can stall an onboarding. First, the client's phone must be in the hands of someone available during the session, since the confirmation happens on the device. Second, a client who used another provider before can hit an error: Meta notes that if the client "worked with a partner in the past and still shares the previous credit line," they "may see an error when attempting to switch to a new partner." Ask about previous providers on the kickoff call, not on go live day. The rest of the access sequence, owners and verification, follows the same logic as our client account access checklist.

Verdict for this section: plan onboarding as a scheduled session with the phone holder present, and check for a previous provider first.

What the client keeps and what the client loses

This is the table to put in front of the client before they agree, because several changes apply to the client's own app, not only to your tools. It reproduces Meta's feature table, with the column that matters to an agency added on the right.

Feature in the app In the app after onboarding Available through the API What it means for your team
One to one chats Message edit and revoke now supported Supported The core of setting works on both sides
Contacts No change Supported Contacts with a WhatsApp number can sync to your tool
Group chats No change Not supported Group conversations stay on the phone only
Disappearing messages Turned off for one to one chats Not supported Tell the client before, not after
View once messages Disabled for one to one chats Not supported Same
Live location Disabled for one to one chats Not supported Worth a line in the onboarding brief
Broadcast lists Disabled, existing lists become read only Not supported The client loses a sending habit, plan the replacement
Voice and video calls No change Not supported Calls stay on the phone, outside your logs
Catalog, orders, status No change Not supported Nothing visible from your tool
Greeting, away message, quick replies, labels No change Not supported The client's labels will not appear in your inbox
Business profile No change Not supported Profile edits stay with the client

The line to discuss first is broadcast lists. Meta's wording is direct: "Existing Broadcast lists will become read-only." A client who has been sending weekly offers to a broadcast list will stop being able to, so the conversation about what replaces it (templates sent through the API, with their cost and their opt in rules, covered in our WhatsApp API rules for teams) has to happen during the sale.

Verdict for this section: for a sales team the losses are acceptable. For a client whose marketing runs on broadcast lists, they are a real cost that must be priced in.

Chat history, six months, one attempt, 24 hours

History is the strongest argument for coexistence over a fresh number, and it comes with three constraints that are easy to miss.

The depth is six months. Meta's feature table states: "All chat messages in the most recent 6 months can be synchronized." The sync is optional, the client decides in the app, and group chats are excluded. Media has its own limit: separate history messages carrying media references are sent "only for media messages sent within 14 days of onboarding".

The timing is strict. Meta's page says: "After you onboard the business customer, you have 24 hours to synchronize their contacts and messaging history, otherwise they must be offboarded and complete the flow again." And it is a single shot: "You can only perform this step once."

For a setting team this history is not a nice to have. It is the context a setter needs to avoid asking a warm lead the same qualifying question twice, which is the difference between a follow up and a restart, as our follow up process for setter teams explains.

Verdict for this section: schedule onboarding when your partner can run the sync the same day, and confirm in writing that the client chose to share history.

Two hands on one number

Coexistence means two places can answer the same prospect: the client's phone and your team's tool. Meta states that "Messages sent and received are mirrored between the Cloud API and WhatsApp Business app," through a notification the partner receives each time the client sends from the app. Whether your tool displays those mirrored messages cleanly in the thread is a question for your partner, and it is the first thing to test.

There is also a gap the mirror does not cover. Meta's page states: "WhatsApp users who use an unsupported companion client to message an onboarded business can do so, but the message will not trigger messages webhooks, so the business won't be able to mirror the message in their own app." In plain words, a lead writing from an unsupported device (Meta lists WhatsApp for Windows and WhatsApp for WearOS as unsupported companions) can reach the phone without ever appearing in your team's inbox. On the business side, onboarding also unlinks every companion device the client had connected, and only the supported ones can then be linked again.

Two rules keep this workable:

  1. Decide ownership per conversation, not per number. A written split (the client keeps existing customers, your setters own new inbound leads) prevents two people answering the same prospect.
  2. Treat any conversation that exists on the phone but not in your tool as an incident, not a curiosity. Your quality assurance across accounts only measures what your tool can see.

Verdict for this section: manageable with a written ownership rule, dangerous without one.

The window and the bill are not the same on both sides

This is the asymmetry that changes how a team should work. Meta's page states: "The 24-hour customer service window restriction applies to messages sent via Cloud API. Messages sent from the WhatsApp Business app are not subject to the customer service window and do not create, extend, or affect Cloud API conversation windows or Cloud API pricing." On cost, it adds that messages sent by the business via the app "will continue to be free, but messages sent via Cloud API will be subject to Cloud API pricing."

Meta's service messages documentation defines the window: "When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts." Once it expires, "you can only send pre-approved template messages." The phone has no such rule.

The temptation is obvious: a setter who misses the window asks the client to "just send it from the phone". Resist it. A message sent from the phone is still mirrored, but it is written by someone outside your team, outside your scripts and outside your response time SLA. It also blurs the numbers you report to the client, since conversations moved to the phone stop being attributable to your setting.

Verdict for this section: the phone is the client's channel, not your team's fallback. Missed windows are a staffing problem to fix, not a routing trick.

Throughput, why 20 messages per second rarely matters

Coexistence numbers are capped. Meta's throughput page states that "For each registered business phone number, Cloud API supports up to 80 messages per second (mps) by default, and up to 1,000 mps by automatic upgrade," while the onboarding page says numbers "that are in use with both the WhatsApp Business app and Cloud API have a fixed throughput of 20 mps." If you read a different figure in an older write up, Meta's page is the reference.

For setting, 20 messages per second is not a constraint. Conversations are one to one, and even a busy campaign from click to WhatsApp ads produces leads at human speed. It becomes relevant only if the same number is expected to send large template campaigns in short bursts.

Verdict for this section: ignore it for setting, check it only if the client plans mass sends from the same number.

The disconnections nobody puts in the proposal

With coexistence, the client's phone is part of your delivery. Meta's reference lists the reasons a number can be disconnected from the partner, including a primary device "inactive for approximately 14 days", a companion device "inactive for approximately 30 days", a changed phone number, the client re-registering on a new device, registering the number with the consumer WhatsApp app, and enforcement or account deletion.

Three consequences for an agency:

  • A holiday can stop your service. A client who leaves the business phone in a drawer for two weeks can take the number offline from your tools.
  • A new phone is an event. Re-registering on a new device is listed as a disconnection reason. Ask the client to tell you before changing devices, and write that request into the onboarding document.
  • Leaving is client side. Meta notes that the partner cannot use its usual deregistration call for these numbers. The client disconnects from the app, under Settings, Account, Business Platform, with the Disconnect Account button, and the partner is notified.

Your partner receives a notification when a disconnection happens. Make sure someone on your side is alerted too, because a silent inbox on a Monday morning looks exactly like a quiet weekend. If calls booked from WhatsApp flow into your CRM, the same monitoring belongs in your DM to CRM integration.

Verdict for this section: coexistence moves part of your uptime into the client's pocket. Say so in the contract and monitor it.

Coexistence or a dedicated number, the verdict

Neither option is better in general. The choice depends on who works the number and how much the client wants to keep.

Situation Coexistence Dedicated number
The client already sells from the app and leads know the number Strong fit Loses the known number
The client wants to keep answering existing customers personally Strong fit Forces the client into your tool or a second number
Your team owns all conversations and reports on every one Weak fit, the phone stays outside your process Strong fit
The client relies on broadcast lists or disappearing messages Costly, those features stop No impact on the client's app
The client's phone is shared, old or often switched off Risky, inactivity and device changes disconnect Strong fit
You need six months of context on day one Strong fit, if synced within 24 hours No history

For a dedicated number, the rules in our WhatsApp API guide for teams apply unchanged. For coexistence, add three lines to your onboarding document: the conversation ownership split, the phone holder's commitment to keep the device active and announce device changes, and the date and outcome of the history sync.

Overall verdict: coexistence is the right default for a client who is already active on the WhatsApp Business app and will stay involved. For an account your team runs end to end, a dedicated number is simpler to audit and harder to break.

Where SetScale fits

SetScale is an AI setter built for teams and agencies: several client accounts, several closers, reporting per seat, with a white label option planned. Channel setup is where multi account operations succeed or fail, which is why the infrastructure view of setting treats numbers, ownership and monitoring as part of the product question. Our WhatsApp page makes the same point from the other side: WhatsApp Business on one phone does not survive a second closer.

The product is not open yet. The waitlist is the only thing on offer today. Join the waitlist.

FAQ

Does coexistence delete the client's chats from the phone?

Meta's page describes the opposite: the client keeps sending one to one messages from the app, and messaging history is kept in sync between the app and the partner tool. What changes is the list of features in the table above, notably broadcast lists becoming read only and disappearing messages being turned off.

Can we onboard coexistence ourselves, without a partner product?

Meta's page is written for Solution Partners and Tech Providers using Embedded Signup. An agency normally goes through a partner's product. Meta also states that Embedded signup v2 will be deprecated on October 15, 2026, so it is a fair question to ask a partner which version their flow runs on.

What happens if the history sync is missed?

Meta gives 24 hours after onboarding. Past that, the client has to be offboarded and go through the flow again, and the sync itself can only be performed once per onboarding.

Are messages sent from the phone included in the client's WhatsApp bill?

Meta states that messages the business sends from the app continue to be free, while messages sent through the Cloud API follow Cloud API pricing. Report the two separately so the client understands what your team's activity actually costs.

Is coexistence available for Instagram or Messenger?

Coexistence is an onboarding path of the WhatsApp Business Platform, documented for WhatsApp Business app users only. Instagram and Messenger access follow their own permission model, covered in our client account access checklist.

Conclusion

WhatsApp coexistence solves a real agency problem: onboarding the number a client's leads already use, with six months of context, without taking the app away. It also leaves the phone inside your operation, with its own window rules, its own blind spots and its own ways of going offline.

Before the next WhatsApp onboarding, decide with the client who owns which conversations, schedule the history sync, and add phone activity to your monitoring. Then report the account the way our client reporting framework suggests, separating what your team did from what happened on the phone. If you would rather run numbers, ownership and reporting as one system across every client, Join the waitlist.