WhatsApp Coexistence: Keep the App and Add Automation

Summary

WhatsApp Coexistence connects the number you already use in the WhatsApp Business app to the Cloud API. The app keeps working on your phone, while your team gets a shared inbox, simple automations and CRM links through Saysimple. In one-to-one chats, view once media, live location and disappearing messages stop working, and broadcast lists become read-only.

TL;DR

Best fit: teams that have outgrown one phone but are not ready to leave the app.
The trade-offs: view once media, live location and disappearing messages stop working in one-to-one chats, broadcast lists become read-only and group chats are not synced to the platform.
Check first: that your app is on version 2.24.17 or higher, and keep the phone in use, because an inactive app can disconnect the link.
Meta's onboarding flow includes a message history synchronization step; confirm with Saysimple what is imported for your number.

The moment WhatsApp on one phone stops being enough

Somebody on the team is running WhatsApp for the business off their own phone. It probably started as the fastest way to answer customer questions and it worked, right up until the number of conversations grew. Now a colleague can't see what was already answered, an out of office day means messages sit unread, and nobody has a clean way to hand a conversation to someone else without forwarding screenshots.

That's a familiar shape of problem. Saysimple has seen it before, most clearly with Pean Holiday Park, a Frisian holiday park that ran WhatsApp marketing through the free consumer app until it hit a hard wall: a 256-contact send limit, and only one employee able to manage the channel at a time. Moving that number onto a real platform, rather than staying stuck in the consumer app, is exactly the kind of jump Coexistence is meant to make less disruptive.

WhatsApp Coexistence is built for exactly that gap: it adds the structure a growing team needs without asking anyone to abandon the app they already know. Rather than migrating a number off the app entirely, Coexistence connects it to the Cloud API alongside the app, so both keep running on the same number at once.

What WhatsApp Coexistence actually connects

Coexistence is not a separate product decision from moving to the API outright, it's a specific configuration: your existing WhatsApp number, already active in the WhatsApp Business app, gets linked to the Cloud API. On Saysimple, that link means the number keeps working in the app on the phone it's on, while the same number is simultaneously connected to the platform. Messages sent through the API show up in the WhatsApp Business app, and messages sent from the app show up on the Saysimple platform. Nobody has to choose one channel over the other for a given conversation.

What changes once the link is active

A few things about the one-to-one chat experience shift once Coexistence is switched on. According to Meta, view once media, live location and disappearing messages stop working in one-to-one chats. Broadcast lists become read-only, so new ones cannot be created. Group chats are not synchronized to the platform, which means they stay in the app. Calls keep working in the app as before.

Chat history is a separate question. Meta's onboarding flow includes a step in which the message history is synchronized, so history can be shared with the platform. What exactly is imported into Saysimple for your number is something to confirm with Saysimple before you activate.

What the team actually gains

The upside sits on the Saysimple side of the connection. Conversations become visible to more than one person, so a colleague can pick up where another left off instead of everyone crowding one screen. Incoming questions can be split across the team rather than funneled through whoever happens to have the phone that day. The Cloud API link also opens the door to automation, a no-code WhatsApp flow for a welcome message or an away message when nobody's available, plus integrations that put WhatsApp conversations next to the CRM or helpdesk record they belong to, instead of leaving them stranded in a chat app nobody else can search.

Aspect	WhatsApp Business app alone	App plus Saysimple Coexistence
Who can reply	One phone, one person at a time	The whole team, through a shared inbox
Automated replies	Basic away message only	Welcome messages, away messages, simple flows
CRM or helpdesk data	Not connected	Linked through integrations
View once media, live location, disappearing messages	Available	Not available in one-to-one chats once linked
Broadcast lists	Available	Read-only, new ones cannot be created
Group chats and calls in the app	Available	Calls keep working in the app, group chats are not synced to the platform

What to check before activating

Not every number qualifies automatically. It needs to already be active in the WhatsApp Business app, and the link itself runs through the Cloud API, so confirm that before starting. Meta's documentation names two things to verify: the business must use WhatsApp Business app version 2.24.17 or higher, and the throughput is fixed at 20 messages per second for a number used on both the app and the Cloud API. Eligibility itself is confirmed during onboarding. One more detail from Meta: messages you send from the app do not open or extend the Cloud API 24-hour customer service window, and they are not priced as Cloud API messages.

Beyond eligibility, settle four things upfront: which number you're linking, that you're deliberately choosing the Cloud API route rather than a full migration, which colleagues need access once the shared inbox is live, and which automations or integrations are worth setting up on day one rather than added later. Keep the phone in use as well, because the connection can be disconnected after about two weeks without activity in the app on the phone.

Who this setup actually fits

Coexistence makes the most sense for a business that wants to keep its existing number and its existing WhatsApp Business app exactly as it is, but has outgrown running everything through one device. That's a company where more than one person needs to answer questions, where an away message or a welcome flow would save real time, or where WhatsApp conversations need to land next to the customer record they already keep in a CRM or helpdesk. It's not aimed at businesses ready to leave the consumer app behind entirely, that's a different, more complete migration to the API.

Frequently asked questions

Can I keep using the WhatsApp Business app?

Yes. The number stays active in the app on your phone, and the same number is also connected to Saysimple.

Which features stop working?

In one-to-one chats: view once media, live location and disappearing messages. Broadcast lists become read-only and group chats are not synced to the platform. Calls keep working in the app.

Does my chat history sync to Saysimple?

Meta's onboarding flow includes a step in which the message history is synchronized, so history can be shared with the platform. What is imported into Saysimple for your number is something to confirm with Saysimple.

Closing thoughts

The appeal of WhatsApp Coexistence is that it doesn't force a choice between the app your team already knows and the structure a growing number of conversations actually needs. The number stays the same, the app keeps working, and the parts that were genuinely missing, shared visibility, automation, a link to the rest of your systems, get added on top rather than swapped in.

Ready to see what that looks like for your own number? Book a demo and we'll walk through the setup together.

Relevant posts

Sources

Meta for Developers: Onboard WhatsApp Business app users. Meta's documentation on connecting WhatsApp Business app numbers to the Cloud API. It covers the requirements (app version), throughput, feature changes and the message history synchronization step described above.