Last updated: August 4, 2026.

Yes. An eligible number already registered in WhatsApp Business app 2.24.17 or later can connect to Cloud API through Meta’s existing-number onboarding. One-to-one app replies can continue, but the provider, 24-hour synchronization deadline, throughput limit, linked-device reset, and unsupported-feature rules still apply.

Meta’s current documentation calls this flow “Onboard WhatsApp Business app users” and notes that it is sometimes referred to as “Coexistence” in support channels and Partner documentation. It is a customized Embedded Signup path for an existing Business app account and number, not a separate Meta product name and not an unrestricted promise that every app feature or message type will synchronize.

This implementation guide owns the eligibility, setup, synchronization, limits, testing, and offboarding questions. CampaignHQ is a Meta Tech Partner; for product capabilities and the buyer-facing workflow, use the CampaignHQ WhatsApp coexistence page.

How coexistence onboarding works

Meta enables coexistence through Embedded Signup for existing WhatsApp Business app users. The exact screens can change as Meta updates the flow, but the current official sequence has five practical stages.

1. Start Embedded Signup through your provider

The business starts the WhatsApp connection from a provider that has configured Embedded Signup for existing WhatsApp Business app users. The flow should show an option to connect an existing Business app account rather than requiring a new API-only number.

2. Choose the existing Business app number

The business enters the phone number already registered in the WhatsApp Business app. Meta then sends a verification message from the official Facebook Business Account to the app.

3. Approve the Business Platform connection

Inside the WhatsApp Business app, the business taps Connect, chooses Connect to the Business Platform, and confirms the connection. The business can also choose whether to share chat history with the provider.

4. Complete verification

The business copies and enters the verification code, then completes the remaining Embedded Signup steps. The provider receives the asset information needed to finish Cloud API onboarding.

5. Synchronize promptly

Meta gives the provider 24 hours after onboarding to initiate contact and message-history synchronization. The Business app should remain open during this process. Sync time depends on history size, internet speed, and how quickly the provider processes the required webhooks.

What syncs between the Business app and Cloud API?

One-to-one chats

Supported one-to-one conversations can appear across the app and the connected platform. When the business permits history sharing, Meta can synchronize eligible messages from the most recent 180 days.

New messages sent from the Business app

Messages sent from the Business app can generate message-echo webhooks. A correctly implemented provider can use those webhooks to show app replies inside the connected conversation timeline.

Contacts

The initial contact synchronization can be requested once after onboarding. After that initialization, additions, edits, and removals to WhatsApp contacts can continue to generate contact-state webhooks. This is different from message-history import, which is a one-time synchronization step.

Group chats

Group chats do not synchronize to Cloud API. They can continue inside the Business app, but agents should not expect those conversations to appear in the connected team inbox.

Recent media history

History can include media placeholders. Meta provides media asset IDs separately only for media sent within 14 days before onboarding, even though eligible text history can cover up to 180 days.

History sharing is optional. If the business declines it, the provider can still complete onboarding, but the connected platform will begin without the historical message set. Decide this before the signup window because history synchronization must be initiated promptly.

What changes or does not carry into Cloud API?

Coexistence does not make every Business app feature available through the API. Meta’s current feature comparison identifies several boundaries:

• Group chats: continue in the Business app but do not synchronize to Cloud API.
• Broadcast lists: broadcast lists are disabled for new sends in the Business app, and existing lists become read-only. API template campaigns replace this function for scaled messaging.
• Disappearing messages: are turned off for individual chats after onboarding.
• View-once messages and live location: are disabled for individual chats.
• Voice and video calls: do not change inside the Business app, but they are not provided through this Cloud API coexistence sync.
• Catalog, orders, status, quick replies, labels, and the business profile: remain available in the Business app, but are not synchronized as Cloud API features through coexistence.

Linked devices also deserve a preflight check. Meta supports up to four companion clients, but all companion apps are unlinked during onboarding and must be re-linked afterward. Meta currently excludes WhatsApp for Windows and WhatsApp for WearOS from supported coexistence companion clients.

Requirements and operating limits

A successful coexistence setup depends on both the business account and the provider integration.

Business-side requirements

• An existing WhatsApp Business app account and phone number, not a personal WhatsApp account.
• WhatsApp Business app version 2.24.17 or higher.
• Control of the primary phone and access to the verification message.
• A decision about whether the provider may synchronize recent one-to-one chat history.
• Time to keep the app open while initial synchronization completes.

Provider-side requirements

• The provider must be a Meta Solution Partner or Tech Provider.
• Its Embedded Signup implementation must support onboarding existing Business app users.
• Cloud API, session logging, and required webhook subscriptions must be configured.
• The provider must process contact sync, history sync, and future Business app message echoes correctly.

Provider implementation checks

The provider should validate the connection as an existing-Business-app onboarding, not run the ordinary new-number registration sequence. Meta’s current flow returns the usual business account, phone-number, and token assets, but the number is already registered. Repeating phone-number registration can break the intended path.

Before a production cutover, the provider should be able to show that it:

• uses the current Embedded Signup flow and the correct existing-app feature option;
• records session information and handles the required advanced-access permissions;
• subscribes to history, app-state-sync, message-echo, and account-update webhooks;
• stores app-originated message echoes without creating duplicate customer messages;
• distinguishes the one-time initial synchronization from future contact-change webhooks;
• can confirm that the phone number is both on the Business app and connected through Cloud API;
• surfaces synchronization failures before the 24-hour deadline expires; and
• has a documented offboarding and reconnection procedure.

Payment ownership should also be clear before signup. A Tech Provider implementation may require the business to add its payment method, while a Solution Partner may use an approved credit arrangement. If an older partner’s shared credit line is still attached, clear that relationship first rather than treating the resulting error as a phone-verification problem.

What a successful signup screen does not prove

Completing Embedded Signup confirms authorization and asset selection. It does not by itself prove that history was approved, that synchronization started within 24 hours, that app message echoes are being processed, that supported companions were re-linked, or that an API template can be delivered. Treat each of those as a separate acceptance check.

Similarly, a message visible in the Business app does not prove that the provider received its webhook, and a message visible in the API inbox does not prove that historical media is available. The go-live test later in this guide checks both directions and separates connection success from synchronization success.

Embedded Signup version deadline

Meta’s current documentation warns that Embedded Signup v2 will be deprecated on October 15, 2026 and directs integration owners to move to v4 before that date. This is primarily a provider responsibility, but buyers should ask which Embedded Signup version supports their onboarding flow and confirm that an older implementation will not interrupt future connections.

Throughput limit

Meta states that numbers used by both the Business app and Cloud API have a fixed throughput of 20 messages per second. This protects compatibility with the Business app, but it also means coexistence may not fit every very-high-throughput messaging program.

If the business previously worked with another partner and still shares that partner’s credit line, switching can trigger an onboarding error. Resolve the old partner or credit-line relationship before planning the cutover.

Pricing and the customer service window

Meta treats app-sent and API-sent messages differently after coexistence onboarding:

• Messages sent by the business from the WhatsApp Business app continue to be free under Meta’s coexistence pricing treatment.
• Messages sent through Cloud API are subject to Meta’s current WhatsApp Business Platform pricing rules.

The 24-hour customer service window applies to Cloud API messaging. Business app messages do not create, extend, or change Cloud API customer service windows or Cloud API pricing.

There is one cutover edge case to plan for. If a customer sent a message just before the business was onboarded to Cloud API, that pre-onboarding message did not open an API customer service window. The first Cloud API reply after onboarding must therefore use an approved template. A new customer message received after onboarding opens the normal window.

This creates a practical reporting requirement: separate app activity from Cloud API delivery and template usage. For current message-category rules, use the WhatsApp Business pricing update and verify the latest Meta pricing documentation before forecasting usage.

Technical go/no-go checks before onboarding

Choose coexistence only after the current number and workflow pass these implementation checks:

• Proceed when the number is already on the Business app, version 2.24.17 or later is installed, the team accepts the 20-messages-per-second limit, and group-chat synchronization is not required.
• Pause when a previous provider or shared credit-line relationship is unresolved, the primary phone is unavailable, or the history-sharing decision is unclear.
• Move to architecture review when the operation may need more than 20 messages per second, depends on app broadcast lists or disappearing/view-once content, or requires group chats inside the API inbox. Use the coexistence vs API-only peak-load guide to model whether coexistence, an API-only number, or a phased plan fits.

Also document who controls the primary phone, which companion devices must be re-linked, whether eligible history should be shared, and who will monitor synchronization webhooks during the 24-hour window. These are operational prerequisites, not product-benefit questions.

Offboarding, reconnection, and provider changes

Coexistence is not guaranteed to stay connected through every device or account change. Meta states that changing devices, reinstalling, or re-registering the WhatsApp Business app can temporarily offboard the Cloud API companion. During reconnection, Cloud API messaging can pause, history does not synchronize, and companion devices may need to be linked again.

Meta supports automatic reconnection when the business accepts the pre-checked reconnection option, but the process can still take several minutes. Do not promise zero interruption. Schedule device changes outside active campaign windows and verify app, API, webhook, and companion-device status before resuming traffic.

To disconnect deliberately, Meta directs the business to Settings > Account > Business Platform in the WhatsApp Business app. Use a controlled offboarding or provider-migration plan rather than disconnecting during active campaigns. The WhatsApp provider migration guide covers the broader switching checklist, and Meta’s reconnection documentation explains the device-change behavior.

Troubleshooting the initial connection

If signup finishes but contacts, history, or message echoes do not appear, check the sequence instead of immediately repeating onboarding:

1. Confirm the phone number reports the Business app and Cloud API connection state expected by the provider.
2. Confirm that contact and history synchronization were initiated within 24 hours.
3. Keep the primary Business app open while the initial synchronization runs.
4. Check that the provider processes history, app-state-sync, and message-echo webhooks.
5. Confirm whether the business declined history sharing; the connection can succeed without importing old chats.
6. Resolve any previous-partner credit-line conflict before repeating Embedded Signup.

If the 24-hour synchronization deadline was missed, Meta requires offboarding and a fresh onboarding flow. Repeating individual sync requests is not a substitute because the initial contact and history requests are one-time operations for that onboarding.

Pre-onboarding checklist

1. Confirm the account type. The number must already be on the WhatsApp Business app.
2. Update the app. Use version 2.24.17 or higher.
3. Confirm the provider flow. Ask whether it supports existing Business app users and the current Embedded Signup version.
4. Map current workflows. List who replies from the phone, which linked devices are used, and whether group chats or app broadcast lists are operationally important.
5. Decide on history sharing. Confirm whether up to 180 days of eligible one-to-one history should be synchronized.
6. Review limits. Accept the 20-messages-per-second throughput and unsupported-feature boundaries.
7. Clear partner conflicts. Resolve old partner or credit-line relationships before signup.
8. Choose a quiet window. Keep the primary app open and allow time for synchronization.
9. Plan the go-live test. Test inbound messages, app replies, message mirroring, agent replies, one approved template, and reporting before starting campaigns.

Assign one technical owner and one business owner for the cutover. The technical owner verifies assets, webhooks, synchronization, and delivery. The business owner verifies the primary phone, history-sharing choice, linked devices, and staff readiness. Record timestamps for signup and synchronization so the 24-hour deadline is visible to both owners.

A practical go-live test

Do not treat a completed signup screen as proof that coexistence is operational. Run a short end-to-end test:

1. Send a customer message to the business number after Cloud API onboarding.
2. Reply from the WhatsApp Business app and verify that the reply appears in the connected platform timeline.
3. Reply from the team inbox and confirm the customer sees the same business number and conversation thread.
4. Verify synchronized contacts and the expected recent one-to-one history.
5. Send one approved API template and verify delivery status and pricing classification.
6. Re-link supported companion devices and confirm that staff can continue their approved workflows.

If any step fails, pause campaign traffic. Check the primary app, provider webhooks, history-sync status, account connection state, and any previous-partner conflict before retrying.

Frequently asked questions

Can an existing WhatsApp Business app number connect to Cloud API?

Yes, if the number is eligible, already registered in the WhatsApp Business app, and the app is version 2.24.17 or later. The connection uses Meta’s Embedded Signup flow for existing Business app users.

What happens if synchronization is not started within 24 hours?

Meta requires the provider to initiate contact and history synchronization within 24 hours of onboarding. If that deadline is missed, the business must be offboarded and complete the onboarding flow again.

How much chat history and media can be synchronized?

If the business approves history sharing, up to 180 days of eligible one-to-one chat history can be synchronized. Media asset IDs are available only for media sent within 14 days before onboarding, and group chats are excluded.

What happens to linked devices during onboarding?

All existing companion apps are unlinked during onboarding. Supported companions can be linked again afterward, but Meta currently excludes WhatsApp for Windows and WhatsApp for WearOS from supported coexistence companions.

Does a Business app message open the Cloud API customer service window?

No. Messages sent from the WhatsApp Business app do not create, extend, or affect the Cloud API customer service window or Cloud API pricing.

Official sources

• Meta: Onboard WhatsApp Business app users
• Meta: Embedded Signup overview
• Meta: Embedded Signup version 4
• Meta: Reconnect offboarded coexistence clients
• Meta: WhatsApp Business Platform pricing

Related CampaignHQ guides

• WhatsApp Business API setup guide
• How to migrate from one WhatsApp provider to another
• WhatsApp automation: benefits and examples

Written by CampaignHQ Team