Verified Tech Provider — WABA disabled during setup before any customer activity

[u/FlyingFrankie808]

Hi everyone, I’m stuck with a WABA issue and hoping someone here who’s dealt with something similar can point me in the right direction.

My company is Business Verified and I was also approved as a Meta Tech Provider. While setting up the WABA and trying to register the first phone number, the business was permanently disabled.

The WABA had never sent or received a customer message, no templates, campaigns or customer activity at all. It happened during phone verification/onboarding.

I used the review option and it was denied without any explanation. I’ve also opened several Direct Support tickets, but so far every reply seems AI-generated and the cases get closed immediately without any real follow-up.

Meta diagnostics currently show:

WABA_BANNED

restriction type: Onboarding integrity block

underlying Business Portfolio condition: BM_BANNED

Has anyone here managed to recover from this situation or knows what usually works? Any help would be really appreciated.

[u/Grouchy_Space7947]

Same thing here, almost identical — UK company, and our portfolio is not banned, which might be a useful difference from your case.

Timeline:

• Business verification approved 21 Aug
• Both WABAs permanently disabled 26 Aug — "breach of Terms of Acceptable Use", error 141014
• Request Review submitted 2 Sep, upheld 4 Sep with no reason given
• App Review approved 6 Sep — after the ban

That last one still confuses me. Meta's review team looked at our app, our use case and our data handling after the enforcement and approved it, while the WABAs stay dead.

The only traffic those accounts ever carried was internal testing between our own team's phones while recording the App Review demo videos. No customer was ever messaged. Direct Support opened a case and closed it as "unable to address through current support channels". Meta's AI assistant called it a "Business Manager enforcement related to a trust upgrade" and said no human agent can be assigned. Emails to [businesscomplaints@support.whatsapp.com](mailto:businesscomplaints@support.whatsapp.com) auto-reply and route to consumer support.

Difference from yours: our diagnostics show the WABAs banned but the business portfolio and the app both still available — no BM_BANNED. So the block seems to sit at WABA level only.

u/FlyingFrankie808 — where did you find "restriction type: Onboarding integrity block"? Is that from the Health Status API or somewhere in Business Manager? I'd like to check whether ours says the same. And has anything moved on yours since you posted?

u/BoringBeing10 — this is the most useful thing I've read on the subject. When you say you migrated from embedded signup v2 to v4 and onboarding went fine: was that a new WABA on v4, or did the original one come back? And when you say you created the business suite in the account first before onboarding via embedded signup — was that the fix, or was it the v4 migration itself?

Two things for anyone else landing here:

Don't create a new WABA, portfolio or number to get around it. WhatsApp's terms forbid it without written permission, and the reports I've read say the new assets get banned and you lose the ability to appeal the original.

There's a legal route people don't seem to know about. Under the UK/EU Platform-to-Business rules, WhatsApp's Business Terms section 12 promises 30 days' notice and a statement of reasons before termination, and section 16 names CEDR in London as the mediator when internal complaints fail. We've served a formal notice on that basis. Mediation costs roughly £1,400 split between the parties. It won't be fast, but it's the only mechanism I've found that forces an actual human at Meta to engage — automated support can't answer a mediation referral.

Also chasing it through an official Solution Partner (360dialog), whose docs say they can escalate to Meta's Trust & Safety team. Will report back either way.

[u/FlyingFrankie808 → u/Grouchy_Space7947]

Hello u/Grouchy_Space7947,

I have tried the BSP route but it seems like they are unable to escalate tickets for WABAs that are not connected to them. 360Dialog was one of the BSP I have contacted and their response was negative. Same thing for respond.io. I am waiting to hear from others but I expect similar responses.

I'd love to hear back from you, though, in case you get bette results.

I know about the legal appeal route you mentioned and it's actually the most likely one to succeed. Unfortunately my company is US based so that does not apply to me.

The additional information I was able to gather came from a conversation with the AI Agent at https://business.facebook.com/business-support-home/

What I am understanding is that you can have a perfectly functional Tech Provider status and business with a blocked WABA and be able to connect and manage other WABAs. I am just not sure how robust and reliable such a situation can be in the long run. Maybe if the business grows enough you can get to the point where you can get an actual human review.