Overview
WhatsApp Coexistence allows you to connect your WhatsApp Business App to respond.io via the WhatsApp API using the same phone number. You can continue using the WhatsApp Business App while unlocking automation, CRM syncing, reporting, and other features on respond.io.
This setup is ideal for teams that want to adopt API-based workflows gradually without giving up the app theyâre already using.
What you can do
Connect your WhatsApp Business App number to respond.io without giving up the app
Send and receive messages from both platforms
View messages sent from the app on respond.io as echo messages
Use respond.io features like automation, CRM integration, team visibility, and more
Note: Contact and message history syncing is currently not supported. Want this feature? Upvote here to show your interest.
Requirements
WhatsApp Coexistence is available only to businesses actively using the WhatsApp Business App, based on Metaâs review of account age and messaging quality.
WhatsApp Business App version 2.24.17 or later. Learn more.
Add phone number to your Meta Business Manager. Learn more.
Your business must not be registered in a currently unsupported country. At the moment, this includes Nigeria and South Africa.
Important: You must open the WhatsApp Business App at least once every 14 days to keep your Channel connection active. If the app is not opened, the connection may be removed, affecting message deliverability.
Setup Guide
Add phone number to your Meta Business Manager
In your Meta Business Suite, Go to Settings
On the side menu, select WhatsApp accounts
Click Add > Link a WhatsApp Business account
Enter your phone number
Connect Channel
On respond.io, go to Settings > Channels > Add Channel. Then, Select WhatsApp.
Click here to connect WhatsApp Business App.
Click Connect With Facebook and log in with your Facebook account and follow the embedded sign-up flow.
Complete the setup. Your WhatsApp Business App will remain usable, and you can start using respond.io
Youâll be able to:
Continue using your WhatsApp Business App
Send and receive messages on respond.io using the same number
View messages sent from the app as echo messages
Echo Messages
Messages sent from the WhatsApp Business App will appear on respond.io as echo messages. These provide visibility into team conversations and allow you to sync contact data or follow up via automation.
Behavior of echo messages:
Will not open a service window
Will not trigger automation
Will not start a new conversation
Will create a contact if one doesnât exist
Feature changes after connecting to respond.io
Once your WhatsApp Business App is connected to respond.io (via WhatsApp Coexistence), some native features of the WhatsApp Business App will no longer be available. These changes are made by WhatsApp and apply to all integrations with third-party platforms like respond.io.
Feature | Change |
|---|---|
Broadcast Lists | You will no longer be able to create or send Broadcast Lists from the WhatsApp Business App. Existing lists will become read-only. However, you can still send broadcasts using the Broadcast module on respond.io. Note: When sending broadcasts via the WhatsApp Coexistence Channel on respond.io, messages are subject to a stricter rate limit of 20 messages per second, as enforced by Meta. Exceeding this rate may cause delivery errors such as ârate limit hit.â |
Message Edit/Revoke | This feature will no longer be supported in individual (1:1) chats. |
Disappearing Messages | Automatically turned off for all individual (1:1) chats. |
View Once Messages | Disabled for all individual (1:1) chats. |
Live Location Sharing | Disabled for all individual (1:1) chats. |
For more information, you can refer to Meta's official documentation.
Known Limitations (Phase 1)
Feature | Supported |
|---|---|
Message and contact history import | No |
Group chats, calls, and status updates | No |
View past chats on WhatsApp Business App | Yes |
CRM and automation on respond.io | Yes |
Companion devices | Must be reconnected after setup |
Message rate limit (Coexistence) | Capped at 20 messages per second (per Metaâs policy) |
FAQ and Troubleshooting
Can I keep using the WhatsApp Business App?
Yes. You can continue using the app while gaining access to API-based tools on respond.io.
Will I be charged if I send messages via my WhatsApp Business App after connecting to respond.io?
No, it will still be free even after connecting your WhatsApp Business App to respond.io.
Will my team lose access to chat history?
No. Chat history remains available in the WhatsApp Business App. Respond.io will not display past conversations during Phase 1.
What happens when someone sends a message from the Business App?
Respond.io will display it as an echo message. It wonât open a service window or trigger automation.
Do messages from the Business App count toward messaging limits?
No. Messages sent from the app are free. Only messages sent via the Cloud API will be counted and billed.
Which countries are currently unsupported?
Nigeria and South Africa.
Do I need to keep the WhatsApp Business App active?
Yes. You must open the WhatsApp Business App at least once every 14 days to keep your connection active. If you donât, the Channel connection may be removed, which can disrupt your message deliverability on respond.io. If the connection is lost, you will need to re-connect your phone number as a new WhatsApp Coexistence Channel.
Will I lose my Meta Verified badge when I onboard?
No. You will not lose your Meta Verified badge when onboarding your WhatsApp Business App to the WhatsApp Business API through WhatsApp Coexistence. Meta now supports transferring your Meta Verified subscription when you connect your number via WhatsApp Coexistence.
Why do I see the error âThe WhatsApp Business Account (WABA) youâre trying to connect already has an existing payment methodâ when setting up WhatsApp Coexistence?
This is a limitation set by Meta. Credit lines for WhatsApp Coexistence accounts cannot be removed or migrated to another provider.
However, there is a supported workaround:
Switch the phone number from WhatsApp Business App to a Personal WhatsApp.
Switch back to WhatsApp Business App.
Connect the same phone number to a new provider.
Why are messages sent from WhatsApp for Windows not appearing in respond.io when using a coexistence number?
This can happen due to WhatsApp Coexistence limitations or connection issues.
Messages sent from unsupported companion devices, such as WhatsApp for Windows or WhatsApp for WearOS, do not trigger WhatsApp webhooks. As a result, these messages may appear in the WhatsApp Business App but will not show in respond.io.
In addition, messages may stop appearing if:
The WhatsApp Business App is not opened on the primary phone for more than 14 days, causing linked devices to be logged out, or
The respond.io partner connection to your WhatsApp Business Account (WABA) has been removed or disrupted
What you can do
Confirm that the message is visible on the primary WhatsApp Business App device, but not appearing in respond.io.
Go to WhatsApp Business Manager and check that respond.io is listed as an active connected partner for your WhatsApp Business Account.
If respond.io is not listed, delete the existing WhatsApp Coexistence channel in respond.io and reconnect it using the Embedded Signup (ES) flow.
WhatsApp Coexistence and linked device behavior are enforced by WhatsApp (Meta). Refer to Meta documentation for more details.
How many devices can I link to my WhatsApp Coexistence account, and are all devices supported?
Businesses can link up to four WhatsApp companion clients (âlinked devicesâ) to their WhatsApp Business App account. Most companion clients are supported for Coexistence, except for WhatsApp for Windows and WhatsApp for WearOS, which are not compatible.
Why did an unsupported message appear after the Contactâs message?
This can happen when a Contact sends a message to your WhatsApp Coexistence number and then edits that message.
When a Contact edits their sent message:
The original message remains visible in the platform.
The edited version is delivered as a new message and appears as an unsupported message.
