How to enable WhatsApp coexistence

WhatsApp coexistence lets the same business number run on the mobile app, WhatsApp Web, and Cloud API at once. Enabling it is part of number onboarding on the Business Platform — not a generic switch on every BSP. In 42agents coexistence is the white-label product default: the agent and inbox do not force you to take WhatsApp away from the SMB.

Steps

1. Step 1

   Confirm you need coexistence

   If the team must keep replying from the phone or WhatsApp Web while an agent/API runs, you need it. If the number will be API-only with no app, that is a different path (less common for LatAm SMBs).

2. Step 2

   Review the number’s current state

   Is it already on Cloud API? Still Business-app only? Document Business Manager owner, WABA, and who holds the SIM/OTP.

3. Step 3

   Start onboarding with a Tech Provider

   With 42agents: sign up at https://dashboard.42agents.app/sign-up and follow embedded signup / connection. Choose the path that keeps official clients (app/Web) per Meta’s current option for that number.

4. Step 4

   Complete Meta verification

   OTP, Business Manager permissions, and terms. Without this there is no stable API or reliable coexistence.

5. Step 5

   Validate app + Web + API

   Send a test message: it should hit the webhook/agent and still be visible where the team watches (app or Web). Test handoff: a human takes the thread without fighting the bot.

6. Step 6

   Train the end client

   Explain it is no longer “only the owner’s phone”: there is a multi-user inbox (3 included) and rules for who answers what.

Important notes

• Coexistence is not the same as personal multi-device on a consumer account.
• Exact eligibility is defined by Meta and can change; onboarding reflects the current state.
• Without clear handoff, coexistence alone does not stop the bot and human from stepping on each other.