WhatsApp Coexistence is one of the most consequential changes Meta has made to the WhatsApp Business ecosystem in recent years, and UK businesses currently running the free WhatsApp Business App are asking what it means for them before they commit to any platform. This FAQ answers the practical questions directly: what Coexistence is, how it works, and where Stitch, the WhatsApp business communication platform, already supports it.
Coexistence is a Meta feature that allows a single phone number to operate simultaneously on the WhatsApp Business app and the WhatsApp Business Platform (the API), synchronising messages between both environments. In practice, this means staff can keep sending and receiving messages from the WhatsApp Business app on their phone, while those same conversations are mirrored into a centralised business dashboard for compliance, visibility and automation. It was built to solve a specific tension: businesses need audit trails and centralised control, but staff are often reluctant to give up the WhatsApp interface they already know.
Meta introduced Coexistence to address the gap between informal WhatsApp Business App usage and the compliance needs of larger organisations. Before Coexistence, moving from the free app to the Business Platform meant staff lost access to their familiar phone-based interface, which created adoption resistance. Coexistence removes that trade-off by letting the number exist on both surfaces at once, so businesses gain a central record without forcing a disruptive change on the people actually sending the messages. Meta has also been actively adjusting the operational constraints around Coexistence, including removing the previous roughly 100k-message threshold that once gated onboarding.
Yes. Stitch's coexistence product mirrors WhatsApp Business App chats into a centralised inbox and CRM, enabling admin coverage, audit and export functionality, and hybrid deployment alongside team inboxes. Around 7 to 8 coexistence onboardings have already been completed, and the feature synchronises one-to-one chats from the WhatsApp Business app into Stitch's message box platform, which in turn integrates with CRMs for centralised record-keeping. This means UK businesses evaluating platform migration today are choosing a provider that has already built for, and deployed, the direction Meta itself is taking the channel.
No, your number stays the same under Coexistence. The feature is specifically designed so that a business's existing WhatsApp Business App number continues operating on the phone while being connected into the centralised platform. Staff keep using the phone-based app they are used to, but the business gains a synchronised record of every conversation. This directly addresses one of the biggest blockers to platform adoption: staff reluctance to abandon a WhatsApp number and interface they already rely on.
Chat history from the WhatsApp Business App is preserved and continues to sync into the centralised inbox once Coexistence is active. Messages are logged centrally and can be downloaded as CSV files for audit purposes, though media files are excluded from export due to encryption. Users keep their message history and contacts on the phone-side app, while the business gains a compliant, searchable record that persists even if a staff member leaves or a number is reassigned. For subject access requests (SARs) or ICO investigations, this centralised logging is what makes an audit trail possible in the first place.
You need the WhatsApp Business App installed on a dedicated business phone number, not a personal WhatsApp account. Specific technical prerequisites include running WhatsApp Business app version 2.2417 or higher, having UK phone number support, and the number having been actively used on WhatsApp Business for at least three months before migration. Businesses are also expected to use work-provided phones with WhatsApp Business installed, rather than personal WhatsApp accounts, to keep the setup within Meta's supported migration path.
Onboarding a single user takes approximately five minutes. The process involves generating a unique URL per user, which triggers a WhatsApp message containing a QR code; the user scans this to link their WhatsApp Business app to the platform. It can be completed remotely over a call or messaging platform, and once the initial setup is done, a business's own internal team can typically manage onboarding additional users independently.
Not currently. One-to-one chats synchronise into the centralised platform, but group chats remain on the WhatsApp Business app and are not yet mirrored into the dashboard, pending Meta's release of a group messaging API. This is a deliberate limitation on Meta's side rather than a gap in the platform connecting to it, and it is being tracked as Meta's API capabilities evolve.
Yes, with some current Meta-imposed ceilings to be aware of. Larger deployments involving hundreds of staff and multiple WhatsApp accounts have been handled through coexistence mode, including a documented case of a business with 600 staff running multiple team inboxes of 10 or more people each. However, Meta currently limits a single business manager to around 20 WhatsApp numbers, which is a real constraint for enterprise-scale rollouts and is being actively pushed on with Meta as deployments grow. If your business is planning a rollout at this scale, it's worth discussing numbering strategy and business manager structure with your provider before onboarding begins.
No, WhatsApp voice calls are not currently supported through the platform layer of Coexistence. WhatsApp voice calls remain peer-to-peer and sit outside the coexistence integration, though work is ongoing with partners to bring WhatsApp calling into cloud API accounts via SIP trunks, as a separate development track.
Both models are supported, and the right choice depends on how your team operates. A single shared team WABA number centralises everything into one inbox with straightforward website "click to chat" routing, while individual WABAs per salesperson keep each person's contacts and conversations isolated, which matters where staff are concerned about colleagues accessing their leads. A hybrid approach is also possible, keeping existing landline or phone-system numbers for some channels while exposing specific WABAs to individual staff as needed. Estate agencies, for example, often need grouped access (an agent plus supporting staff), while lone recruiters tend to prefer keeping their own direct number.
Yes, permissions can be configured at both an organisation-wide and per-number level. Role types include Organisation Admin, Team Lead, and User, and settings exist to restrict a user from seeing other users' chats, as well as to mask phone numbers so only admins see full contact details. The only fully isolated option, though, is giving each user or team their own dedicated WABA number, since some metadata can still be visible where multiple users share access to the same inbox.
Pricing is based on the number of WhatsApp Business numbers connected and the number of users accessing the centralised dashboard, rather than a per-message charge for normal WhatsApp Business app usage. As a guide, a Stitch-provisioned private coexistence number costs around £5 per month, though using an existing landline or phone-system number (a DDI) is typically cheaper than provisioning a new one. In one documented example, coexistence across roughly eight WhatsApp numbers was estimated at an additional £50 per month plus setup fees. Charges only apply for template messages sent through the platform, and these costs are expected to be minimal for most businesses.
Conversations remain fully accessible even after a staff member leaves, because WhatsApp numbers are linked to the business, not to the individual. WhatsApp accounts are tied to phone numbers rather than to specific staff, which means numbers can be reassigned without losing chat history. All messages captured through the platform are logged into the connected CRM, and chat histories remain available there even if a number is deleted or a user departs, which is a key part of the compliance case for moving off personal WhatsApp use.
Coexistence is functional and in active use today, but it is still evolving as Meta rolls it out further. Technical issues such as webhook media download failures and Meta's phased regional rollout mean the feature has not yet reached full general availability at enterprise scale. Meta's approach also reflects a broader strategic goal of moving informal or "grey market" WhatsApp use into official, monitored channels, rather than immediate monetisation of the feature itself. Businesses adopting Coexistence now are positioning themselves ahead of where the channel is heading, rather than waiting for a fully mature rollout before starting the transition.
Coexistence closes a specific compliance gap: informal WhatsApp use on personal devices, with no central visibility or audit trail. Before centralisation, staff holidays or absences often meant phones being left with colleagues to monitor messages, with no formal record of who handled what. Centralised logging and CSV export give businesses an audit trail that supports SAR responses and stands up to ICO or regulatory scrutiny, and it ensures no message is deleted without trace. For businesses already worried about WhatsApp being the least-controlled channel in their communication stack, Coexistence turns an unmanaged risk into a documented, exportable record.
Coexistence is not a future promise. It is a working feature that Stitch has already deployed across multiple onboardings, letting UK businesses keep their existing WhatsApp number, keep their staff's familiar app experience, and gain the centralised compliance and audit layer that growing businesses need. If you are currently running the free WhatsApp Business App and weighing up whether migration means starting from scratch, the honest answer is that it doesn't have to. Book a demo to see how your existing number and chat history carry across into a centralised, compliant setup.
