What “pending” actually means
On WhatsApp Business Platform (Cloud API), a phone number has a status. Connected means Meta has registered the number on your WhatsApp Business Account and you can send and receive. Pending means that registration is not finished — OTP, display name, certificate, migration, or partner setup is still open.
Refreshing the screen does not fix it. Pending is a state in Meta’s systems. It stays until the missing technical step is completed, or until Meta finishes a review you already triggered.
ZantaTech is a Meta Tech Partner. We register and connect numbers that sit on pending: Business Manager, WABA, phone registration, display name, and the API / webhook so your CRM can talk to WhatsApp.
Why numbers get stuck in pending
- OTP or voice PIN never completed — SMS did not arrive, the SIM is in another country, or the call was missed. Registration stays pending until the code is entered correctly.
- Display name still in review — Meta must approve the business name that appears in WhatsApp. A mismatch with your legal name or website often keeps the number from going live.
- Number still on WhatsApp app or another WABA — the same number cannot be a consumer WhatsApp and Cloud API at once, and it cannot sit on two Business Accounts. Pending often means a previous registration was not released.
- Business verification incomplete — some countries and some use cases need a verified Meta Business. Until that file is accepted, phone status can stay pending.
- Partner or app connection incomplete — the number was added in the UI but the technical register/connect call (or BSP / Tech Partner flow) never finished. That is the case we see most often when teams “did everything in Business Manager.”
The technical work required to register (pending → connected)
Connecting a pending number is not a settings toggle. It is a sequence Meta expects, in order:
-
1
Business Manager and WABA Confirm the Meta Business is the right one, the WhatsApp Business Account exists, and you have admin. Wrong BM is a common reason a number never leaves pending.
-
2
Phone registration Register the number against the Cloud API / partner app: certificate or register API, then OTP or voice verification on the live SIM (or the number’s voice/SMS route).
-
3
Display name and quality Submit a display name that matches the brand Meta can check on your website or documents. Track review until it is approved, not just submitted.
-
4
Connect to your stack Attach the number to the WhatsApp product, webhooks, and your CRM or automation (ZantaCore, Odoo, or custom). Pending in the UI often means this last connect step never ran.
We run that sequence for you. You keep the SIM or number provider available for the OTP window; we handle Meta, APIs, and the partner registration that Business Manager alone does not finish.
What we need from you
- The phone number (with country code) and whether it currently has WhatsApp installed.
- Meta Business Manager ID, if you already have one.
- Legal business name and website — for display name review.
- Who can receive the OTP (SIM in hand, or access to the voice/SMS inbox).
- Where messages should land after connect (CRM, website chat, or WhatsApp only).
Use the form on this page. We reply with the exact next step for your number — not a generic checklist.
What we do not do
We do not bypass Meta policy, buy grey-market numbers, or keep a number on consumer WhatsApp while registering Cloud API. If the number must be migrated, we tell you before anyone unregisters the app, so you do not lose chat history by accident.
Frequently asked questions
The number has been pending for weeks. Is it dead?
Usually not. Long pending almost always means a step was skipped: OTP, display name, old WhatsApp still linked, or the partner register call. We inspect the WABA and phone object in Meta and tell you which of those it is.
Do I need a Meta Tech Partner?
You can try self-serve Cloud API. Many teams still get stuck because embedded signup, certificates, and “register” vs “connect” are easy to leave half-done. A Tech Partner completes that path and ties the number to your actual product.
Will this work with our CRM?
Yes. After the number is connected we can route it into ZantaCore or Odoo CRM, or your own API. The pending problem is upstream of CRM — the number must be connected in Meta first.
