WhatsApp coexistence requirements: what to check first

Most coexistence problems happen before any configuration: the number was the wrong type, the business account was not in order, or someone tried to connect something already occupied elsewhere.

This is the list to check before starting, in the order worth checking it.

1. The number is on the right app

There are three apps and only one works:

If the number is on regular WhatsApp, switching to Business is free and preserves conversations, but it has to happen first.

2. The number is not occupied elsewhere

A number can only live in one API account at a time. The situations that block:

• Already migrated to the Cloud API by you or a previous vendor
• In use on a support platform running through the official API
• Registered to a WhatsApp Business account in another portfolio

In all cases the way out is the same: release the number from where it is before connecting. And be warned — that release is usually the slowest step of the whole process, because it depends on the previous vendor.

3. The Meta business account is in order

Coexistence happens inside a Meta business portfolio. Before starting, check:

• the portfolio exists and you have admin access
• the business has no active restriction
• WhatsApp platform terms have been accepted

Business verification is not required to start, but it is what raises sending limits and unlocks features. Anyone planning to use this seriously should resolve it early, because the process takes days and depends on documents.

4. Someone with access and time

It sounds obvious and it is the most common cause of a half-finished process. Connecting requires:

• access to the phone with the app, to confirm
• admin access to the Meta portfolio
• the same person on both ends, or two people in the same room

Trying to do it with one person's phone and another person's Meta account, over chat, is how most attempts fail.

5. A time window for the sync

After connecting there is a period during which recent history is synchronized. While it runs, do not touch the configuration.

Choose the moment: starting at 6pm on a Friday as the team leaves is asking for someone to interfere mid-way. Early in the week, in the morning, with someone watching, is the scenario that works.

Checklist, to copy

BEFORE CONNECTING

[ ] Number is on the WhatsApp Business app (not regular)
[ ] Number is NOT registered to any Cloud API account
[ ] Number is NOT on a support platform using the official API
[ ] Meta business portfolio exists and I have admin access
[ ] WhatsApp platform terms accepted
[ ] Business verification resolved (or under way)
[ ] Phone with the app in hand at connection time
[ ] A few hours without anyone touching the configuration

If an item is unticked, resolve it first. Starting with a loose end is what produces a half-connected number.

The three situations that need a decision, not a checklist

The number belongs to a platform you want to leave. Technically you can release and reconnect, but you lose support coverage in between. Plan the switch for a low-volume day.

The number is personal and became commercial over time. Very common in small business. It works, as long as it moves to the Business app — but consider whether it is the number you want to advertise for years.

The company has several numbers. Start with one. Connecting four at once multiplies what can go wrong and prevents knowing what caused what.

After connecting

Two cautions in the first weeks:

Do not send in bulk. A new number on the API has low limits and a reputation to build. Volume sending right at the start is the fastest way to tank quality.

Watch the quality rating. The platform rates the number, and the rating falls with blocks and reports. The piece on WhatsApp number quality covers what moves that indicator.

To understand the difference from taking the number out of the app for good, see coexistence or migration.