Coexistence: Running the WhatsApp Business App and API on One Number
Coexistence is a WhatsApp feature that lets a single phone number use the WhatsApp Business app and the WhatsApp Business API at the same time. Historically, connecting a number to the API meant giving up the friendly mobile app — agents lost the familiar chat interface, and existing conversation history was left behind. Coexistence removes that trade-off: your team keeps replying from the phone app while automation, chatbots, broadcasts, and CRM integrations run through the API on the very same number. For Indian businesses that grew up on the WhatsApp Business app and don't want to abandon a number their customers already trust, coexistence is often the smoothest path onto the API.
In one line
Coexistence means one WhatsApp number works with both the WhatsApp Business app and the API simultaneously, so your team can chat from the phone while automation and broadcasts run through the API — no number change, no lost history.What coexistence actually means
Under the traditional model, a phone number could be registered to exactly one WhatsApp surface at a time — either the consumer app, the WhatsApp Business app, or the API. Migrating to the API was a one-way door: the mobile app stopped working on that number. Coexistence changes the rule. When you enable it, your number is registered against the Cloud API while the WhatsApp Business app on the phone stays linked and functional, similar to how the app already supports linked companion devices. Both surfaces read and write to the same number, so a customer sees one continuous conversation regardless of whether a human replied from the phone or an automated flow replied through the API.
Why coexistence matters for your business
For most small and mid-sized Indian businesses, the number on WhatsApp is a genuine asset — it's printed on packaging, saved in thousands of customer phones, and carries months or years of chat history. Coexistence lets you add API power without touching any of that. You gain broadcasts, template messaging, chatbots, and CRM/helpdesk integration while your frontline staff keep working in the interface they already know. The result is a gentler, lower-risk migration: no customer confusion from a new number, no scramble to re-onboard your team onto a new dashboard on day one, and no gap where messaging stops working during the switch.
- Keep your existing WhatsApp Business number — no reprinting cards, packaging, or profiles
- Retain recent chat history so agents don't lose context mid-conversation
- Let staff reply from the familiar phone app while automation runs via the API
- Layer on broadcasts, templates, and chatbots without a disruptive cutover
How coexistence works in practice
Setup runs through Meta's onboarding flow, usually inside the Embedded Signup that InfiQ presents during onboarding. You scan a QR code from the WhatsApp Business app to link it to the API, WhatsApp syncs a window of recent contacts and chats so history carries over, and from then on both surfaces stay connected. Inbound messages appear in both the app and your InfiQ inbox; outbound messages sent from either side are stitched into the same thread. There are practical boundaries to plan around: coexistence is designed for the WhatsApp Business app specifically (not the personal consumer app), it targets small-team usage rather than very large agent floors, and the volume of history that syncs is limited to a recent window rather than your entire archive. Treat it as a bridge that keeps everyone productive while you scale into fuller API workflows.
Common mistakes and how to avoid them
The biggest error is assuming coexistence is a shortcut around the fundamentals of running on the API. It is not. Once your number is on the API, sending marketing or utility content to people who haven't messaged you recently still requires approved message templates, and every delivered message is billed by category (marketing, utility, or authentication). Teams sometimes expect the phone app to keep behaving exactly as a standalone install, then get confused when template rules, opt-in expectations, and the 24-hour free service window start to apply. Other frequent slip-ups: trying to coexist with the personal WhatsApp app instead of the Business app, expecting years of chat history to fully migrate, and skipping proper Business Verification and display-name setup. Plan the account structure deliberately and confirm you retain full ownership of your WhatsApp Business Account and BSUID from the start.
- Templates are still required for messages outside the 24-hour service window
- Billing is per delivered message by category — coexistence does not make messaging free
- Use the WhatsApp Business app, not the personal consumer app, to enable it
- Only a recent window of chat history syncs, not your complete archive
- Confirm you keep ownership of your WhatsApp Business Account and BSUID
Frequently asked questions
Can I really use the WhatsApp Business app and the API on the same number?+
Will I lose my chat history when I enable coexistence?+
Does coexistence make WhatsApp messaging free?+
Do I still need message templates with coexistence?+
Is coexistence right for a large support team?+
Can I use coexistence with my personal WhatsApp account?+
Do I keep ownership of my WhatsApp Business Account with coexistence?+
How do I set up coexistence with InfiQ?+
Move onto the API without leaving your number behind
Talk to an InfiQ onboarding specialist and set up coexistence so your team keeps chatting from the phone while automation and broadcasts run through the API on the same trusted number.