Keep the WhatsApp Business app on your phone and use the same number on the API, where Meta allows it. You need app version 2.24.17+ and a provider.
Or scan with your phone
For years the rule was simple and painful: the API needed a number that wasn't on any WhatsApp app, so you either gave up the app or bought a second number. Plenty of forum answers still say so. It stopped being true in 2025. Meta's rules here are as of mid-October 2026.
Meta's documentation calls it onboarding WhatsApp Business app users and notes it's “sometimes referred to as Coexistence”. Your number stays registered on the WhatsApp Business app. A provider connects the same number to the Cloud API, and from then on messages are mirrored: what customers send arrives in both places, and what you type on your phone reaches the provider too. Meta's developer docs call those copies of your own messages “message echoes”. Meta notes a few exceptions: a message from a customer using a companion device Meta doesn't support shows only in the app, and a customer's very first message can occasionally show only in the app.
So, where Meta allows it, a team inbox or an AI agent can work the number while you still answer from your pocket. In Zymbler, a reply you send from the phone shows up in the inbox and pauses the agent in that chat, so you and the agent don't answer the same customer at once. With Let the AI pick the conversation back up on, the agent answers again once you've been quiet for the hours you set (1 to 24) and the customer writes again.
From Meta's documentation:
Meta added countries in stages. The dates are from Meta's WhatsApp changelog, whose launch entry names no countries:
| Added | Countries and regions |
|---|---|
| 11 February 2025 | Launch, in most countries |
| 5 May 2025 | India |
| 23 October 2025 | Australia, Japan, the Philippines, Russia, South Korea, Turkey, the EU and EEA, the UK |
| 15 April 2026 | Nigeria, South Africa |
Meta's coexistence guide no longer lists any excluded countries. Meta can still refuse a number with its error “This feature is unavailable for phone numbers from this region”, and Meta's window has the final say on your number.
With Zymbler as the provider:
| Feature | Business app only | API only | Coexistence |
|---|---|---|---|
| Phones and devices | Your phone and linked devices | Zymbler, in a browser | Your phone, up to 4 linked devices and Zymbler |
| Who replies | You | The agent and your team | You, the agent and your team |
| Chat history | On your phone | None imported | Up to 180 days, if you share |
| Broadcast lists | Yes | No; use templates | Read-only; use templates |
| Message fees | Free | Per message, billed by Meta | App free; API per message |
It suits you if you already sell on the WhatsApp Business app and:
It's a poor fit when:
Meta's own feature comparison lists what changes in the WhatsApp Business app once the number is connected:
Greeting and away messages set in the app keep working after you connect, and they can clash with the agent. If an agent answers for you, switch them off in the app.
When you connect, Meta asks on your phone whether to share your chat history with the provider. Meta's rules:
Zymbler asks Meta for your history and contacts automatically as soon as the number goes live. Progress shows under the number in Channels: Importing your chats…, then Your chats are in with a count of conversations and messages. If you chose not to share, it says Chat history wasn't shared, and new messages still arrive normally. If Meta turns down the request, it says We couldn't import your chats and offers Retry import, which works for 24 hours after connecting. Meta never accepted the first request, so a retry is still the one request Meta allows.
Zymbler uses the contacts Meta shares to put names on conversations, and doesn't create a contact for anyone who hasn't had a conversation. When one of those customers writes again, the agent can see their earlier messages. Imported contacts start without a lead score, which builds from the new conversation.
Meta fixes a coexistence number's throughput at 20 messages per second, “to remain compatible with the WhatsApp Business app”. A number on the Cloud API alone gets up to 80 by default. For a small business that ceiling rarely matters. Zymbler's Workflows send to 20 contacts every 10 seconds, well under the ceiling.
Meta can disconnect a coexistence number from the API when:
Your chats stay on the phone. If the number drops off, open the Business app, then connect again from Channels in Zymbler.
Meta says messages you send from the WhatsApp Business app “will continue to be free”. Messages sent through the API, including an AI agent's replies, follow WhatsApp Business Platform pricing. Since 1 July 2025 Meta has billed per delivered message, and since 1 October 2026 that includes replies inside the 24-hour window. Each business phone number gets 1,000 free service messages a month. Meta bills these fees to your own WhatsApp Business account.
Meta says messages from the app “do not create, extend, or affect” the API's 24-hour window. And if a customer wrote just before you connected, Meta says the API can only answer them with a template, because no window was opened on the API side. You can still reply from the app. See what changed on 1 October 2026 or estimate your own bill with the WhatsApp pricing calculator.
The steps are the same with any provider; the button names below are Zymbler's.
Meta's own error messages, one by one, are in WhatsApp coexistence not working or number ineligible. These are the cases we've run into connecting businesses' numbers, most common first.
You entered the number and Meta asked you to “Add your WhatsApp phone number”, then refused it. Meta didn't offer coexistence. In the cases we've seen, the cause was the Facebook login in the window: a staff or agency account only sees its own business portfolios, so Meta treats the number as someone else's. Have the person who owns the business portfolio run the connection with their own Facebook account.
It's the “no other partner still attached” requirement above, as it shows up in practice. The number's WhatsApp Business account is still tied to another provider, as a partner or through their credit line. Meta's fix: in the WhatsApp Business app, go to Settings → Account → Business Platform and disconnect the current partner, then try again. If you still share a past provider's credit line, ask them to stop sharing it.
Disconnect from the phone: in the WhatsApp Business app, Settings → Account → Business Platform → Disconnect Account. Providers can't deregister a coexistence number through the API, and in our experience, forcing a number off from the provider side can knock it offline for customers. The app is the safe way out, and your chats stay on the phone.
WhatsApp, Meta, Meta Business Agent, Meta One, Messenger and Instagram are trademarks of Meta Platforms, Inc. or its affiliates. Zymbler is independent and not endorsed by Meta.
Zymbler replies to every customer in seconds, day and night, remembers what each one told it, and hands the chat to your team when it matters.