All articles
WhatsApp API

WhatsApp Number Ineligible in Coexistence: 2026 Guide

WhatsApp number showing 'ineligible' during Coexistence registration? Here are the real Meta eligibility rules and the fix order that works in 2026.

RichAutomate
9 min read 0 views
WhatsApp Number Ineligible in Coexistence: 2026 Guide

If your WhatsApp Business number shows ineligible or not eligible during Coexistence registration, the number is failing one of Meta's pre-checks: it is not actually live on the WhatsApp Business App right now, it is already attached to a Cloud API account or another WABA, the app build is too old, or the account sits in a state Meta will not duplicate such as previously deleted, restricted, or mid business verification. Fix the failing pre-check on the phone first, then re-run registration, because in most Indian cases the number turns eligible on its own within hours and never needs a support ticket.

The error message is deliberately vague. Meta reports a single eligibility verdict and does not tell you which criterion broke, so the only reliable method is to test each criterion yourself in a fixed order. This guide covers what Coexistence really does to your number, the full criteria list, a cause and fix table, the remediation order, realistic waiting times, and the point at which a full migration is the cheaper decision.

What Coexistence actually changes about your number

Coexistence keeps the WhatsApp Business App working on the phone while the same number is also connected to the WhatsApp Cloud API through a provider. Incoming chats still arrive in the app, and your automations, broadcasts, chatbot and CRM run through the API on the same number at the same time. Meta syncs a limited slice of recent chat history and your contact list into the cloud so the API side has context from day one.

This is not a trial mode. The moment registration succeeds, that number is a real API sender: messaging limits, template approval rules, per-conversation pricing and quality ratings all apply to it. It is also not the same thing as a full migration, where the app stops working on the number and every conversation moves to the API. The distinction matters for eligibility, and we break it down fully in our WhatsApp Business App and API Coexistence guide for India.

The checks exist because Meta has to be certain the number is on exactly one live app install before it mirrors that number into the cloud.

Meta's eligibility criteria for Coexistence registration

A number qualifies only when every one of these is true at the same moment you run registration:

  • The number is currently active on the WhatsApp Business App. Not the consumer WhatsApp app, not a number you deleted last month, and not a number sitting on a device that has been logged out.
  • The number is not already registered on the Cloud API or any other WABA. A half-finished setup from an earlier provider is the single most common blocker in India.
  • The WhatsApp Business App is updated to a version that supports Coexistence. Older builds do not expose the linking flow at all, and registration will read the number as unsupported.
  • Coexistence is available in the number's country and for that account type. Meta has rolled the feature out in stages and availability still varies by market and by app build.
  • The number was never deleted, banned or restricted on WhatsApp. A number that previously carried a policy strike may stay ineligible even after the restriction lapses.
  • The business account is in a clean verification state. A Business Manager stuck mid verification, or one that failed verification, commonly blocks the linking step.
  • Two-step verification PIN is known or cleared. If an old six digit PIN is set on the number and nobody remembers it, the registration step cannot complete.
  • One device owns the app install. A number being juggled across a reinstall, a new phone, or a pending chat transfer reads as unstable to Meta's check.

Why registration says ineligible: causes and fixes

Match the symptom you see to the most likely cause before touching anything. Changing three things at once makes the next attempt impossible to diagnose.

What you seeMost likely causeFix
Number ineligible immediately, no OTP sentNumber already attached to another WABA or a stale Cloud API setupFind the old Business Manager, remove the number from that WABA, wait for the release to propagate, retry
No Coexistence or linking option inside the appApp build too old, or feature not yet enabled for that installUpdate the WhatsApp Business App from the store, force close, reopen, check again after a day
Ineligible after a recent reinstall or phone changeAccount state still settling on Meta's sideUse the app normally for a day, send and receive real chats, then retry
Registration fails at the PIN stepOld two-step verification PIN set on the numberDisable or reset two-step verification in app settings, then start registration again
Eligible on one number, ineligible on another in the same businessThat specific number has a past deletion, ban or restrictionCheck the number's standing, and if it was restricted before, plan around a different number
Ineligible while Business Manager shows verification pendingBusiness verification incomplete or failedComplete verification with GST and registration documents that match the legal entity name exactly, then retry
Number works on consumer WhatsApp onlyNot on the WhatsApp Business App at allMove the number to the WhatsApp Business App first, use it for a day, then register

The remediation order that saves the most time

Work top to bottom and retry registration after each step. Stop as soon as the number turns eligible.

Stop overpaying on WhatsApp

Get a 1-minute BSP audit on WhatsApp

Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.

DPDP-compliant · India-hosted · 1-min reply
  1. Confirm the number is live on the WhatsApp Business App on one phone, with recent sent and received messages.
  2. Update the app from Play Store or App Store and reopen it fully.
  3. Clear any existing API attachment. If the number ever touched another provider, remove it from that WABA in Business Manager. Numbers released from an old account are not always instantly free, so allow a little time before retrying. If you are coming off another provider, our guide to switching WhatsApp BSP in India covers the release sequence.
  4. Reset two-step verification so no unknown PIN blocks the final step.
  5. Check business verification status in Business Manager and finish it if it is pending or rejected.
  6. Retry once, then wait. Repeated back to back attempts do not speed anything up and can leave the number in a temporarily locked retry state.

Want the eligibility checks run for you? Start a 14 day trial with 100 free credits and our onboarding team will read the registration response, tell you which criterion failed, and sequence the fix. Create your account.

How long Meta's eligibility checks take

Meta does not publish a service level for this check, so treat any exact hour count you read online with suspicion. In practice the pattern looks like this: an app update or a PIN reset usually clears within minutes to a few hours, while releasing a number from an old WABA and having it read as free typically takes a few hours to a couple of days. Business verification is the slow one and runs on its own review queue, which can stretch considerably longer when documents do not match the legal entity name.

Make one change, retry once, then leave the number alone for the rest of the day. Eligibility is re-evaluated on every attempt, so patience costs less than churn.

When to migrate fully instead of coexisting

Coexistence is worth fighting for when a real human team still answers chats on the phone every day and you only want automation layered on top. If that is not your situation, a full migration is usually faster to get live and simpler to support.

Choose a full migration when the number is stuck ineligible for reasons you cannot change, when nobody actually uses the phone app any more, when you need multi agent inboxes and routing rather than one device, or when the app install itself is the unstable part. The trade is that the WhatsApp Business App stops working on that number once migration completes, so exports and chat history need planning first. Our walkthrough on how to migrate a WhatsApp Business App number to the API covers the export, downtime window and template setup.

One more case for migrating: a number with a history of user reports. Coexistence does nothing to repair quality signals, and a number already carrying complaints will hit the same walls on the API. If that sounds familiar, read what to do when a WhatsApp Business number gets blocked or reported by users before you register anything.

What to send support if the number stays ineligible

If the number is still ineligible after the full remediation order, a ticket is reasonable. Vague tickets get vague answers, so include every one of these:

  • The number in full international format, with country code.
  • A screenshot of the exact ineligible message, with the timestamp visible.
  • The Business Manager ID and WABA ID you are registering into.
  • Whether the number has ever been on the Cloud API before, and with which provider.
  • The WhatsApp Business App version number from app settings.
  • Your business verification status, with the date of the last submission.
  • A list of what you already tried and the result of each attempt.

Be honest about past restrictions. Meta reviewers can see the account history anyway, and a ticket that omits a previous deletion just adds a round trip. No provider can guarantee that a number will be approved, and anyone promising that a number can never be banned is not describing how WhatsApp policy works.

What Coexistence costs to run in India

Eligibility is free to attempt, and the cost only starts once the number is live and sending. Our model is usage only: Rs 0 setup, Rs 0 monthly floor, and no per seat charge for keeping the app running alongside the API.

On Client Pay you are billed Rs 0.10 per message by us while Meta bills your conversation charges directly to your own payment method. On SaaS Pay we handle the Meta side and bill Rs 1.20 per marketing message and Rs 0.30 per utility or authentication message. Every new account gets a 14 day trial with 100 free credits, which is enough to finish registration, approve a first template and test real delivery before spending anything. Model your own volume with the WhatsApp API cost calculator, or compare both billing modes on our WhatsApp API pricing page.

Stuck on an ineligible number this week?

Run the eligibility checks with a team that reads the registration response for a living. Trial is 14 days with 100 free credits, and there is no setup fee.

Start free on RichAutomate

The short version: ineligible is a state, not a verdict. Work the criteria in order, change one thing per attempt, and give Meta's checks a day before escalating. Most numbers clear on their own, and the ones that do not are usually telling you that a full migration was the right call from the start.

Ready to ship this?

Get the full migration playbook on WhatsApp

A founder-led 1-minute reply with the migration steps, template approval timeline, and a 14-day pilot offer. DPDP-compliant. India-hosted. No spam.

DPDP-compliant · India-hosted · 1-min reply
Tagged
WhatsApp APICoexistenceCloud APITroubleshootingIndiaBusiness VerificationNumber Migration
Written by
RichAutomate
Editorial team at RichAutomate. We build the WhatsApp Business automation platform Indian D2C brands, fintechs, and agencies use to ship campaigns and flows on the official Meta Cloud API.
FAQ

Frequently asked questions

Why does my WhatsApp number show ineligible during Coexistence registration?
Because it fails at least one of Meta's pre-checks. The usual causes are: the number is not currently live on the WhatsApp Business App, it is already attached to a Cloud API account or another WABA, the app version is too old to support Coexistence, an old two-step verification PIN is set, business verification is pending or failed, or the number was previously deleted or restricted. Meta reports one combined verdict without naming the failing check, so you test each criterion in order.
How long does it take for a number to become eligible after I fix the problem?
It depends on what you fixed. App updates and PIN resets usually clear within minutes to a few hours. Releasing a number from an old WABA so it reads as free typically takes a few hours to a couple of days. Business verification runs on a separate review queue and can take considerably longer, especially when your documents do not match the registered legal entity name exactly. Retry once after each change rather than repeatedly.
Can I use Coexistence if my number was on another provider's API before?
Yes, provided the number is fully released from that provider's WhatsApp Business Account first and is back in active use on the WhatsApp Business App. A half-removed number is the most common reason Indian businesses see ineligible. Ask the previous provider to confirm the number has been removed from their WABA, then allow time for the release to register on Meta's side before you retry.
Does Coexistence protect my number from being banned?
No. Nobody can promise that. Once Coexistence succeeds, the number is a real API sender and is subject to the same messaging limits, template rules, quality rating and policy enforcement as any other WhatsApp Business API number. Opt-in discipline, relevant templates and low block rates are what protect a number, not the setup method you used to connect it.
Should I coexist or migrate fully to the API?
Coexist when a team still answers chats on the phone daily and you only want automation added on top. Migrate fully when nobody uses the app any more, when you need multi-agent inboxes and routing, or when the number stays ineligible for reasons you cannot change. Migration removes the WhatsApp Business App from that number permanently, so export chats and plan the cutover window before you start.
RichAutomate · WhatsApp BSP for India 2026

Ship WhatsApp campaigns + flows on a transparent, compliance-ready BSP.

₹0 platform fee. DPDP audit log included. Visual flow builder. Multi-tenant from day one.

Start free trial
Want this for your brand?

Get a free 24-hour BSP audit

Send us your last invoice. We line-item it against Meta's published rates and benchmark against three alternatives.

Limited Spots Available

Get a Free
Automation Audit

Stop leaving revenue on the table. Get a custom roadmap to automate your growth.

Secure & Confidential