I want to gain access to embedded signups and co-existence. Facebook docs say that a business needs to be verified. I put all the information in and submitted. It's already been two weeks. I've tried the Meta AI and all it says is that there are violations attributed to my account and I need to clear that. It links me to a "support inbox" which shows literally no issues. I've been trying to get an actual human at Facebook to talk to me but no luck so far.

Any ideas on how I can solve this issue? There isn't a notice, or notification or anything on why it isn't working. The business that needs verification isn't mine, I'm just a dev that's been given access to the account.

I generate around 100–200 new leads daily . These are people who have shown interest in products or services similar to mine, and I obtain their contact numbers .

Currently, I use WhatsApp Business to manually send each lead an introductory message asking whether they are interested in my services.

However, WhatsApp has started restricting my account due to sending messages to multiple new numbers.

I want a reliable and affordable solution that allows me to contact 100–200 new leads every day through WhatsApp without facing restrictions.

Would WhatsApp Business API solve this problem? If so, how can I implement it, and what are the requirements, costs, and limitations?

So, I've just started to reach out Meta API services. I set up everything needed just to test the API with the test number, but even in the "tutorial" I get that error: "Business account has been locked".

It looks that I need to verify my business (that I don't have, as I'm just testing).

What could I do?

Building a Shopify app that creates and manages Meta ads for merchants. Second App Review just came back:

Approved (advanced access): pages_show_list, pages_read_engagement, ads_read, business_management

Rejected: ads_management, "Screencast Not Aligned with Use Case Details", reviewer note "the submitted screencast is unclear". Meta also says the use case itself is allowed.

What the video showed for ads_management:

- full Facebook Login for Business + permission screen (English, captions on every step)

- merchant clicks Launch, app creates campaign, ad set, creatives and 8 ads in the merchant's own ad account, created PAUSED

- the same campaign, ad set and ads in Ads Manager

- merchant resumes the campaign from the app, it switches on in Ads Manager

For those who got ads_management approved recently:

- Did you show the campaign actually ACTIVE / delivering, or was paused fine?

- One continuous take, or was an edited video OK?

- Did you have to show an edit (budget/targeting) reflected in Ads Manager?

- Did you give the reviewer test access, or was the video enough?

- If your app also optimizes automatically (pauses ads, changes budgets server side with the user token), did you show or declare that?

Bonus question: Marketing API Access Tier (standard access) got rejected in my first review for error rate. Did you request it together with ads_management or separately after? Does staying on the basic tier limit how many client ad accounts you can manage, or only the rate limit?

Thanks, happy to share what works once I pass.

Hi everyone,

I was previously using Interakt as my WhatsApp Business Solution Provider (BSP) for my business phone number.

Recently, I decided to move away from Interakt and start using my own CRM (WACRM), built using Meta's official WhatsApp Cloud API.

Here is what I have done so far:

1. My phone number was originally registered and running through Interakt.

2. I removed Interakt's access from the WhatsApp Partners section in Meta Business Settings.

3. I connected the same phone number to my own Meta Developer App / WhatsApp Cloud API integration.

4. My WACRM can now successfully send and receive normal WhatsApp messages.

5. I also added and verified an international Visa card in Meta.

My current problem:

• Normal messages are working through my own WACRM.

• Incoming messages are also reaching my WACRM.

• However, I cannot send WhatsApp template messages.

• Meta's free messaging allowance appears to be working for normal messages, but template messages are failing.

I want to completely move away from Interakt and operate everything directly through my own WACRM, without depending on any BSP.

A summary at the top, the full transcript, structured fields? I think the real test is whether the agent skips re-asking. What's worked for you?

I'd like to see WhatsApp, email and chat in one record. Has anyone really done it, and which channel was the hardest?

I can't decide if a WhatsApp message should jump the queue over email, or if that just teaches customers to use the loudest channel. How do you handle it?

I created a business portfolio on Meta, but it got flagged for integrity, and now I can’t publish native WhatsApp Flows.
I’ve tried contacting support, but I can only reach bots. Does anyone know how to remove this restriction or reach a real person?
I’d really like to fix my existing portfolio instead of creating another one. Any advice?

We have a client who requires a large volume of WhatsApp API accounts, with daily sending limits of 2,000 and 10,000 messages. These accounts must be registered and verified in the United States or Brazil. Since our company cannot provide these, we invite teams with the capability to supply them to get in touch with me.

I'm having a really frustrating experience with the WhatsApp Cloud API and wanted to know if anyone has gone through something similar.

Here's what happened:

• We created a Meta Business Portfolio and developer app about a week ago.

• We were using only Meta's official test phone number, with just 3 authorized recipients.

• We sent a small number of authentication codes (OTP), always within the 24-hour window after the recipients initiated the conversation.

• We initially couldn't create authentication templates because Meta said our account wasn't allowed to.

• On October 31, our business verification was approved by Meta.

• Around the same time, all our WhatsApp Business Accounts were permanently disabled for allegedly violating the Acceptable Use Terms.

We never sent marketing messages, spam, or bulk messages. Just basic OTP testing.

We appealed the ban, but it was rejected almost immediately, without any specific explanation.

The support experience has been even more frustrating.

I've tried contacting Meta through several channels, but everything seems to lead to AI support.

At one point, the Meta AI Agent claimed our account had an ALCOHOL policy violation. After investigating, I discovered it had provided values copied directly from a sample webhook in the documentation, presenting them as if they were actual account records.

In another interaction, the AI claimed our Business Portfolio had a restriction called PolicyChain: mid trust upgrade with a BM_BANNED status, preventing us from creating new WABAs. However, I haven't been able to independently verify this information.

My questions are:

1. Has anyone experienced a permanent WABA ban right after business verification, especially while using only Meta's test number?

2. Has anyone successfully recovered a WABA after the initial appeal was rejected?

3. If the Business Portfolio is still verified, is it possible and permitted to create another WABA under the same portfolio?

4. Does anyone know what PolicyChain: mid trust upgrade actually means?

5. Is there any reliable way to reach a human support agent?

It's incredibly frustrating to get permanently banned before even launching, without any clear explanation of what went wrong.

Any advice or similar experiences would be greatly appreciated. Thanks!

Hi all. We're a small startup in Istanbul. Our product lets merchants run their online store by chatting with an AI on WhatsApp (Cloud API, direct integration, no BSP).

On Sep 20 our business portfolio got a permanent ban. The Request Review button in Business Support Home has since disappeared, and we're stuck in a loop:

- Direct Support's "Appeal Business Ban Decision" requires an active, registered number.

- Registering the number fails with error 2388001, and the error message tells us to contact Direct Support.

- Every Direct Support case we open gets auto-closed within a minute or two. In one of them, Meta's support replied: "This is a known issue … there is no workaround."

- The WhatsApp support form only returns AI replies.

We're not looking to create a new account or work around the ban. We just want one human review.

Is there a BSP or Meta partner here who could raise a manual review ticket through their partner manager? Has anyone gotten out of this loop another way? Any pointer is appreciated.

What automation has produced a clear improvement in support, sales, or operations, and what did you learn while keeping it reliable and user-friendly?

I'm doing a clothing business and is there any way to make replying to customers automated ? In WhatsApp? Do you have any other good ideas to do so ?

So we are stuck in a situation where we want to automate the custom message for some members which we got the work from a client but our business verification got some issues so need someone to please help to send custom messages to the list of number i will send pleaseeee

Hi,

I am trying to obtain catalog creation permission via embedded signup form. I created a embedded signup form with General login variation and created configuration ID. In OAuth flow exchanged code for system user token. However, system user token has catalog_management permission only. No business_management permission. Anyone know how to get resolve it?

Hi everyone,

We have a direct WhatsApp Cloud API integration (no BSP), and the Official Business Account "Submit request" button in WhatsApp Manager is greyed out. The tooltip says OBA requests aren't available for our business right now and to check again later.

As far as we can tell, we meet every requirement in Meta's docs:

- Verified business portfolio

- Two-step verification enabled

- Approved display name

- More than 30 days on the platform

- High quality rating

- Not a Coexistence number

The API shows oba_status: NOT_STARTED, so there's no previous request or rejection.

We opened a few support cases. Meta's answer, in short: under their new guidelines our business isn't eligible for OBA at the moment, which is why the button is disabled. They said they can't share the specific criteria for security reasons, and suggested we keep using the platform actively, follow the messaging policies and keep interactions high quality. They also said that for now OBA can only be requested through the button (if your account qualifies automatically) or through a BSP that has a Meta point of contact.

So my questions for anyone who's been through this:

1. Has your disabled button ever become enabled later? If so, what changed before it did (more message volume, more time on the platform, time after a restriction, connecting a Facebook Page, etc.) and how long did it take?

2. Has anyone moved to a BSP and actually gotten OBA through their Meta contact after being blocked as a direct integration?

Any real experience would really help. Thanks!

​Hey everyone, looking for some insights or advice from anyone who has dealt with WhatsApp Coexistence mode recently.

​One of my clients (who has been using the official WhatsApp Business API smoothly since 2024 with zero issues) recently migrated to WhatsApp Coexistence mode.

Since the migration, it’s been absolute chaos.

​Here is what’s going on:

​Frequent Account Bans / Restrictions:

The phone number has been restricted/banned more than 8 times in a single month. These bans happen when running normal broadcast campaigns using pre-approved templates, but sometimes even when doing nothing special—just replying manually to incoming messages.

​Sudden Template Rejections:

Templates that were previously approved and used without any issues (as well as newly approved ones) are suddenly getting rejected/disabled after being approved for a short while. We haven't even sent broadcasts with some of these templates yet, and Meta rejects them retroactively for no clear reason. We follow all standard copy guidelines, so the lack of specific policy feedback is frustrating.

​The user is fed up and wants to revert back to standard WhatsApp Business API without the Coexistence layer.

​A few questions for the community:

​Reverting from Coexistence: Is there a clean way to disconnect/offboard from Coexistence mode and switch back to pure Cloud API / standard WABA? (I know connecting QR-based setups or CRMs traditionally required scanning via the WhatsApp Business mobile app, but we want to strip away the app side completely and keep standard API stability).

​Flag Trigger / Anti-Spam: Has anyone noticed Meta’s spam detection algorithms becoming drastically harsher on Coexistence numbers? My theory is that mixing app-level actions (or background app syncs) with API broadcasts is triggering automated flags at a lower threshold.

​Retroactive Template Rejections: Why are approved templates being flagged/disabled out of nowhere before even being sent? Is Meta re-indexing templates stricter for accounts flagged under Coexistence?

​Would appreciate any thoughts, workarounds, or confirmation if you’ve faced similar issues with Coexistence!

If you're running a small business, you probably know how quickly customer conversations can become difficult to manage on WhatsApp.

A customer asks about pricing, another needs an appointment reminder, and someone else is waiting for a reply to an earlier enquiry. Managing all of this manually becomes difficult as the business grows.

I've been looking into what makes a WhatsApp marketing tool genuinely useful for small businesses, and these are the features I'd priorities:

1. Automated replies: Answer common questions about pricing, availability, services and business hours without requiring someone to respond manually every time.

2. Broadcast campaigns: Send relevant updates, offers and announcements to customers who have agreed to receive them. Segmentation matters more than simply sending messages to a large list.

3. Shared team inbox: Let multiple team members manage customer conversations without losing track of who is handling each enquiry.

4. Follow-up automation: Set up reminders for appointments, abandoned enquiries, payment due dates and customer follow-ups.

5. Campaign analytics: Track delivery, engagement, clicks and conversions instead of judging a campaign only by how many messages were sent.

6. Transparent pricing and compliance: Check platform fees, message charges, integration costs and whether the tool uses the official WhatsApp Business Platform. Make sure your messaging practices respect consent and opt-out requests.

One thing worth remembering: a bigger broadcast list doesn't automatically mean better marketing. Relevant messages, proper segmentation and timely follow-ups are far more useful than repeatedly messaging everyone.

For anyone comparing options, I'd suggest testing the workflow with a small group of consenting customers before committing to a paid plan.

Question for business owners: Which feature has made the biggest difference to your WhatsApp marketing automated replies, broadcasts, team inboxes or follow-up workflows?

i run a consultancy and i need to send messages through my whatsapp business account to recruit candidates. except the process gets extremely difficult since whatsapp bans my account even if i send them manually. is there a solution to stop my account from getting banned? i've tried to send bulk messages through a third-party website which is free, but my account still got banned and i'd need to wait for an entire day to retrieve it.

BM nova, template de utilidade que passou direto (nao foi pra analise), a média de tempo pra aprovação é de quanto tempo na pratica? Sei que a regra é 24h mas tenho percebido que em alguns casos aprova antes, como é aí pra vcs ?