WhatsApp Coexistence Mode: What UK Businesses Need to Know in 2026

WhatsApp's coexistence mode solves the dilemma that held many companies back from professionalising their customer service: can you keep WhatsApp Business on your phone while connecting the same number to Meta's official API? Yes. Since 2025 Meta has enabled this feature, which became available in the UK in 2026, and in this guide I break down what's allowed, what's not, and how to activate it without losing your chat history or risking a ban.

TL;DR

• Coexistence mode lets you use the WhatsApp Business app and the official API (Cloud API) on the same number, simultaneously.
• You don't lose contacts or conversations: up to 6 months of 1:1 chat history is synced.
• Some app features are disabled in 1:1 conversations: disappearing messages, view once, live location, and broadcast lists.
• Groups, status, and voice/video calls remain in the app but don't go through the API.
• You need to open the app roughly every 14 days to keep the connection alive.
• Voyia, our Meta-validated official API app, supports coexistence mode.

What is WhatsApp coexistence mode?

For years, choosing between WhatsApp Business (the free app) and the official API (Meta's Cloud API for automation and team-based customer service) was a one-way street. To join the API, you needed a new number or had to migrate your existing number and lose everything on your phone: conversations, saved contacts, the history your business spent years building.

Coexistence mode ends that dilemma. It lets you register the same phone number simultaneously on the WhatsApp Business app and Meta's API platform. In practice, your receptionist can keep replying from their phone as usual, while the same number feeds into a CRM, a chatbot, or a shared inbox for the whole team.

It's the missing bridge between manual and automated customer service. You no longer have to choose between "human on the phone" or "robot on the API" — you have both operating on the same number, with messages synced between the two ends. If you're still deciding between the two worlds, it's worth reading our comparison WhatsApp Business App vs Official API before proceeding.

How activation works in practice

Activation happens through Embedded Signup, Meta's official registration flow. Unlike traditional migration, here you explicitly choose "connect an existing WhatsApp Business app" rather than creating a number from scratch.

The onboarding step-by-step

1. Ensure your WhatsApp Business App is version 2.24.17 or higher (coexistence doesn't work with the personal WhatsApp app).
2. Have a Meta Business Portfolio (formerly Business Manager) set up.
3. Start the connection flow from your chosen API platform and grant permissions to Meta.
4. Select your business portfolio and the option to connect an existing app.
5. Enter the number and scan the QR Code displayed on screen with the phone where the app is installed.
6. Choose the chat history option — this decision is permanent, so think carefully before confirming.

After that, up to 6 months (180 days) of 1:1 conversation history becomes available on the API, without media files. Each new message exchanged from either end is automatically synced, so the conversation remains consistent whether you're on the phone or in the team dashboard.

The "heartbeat" that keeps everything alive

One operational detail many people overlook: you need to open the WhatsApp Business App on your phone at least once every 14 days. This is the sync signal (the "heartbeat") that keeps coexistence active. If the primary phone remains inactive for around 13 days, the connection breaks for security reasons. In 2026 Meta made reconnection easier — switching devices no longer requires redoing the entire registration — but the habit of keeping the app alive still applies.

What is allowed in coexistence mode

The list of what still works is generous — that's precisely the strength of this feature:

• Use the same number on the app and API simultaneously, without a new number.
• Human and automated customer service side by side: the team replies from the phone, the chatbot replies via the API.
• Sync of 1:1 conversations between app and API (last 180 days, no media).
• Shared inbox with multiple agents via the API.
• Sending templates (HSM messages) approved by Meta from the API.
• Catalogue, business tools, and voice/video calls continue to work in the app.
• Groups and status remain available in the app as normal.

It's the best of both worlds for those who don't want to abandon their current way of working but need scale, automation, and reporting.

In the daily routine of a client who handles customer service via Instagram and WhatsApp simultaneously, I saw this difference in practice: the salesperson closed deals on their phone with the usual naturalness, while the chatbot via the API qualified new contacts outside business hours and opened the conversation already loaded with history. No one had to learn a new tool overnight — the transition happened at the team's pace, which is exactly the kind of change that usually works.

What is NOT allowed (the real limitations)

Here's the part that providers often hide. When you activate coexistence, some app features are disabled in 1:1 conversations and others simply don't go through the API. Knowing these limits upfront avoids frustration later.

Feature	In coexistence mode
Disappearing messages (1:1)	Disabled
View once messages	Disabled
Live location (1:1)	Disabled
Broadcast lists / native campaigns	Disabled
Group messages	App only; not sent to API
Status (stories)	App only; not synced with API
Voice and video calls	App only; API doesn't make calls
Standard business verification	Not available for coexistence accounts

Two points worth reinforcing. First: the WhatsApp API does not make voice or video calls — if your workflow depends on that, it remains manual on the phone. Second: bulk sending via the API may receive lower priority. Meta tends to prioritise numbers not in coexistence for very high volumes, so those running heavy campaigns need to evaluate this. For large-scale sending, the native broadcast list option disappears — you'll use templates via the API instead.

Coexistence or full migration: when to use each

Not every business should activate coexistence. The decision depends on volume, operations, and who responds. I've compared the two scenarios:

Criterion	Coexistence mode	Full migration to API
Customer service on phone	Retained	Ended (API only)
History preserved	Yes (up to 180 days)	Depends on migration
Heavy bulk sending	Limited / lower priority	Full
Native app features (status, groups on API)	Restricted	Not applicable
Team transition curve	Smooth	Abrupt
Ideal for	SMEs wanting to professionalise without disruption	100% automated, high-volume operations

My recommendation, after 15 years implementing digital solutions: start with coexistence if your team still handles a lot of customer service via phone and you want to add automation without flipping the switch all at once. Migrate fully to the API when volume and automation justify giving up the native app features. And in any scenario, understanding how to avoid number blocking is a prerequisite — the official API is precisely what protects your number from bans.

Geographic restrictions and technical requirements

Initially, coexistence mode had a long list of blocked countries — including the UK. That changed. Throughout 2025 Meta expanded availability, and in 2026 the feature became available globally, including the UK. Still, it's worth checking availability at the time of activation, as Meta adjusts coverage frequently.

On the technical side, summarising the requirements: WhatsApp Business app 2.24.17+, a business account (not personal), a Meta Business Portfolio set up, and an active physical phone with the app installed. Meta's official WhatsApp Business Platform documentation is the source of truth for region-specific details.

Voyia: Meta-validated official API with coexistence

This is where our solution comes in. Voyia is a Meta-validated official WhatsApp API app — and yes, it supports coexistence mode. That means you connect your existing number, keep customer service on your phone, and gain automation, chatbot, shared inbox for the team, and reporting on the same number.

Voyia was designed with the UK market in mind. Instead of charging per agent, it offers unlimited agents for business WhatsApp — your entire team on the same account without multiplying the bill per employee. And unlike many platforms, it doesn't add markup on messages: you pay Meta what Meta charges, with no hidden per-conversation fee.

In practice, coexistence with Voyia delivers what most SMEs need: continue serving customers the way you already do, without losing history, and add automation on the same number — with the security of the official API and without the risk of being banned from regular WhatsApp Business.

Common pitfalls and how to avoid them

Some traps frequently appear for those who activate coexistence without guidance:

• Forgetting the 14-day heartbeat. If the primary phone stays idle, the connection drops. Keep opening the app.
• Expecting native bulk sending. Broadcast lists disappear; plan campaigns using API-approved templates.
• Deciding on history on impulse. The option to sync conversations is permanent — confirm calmly.
• Relying on calls via the API. Voice and video remain app-only. Don't promise this to customers as an automated feature.
• Ignoring the region. Check availability at the time of activation, even with the global 2026 rollout.

None of these are deal-breakers — they're just expectations to align before you start. Most problems I see come not from the technology, but from poorly calibrated promises: someone sold "unlimited sending" or "automatic calls" and the customer discovered the limit at the worst moment. With coexistence mode properly explained, that doesn't happen — the feature delivers exactly what it promises, no surprises.

Conclusion: the smoothest path to professionalisation

WhatsApp coexistence mode is the least disruptive way to move a customer service operation from the phone to the official API. You keep what works, add automation and team on the same number, and respect Meta's rules — without the risk of a ban that looms over those who push the limits of the regular app.

If your business wants to take this step without losing history or complicating your team's life, Voyia is ready to activate coexistence with you. Want to see how it would look on your number? Get in touch and we'll show you the full flow, from QR Code to your first chatbot running.