Number shows Pending or Offline after connecting
In WhatsApp Manager, Offline is the normal state of a WhatsApp Business app number before it joins the Cloud API, and it says nothing about eligibility. After a Coexistence connection, Meta's own check is is_on_biz_app true and platform_type CLOUD_API, and only a status of connected can send and receive. If the number stays Pending or Offline, read those fields before reconnecting.
easyCoexistence monitors each connected number around the clock, records Meta's disconnection reasons on its timeline, and lets your own AI read the live state with get_number_health.
Meta requires a business phone number to have the status connected to send and receive messages through the API.
One of the connection statuses Meta's phone number API lists, with CONNECTED, DISCONNECTED, FLAGGED, RESTRICTED and RATE_LIMITED.
With platform_type CLOUD_API, Meta's test that a number works with both the Cloud API and the WhatsApp Business app.
Meta tells platforms to skip phone number registration for a Coexistence number, because it is already registered.
The Cloud API error for a number attached to an account but never registered.
The can_send_message value Meta's health status returns when a number fails one or more messaging requirements.
Where do Pending and Offline show up?
They are Meta's labels, shown in WhatsApp Manager > Phone numbers and reflected in the status Meta's API returns for the number. They are not easyCoexistence labels. Our dashboard has its own: Connected, Degraded, Disconnected, Banned / restricted, Suspended and Unknown, set from our monitoring of quality, disconnection events and bans.
The two views answer different questions, so they can disagree for a while. WhatsApp Manager shows how Meta classifies the number right now. Our dashboard shows whether the connection is up and healthy and records each change on the number's timeline. When they disagree, the live fields described below settle it.
Is Offline normal before connecting?
Yes. A number that lives only in the WhatsApp Business app is not on the Cloud API yet, so if WhatsApp Manager lists it at all, it can show Offline or Offline / Unverified. That state does not block Coexistence and says nothing about eligibility; only Meta's connection step decides that.
Do not try to bring it online from WhatsApp Manager by registering it or requesting a code. That is the migration path, which moves the number off the WhatsApp Business app. Coexistence connects the number through Meta's signup window with a QR code scanned in the app, and Meta tells platforms to skip registration for it.
What should a finished connection show?
Meta gives one precise test, and the phone confirms it in plain words. If WhatsApp Manager still shows the old label a few minutes after connecting, reload it before acting; the fields below are the reliable check.
- Meta's fields on the number:
is_on_biz_apptrue andplatform_typeCLOUD_API. - Meta's status: connected, which is required to send and receive through the API.
- On the phone: the WhatsApp Business app says the number is connected to the API.
- In the app: Settings > Account > Business Platform lists the provider.
What if the fields show it left the business app?
Then the number was most likely verified with an SMS or voice code instead of the QR code. That is the migration path, not Coexistence: the number leaves the WhatsApp Business app (is_on_biz_app false), sits on the Cloud API without being registered, and the first send fails with error 133010. We verified one real case on 19 October 2026.
It cannot be finished as Coexistence afterwards. There are two ways out, and both need the provider's team: keep the number on the API only, with registration completed, or return it to the app and connect again by QR code. Never request a code in Meta's window during a Coexistence connection.
Offline or Disconnected weeks later
A number that worked and then drops has a different story. Meta disconnects a Coexistence number when the WhatsApp Business app on the phone is not opened for about 14 days, reported as PRIMARY_INACTIVITY in an account_update webhook. Other reasons Meta reports include a linked device unused for about 30 days, a change of number on the phone and the number registered again on another device.
On easyCoexistence the dashboard shows the number as Disconnected with Meta's reason, and the owner gets an email. The fix for inactivity is to open the app on that phone, let it sync, then reconnect. API messages do not count as opening the app.
How do you or your AI check the live state?
Ask your AI to run get_number_health, or ask it in plain words to check the health of your WhatsApp number. The tool reads Meta's live snapshot of the number (status, platform_type, is_on_biz_app and quality) and returns the last 15 events of its monitoring timeline. A coexistence_link_ok field sums up whether the number is still linked to the app. Separately, easyCoexistence reads Meta's health status and emails the owner when sending becomes BLOCKED.
{
"live_snapshot": {
"status": "CONNECTED",
"platform_type": "CLOUD_API",
"is_on_biz_app": true,
"quality_rating": "GREEN"
},
"coexistence_link_ok": true
}Common mistakes
- Registering the number in WhatsApp Manager to clear Offline before connecting. That is the migration path, which moves the number off the business app.
- Requesting an SMS or voice code in Meta's window. A Coexistence connection uses the QR code scanned in the app.
- Removing and reconnecting at the first sight of Pending, before reading is_on_biz_app and platform_type.
- Reading the dashboard label as Meta's status. They come from different checks; the live fields settle it.
The number stays in the WhatsApp Business app, with your automations working on it through Meta's official API. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Can the number send while it shows Pending?
Meta requires the status connected to send and receive through the API, so API sends fail until it is. The app on the phone keeps working.
Does Offline mean the phone is switched off?
Not by itself. The API does not need the app open at every moment; what Meta enforces is opening the app on that phone at least every 14 days.
Why does the dashboard say Connected while WhatsApp Manager says Pending?
The dashboard marks a number Connected when Meta finishes the signup and then follows quality, disconnections and bans. get_number_health reads Meta's live status directly.
Do customers' messages still reach the phone?
Yes. The WhatsApp Business app keeps receiving and sending on the phone whatever the API status shows.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on