Keep using the WhatsApp Business app on your phone while Avox runs on the same number - setup, what syncs, checks, errors and FAQ.
With Meta's Coexistence, one WhatsApp number works in the WhatsApp Business app on your phone and in Avox at the same time. Your team keeps chatting from the app, and Avox adds the shared inbox, automation, templates, Flows and the Avox API on the same number.
For the concept in depth, see Coexistence. For the sync details, see Coexistence sync.
Start a connection
Finish Webhook setup and Test endpoint
Click Continue to Meta Embedded Signup
Confirm your app profile
Scan the QR code on your phone
Tap Connect on your phone
Finish in the window
Your own server isn't involved. Coexistence runs between the WhatsApp Business app on your phone, Meta and Avox. To send through the same number from your own systems, use the Avox API.
No. They keep messaging the same number and see the same business name.
Yes - that's the point of Coexistence. Keep the app signed in on the primary phone and open it regularly.
Messages sent through the platform appear in the app's chats as well, so your team sees the whole conversation.
That's a change on Meta's side, not in Avox. Connecting a number as New number (Bot only) is for numbers not used in the WhatsApp Business app.
The Inbox and Contacts show the results, and Logs lists the sync events Meta sent. Details are on Coexistence sync.
Yes - each number is its own connection, up to your plan's number limit. See Plans.
Keep using the app as before, and keep the primary phone signed in. Conversations they answer in the app also show in the Avox inbox, so anyone working in Avox sees the same history.
Open Health: the heartbeat shows Operational, Degraded or Down, and Check health now asks Meta whether the number can send.
With WhatsApp account alerts on in Compliance, the Switchboard's Owner (its first Admin) is emailed when Meta sends an alert about the account, and every Admin is emailed when a template is rejected, paused, disabled or flagged, or a Flow is blocked, throttled or deprecated.
Last updated