Two modes of WhatsApp Business API: standard and coexistence
WhatsApp Business API connects in one of two modes. In the standard mode the number moves into AISAR entirely and the WhatsApp Business app on the phone is no longer used for it. In coexistence mode the number stays in the app and works in AISAR at the same time, keeping its chat history. Here is how the two differ, what coexistence gives up, and how to choose.
What matters
- Both modes are the official WhatsApp Business API under a Meta agreement. Neither is the same as connecting a regular number by QR code: see Connecting WhatsApp.
- The mode is chosen once, when the number is connected, and changing it means reconnecting.
- The one practical difference that decides most cases: WhatsApp calls through AISAR telephony work only in the standard mode.
Standard mode
The number moves fully under AISAR. The WhatsApp Business app on the phone is no longer used for it — every conversation happens in the shared inbox. Companies usually set aside a separate number for the official channel so the team keeps the one it is used to.
- WhatsApp calls work through AISAR telephony, with call recording and the shared call flow.
- The display name, avatar and verification request are managed from AISAR and Meta Business Suite.
- The whole team can reply at once, and no phone has to stay online.
Coexistence mode
The number stays in the WhatsApp Business app on the phone and is connected to AISAR at the same time — the connection is confirmed by scanning a QR code from the app. Chat history is preserved and continues in both places. This suits teams that do not want to give up the app: the owner keeps replying from the phone while the team joins the same number through AISAR.
What exactly comes over from the app
- Conversations — up to 180 days back. Text arrives for the whole period; attachments only for the last two weeks, older messages keep a placeholder without the file itself (a Meta limit, not an AISAR one).
- Contacts from the app — as a separate synchronisation step, alongside the history.
- The import starts right after connection: there is a 24-hour window for it, otherwise the number has to be disconnected and connected again.
- The number’s owner can decline history sharing right in the WhatsApp Business app — then nothing is imported, while new messages keep arriving as usual.
What coexistence gives up
- Calls to such a number ring only on the employee’s phone — AISAR never receives them: no call card, no recording, no routing through the call flow. Outbound calls from AISAR on that number are unavailable too.
- The display name and verification are managed inside the WhatsApp Business app, not in AISAR.
- The phone running the app stays part of the setup: if it goes offline for long, synchronisation suffers.
What is the same in both modes
- The shared inbox, the built-in CRM, deals and funnels, tags and tasks.
- Broadcasts by Meta-approved templates and the 24-hour messaging window: see The WhatsApp Business 24-hour window.
- Billing: the AISAR subscription separately, the messages themselves directly to Meta. See What WhatsApp Business API costs.
- No blocks for messaging-policy reasons, unlike a regular number connected by QR.
Side by side
| What | Standard | Coexistence |
|---|---|---|
| The WhatsApp Business app on the phone | No longer used for this number | Stays and keeps working as before |
| Chat history at connection time | Nothing to import — the number had no app behind it | Imported: up to 180 days of conversations, plus contacts |
| Where conversations happen | In AISAR only, by the whole team | In the app and in AISAR — messages stay in sync |
| WhatsApp calls | Work: call card, recording, call flow, voice agent | Never reach AISAR — only the employee’s phone rings |
| Display name and verification | Managed from AISAR and Meta Business Suite | Managed in the app on the phone |
| The number | Usually a separate one is set aside | The working number stays as it is |
| Templates, broadcasts, the 24-hour window | The same in both modes | The same in both modes |
| Risk of a messaging-policy block | None — a Meta agreement | None — a Meta agreement |
What coexistence is good for
- The team keeps its habits: whoever answered from the phone goes on answering from the phone.
- History is not cut in half — the same thread lives in the app and in AISAR.
- Automation can arrive gradually: an AI agent and templates on part of the conversations first, the rest later.
- Less risk during rollout: if something goes wrong, the number keeps working in the app.
- No separate number is needed for the official channel.
How to choose
- You need WhatsApp calls inside AISAR — with a card, a recording and routing — standard mode only. This is what usually decides it.
- You need full control of the profile and a team that does not depend on a phone — standard mode.
- You need to keep the app on the phone and the history on an existing number — coexistence.
- Not ready for business verification and want to try it in a minute — that is not WABA at all, but the QR connection.
See also
How to connect the official channel — in Connecting WhatsApp Business (WABA). How an official number differs from a regular one in capabilities and risk — in Connecting WhatsApp and the comparison at aisar.app/guides/whatsapp-vs-waba.