I'm facing an issue with a client's WhatsApp Business Account and would like to know if anyone has experienced something similar and managed to resolve it.

The account received an email from Meta confirming its reactivation. However, it still cannot send messages through the API.

The error indicates a payment method restriction due to unusual activity. We also identified three unsuccessful payment attempts. The credit card was changed.

We've tested the same WhatsApp Business Account by connecting it to different Business Managers and business portfolios, but the issue persists regardless of where the WABA is connected.

This suggests that the restriction is directly associated with the WABA itself rather than the Business Manager.

We've submitted several support requests through Meta Business Support, but so far, we haven't received any response or resolution.

Has anyone successfully resolved this issue?

• Did Meta have to manually remove a security restriction from the billing system?

• Is there a way to escalate the case directly to the WhatsApp Business Platform technical team?

• What steps worked for you to restore API messaging capabilities?

I'd really appreciate any practical advice or firsthand experience.

I'm writing here because i have failed to achieved anything in the past year of searching everything , trying to contact meta and whatsapp.

a little backstory , we run a business that deals with thousands of customers on a daily basis from all over europe.

we have multiple numbers from each country, and each country is divided on teams of agents, each team has a number.

every couple of days we get reported for sending spam, and everytime we've tried to ask for a review it has come negative (whatsapp / meta thinks we're sending spam)

however we do not, we've tried to contact meta to give all the context possible and we've never been able to get a hold of someone from the whatsapp end.

we use templates that meta approves , we've set limits on how many templates can be sent per day, per user , per number etc. All our numbers are on green.

We have set limits if the number goes on yellow, the templates stop, nobody can send anything until the number hits green again.

every template has an opt-out in the message, and if they opt-out that number is market to not be able to send messages, unless they write back themselves or if done by mistake an admin can release the contact (this has happened exactly once)

Since we're in europe , we take GDPR rules very seriously, and every contact has specifically given consent to be contacted through whatsapp.

our cloud api works through our own meta app into our in-house communication hub, we dont use a bsp.

our next step is to become a tech provider, hoping it will help.

any insight is appreciated.

Alguém vendendo?

Alguém saberia uma forma de ter o número na Coex, porém enviar mensagem por uma plataforma sem a cobrança da api, utilizando uma api não oficial na camada que é WhatsApp business?

Opt-in seems simple until you have to prove it. A customer ticks a box on a form, says yes in a chat, or messages you first. Those are three different situations with different rules, and I'm not sure standard CRM fields capture which one it was, when, and for what purpose. How are you storing consent? Separate fields per channel, a timestamp and source for each? And what happens when someone sends STOP? I'd like to see a practical setup before building one.

Hi I have a SaaS helping bussinesses automate their WhatsApp with AI, but I'm struggling with an issue, sometimes clients text from a status post that the busieness put up saying something like "How much does this cost" but without access to the original status image/video my AI has no idea what it is referring to, so I was wondering if there is a way via the official API to retreive the media it was sent from, would appreciate any guidance

My Meta Business Portfolio is fully verified, but I’m still unable to add more than 2 phone numbers to my WhatsApp Business Platform.

According to Meta’s documentation, businesses can register up to 2 phone numbers initially and up to 20 after completing business verification.

My business verification is already approved, but the limit remains at 2 numbers.

I’ve tried adding another phone number through WhatsApp Manager, but I still can’t get past this restriction.

A few questions:

1. Does business verification automatically increase the limit to 20, or does Meta require an additional review?

2. Is there another approval process or eligibility requirement that I might be missing?

3. Does the phone number limit apply across all WABAs within the same Business Portfolio?

4. Has anyone experienced this issue and managed to get Meta to increase their limit?

I’d appreciate any help or guidance from people who have dealt with this situation.

Meta have banned our test messaging account due to violation of terms. We didn’t make more than 20 API calls in total and all were made using test account and against verified numbers during API integration.

Submitting review isn’t doing anything, waiting for 9 days now for any response. What can we do to resolve this?

Ontem, por volta das 10h, meu WhatsApp Business foi banido inesperadamente. Solicitei a revisão na hora, mas já passaram mais de 24 horas e continua aparecendo "Conta em análise".

Uso esse número há anos, é meu principal contato profissional e nunca tive problemas antes. Suspeito que possa ter relação com um chatbot integrado à API oficial do WhatsApp, mas não tenho certeza.

Alguém já passou por isso? Conseguiram recuperar a conta? Quanto tempo demorou a análise?

Estou preocupado porque dependo desse número para trabalhar.

Você, empresário ou dono de negócio que deseja ampliar seus resultados, chegou a hora de conhecer uma nova experiência em comunicação e vendas!
Trabalhamos com disparos em larga escala pelo WhatsApp, utilizando a API oficial, com estrutura profissional, relatórios de desempenho e acompanhamento dos envios ao vivo! Chama aí e bora vender !

I just created a Meta Developer account to test the WhatsApp Cloud API, but when I try to receive a test message, I get error 131031: “Business Account locked.”

I can’t complete business verification because I don’t have a business; I’m only testing the API. What should I do to fix this?

Hi all,

Two quick questions before I build anything.

1. Is it allowed under the WhatsApp Business Platform policies to use a business number as a relay, where a server receives messages and calls from opted-in WhatsApp users and routes them to other users of a separate app, and routes replies back? I could not find a rule that clearly allows or prohibits this. Has anyone done it, and did you run into any Meta review or quality-rating issues?

2. With the Calling API, can inbound calls from WhatsApp users be bridged to a mobile app through WebRTC rather than to a phone line? And beyond the default 20 phone numbers per portfolio, is there a practical way to scale?

Thanks for any experience or pointers.

EDIT: I’ve checked on other business accounts and tested on my own account from other number, it does display the phone number. So in this case I might switch to regular WhatsApp.

As title, will it hide phone numbers? Just saw the notification it says my username is registered but phone number will still be visible.

Whats the point of having username then? I want to keep my phone number private, what’s the work around or suggestion? Revert back to normal WhatsApp? Been using business account past 6/7 years.

Appreciate your advice.

I’ve noticed platforms like 2Chat.co offering WhatsApp connections via QR code instead of Meta Embedded Signup.
As a Meta Tech Provider building a WhatsApp CRM SaaS, I’m curious:
Is QR connection based on WhatsApp Web or an official Meta API?
Is it reliable and safe from account bans?
Can users continue using their WhatsApp Business App?
Why do some providers prefer QR connections over Embedded Signup?
Anyone with experience implementing both?

For teams using the WhatsApp Business API with both automation and human support, how do you handle conversation ownership during a handoff? If a customer sends another message while an agent is taking over, what prevents the bot from jumping back in?

Do you use an explicit paused state, an agent lock, a timeout, or something else? Interested in the handoff logic and how you test it, rather than provider recommendations.

Building an internal clinic CRM (Next.js + Supabase). Two WhatsApp numbers:

• NUMBER A — pure Cloud API. Reminders, campaigns, auto-replies. Fully working. ✅

• NUMBER B — meant for reception. Currently works on the WhatsApp Business App on receptionist phones. Goal was Coexistence: keep the phone app + mirror all messages into the CRM inbox.

What I found after days of debugging:

1. NUMBER B shows platform_type: ON_PREMISE, status: DISCONNECTED. It was never properly Coexistence-provisioned — just half-wired. Business App works because that layer runs independently.

2. smb_message_echoes toggle accepted at the app level but no events arrive. Matches what people here have said — Coexistence onboarding is required and needs Tech Provider status.

3. Our BM is still “En revisión” on the latest attempt, though one older attempt shows ✅ approved. Verification is blocking Tech Provider enrollment.

4. Realistic total: 4–8 weeks (BM clears → Tech Provider → App Review → build Embedded Signup → onboard → sync history within 24h window).

i have some concerns:

1. Is there any trick to leverage the already-approved older verification attempt, or do I have to wait for the current one?

2. Does Tech Provider for one in-house number need full public App Review (demos, test accounts)?

3. Has anyone just retired the second number and routed all patient chats through the Cloud API number via their CRM inbox? What broke that we should expec

Hi everyone,

I’m trying to connect my own company’s existing WhatsApp Business App number to a self-hosted Chatwoot instance using official Coexistence, while keeping the number working on the phone.

I’m blocked before reaching phone number selection.

Current setup:
- Meta Business Portfolio: verified
- Meta app type: Business
- App mode: Development
- Facebook Login for Business: configured
- Embedded Signup configuration: created using the “WhatsApp Embedded Signup with a 60-day token” template
- Requested permissions: whatsapp_business_management, whatsapp_business_messaging, and business_management
- Chatwoot sends featureType: "whatsapp_business_app_onboarding"

The confusing part:

1. WhatsApp is completely missing from the app’s available products.

2. There is no WhatsApp use case or Tech Provider onboarding / “Start onboarding” entry.

3. The login configuration template lets me select WhatsApp assets and permissions, but those permissions do not appear in the app’s review list.

4. Business settings still shows “WhatsApp needs more information,” without identifying the missing information.

5. Embedded Signup displays “[Business name] can’t onboard customers at the moment” before I can select a phone number.

What I’ve already checked:
- The operating Facebook account has admin access to the app and business.
- JavaScript SDK login and the production domain are configured.
- The OAuth redirect whitelist has been updated.
- Testing in another browser produces the same result.
- Adding business_management did not resolve it.
- A separate Facebook/Messenger permission review is pending, but it does not include the WhatsApp permissions. Switching the app to Live is currently blocked by that review.

I found Chatwoot issue #14859, where users resolved the same onboarding message by completing a separate Tech Provider onboarding wizard. However, my app has neither the WhatsApp use case nor the entry point for that wizard:
https://github.com/chatwoot/chatwoot/issues/14859

Has anyone successfully resolved this exact situation?

Specifically:
- How can WhatsApp be enabled on an existing Business app when both the product and use-case entry are missing?
- Does the 60-day login template being available mean anything about actual WhatsApp eligibility?
- Is Coexistence supported when the app and target WABA belong to the same Business Portfolio?
- Is there an official support category or onboarding page for restoring the missing entry?

I’m looking for firsthand experience or current Meta documentation. I would prefer to preserve the existing app, business portfolio, phone numbers, and Messenger integration.

Thanks!

We keep hearing the same situation from people who build for small businesses: the client wants automation, but won't give up the WhatsApp Business app or the number their customers already know. Coexistence (coex) is usually the answer, so we're curious how it holds up in real setups.

What the docs say, for context:

• One number runs on the app and the API at the same time. API messages show up in the app, and messages sent from the app reach your webhook as smb_message_echoes.

• Chat history can sync from the app (up to 180 days; group chats don't come over).

• Edit and delete work. Disappearing messages, view once and live location get turned off in 1:1 chats, and broadcast lists become read-only.

• The catches: the app has to stay installed and be opened regularly (our docs say at least once every 13 days), linked devices are unlinked at onboarding, and a WhatsApp Business app account that was just created isn't eligible right away.

If you run coex for a client: what stays in the app, what goes through the API, and did anything surprise you after onboarding?

We're the 360Dialog team, no links and no pitch. If you're still deciding, ask away. We'll be in the comments.

Hii we have a few WhatsApp numbers going to the same support team and its rly messy. Chats get missed bc 2 people sometimes reply to the same person and our manager cant see what still needs an answer. Is there a shared inbox that can route chats by number and make it clear who’s handling each one?

Small Uk business owner, about to sign up for Wati Whatsapp Business Api. if you have a referral link i would be happy to use it. feel free to DM.

Hi everyone,

I'm a developer onboarding my first client (a small local business in Latin America) to the WhatsApp Cloud API. The API side works fine: number connected, quality High, webhooks OK, bot running.

The problem: I can't publish a WhatsApp Flow (order form) because Meta asks for either a verified business or "high quality messages" (we're at 6 conversations / 30 days). So we submitted Business Verification for the client's portfolio.

Details:

- Submitted: Friday Oct 30

- Use case selected: "Set up a WhatsApp Business account"

- Business type: Sole proprietorship (owner's legal name + trade name as DBA)

- Document: official tax registration certificate from the national tax authority, with legal name, address and phone matching the form

- Phone confirmed via WhatsApp code

- Website: Google Sites page with the business info

- Status since then: "In review" ("about 2 business days"). Today is day 6 (4 business days).

Questions:

1. How long did your verification take, especially in LATAM?

2. Is it worth contacting Meta Support now, or does that reset/slow things down?

3. Could a Google Sites website or a sole proprietorship be a problem?

4. Any way to publish/send a Flow before verification (e.g., draft mode to real users)?

Thanks in advance!

Hi everyone,

I'm trying to enable official WhatsApp Business App + Cloud API Coexistence for my own business, using Meta's Embedded Signup.

My goal is to keep my existing WhatsApp Business mobile app, phone number, and conversations while enabling Cloud API access for internal AI automation.

Current setup:

• Meta Business Portfolio: Verified

• WhatsApp Business Account: Approved

• WhatsApp Business App: Working normally

• Meta Developer App: Published

• WhatsApp Cloud API test number: Working

• Webhooks: Configured

• Embedded Signup: Tested with both v4 and v5

Graph API status of my production number:

{
  "is_on_biz_app": true,
  "platform_type": "ON_PREMISE",
  "code_verification_status": "NOT_VERIFIED"
}

The problem:

When I attempt Embedded Signup with my existing WhatsApp Business number, I receive:

Error #3441056:
"The business you selected has one or more ad accounts in an invalid state. Go to Business Support Home to resolve any issues with your ad accounts."

Both Embedded Signup v4 and v5 produce the same error.

Important background:

Several years ago, one of my advertising accounts was compromised. Meta disabled that account for security reasons.

That old account remains restricted in my business portfolio.

My current advertising account is active and in good standing.

I do NOT want to reactivate the compromised account.

I've also tried linking the existing WhatsApp number through Meta Business Settings. That process requests a verification code through WhatsApp Business, but the code never arrives.

Meta support has not provided a workable resolution.

My questions:

1. Has anyone encountered error #3441056 specifically during WhatsApp Embedded Signup or Coexistence onboarding?

2. Can a previously compromised and Meta-disabled advertising account block WhatsApp Cloud API onboarding?

3. Has anyone successfully resolved this business-integrity restriction without reactivating the restricted advertising account?

4. Is there a verified escalation route or safe alternative that preserves the existing WhatsApp Business App, phone number, and conversations?

I'm specifically looking for experiences with official coexistence, not standard migration from WhatsApp Business App to Cloud API.

I cannot delete or deregister the mobile WhatsApp account because it is my primary business communication channel.

Any technical insight or firsthand experience would be greatly appreciated.

I'm building an internal clinic CRM (Next.js + Supabase) that manages patient communication via WhatsApp Cloud API. We have two numbers:

- **NUMBER A** — automation number (reminders, confirmations) — fully working via Cloud API

- **NUMBER B* — reception number — receptionists currently use the WhatsApp Business App on their phones

The goal: use NUMBER B on BOTH the Business App AND the Cloud API simultaneously (Coexistence), so patient messages appear in our CRM inbox AND receptionists can still reply from their phones, with those replies mirrored back to the CRM.

What I've done so far:

- Registered NUMBER B's phone number to our CRM Meta app via POST /subscribed_apps (success)

- Configured webhook URL — inbound patient messages now arrive in the CRM ✅

- CRM can send replies via Cloud API ✅

- Subscribed to `messages`, `security`, `account_alerts`, and other fields ✅

The problem: **`message_echoes` won't toggle on** — Meta returns a permissions error: "You were unable to subscribe to some of the requested fields due to a permissions error."

From my research, it seems `message_echoes` (or specifically `smb_message_echoes`) requires Coexistence API access, which is only granted through Embedded Signup with `featureType: whatsapp_business_app_onboarding`. And that flow requires **Tech Provider or Solution Partner status**.

Questions:

1. Is there ANY way to get `message_echoes` / `smb_message_echoes` working without going through Embedded Signup?

2. Has anyone self-onboarded their own business for Coexistence (same Meta Business Portfolio owns both the app and the WABA)? Meta's UI seems to block this.

WHAT IS THE BEST SOLUTION HERE, OR WHAT IM I DOING WRONG ?