WhatsApp Coexistence

How Coexistence mode works: using WhatsApp Business App and Cloud API on the same number.

Looking for the high-level overview first? Start with WhatsApp Coexistence and then return here for the implementation details.

What It Is

WhatsApp Coexistence allows an existing WhatsApp Business App number to be used with WhatsApp Business Platform (Cloud API) at the same time. This lets businesses keep in-app messaging workflows while also running API-based automation and integrations.

Why Teams Use It

  • Keep the existing business number, history, and app usage patterns.
  • Add API capabilities such as webhook integrations and scale messaging workflows.
  • Avoid forcing operational teams to abandon the WhatsApp Business App.

How Communication Works

Coexistence relies on mirrored delivery behavior between app and API channels:

  • Messages sent through API can appear in the WhatsApp Business App.
  • Messages sent from the WhatsApp Business App can be delivered to your webhook via smb_message_echoes events.

In Dualhook, your webhook receives message events directly from Meta via Webhook Override. Dualhook monitors management and health events for operational visibility.

Pricing Behavior

  • Messages sent in the WhatsApp Business App remain free.
  • Messages sent via Cloud API are billed under Meta platform pricing.
  • Template and policy rules still apply for API-initiated conversations.

Dualhook billing remains separate from Meta message billing.

Linked Devices

Before onboarding, businesses can use up to four companion/linked devices on the app side. After coexistence onboarding, companion apps are unlinked and only supported companion clients should be re-linked.

  • WhatsApp for Windows and WearOS companion clients are not supported in this flow.
  • Unsupported companion clients may not generate smb_message_echoes.
  • If echoes are missing, your backend may not mirror those app-originated messages.

Functional Limitations

  • Standard business verification is not supported for coexistence numbers.
  • OBA (blue badge) is not supported on coexistence numbers.
  • The WhatsApp Business Calling API is not available for coexistence numbers. This includes both Graph API/WebRTC calling and SIP calling integrations. Voice and video calls continue to work normally in the WhatsApp Business App, but they are not exposed through the Calling API or calls webhooks.
  • Calling health values such as can_receive_call_sip = BLOCKED and errors 138024 or 138025 are expected on coexistence connections. They do not affect messaging or in-app calls, and SIP cannot be enabled to clear them while the number remains in coexistence mode.
  • Direct migration between WABAs is not supported in typical coexistence flows.
  • Coexistence is not compatible with unofficial WhatsApp APIs.

If verification or badge requirements are critical, evaluate Meta Verified for Business where applicable.

Regional Availability

Coexistence onboarding availability is region-dependent. Check Meta's current supported/restricted region list before planning rollout.

Operational Notes

  • Do not uninstall the WhatsApp Business App after coexistence setup — doing so can break the connection state.
  • Open the WhatsApp Business App at least once every 13 days to keep coexistence active. See 13-Day Heartbeat.
  • Dualhook triggers Meta's separate one-time contact sync first and history sync second after Webhook Override is accepted. If Meta rejects one request, Dualhook still attempts the other in the documented order because both must be requested within 24 hours. Keep WhatsApp Business open while Meta prepares the sync. The resulting smb_app_state_sync and history payloads go directly to your endpoint, and history is only delivered if the business chose to share it during onboarding.

Eligibility

Coexistence is intended for businesses already actively using the WhatsApp Business App. Newly created app accounts may not be immediately eligible for platform onboarding.

  • In many onboarding flows, the number is expected to have at least 7 days of active WhatsApp Business App usage.
  • Use the latest WhatsApp Business App version on a device that can complete QR-based signup when required.
  • Meta eligibility can depend on account tenure, quality, and readiness signals.

Account-Selection Caveat

Choose the owning Meta Business Portfolio carefully during onboarding. In many coexistence flows, the selected business ownership context cannot be changed after registration without rework.

One-Way Onboarding

Coexistence onboarding is designed for numbers already registered on the WhatsApp Business App and moving into app+API coexistence. It is not the reverse path for taking an already API-only number and registering it in the app through coexistence.

Disconnecting or Rolling Back

A number can be disconnected from platform coexistence via app/business settings, but this should be treated as a controlled change. Before disconnecting:

  • Align app team and API/integration team.
  • Review webhook and data implications.
  • Pause automations that depend on platform events.

Related

  • 13-Day HeartbeatWhy the WhatsApp Business app must be opened every 13 days and how Dualhook tracks it.
  • WhatsApp Webhook OverrideHow Dualhook uses WhatsApp Webhook Override to route supported customer-path webhooks directly from Meta to your server.
  • Meta BSUID, Usernames & Contact Book Transition GuideOverview of Meta's WhatsApp BSUID rollout: usernames, contact book behavior, parent BSUIDs, API recipient support, webhook changes, and migration timeline.
  • WhatsApp Embedded Signup GuideThe vendor-neutral implementer's guide to Meta's Embedded Signup flow: prerequisites, the exact client and server calls, Coexistence, v4, and what breaks in production.
  • How to Leave Your WhatsApp BSP and Own Your WABAMigrate a WhatsApp business phone number away from a Solution Partner: what Meta preserves, what resets, the prerequisites, billing during migration, and the Coexistence caveat.
Browse more docsStart Free Trial