Categories Alternatives Whatsapp Marketing

WhatsApp Coexistence: Existing Number Setup and Limits

WhatsApp coexistence with the Business app and Cloud API on one number

Last updated: September 15, 2026.

Yes. You can connect an eligible WhatsApp Business app number to Cloud API and keep replying from your phone. Your provider must support Meta’s existing-number signup flow. Before connecting, check the app version, decide whether to share chat history, and confirm how your team will test synchronization and delivery afterward.

Meta calls this flow “Onboard WhatsApp Business app users,” often shortened to “coexistence.” It connects an existing Business app account to Cloud API. It does not transfer every app feature into your provider’s platform.

Use this guide to prepare your number and check the connection before campaigns begin. CampaignHQ is a Meta Tech Partner offering Email + WhatsApp retention automation. See the CampaignHQ WhatsApp coexistence page for its shared-inbox and automation workflow.

How coexistence onboarding works

The Embedded Signup flow for existing WhatsApp Business app users has five practical stages. Meta may change the screens; your provider should guide you through its supported version.

1. Start Embedded Signup through your provider

Start the connection from your provider’s platform. Choose the option to connect an existing Business app account, not a new API-only number.

2. Choose the existing Business app number

Enter the number already registered in your WhatsApp Business app. Look for a verification message from the official Facebook Business Account inside the app.

3. Approve the Business Platform connection

In the app, tap Connect, then Connect to the Business Platform, and confirm. Choose whether to share your chat history with the provider.

4. Complete verification

Copy and enter the verification code, then finish Embedded Signup. Your provider receives the account identifiers and authorization code needed to connect Cloud API.

5. Synchronize promptly

Meta gives the provider 24 hours after onboarding to synchronize contacts and message history. Start immediately and keep the Business app open until the provider confirms completion. History size, internet speed and the provider’s processing speed affect how long this takes.

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

A webhook is an update Meta sends to your provider when something happens. A message echo reports a new reply sent from the Business app, so the provider can display that reply in its conversation timeline.

Contacts

The provider can request the initial contact import once. Later additions, edits and removals can trigger contact updates called app-state-sync webhooks. These ongoing updates are separate from the one-time history import.

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 you decline, the connection can still succeed, but old chats will not appear in the provider’s inbox.

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

Check your account first, then ask your provider to confirm its integration is ready.

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. Ask its technical owner to confirm that it:

  • supports existing Business app users in Embedded Signup and records the signup session;
  • skips phone-number registration, because this number is already registered;
  • processes history, contact-update, message-echo and account-update webhooks;
  • shows app replies without duplicating messages in the team inbox;
  • monitors synchronization and alerts you before the 24-hour limit; and
  • has an offboarding and reconnection procedure.

Confirm who pays Meta before signup. A Tech Provider flow may require your payment method; a Solution Partner may use a credit arrangement. If you still share a previous partner’s credit line, resolve that relationship first. It can cause a switching error that phone verification will not fix.

Check the provider’s Embedded Signup version

Meta directs providers using Embedded Signup v2 to migrate to v4. Ask your provider to confirm its upgrade plan against Meta’s current version documentation before scheduling onboarding. This is a provider-integration change, not a requirement to replace your Business app number.

Throughput limit

Numbers used by both the Business app and Cloud API have a fixed throughput of 20 messages per second. Confirm that your planned workload fits this limit.

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

If your workflow needs group chats in the API inbox, app broadcast lists, disappearing or view-once content, pause onboarding. Those features do not carry across as described above. If peak messaging volume may exceed the throughput limit, use the coexistence vs API-only peak-load guide to assess the operating model before setup.

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.

Reconnection can run automatically if you keep the pre-checked reconnection option and no other partner connects the account in the meantime. It can take several minutes. Schedule device changes outside active campaigns, then verify app, API and linked-device access 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 the inbox is incomplete, use the symptom to choose the next check:

  • No old chats: confirm that history sharing was approved and the provider received history webhooks. Acceptance of a sync request alone does not prove history was shared.
  • No app replies in the inbox: check message-echo processing and whether an unsupported companion device was involved.
  • Missing contacts: check the initial contact-sync request and app-state-sync webhooks.
  • No API delivery: ask the provider to verify the account connection state and whether an approved template is required.

If the 24-hour synchronization window was missed, Meta requires offboarding and a fresh signup flow. Initial contact and history requests are one-time operations for each onboarding; do not repeatedly submit them as a repair.

Assign cutover owners

Choose a quiet window and assign one technical owner and one business owner. The technical owner checks webhooks, synchronization and delivery. The business owner keeps the primary phone available, confirms the history-sharing choice, re-links supported devices and briefs staff. Record the signup time and synchronization completion time where both owners can see them.

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 a test fails, pause campaigns and give the technical owner the failed step, message identifiers and timestamps. Resume only after the same test passes.

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 the 24-hour synchronization window is missed?

Meta gives the provider 24 hours after onboarding to synchronize contacts and message history. If that window 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

Related CampaignHQ guides

Written by CampaignHQ Team

More From Author