WhatsApp business app api coexistence is a Meta feature that lets one phone number run on the WhatsApp Business app and the Cloud API at the same time, with messages mirrored between the two. It is the option for a South African business that has outgrown the app but cannot stop answering customers from a phone. It sits inside the wider WhatsApp marketing guide for South African businesses; this post covers what you gain, what the app loses the day you connect, and whether a +27 number can use it.
Most pages on this topic are written by software providers selling the connection. The useful part is the list of things that stop working in the app once you connect, and Meta's own onboarding documentation states them plainly. The sections below work from that documentation, flag where it is silent, and finish with the questions to put to a provider before you pay for anything.
Quick Answer
Coexistence keeps your existing number, contacts and recent chat history in the Business app while a provider connects the same number to the Cloud API for automation, a shared inbox or a CRM. The cost is feature loss in the app: broadcast lists become read-only, groups are not synced and disappearing messages are switched off. Meta's documentation does not state whether South African numbers are eligible, so get written confirmation from your provider for your specific number.
In This Post
Not sure your number should be connected at all?
Send us how many people answer on the number today and what you want automated, and we will tell you whether coexistence or a full move is the question to ask your provider.
Get a set-up recommendationHow Does WhatsApp Business App API Coexistence Work?
Coexistence is an onboarding route in which a Meta-approved provider connects your Business app number to the Cloud API without deleting the app account. According to Meta's documentation on onboarding Business app users, the provider must be a Solution Partner or Tech Provider, and the connection runs through Embedded Signup, the login flow in which you authorise the provider to attach your number.
After onboarding, your team can still message customers one-to-one in the app. Meta's documentation describes a webhook, smb_message_echoes, that fires when you message a customer from the app or a supported linked device, so the provider's system sees what your staff typed on the phone. Messages sent through the provider's software appear in the app. Running the WhatsApp Business app and API together means one number, two places to answer.
Meta launched the route on 11 February 2025, according to its WhatsApp Business Platform changelog, and has widened the list of countries since. Our guide to moving a WhatsApp number between homes covers the delete-and-register route, which coexistence lets you skip, and the other migration routes.
What Changes in the Business App Once You Connect?
Connecting turns the Business app from the whole system into one front end, and a handful of its features are switched off or stop syncing. This table is taken from Meta's onboarding documentation as fetched in October 2026; check the current page before you commit, because Meta edits it.
| Item | What Meta's documentation says | What it means for an SA operator |
|---|---|---|
| Broadcast lists | Disabled: no new lists, existing lists become read-only | Your monthly specials list stops being something you can send to or build. Plan a template-based replacement first |
| Group chats | Not synchronised; not supported while connected | Supplier, delivery-driver or customer groups need a separate plan |
| Disappearing messages | Turned off for all one-to-one chats | Relevant if you used them for sensitive quotes or ID details |
| View once and live location | Disabled | A driver sharing live location with a customer needs another route |
| Chat history | Messages from the last 180 days sync; media IDs only for messages sent within 14 days of onboarding | Older chats stay on the phone but not in the provider's system |
| Linked devices | Up to four companion devices; all are unlinked at onboarding and supported ones can reconnect. WhatsApp for Windows and WearOS are unsupported | Reception's desktop link needs re-pairing; check your desktop set-up |
| Voice and video calls, channels | Not supported while connected | If customers phone you through WhatsApp, plan another way to take those calls |
| Business tools | Catalogue, orders and status are listed as not supported | Do not assume your app catalogue keeps working; confirm with the provider |
The broadcast-list trap
Under WhatsApp business app api coexistence, Meta disables broadcast lists: you cannot create new ones and existing lists become read-only. A business that sells through list sends must move to approved template messages to the same contacts, which are subject to Meta's messaging limits (covered below). Build and test that replacement before you onboard, not after the first quiet week.
Two of those rows connect to other guides. If your lists are the problem, read how broadcast lists compare with groups before choosing. If your backups matter, our backup and restore guide covers the app side; backing up before you connect is a sensible precaution rather than something Meta's onboarding page requires.
Can a South African (+27) Number Use WhatsApp Coexistence?
Meta's documentation does not confirm WhatsApp coexistence South Africa availability either way, so eligibility of a +27 number is unverified from the platform side. The onboarding page contains no country restrictions, and the changelog entries that name countries (India in May 2025; Australia, Japan, the Philippines, Russia, South Korea, Turkey, the EEA, the EU and the UK on 23 October 2025) do not name South Africa. The only South African entries in the changelog concern authentication pricing, and the changelog page carries no 2026 entry mentioning coexistence or a country addition.
Two provider blogs read for this post say South Africa is supported. Chakra HQ states that Nigeria and South Africa were added in May 2026, and Whautomate lists both among supported countries without a date. Whautomate adds that Meta does not publish a fixed, dated country list. Both are secondary sources selling the connection, so treat them as a lead rather than confirmation.
The practical test
Do not rely on any blog, this one included, to decide eligibility. Ask the provider to run the Embedded Signup flow with your actual +27 number, or to confirm in writing that they have onboarded South African Business app numbers. A flow that rejects the number at the first step costs you an afternoon. A signed annual contract for a connection that does not work costs far more.
A second SA-specific point is the number itself. Meta's phone-number requirements say the number must be owned by you and able to receive voice calls or SMS. A business number registered to a former employee, or on a contract you do not control, will stall this process as it would any other. The same idea underlies the comparison of the WhatsApp Business app and the API: decide the tier first, then the number.
Should You Coexist, Stay on the App or Move to the Full API?
The right set-up depends on how many people answer, how much of your selling runs through broadcast lists and groups, and whether you need automation or a CRM. Use this table to judge whether WhatsApp business app api coexistence suits you; the verdicts are our reading of Meta's documented limits, not a Meta recommendation.
| Your situation | Fit | Why | Best for |
|---|---|---|---|
| One to three people, answering on phones, little automation wanted | Stay on the app | Nothing to lose. The app's multi-device linking covers a small team | Salons, trades, small shops |
| Staff answer on phones, but you want auto-replies, a CRM link or order notifications | Coexistence | Keeps the number, contacts and recent chats while adding the API layer | A busy number you cannot take offline |
| Sales run on broadcast lists or groups | Fix that first | Coexistence makes lists read-only and does not sync groups | Food sellers, event organisers, stokvel-style groups |
| Larger team, shared inbox, chatbot handling most enquiries | Full API through a provider | The app becomes the minor channel; coexistence adds little | Higher volume or multi-branch operations |
| Brand-new number with no history worth keeping | Register on the API directly | There is no history to preserve, so the main benefit of coexistence disappears | New lines for campaigns |
To judge what you would build on the API side, see what the WhatsApp Business API is and the options for WhatsApp automation. If the aim is CRM visibility, WhatsApp CRM integration shows what a connected number can feed.
Running sales on broadcast lists today?
Send us the size of your list and how often you send, and we will assess whether it can move to template messages without breaking the offer.
Request a fit assessmentHow Do Billing, Speed and Messaging Limits Change?
A coexistence number has two billing regimes: messages sent from the Business app stay free, and messages sent through the Cloud API are charged at Cloud API pricing. Meta's onboarding documentation says so directly. Meta's per-message pricing has been in effect since 1 July 2025 and lists South Africa (+27) as its own market on the rate card, so look up the current rate for your message category rather than trusting a number in a blog. Our WhatsApp Business API pricing guide works through the model.
Speed is capped. Meta's documentation gives a fixed throughput of 20 messages per second for a number used on both the app and the API. Worked out, that is 1,200 messages per minute. As a working judgement rather than a Meta statement, a small business is more likely to hit the messaging limit than that cap.
A messaging limit, as Meta defines it, is the maximum number of unique WhatsApp phone numbers your business can deliver messages to outside a customer service window in a moving 24-hour period. New business portfolios begin at 250, and the first step up is 2,000, reached through business verification, partner verification, or 2,000 delivered template messages to unique users within 30 days using high-quality templates, per Meta's messaging limits documentation. If you are replacing a broadcast list of a few thousand contacts, that limit decides how fast you can reach them.
What Keeps the Connection Alive After Onboarding?
A coexistence connection stays live only while the Business app on the primary phone is in use: Meta's documentation lists a disconnection reason, PRIMARY_INACTIVITY, described as the primary device being inactive for approximately 14 days. A phone left in a drawer over a long December shutdown is the realistic risk for a seasonal business.
You can also disconnect yourself in the app under Settings, then Account, then Business Platform, by choosing Disconnect Account, and the provider receives a PARTNER_REMOVED event. Treat this as an exit route and ask the provider what happens to your automations, templates and stored chats if you use it. Where several people share the number, running one number for a whole team sets out how to divide the work across the app and the connected software.
What Should You Ask a Provider Before You Connect?
A provider question list exists to replace a sales demo with written answers on the points Meta's documentation leaves open. Put these to every provider you shortlist before any WhatsApp coexistence setup begins, and keep their replies on file.
- Have you onboarded a +27 Business app number through coexistence, and will you confirm mine before I pay? This is the SA availability question.
- Are you a Solution Partner or Tech Provider? Meta's documentation requires one of the two for this route.
- Which app version must my phone run? Meta's requirement is Business app version 2.24.17 or higher.
- What do you do with the 180 days of history? Ask where it is stored, who can read it and how it is deleted if you leave.
- What happens to my broadcast lists and groups? The honest answer is the list in the table above.
- What is the pricing for each message category in Rand terms? Meta's rate card is its own; get the provider's mark-up in writing.
- Is there a written contract covering how chats are processed? Customer messages are personal information. Under POPIA section 21(1), as reproduced at popia.co.za, a responsible party must have a written contract with an operator that processes personal information for it, making the operator maintain the section 19 security measures; whether a given provider is your operator is a question for your legal adviser. Your opt-in records remain your responsibility; see WhatsApp opt-in strategies.
What survives the connection
Coexistence carries messages from the last 180 days into the provider's system, and Meta gives the provider 24 hours to synchronise that history or the number must be offboarded. Media IDs come through only for messages sent within 14 days of onboarding. Anything older, and every group chat, stays on the phone, so export what you cannot lose before you connect.
Why South African Businesses Choose Growth Pulse Media
Growth Pulse Media is a Johannesburg agency founded by Dirk van Greuning, who built and scaled a large South African ecommerce business before starting it. Meta Ads, Google Ads, GA4 and Shopify work is executed in-house, with a limited client load so the person you brief is the person who reviews the work.
Connecting a number is one decision; what the number is for is another. Our WhatsApp marketing service page sets out how we approach the channel alongside paid acquisition, and our guide to click-to-WhatsApp ads covers where campaign traffic lands on the number you are about to connect.
Want a second opinion before you sign?
Ask for a free audit of how the number is used today and where enquiries come from. No obligation, and we will get back to you within 24 hours.
Request a free auditWho This Is Not For
You are a one-person shop with no automation need. The Business app already does what you need, and connecting it only adds a monthly cost and removes features.
You sell mainly through broadcast lists or groups. Coexistence disables the first and does not sync the second. Fix the sales mechanism before the plumbing.
You want a developer's integration walkthrough. This post is a decision guide for operators. Embedded Signup and webhook implementation sit in Meta's developer documentation.
FAQ
What is WhatsApp Business app and API coexistence?
It is a Meta onboarding route that lets the same phone number run on the WhatsApp Business app and the Cloud API at once. Messages sent on either side are mirrored to the other. The business keeps its number and recent chat history instead of deleting the app account.
Is WhatsApp coexistence available in South Africa?
Meta's documentation does not state South African availability, and its changelog does not name South Africa among the countries added. Two provider blogs, Chakra HQ and Whautomate, list South Africa as supported, but they are secondary sources. Ask your provider to confirm in writing that your +27 number can be onboarded.
What do I lose in the Business app when I connect to the API?
According to Meta, broadcast lists are disabled and existing ones become read-only, group chats are not synchronised, and disappearing messages are turned off for one-to-one chats. View once and live location messages are disabled, and voice and video calls and channels are not supported while connected. All linked devices are unlinked at onboarding. Supported devices can then be reconnected.
How much chat history syncs under coexistence?
Meta's documentation says messages from within 180 days of onboarding are synchronised. Media IDs are only included for messages sent within 14 days of onboarding. Older chats remain on the phone but do not appear in the provider's system.
Do I pay for messages sent from the app on a coexistence number?
No. Meta states that messages sent through the Business app stay free, while messages sent through the Cloud API are subject to Cloud API pricing. The rate depends on the message category and the recipient's country calling code.
Can coexistence disconnect on its own?
Yes. Meta lists primary-device inactivity of approximately 14 days as a reason for disconnection. Keep the phone with the Business app switched on and in regular use, and note this risk if the business closes for an extended holiday.
Connect the number once, with your eyes open
Tell us how your number is used across Meta Ads, your Shopify store and your team's phones, and we will help you work out the questions to ask before you commit to WhatsApp business app api coexistence. No obligation. We will get back to you within 24 hours.
Talk to Growth Pulse Media

