WhatsApp Coexistence — what it is and how it differs from “pure” API
For years the tradeoff was brutal: stay on the WhatsApp Business app (easy, on the phone, no real automation) or migrate to the Cloud API (templates, workflows, team inbox) and lose the app on that number.
WhatsApp Coexistence is Meta’s answer: the same number can live in the app and on Cloud API at the same time.
What Coexistence is (in one sentence)
It’s the official hybrid mode where your WhatsApp Business App number connects to the WhatsApp Business Platform (Cloud API) without killing the app or throwing away your chat history.
How it works in practice
- The team can keep replying from the phone (Business app).
- The same line feeds a shared inbox, workflows, templates, and agents (via platforms like Wroups on Cloud API / Kapso).
- Messages sync: what goes out or comes in on one side shows up on the other.
- You can import recent history (Meta typically allows ~6 months of 1:1 chats during onboarding) so you don’t start from zero.
In Wroups, WhatsApp onboarding is built around that hybrid model (coexistence) — for SMBs that can’t “turn off the business phone” overnight.
Coexistence vs dedicated Cloud API
| Coexistence (app + API) | Dedicated Cloud API | |
|---|---|---|
| Number | The one you already use in WhatsApp Business App | Often a new API number |
| Mobile app | You keep using it | You don’t run that number from the classic Business app |
| Prior history | Can be preserved / synced | Doesn’t inherit app chat history |
| Automation | Yes, via Cloud API | Yes, via Cloud API |
| Best for | SMBs that need phone + system hybrid | High-volume, API-first ops |
Both use Cloud API under the hood. Coexistence isn’t “another API” — it’s an onboarding/usage mode of the same Cloud stack, sharing the number with the app.
What Coexistence is not
- Not an unofficial hack (weird Multi Device / shady APIs). It’s a Meta product.
- It doesn’t remove template rules, 24-hour windows, or conversation costs when you send via API.
- Some app features may be limited when coexisting with API (Meta documents restrictions; review them when you connect).
- You still need a provider / platform (BSP or a stack like Kapso + Wroups) to run inbox and automation seriously.
How it fits with Wroups
- Connect WhatsApp from onboarding / Settings.
- Choose the setup flow (including coexistence when it applies).
- The team sees conversations in the shared inbox; workflows and templates use the API.
- If someone replies from the Business app, that outbound can also show up in the centralized operation.
Read more in Connect & status or get started at msg.wroups.com/signup.
7 tips before WhatsApp service replies stop being free
Meta will charge for service messages (and in-window utility) from October 1, 2026. Use this summer to cut chatter, tighten saved replies, and measure what you actually send.
Workflows vs manual WhatsApp — when to automate
Not everything should be a bot. How to decide what to automate with workflows and what to leave to the team.