WhatsApp Coexistence lets you automate your existing WhatsApp Business number

WhatsApp Coexistence connects the number your customers already message to Meta's Cloud API, where an agent can answer it, and the WhatsApp Business app stays on your phone. Meta's documentation calls it onboarding WhatsApp Business app users, and you'll also see it written as WhatsApp Business coexistence. Few owners know any of these names. They just want to know if they can automate their WhatsApp Business account and keep the app.

For years they couldn't. The Cloud API wanted a number of its own, and Meta won't register a number that's still in use on WhatsApp until it's been deleted from the app. So automating the number your customers knew meant giving up the phone that answered it.

With Coexistence, one number does both jobs:

• calls, groups and Status stay on the phone
• whatever you type in the app still goes out free
• every one-to-one chat also reaches your provider, where an agent can answer it
• both sides stay in sync, so each one sees what the other sent

When it reached Nigeria and South Africa in 2026, the head of a brand-storytelling firm summed up what changed for businesses there. One number could now take calls, post Status updates and run on several devices, and still answer customers automatically.

We spent this week building Clawnify's side of it. That meant reading Meta's documentation end to end, switching the feature on for our own Meta app, and shipping the receiver for everything a connected number sends.

Meta's Coexistence documentation lists what changes in the app, and it's a short list. The catalog, labels, quick replies, Status and the business profile carry on as before.

Meta supports every linked app except WhatsApp for Windows and WhatsApp for WearOS. Replies sent from those two never reach the provider, so an agent can't see that you already answered, and messages show up there as placeholder text. A team that works from the Windows app is better off on WhatsApp Web.

The rule we'd watch most closely sits in Meta's webhook reference, away from the Coexistence page. If the main phone is idle for about 14 days, Meta ends the connection, and the automation stops with it. The same reference lists other ways a connection ends, such as moving the number to the regular WhatsApp app or registering it again on a new phone.

We'd give the automation a number of its own when:

• it has to work in groups, which never reach the API
• nobody can promise the main phone stays in use every two weeks
• you send in bulk, and a Coexistence number is held to 20 messages a second
• the number also carries personal chats you'd rather no provider received

An assistant you text yourself is simpler still on a number of its own, the setup we covered in AI text messaging.

Connecting starts a feed from Meta to your provider that covers every one-to-one chat on the number, personal ones included. New customer messages are only one part of it. Meta documents each kind of delivery separately, and we built our receiver around the differences. Here's what arrives, and what we think an agent should do with each.

The history row is the one to get right. Meta delivers part of the history copy in the same shape as a new message, so a receiver that sorts deliveries by what they contain can answer a six-month-old question as if it had just arrived. Ours goes by the label Meta puts on each delivery, and passes only new messages to the agent.

The history also comes once. Meta gives the provider 24 hours from the moment you connect, and running it again means disconnecting the number and going through the signup a second time. So we built our receiver to store every delivery first, before it does anything else with it.

Anything you type in the Business app stays free, and Meta's Coexistence documentation says so. What your provider sends through the API is charged per message. Since 1 October 2026 that includes replies inside the customer service window, the 24 hours that open each time a customer writes or calls. Each number gets the first 1,000 of those replies free every month. Outside the window only approved templates can go out, and they're charged from the first one.

Say a salon owner wants an agent on the salon's existing number to handle bookings. Suppose each booking takes four agent replies inside the window: an answer, the times on offer, a follow-up and the confirmation. The free 1,000 then covers about 250 bookings a month. A reminder the day before usually falls outside the window, so it goes out as a template and is charged. Anything the owner answers personally from the app costs nothing. So we'd split the work. The agent takes the questions that repeat, and the owner keeps the conversations worth a personal reply.

Add a payment method to the WhatsApp account before switching anything on. Meta's pricing page warns that without one, service replies may stop being delivered.

There's no Coexistence switch in the app. It runs through Meta's Embedded Signup, a window your provider opens from its own website, and Meta lets only approved Tech Providers and Solution Partners offer it. These are the steps on the business side, as Meta's documentation sets them out.

We switched the feature on for our own Meta app this week. Meta's launch check said business app onboarding was on. Then we opened the signup to connect a number, and it went straight to adding a new one, with no option for an existing Business app. Our business is verified. Our App Review went in on 4 November, with screen recordings of us sending a message and creating a template through the API. For now, we can't connect a Business app number, our own included.

Before you pick a provider for your number, ask it three things. Has Meta approved it to offer Coexistence? Which of your chats will its agent answer, and which will it leave to you? And what stops it from answering a six-month-old message in the history copy? Push hardest on the last one.