WhatsApp Guides
WhatsApp Coexistence: Can You Keep Your Existing Number and Business App?
Your business number may already be on every sign and brochure. Check the supported onboarding route, account eligibility and day-to-day behavior before changing it.
Your WhatsApp number is on the shop sign, visiting cards and old customer invoices. The team wants a CRM, but replacing that number would create a different problem.
WhatsApp coexistence is worth investigating in this situation. Meta documents a supported onboarding route for eligible businesses to connect an existing WhatsApp Business App account and phone number to the Platform. Eligibility and the actual onboarding result must be checked for your account.
The important word is “checked.” Do not treat a general promise about coexistence as proof that every account, feature and old conversation will behave exactly as you expect.
Clarify your current setup
Before onboarding, identify which application currently uses the number, who controls the business account and whether a provider already manages a Platform connection. Confirm who can approve the connection and who will retain administrative responsibility afterwards.
Explain the continuity you need in concrete terms. Does the owner need to keep answering from the phone? Must another employee see new enquiries in the CRM? Is old history essential for a specific workflow? Each requirement needs its own answer.
Ask these questions before making changes
- Is this exact number and account eligible for the offered coexistence flow?
- Which messages and events will appear in the app and in the CRM?
- What history, if any, can be synchronized, and what permissions are needed?
- Which app functions remain available, and which differ after connection?
- What happens to existing linked devices and staff access?
- How are app activity and Platform activity billed and reported?
- Who handles reconnection if the phone or registration changes?
Ask for current documentation and an account-specific explanation. Avoid relying on a fixed history period or feature list copied from an old comparison article.
Use the correct onboarding route
Coexistence is a specific supported setup, not a label for every method that puts WhatsApp on a desktop. Meta’s Business App onboarding documentation is the official reference for the route.
SHVYA includes a WhatsApp Coexistence onboarding flow. Ask the setup team to confirm that it is available and suitable for your organization before proceeding. The existence of a setup screen does not establish your account’s eligibility or complete the connection.
Do not delete or re-register the current account simply to get past an unfamiliar setup message. Establish what the supported flow requires and preserve business continuity while resolving the issue.
Test the behavior your team depends on
Use an authorized test contact and a short acceptance record. These checks are a proposed rollout process, not a statement that your account has already passed.
- Send a new inbound enquiry and confirm where it appears.
- Reply from the intended staff interface and verify receipt.
- Check the app-side workflow the owner expects to keep using.
- Review how the conversation appears to another authorized teammate.
- Test the relevant attachment types with harmless sample files.
- Inspect any available history synchronization for missing context.
- Confirm ownership and automation behavior when someone replies manually.
If a required behavior is absent, record the gap and agree on a workaround before moving the wider team. A successful connection message is only one part of acceptance.
Plan for device changes
Meta’s reconnection guidance describes cases where changing devices or re-registering the app offboards the Cloud API companion. Include device changes in your support procedure rather than treating them as an unrelated personal-phone task.
Keep the responsible administrator, provider contact and recovery steps documented securely. Avoid sharing credentials in a group chat to make support faster.
Keep continuity separate from team discipline
Keeping the number does not decide who owns a lead. If one person replies in the app while another works in the CRM, the team still needs clear responsibility and a rule for pausing incompatible automation.
Use the shared inbox ownership guide to design that process, and review the cost checklist for the commercial questions. The best outcome is continuity that has been demonstrated in your daily workflow, with limitations understood before launch.
