All postsWhatsApp coexistence: how to connect a sales rep's number to the official API without losing chat history
Vinícius Molina
9 min
WhatsApp coexistence is a Meta feature that lets one phone number run on the WhatsApp Business app and on the official WhatsApp Business Platform (Cloud API) at the same time. The rep keeps the phone, the number and the chats. The company gets a record of every message, CRM integration, campaigns and metrics on that number.
Until recently, moving a number to the official API meant taking it off the app. The rep lost the WhatsApp they used every day, and the history with customers stayed behind. So most companies left their team's WhatsApp outside any system. Coexistence changes that trade-off.
This guide covers what coexistence is, what Meta requires, what stops working, how onboarding works through a tech provider, and how Arco Educação, one of Brazil's largest education companies, used it to connect 125 consultants, each on their own number.
What WhatsApp coexistence is
Meta's developer docs describe it as onboarding WhatsApp Business app users to the Cloud API. In practice, the number gets two doors that see the same conversation:
- The WhatsApp Business app on the rep's phone, as always.
- The official API, connected to a platform such as Sailer, which records messages, syncs with the CRM and sends at scale.
A message sent from the app shows up in the platform. A message sent from the platform shows up in the app. For the customer nothing changes: same number, same person.
Coexistence vs. a central number vs. unofficial tools
| Model | Rep keeps the number | History | Ban risk | Company visibility |
|---|---|---|---|---|
| Each rep on the app, no system | Yes | Stays on the phone | Low | None |
| One central company number on the API | No | Starts from zero | Low | High |
| Unofficial tool (QR code) | Yes | Depends on the tool | High | Partial |
| Coexistence, app + official API | Yes | Up to 6 months synced | Low | High |
Meta's requirements for coexistence
Check these before you plan the rollout. They come from Meta's developer documentation, checked in October 2026.
| Requirement | What Meta asks for |
|---|---|
| App | WhatsApp Business (not regular WhatsApp), version 2.24.17 or later |
| Who connects it | A Meta Tech Provider or Solution Partner, through Embedded Signup |
| History | 1:1 messages from the last 6 months can be synced; the provider has 24 hours to run the sync |
| Phone activity | The primary phone must be opened regularly; after about 14 days of inactivity the number is disconnected from the API |
| Linked devices | Supported, except WhatsApp for Windows and WearOS, whose messages don't reach the API |
| Throughput | Numbers in coexistence have a fixed throughput of 20 messages per second |
If a rep uses regular WhatsApp on the number customers know, the first step is moving that number to the WhatsApp Business app. Coexistence only works from there.
What changes in the app
Some app features are switched off once the number is connected. Tell the team in advance so nobody thinks it's a bug:
- Disappearing messages are turned off in 1:1 chats.
- View once is disabled in 1:1 chats.
- Live location is disabled in 1:1 chats.
- Broadcast lists are disabled, and existing ones become read-only.
Broadcast lists were the workaround reps used to reach their book of accounts. With the API connected, that job moves to campaigns built on approved templates, segmented and tracked.
What stays in the app but doesn't reach the API
Some features keep working on the phone but the API can't see them: group chats, voice and video calls, catalog and orders, quick replies and away messages, channels, and business profile edits. If a meaningful part of your sales happens in groups, design for it.
Cost and the 24-hour window
Messages sent from the app stay free and, per Meta, aren't subject to the customer service window. Messages sent through the API follow Cloud API pricing: free-form text inside the 24-hour window, a paid template outside it. Our WhatsApp 24-hour window guide explains the rule.
How to connect a rep's number, step by step
The flow is short, and the rep is involved for a few minutes. With an accredited tech provider it goes like this:
- Prep. The company picks the Meta Business portfolio that will hold the numbers and checks that every rep is on an up-to-date WhatsApp Business app.
- Embedded Signup. In the provider's flow, the rep chooses to connect an existing app account and enters the number.
- Confirm on the phone. The rep gets a message from Meta's official account in the app, taps connect and confirms the link to the platform.
- Share history. The app asks whether to share chat history. Once confirmed, 1:1 chats from the last 6 months are synced.
- Verification code. The rep pastes the code into the flow and the connection is done.
- Sync and book of accounts. The provider imports history and contacts, and the platform links each conversation to the right record in the CRM.
The app itself has a disconnect option under the account settings, in Business Platform. That's why the internal policy needs to be clear from day one.
Pitfalls to avoid
- Company portfolio, not the rep's. Numbers should sit in a Meta Business portfolio the company controls, with a corporate email and more than one admin.
- Keep the phone active. A rep on vacation who doesn't open the app for two weeks can be disconnected. Agree on a routine, or use temporary coverage of the book.
- Groups aren't recorded. Whatever happens in groups doesn't reach the API. Decide what belongs there.
- One orchestrator per number. Each number runs through one provider on the API. If your CRM also sends messages, decide who triggers and who executes.
- Written policy. The rep's number becomes a company channel with customers. Put it in writing with legal and HR. See corporate WhatsApp and privacy.
From coexistence to sales governance
Connecting the number is the start. The value is in what the company can do next:
- Book of accounts tied to the CRM. Every customer has an owner, synced with Salesforce, HubSpot or the CRM you already run.
- Campaigns from each rep's number. Build a campaign once, and each message goes out from the owner's number. Replies land in the right conversation.
- Response time and overdue follow-ups. For the first time, measured per rep and per team.
- Continuity. When someone leaves or goes on vacation, the book changes hands with history intact.
- Copilot and analytics. AI summarizes chats, suggests replies, fills the CRM and scores every conversation against the playbook.
That's what Sailer Fleet adds on top of coexistence. Sailer AI is a CRM and AI agent platform for selling on WhatsApp: it connects the brand's numbers and every rep's number to the official API, puts AI agents and people in the same inbox, fills the CRM on its own and measures every conversation. Sailer is an official Meta Tech Provider.
Arco Educação: 125 consultants on their own numbers
Arco Educação serves more than 12,000 schools in Brazil and runs sales on Salesforce. Its consultants talked to schools from their own WhatsApp, and every outreach took about 3 minutes per message to copy, paste and attach.
With coexistence and Fleet:
- The pilot started with 11 consultants and reached 125 of 135 in two months.
- 16,500 messages went out from the consultants' own numbers to more than 8,000 schools.
- The reply rate was 26%, a number nobody measured before.
- 825 hours saved, roughly R$43,000 in two months.
No consultant changed number or phone. Read the Arco Educação case and our guide to managing your sales team's WhatsApp.
Frequently asked questions
What is WhatsApp coexistence?
It's the Meta feature that lets the same number run on the WhatsApp Business app and the official API at once. The rep keeps using the phone with the same chats, while the company records messages, syncs them to the CRM and sends campaigns from that number, all within Meta's rules.
Do I lose chat history when I connect a number to the API?
No. Chats stay in the app, and Meta lets the platform sync 1:1 messages from the last 6 months if the number's owner agrees to share history. Group messages aren't included in the sync and remain only in the app, so plan around them if groups matter.
Does coexistence work with regular WhatsApp?
No. It requires the WhatsApp Business app, version 2.24.17 or later. If a rep uses regular WhatsApp on the number customers know, move that number to WhatsApp Business first. After that, an accredited Meta provider connects it to the API through Embedded Signup in a few minutes.
What stops working in the app?
In 1:1 chats, disappearing messages, view once and live location are turned off. Broadcast lists are disabled too, and existing ones become read-only. Groups, calls and the catalog keep working in the app, but they don't pass through the API, so they won't show up in the platform.
Do I need a Meta partner to use coexistence?
Yes. The connection runs through the Embedded Signup flow of a Meta Tech Provider or Solution Partner. Sailer AI is an official Tech Provider and handles the connection as part of a Fleet rollout, together with the CRM integration and the usage policy for the team.
