Can You Use the WhatsApp Business App and Cloud API Together?

Short answer: yes. Since May 2025, Meta's coexistence feature lets a single phone number run the WhatsApp Business app and the WhatsApp Cloud API at the same time. You keep chatting from the app while a connected platform sends templates, runs automations, and works a shared inbox. New messages sync in both directions, so whichever side answers, nobody loses the thread. Before 2025 this was impossible; connecting the API removed the number from the app.

For years the answer to this question was a flat no. A number was either on the app or on the API, never both, and switching meant losing the app for good. That is why so many businesses stalled on the fence. Coexistence changed the answer, and it is worth understanding exactly how, because the mechanics decide whether it fits your setup.

How one number runs both at once

When you connect through the coexistence path in a platform's signup flow, Meta links your existing Business app number to a WhatsApp Business Account and the Cloud API without unregistering the app. The two sides stay in sync through a mechanism Meta calls messaging echoes: a message you send from the app is echoed into the API inbox, and a message the API sends is echoed into the app. Your saved contacts sync over as well, so the platform side is not starting from an empty list. The full walkthrough lives on our WhatsApp coexistence page.

In practice, this means a small team can keep doing what they already do, tapping out one-to-one replies on a phone, while gaining the ability to schedule campaigns, fire auto-replies, and route conversations to the right agent from the same number.

What each side handles best

• The app is best for: quick personal replies, browsing recent chats on your phone, and anything you already do by hand.
• The API is best for: bulk approved template campaigns, scheduled sends, chatbots, and a multi-agent shared inbox where a whole team works one number.

Because messages echo across both, a customer never sees two versions of you. They message one number and get answered, whether a person typed the reply in the app or an automation sent it through the API.

The limits you should know

Running both together is powerful but not unlimited. A few honest constraints:

• Throughput. Coexistence caps sending at roughly 20 messages per second, well below a full API setup that can push 80 or more per second.
• App-only features. Group chats, Status updates, calls, catalog, Shop, and WhatsApp Pay stay inside the app and are not exposed to the API.
• Companion devices. Linked devices like WhatsApp Web unlink when you onboard, and you need to keep the app open periodically to keep the connection healthy.
• Eligibility. The number must already run the Business app, not be on another API account, and sit under a Meta Business Portfolio you administer.

A day on a coexistence number

It helps to see how the two sides trade off in practice. Picture a home-services company running one number:

• 8 a.m. The platform sends an approved appointment-reminder template to the day's booked customers. Those go out through the API, scheduled the night before.
• 9 a.m. A customer replies asking to move their slot. The reply lands in the shared inbox and echoes to the owner's Business app on the phone. Whoever is free answers.
• Midday A new lead messages from a click-to-chat link. An auto-reply greets them instantly through the API, asks two qualifying questions, and routes the thread to the sales rep.
• Evening The owner clears a few personal follow-ups by hand in the app, and those messages echo back into the platform so the record stays complete.

No customer ever knows which side sent what. They messaged one number and got fast, consistent answers. That blend, automation for the repetitive sends and a human in the app for the nuanced replies, is the whole point of running both together.

Does this work for US businesses?

Yes, the United States is supported. A US business can link its Business app number and immediately send approved utility templates and support replies. The one caveat is platform-wide, not coexistence-specific: Meta paused marketing template delivery to US numbers in April 2025, so promotional blasts to US recipients are on hold while utility and transactional messaging work normally. Coexistence does not change that rule in either direction.

Making both sides work as one team

The moment two channels feed one inbox, the practical question becomes who answers what. This is where routing matters: sending each synced conversation to the right person automatically keeps sales chats with sales and support chats with support, so nothing sits unanswered while an agent scrolls. Pair that with auto-replies for the first response and your one number behaves like a proper contact center without feeling like one.

The bottom line

Yes, you can absolutely run the WhatsApp Business app and the Cloud API on the same number today, and for a growing team it is often the smartest way to add automation without disruption. Understand the throughput cap and the app-only features, confirm your number is eligible, and connect through coexistence to keep everything you have built while gaining everything the API offers.

Common questions

Do I need two phones or two numbers to use both? No. That is the entire benefit of coexistence: one number and one phone run both the app and the API together. You do not buy a second SIM or juggle devices; the same line your customers already message gains automation.

Will my customers see two accounts? No. Customers see one WhatsApp business, one number, one conversation. Whether a reply came from a person in the app or an automation through the API, it lands in the same chat thread, so the experience is consistent from their side.

What happens if I stop using the app? Coexistence expects the app to stay active. If it sits unopened for a couple of weeks, the connection can drop. If you truly no longer need the app, that is a sign you should consider a full migration to the API instead of coexistence.