What is Coexistence?

Coexistence allows an account running on WhatsApp Business App to be connected to the API side via Embedded Signup. In this model, scanning a QR code is not required.

How it differs from the classic QR flow

In QR-based methods, device connectivity and session management may be more fragile. In the Coexistence model, OAuth-based onboarding provides a more controlled connection experience.

• Fetch OAuth URL
• User authorizes in popup
• Finalize connection with code and state

Integration steps

1. Create auth URL

Call the auth endpoint with hotel context. At this step, hotelId is embedded into state.

2. Authorize through popup

The user shares the WhatsApp Business account and returns via callback.

3. Connect call

Connection is finalized with code + state and a new social record is created.

Critical frontend checks

• Popup blocker handling
• Timeout handling
• User-friendly error messages
• Refresh social list immediately after success

Why provider distinction matters

Different providers under the same platform (meta, meow, coex) require different behaviors. For example, for Coexistence accounts, a disconnect flow can be more appropriate than "pause/resume".

Migration strategy

The following approach is safe in production:

• Route new connections to the WhatsApp API flow
• Separate legacy accounts with provider labels
• Train operations team for the new action set

Conclusion

Coexistence shortens onboarding time while improving connection quality. With correct UI distinctions and provider-based actions, teams can run more predictable operations.