Same boat here. Different flavor though. Ours got disabled for a spam/content violation, not the automation flag you guys are seeing, but same story: an automated system decided, and getting an actual human to look at it again has been impossible.

Case #: 1431143012368255

Following this thread, hoping Meta actually looks into these patterns

UPDATE 8/7/2026: Our portfolios have been unrestricted, and embedded signups are fully functional again.

Meta hasn't shared any information regarding the root cause, but everything appears to be back to normal.

@Meta, any insight into what happened would be greatly appreciated.

We at Ascendum are facing the same problem. We were blocked due to "automation," even though the process was carried out by a team of specialists.

Hello all,

We're also facing this exact same issue. We're a badged Meta Tech Partner and we do millions of messages in monthly volume. This is what happened with us:

Ad account got restricted with a message that we were using some automated systems, which we were not. That led to restriction of our Meta Business portfolio. That led to us loosing our Access Verification and the whatsapp_business_management Advanced permission.

We have never even run any ads from this Meta Business portfolio. We tried to request review a few times by going through the captcha and then uploading identity verification document. It worked first few times. But then last time we tried, it did not reinstate us. Now there's no button to request review.

We found a workaround where using apps Admin System User token is helping us continue providing whatsapp_business_management permission related features to existing users (like WABA and template management). So basically instead of using business's generated token we're using our main app level token and that seems to be working.

But this is a temporary hack and not a permanent solution. Our ad and Meta accounts are still restricted and as I can see from this thread and the WhatsApp group, this is wide spread.

Meta ads policy team needs to review this and resolve the issue with priority.

Ram

Hi everyone, we are in exactly the same situation.

We are a badged Meta Tech Partner supporting about 400 businesses. Since July 17, our fully verified portfolio has repeatedly been restricted for alleged advertising automation, despite using only the official WhatsApp Embedded Signup flow and the two required WhatsApp permissions. We do not run or manage advertising.

Verification restores access temporarily, but the restriction returns when legitimate Embedded Signup activity resumes. After roughly 15 support cases which never made it through Meta's first line of support, one case has finally reached a specialized team, but we have not gotten any info yet. We have paused trying to do the self-service verification on advise of this tech team to avoid triggering the loop again; existing connections remain operational yet we can't do graph calls because of the whatsapp_business_management permission being rejected during a restriction.

This needs to be fixed quickly, our business is bleeding for 15 days straight now, despite being fully compliant with all applicable Meta policies and terms.

Are you guys having trouble with payments too? I just can’t make a payment. I get error [...] every time, no matter which card I use.

Hey there! LATAM Tech provider here! this issue has really affected a lot of SAAS business on your cloud api, we need a solution ASAP

We've also had problems with the portfolios here. We requested an appeal, and after 2 minutes, for no reason, it was restricted again. Now, the rate limit for validating with an ID is also broken, preventing us from requesting a new appeal.

It's worth mentioning that these restrictions came out of nowhere, affecting businesses that were fully verified and not misused according to META's policies.

Adding to what David, Muhsin, and Sebastian have shared: We are experiencing the exact same automated loop, confirming this issue extends beyond LATAM and is also heavily affecting the MENA region.

We operate Mazbot, a verified Tech Provider serving WABAs across Egypt, KSA, and the UAE.

We are stuck in a verification loop. When we complete the ID/SMS verification, it is successfully accepted and the status momentarily shows 'AVAILABLE'. However, an automated trigger instantly re-locks the portfolio before any manual review can take place.

We are fully verified with zero ad-policy violations. This appears to be a systemic backend desync misfiring on legitimate Tech Providers.

I am already in the WhatsApp group. We kindly hope Meta Engineering can investigate this automated loop soon so we can all get our connected merchants back online. (Reference Case: #1380980743947195).

We’re experiencing the same issue. We currently support close to 3,500 WhatsApp accounts, with a similar number of accounts connected through Instagram and Facebook.

The problem started almost a month ago. We went through the review process, regained access for about a day, and were then blocked again. Since then, we’ve been stuck in a repeated review and suspension cycle. At this point, the verification flow no longer accepts our phone numbers or progresses at all.

The support experience has also been frustrating. We continue to receive standard responses without any clear explanation of what triggered the issue or what corrective action is expected from us.

As a tech partner, if there is a problem with how our customers are using the integration, we need specific information so that we can investigate and address it. Right now, we are not being told what is wrong, which policies may have been violated, or what changes we need to make.

Without that information, we have no clear path toward resolving the issue.

José, we're dealing with the exact same nightmare right now. Sharing what's happening to us because a warning like yours would've saved us a ton of pain.

We operate a WhatsApp AI sales tool for small ecommerce sellers across LATAM and Brazil. We're an Official Meta Tech Partner running on the Cloud API, and around July 19th our business portfolio got hit with a restriction citing the same "unauthorized automations" language. As of this moment, it's still locked down. Our merchants are small businesses whose only sales channel is often WhatsApp — for them, every hour offline isn't just annoying, it's lost income they can't get back.

Here's what lines up almost perfectly with what you described:

The official reason shifts constantly. Each time we open a support case we get a different justification, and none of them actually match our real activity. Our working theory: there's a single automated trust-and-safety trigger somewhere upstream, and every agent we talk to is just describing a different symptom of it. Trying to solve the "reason" they give you is a waste of time — it's not the real cause.

Disconnecting accounts changes nothing. The block is tied to the portfolio itself, and to the web of connections between assets — admins, payment methods, app ID, verified business data. Removing clients after the fact doesn't reset any of that.

Standard Business Support has been a dead end.

In the meantime, we're putting together a compensation plan for our merchants (extra days of service plus message credits) for once this gets resolved, and we're already dreading the reconnection process — re-linking thousands of numbers is a massive undertaking on its own.

Beyond the 5 companies you named, we're personally aware of at least 5 more SaaS platforms going through the identical situation. This has all the signs of a systemic issue, not something specific to any one of us. I want to believe it's an unintentional technical glitch on Meta's end rather than something deliberate — and that it gets fixed and acknowledged soon.

Happy to compare notes and timelines in more detail with the group.

We’re seeing the same pattern as well. We use Meta for WhatsApp, Instagram, Facebook/Messenger APIs, not ads, and our Business Portfolio was repeatedly restricted with the same account-integrity/automation reason.

The restriction cascaded into API permissions like whatsapp_business_management, pages_show_list, and Instagram permissions, breaking Embedded Signup, template sync, Facebook page listing, Instagram inbox creation, and Instagram messaging for production customers.

We tried appeals, removed stale/restricted partner assets, WABAs, ad accounts, admins/system users, and even moved the app to another verified portfolio. That restored access temporarily, but the new portfolio was later restricted too.

Meta support confirmed portfolio restrictions can deactivate Advanced Access permissions, but they still won’t disclose the exact trigger or asset category. We have around 3,000 connected accounts, so this has been a serious production incident for us. Happy to compare timelines and notes.

José, we're going through the same thing right now. Sharing our story because a post like yours would have saved us days.

We run a WhatsApp AI sales platform for small ecommerce merchants in LATAM and Brazil. We are Official Meta Tech Partners using Cloud API, Around July 19 our business manager got restricted with the same "unauthorized automations" reasoning. The portfolio is still blocked as I write this. Our merchants are small businesses that sell through WhatsApp or don't sell at all, so every day offline is not an inconvenience, it's their revenue and lives.

What matches your experience almost exactly:

The stated reason keeps changing. Every support case gets a different explanation, none of which describes anything we're actually doing. Our read so far: there's one upstream flag from an automated integrity system, and each support agent is reading a different downstream symptom of it. Chasing the stated reason is chasing shadows.

Removing accounts doesn't clear it. The flag lives at the portfolio level and in the links between assets (admins, payment, app ID, verified business info). Disconnecting customers after the flag does not reset anything.

Generic Business Support is going nowhere.

Meanwhile we're preparing compensation for our merchants (extra days plus conversation credits) for when this is over, and bracing for the re-onboarding, which is its own project when you have thousands of connections.

On top of the 5 companies you mention, we also know of at least 5 other SaaS platforms experiencing exactly the same thing. This looks like a general problem, not something any of us did individually. I hope it's not deliberate, but rather a technical error on Meta's side that gets acknowledged and fixed soon.

Happy to compare timelines in more detail at the group.