WhatsApp coexistence: keep the app. Add the CRM.
Coexistence lets your WhatsApp Business app and the Cloud API share one number — the app stays on your phone, while your team gets a shared inbox, automation, and broadcasts on the same chats. This guide covers how it works and, just as carefully, what changes in your app — all of it from Meta's own documentation, before you connect anything.
The basics
One number. Two surfaces. Chats mirrored both ways.
Until recently, connecting a number to the WhatsApp API meant the app on your phone stopped working — the single biggest reason small businesses never made the jump. Coexistence removes that trade: the app keeps running, and every message — sent from the phone or from the CRM — shows up on both sides in real time. You connect by scanning a code from the app, the same way you link WhatsApp Web.
Coexistence is not available in Trinetra yet — it's in active development, and this guide is here first so you can decide with the full picture.
What you gain
The app for you. The CRM for the team.
-
The app keeps working
Your WhatsApp Business app stays live on the same number. Reply from your phone at a customer visit; your team replies from the CRM — same conversation.
-
A shared inbox for the team
Every chat lands in one inbox with assignment, labels, and notes — instead of living on one person’s phone.
-
Automation and broadcasts
Welcome flows, auto-replies, and template broadcasts run from the CRM while you keep chatting from the app.
-
Up to 6 months of history
Per Meta’s documentation, coexistence can import up to 6 months of your 1:1 chat history — a one-time import that must run within 24 hours of connecting.
What changes in your app
The fine print of coexistence — in full.
Coexistence is not a free lunch. When a number pairs with the Cloud API, Meta switches off a specific set of WhatsApp Business app features, keeps a few things phone-only, and adds rules for keeping the connection alive. None of this is a Trinetra thing — it applies whichever platform you connect — and none of it is secret: it's in Meta's own documentation, gathered here in one place. Read it before you connect a number — with anyone.
See the full list of what changes in your app We'd rather you read this before you connect — not after.
App features that switch off
Per Meta’s documentation, these WhatsApp Business app features stop working while the number is paired with the API:
- Labels → In Trinetra: conversation labels in the shared inbox.
- Quick replies → In Trinetra: canned replies, shared across the team.
- Greeting and away messages → In Trinetra: welcome flows and auto-replies.
- Catalog and orders → No replacement in Trinetra today. If catalog orders run your business, coexistence is the wrong tool — a second number is the better setup.
- Broadcast lists become read-only — new lists can’t be created → In Trinetra: broadcasts with per-recipient delivery status.
- Disappearing, view-once, and live-location in 1:1 chats → No equivalent — these switch off in 1:1 chats.
Stays on your phone only — the CRM won’t see it
These keep working in the app but never appear in the CRM:
- Group chats — they keep working on your phone, but per Meta’s documentation they don’t sync to the API
- Status posts — keep posting from the app; nothing changes
- Calls — Meta’s documentation lists voice and video calling as unsupported with coexistence; treat calling on the paired number as unavailable until Meta clarifies
Rules for staying connected
Per Meta’s documentation:
- Open the app regularly — the pairing disconnects after approximately 14 days of app inactivity. Because “approximately” is doing real work in that sentence, our advice is stricter: open the app at least once a week
- Don’t uninstall the app — uninstalling disconnects the number from the API
- WhatsApp Web and desktop sessions log out when you connect — you re-link them afterwards (up to 4 companion devices)
- Disconnecting is done inside the app: Settings → Account → Business Platform (path as of July 2026)
Limits
Also per Meta’s documentation:
- Message throughput is capped at 20 messages per second on a coexistence number
- History import is one-time: up to 6 months of 1:1 chats, requested within 24 hours of connecting. Media older than 14 days imports as text without the file. Group chats are excluded
- Standard business verification is listed as not supported for coexistence numbers — partner-led verification or Meta Verified are the documented routes
- Meta’s documentation does not state whether the switched-off app features come back after you disconnect. Treat the trade-offs as one-way until Meta documents otherwise
Sourced from Meta's official documentation, checked 29 July 2026. Meta can change this behaviour — confirm against Meta's current docs before you rely on it.
If your business runs on catalog orders, WhatsApp groups, or calls on this number, coexistence is the wrong tool today — a second number on the full API, or staying on the app, will serve you better. We'll tell you that in-product too.
Which setup fits you
Coexistence vs full API vs app-only — honestly.
-
Coexistence
App + CRM on one number
- Keep chatting from your phone
- Team inbox, automation, broadcasts on the same chats
- Up to 6 months of history comes across (one-time)
- Trade-offs: catalog, groups sync, calls, 20 msg/sec cap
Fits: owner-led businesses where the phone is still the main tool.
-
Full API
CRM-only number
- No app on the number — CRM is the single surface
- Full throughput tiers, standard business verification
- No 14-day app rule, no device juggling
- Trade-off: nobody replies from the phone app anymore
Fits: teams that have already moved off the founder’s phone.
-
App only
What you have today
- Catalog, groups, calls, status — everything works
- One phone, one person replying
- No shared inbox, no automation, no broadcasts at scale
- History lives on that one device
Fits: solo sellers with volumes one person can handle.
Where Trinetra is today
Not available yet — and we'd rather say so.
Coexistence is not available in Trinetra yet. It's in active development, and the Cloud API foundation it depends on — Embedded Signup connect, the shared inbox, broadcasts, and automation — is already live. Until it ships, connecting a number to Trinetra works the standard Cloud API way, which replaces the app on that number.
When coexistence lands in Trinetra, this page's trade-off list is the one we'll ask you to read in-product before you connect — same list, same honesty, no surprises afterwards.
Coexistence is planned to reach existing Trinetra workspaces first — a trial started today is a head start, not a dead end.
FAQ
Coexistence, answered straight.
What is WhatsApp coexistence?
Coexistence is a Meta capability that lets one phone number run on the WhatsApp Business app and the WhatsApp Cloud API at the same time. Chats mirror both ways: a message sent from the app shows up in the connected CRM, and a CRM reply shows up in the app — one number, two surfaces.
Does Trinetra support WhatsApp coexistence today?
Not yet. Coexistence support is in active development at Trinetra, and the Cloud API foundation it depends on is already live. Email us for a launch note, or start a trial today — coexistence is planned to reach existing workspaces first.
Will I lose my chat history when I enable coexistence?
Your existing chats stay on your phone either way. Per Meta’s documentation, up to 6 months of 1:1 history can additionally be imported into the connected platform — a one-time import that must be requested within 24 hours of connecting. Group chats are excluded, and media older than 14 days imports as text without the file.
What stops working in the WhatsApp Business app with coexistence?
Per Meta’s documentation: labels, catalog and orders, quick replies, greeting and away messages switch off; broadcast lists become read-only; disappearing, view-once, and live-location messages switch off in 1:1 chats. Group chats keep working on the phone but don’t sync to the API. The complete grouped list is on this page under “What changes in your app”.
Why does a coexistence number disconnect after about 14 days?
Meta’s documentation states the pairing ends after approximately 14 days without the WhatsApp Business app being opened, and that uninstalling the app disconnects the number immediately. Our advice is stricter than the documented rule: open the app at least once a week and stay clear of the line.
Can I still use WhatsApp Web and desktop with coexistence?
Yes — with one bump at the start. Per Meta’s documentation, existing Web and desktop sessions are logged out when the number connects to the API; you re-link them afterwards, up to 4 companion devices.
Is coexistence better than moving fully to the Cloud API?
It depends on whether the phone app is still part of how you work. Coexistence keeps the app alive but caps throughput at 20 messages per second and, per Meta’s documentation, doesn’t support standard business verification. A full API setup has none of those limits — but nobody replies from the phone app anymore. The decision table on this page compares the three setups honestly.
Decide with the full picture.
Get one email when coexistence goes live in Trinetra — or start on the Cloud API today and be first in line.