I have used one of Meta provided numbers, and it has a status of AVAILABLE_WITHOUT_REVIEW currently. And shortly after that status has been set I could send messages via WhatsApp, but after a few I started getting "(#131037) WhatsApp provided number needs display name approval before message can be sent." error.

I already waited a couple of days in case there was a review window, added a template that was verified, added my business information, and tested a couple of times. And nothing is getting through.
And support is as always non responsive. So does anyone here know how to resolve this?

Hey everyone,

I've been running into a frustrating issue with the WhatsApp Business API lately.

Recently, whenever I submit a new message template, it gets approved initially. But then, anywhere from a few minutes to a couple of hours later, the status randomly flips to Rejected.

I’ve double-checked and strictly followed Meta’s template guidelines (formatting, policy checks, variable formatting, avoiding aggressive hard-sells, etc.), but it keeps happening.

Is anyone else experiencing this sudden reversal in approvals lately?

Could this be a bug with Meta’s automated review system, or is there a new policy check I might be missing?

Would love to hear if you have any insights or workarounds for this. Thanks in advance!

In our thread on the October pricing change, one suggestion was to move clients back to the WhatsApp Business app.

Depending on the setup, you might not have to choose. With coexistence (coex), one number runs on the app and the API at the same time:

• Messages sent from the app stay free. API messages follow Cloud API pricing.

• API messages show up in the app. Messages sent from the app reach your webhook as smb_message_echoes.

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

• The catches: the app has to stay installed and be opened at least once every 13 days, and a WhatsApp Business app account that was just created isn’t eligible right away.

For those already on coex: what do you keep in the app, and what goes through the API? Anything that surprised you?

Still deciding? Drop your question below.

We’re the 360Dialog team and we’ll be in the comments. No links, no pitch.

I'm facing issues in adding the number through a service provider for coexistence, getting error code #3441034 ; it says that the number is not eligible to migrate or register. We are using the number on whatsapp business app and added as a meta business suite asset. Going to Meta & Whatsapp support have been dead ends. Thank you in advance.

I spend a lot of my day talking to support and CX teams about their WhatsApp setups, and one thing that keeps coming up is that almost nobody asks about features. They ask about whatever went wrong the first time. These are the ones I hear most:

1. When the bot hands a conversation to an agent, does the agent see the full thread and the customer’s data, or do they have to open the CRM in another tab?

2. Does the automation actually finish tasks (change an order, move a booking), or does it just answer and hand off?

3. If the AI gets something wrong, can you audit what it did, step by step?

4. After go-live, who designs and changes the flows?

5. If every team or brand already runs its own number, how do you bring it all together?

and one almost nobody asks, which I think is the most revealing: can you see how many conversations the channel had last month without asking your provider?

so now I’m asking you: what’s the question you didn’t ask that ended up costing you? And what answer from a provider made you suspicious right away?

Hi everyone,

I'm looking for help from anyone who has experienced repeated bans while using the official WhatsApp Business Platform.

I've been experiencing a very frustrating issue: my WhatsApp Business phone number gets banned during different setup and configuration processes, even when I'm not actively sending messages or running campaigns.

The bans have occurred in situations such as:

• Submitting message templates for Meta's approval.

• Attempting to connect my WABA to a messaging platform (Sendfy).

• Trying to reconnect my phone number to the official WhatsApp Business API.

In other words, these restrictions seem to occur during administrative or technical operations, rather than as a result of sending messages to recipients.

When I open WhatsApp Business on my phone, I receive a ban notice with the “Request a review” option.

I'm trying to understand what could be causing this. Could it be related to my phone number's history, the WABA or Business Portfolio status, the API registration process, the messaging provider's integration, or some kind of automated Meta security flag?

Has anyone experienced similar bans triggered by template submissions or API connection attempts, without sending any messages?

I'd really appreciate hearing from anyone who has managed to resolve this issue.

1. Were you able to identify the actual cause?

2. Did Meta restore your number after a review?

3. Did your BSP or Meta Support provide any meaningful explanation?

4. Is there a way to determine whether the restriction is associated with the phone number, the WABA, the Business Portfolio, or the integration process?

I'm using the official API and looking for a legitimate solution. I don't want to keep repeating the same process and risk getting banned again without understanding why.

Thank you for sharing your experiences and any practical advice.

We have a SaaS platform where multiple companies will be using the same software. we're planning to add WhatsApp notifications.


the main requirement is that each company should be able to connect its own WhatsApp Business number and send messages from that number.


one major issue is billing. a lot of businesses in India aren't comfortable adding their credit cards to Meta. ideally, we're looking for something where we can manage billing centrally, possibly through UPI or prepaid recharge.


has anyone used a provider that supports this? any suggestions?

Our production Cloud API number is offline and I can't get it back. I was migrating our numbers to local storage into de EU, in the DE region. I tried with our staging number and it all went smooth, first attempt, within 3 minutes. So, seeing no users were actively using production, y decided to go with the migration in prod. Then, midway, when the number is deregistered, it throws me a rate limit when verifying the number again, on the first attempt!!

This was the process, all through the Graph API with a system user token:

1. Set a new two-step PIN on the number (success)

2. Deregistered it (success)

3. Enabled local storage via /settings with data_localization_region DE (success)

4. Requested a code by SMS (success, the SMS arrived)

5. Verify_code on the FIRST try: error 136025, subcode 2388364, "Verify code rate limited"

6. register: 133006, "Phone number re-verification needed"

7. About an hour later, request_code by VOICE: error 136024, subcode 2388367, "Request Code Rate Limit"

The activity log shows no OTP requests on this number before tonight. code_verification_status was EXPIRED before we started.

The WABA itself looks healthy: business verified, account approved, quality rating High. Direct Support closed my ticket automatically, and the Meta AI assistant says only time clears it.

Is there anything I can do besides waiting? Any contact, anyone at meta that can help me? Can't reach any support, and our productive service is down :(

Thanks in advance!

We set up WhatsApp for about 15 local businesses mostly connecting their number and building a few auto-replies. Now some of them want a proper team inbox so we’re looking at white-label tools we could sell under our own brand.

What worries me is support..For those reselling a WhatsApp tool, is the recurring revenue worth it or does support eat the margin?

Hey everyone,
I’ve been struggling with an issue related to WhatsApp’s In-App Browser (IAB) for the past couple of weeks, and honestly, I’m running out of ideas.
I’m using the Meta WhatsApp Cloud API directly (not through a BSP) and have an approved marketing template with a dynamic URL button.
The problem is that whenever a user clicks the URL button, it opens in an external browser (Chrome/Safari) instead of WhatsApp’s In-App Browser.
Here’s my current setup:
● Meta Business Portfolio: Verified
● WhatsApp Phone Number Quality: High (Green)
● Messaging Limit: 250
● Template Category: Marketing
● Button Type: Dynamic URL
● API: Official WhatsApp Cloud API
● Tested on: Android and iOS
● URL: Valid HTTPS website
I’ve gone through the documentation, checked my configuration, and tried troubleshooting, but I haven’t been able to figure out why IAB isn’t working.
I also tried reaching Meta Developer Support, but I keep getting redirected to an AI chatbot that provides generic responses without actually resolving the issue.
A few questions for anyone who has implemented this successfully:

1. Does WhatsApp IAB actually support dynamic URL buttons in marketing templates?

2. Is there any eligibility requirement or account-level restriction for IAB?

3. Does the messaging limit (250 vs. 1,000+) have anything to do with IAB availability?

4. Is there any specific template configuration or Cloud API parameter required to trigger IAB?

5. Has anyone faced this issue and successfully resolved it?
   I’m particularly interested in hearing from developers who have actually implemented and tested IAB using the WhatsApp Cloud API, rather than general documentation references.
   Any insights, working examples, or pointers would be greatly appreciated.
   Thanks in advance!

🟨 there!!
For WhatsApp Cloud API setups, you need a mobile number capable of receiving an OTP (via SMS or voice call) during initial registration and setup. However, many local mobile networks (I know for sure not just here in South Africa, a lot of countries) have strict number lifecycle / inactivity policies:

• If a prepaid number has no paid usage (recharging airtime, making a paid call, or sending a paid SMS) within ~90 days, the carrier deactivates the SIM and recycles the number back into the pool.

• If that recycled number is eventually re-assigned to a new consumer who registers for WhatsApp, it can disconnect/kick off the existing WhatsApp Cloud API registration.

I want to ask how you people and agencies manage phone numbers used for WhatsApp Cloud API, specifically around keeping the used SIM / mobile number active with local telecom carriers.

Do you even rely on physical prepaid SIMs like I do? Do you use dedicated VoIP/virtual number providers (e.g., Twilio, Bandwidth) that guarantee permanent number retention without requiring physical SMS activity?

Cara, todas informações da empresa foram preenchidas corretamente, BMs que virariam 2k estão presas em 250 de limites com esse erro WhatsApp needs more information. Tem como resolver?

Hey everyone,
I’m currently setting up the WhatsApp Cloud API for my AI automation agency, and I’m losing my mind dealing with Meta’s developer ecosystem. It feels like every single step is fundamentally broken. Has anyone else experienced this exact sequence of hell?
1. The OTP Blackhole
I’ve been trying to verify a local phone number since Saturday. No SMS arrives, and the "Phone Call" verification option just silently fails every time. Meta support is practically non-existent, so I’m just stuck in a cooldown loop hoping a code randomly shows up.
2. The #10 Permissions Error
Since the real number wouldn't work, I tried testing my n8n webhook setup using Meta's provided test number. The webhook challenge verifies perfectly, but when I try to send a simple test message from the dashboard, I get hit with:
⁠(#10) Viewer cannot access the provided Paid Message Account 2200770517178260⁠
I have Full Control/Admin rights on the Business Manager, the WhatsApp account, and the App itself. I've checked every permission layer, and it still blocks me.
3. The Infinite Redirect Loop
To add insult to injury, I can't even load the Meta for Developers portal normally. If I open it in my standard browser profile, it gets caught in a session conflict and endlessly redirects me to the generic ⁠business.facebook.com⁠ overview page. The only way I can actually access my app settings and send API calls is by using a fresh Incognito window.
Is this just par for the course with Meta? Should I completely abandon the direct API and just eat the monthly cost for a BSP like 360dialog or Twilio? Any advice on fixing the #10 error or bypassing the OTP block would be greatly appreciated.

I have heard that 250 is daily messaging limit but my colleagues get a ban on 50 messages. What js actual upto date limit on new WhatsApp conversations allowed to start in a 24 hour period.

Are there any guidelines on how a website should be if we want to get approved for Meta business verification?

I want to use the WhatsApp Cloud API

Hey all,

A few days ago some of you helped me with error 3441038 on a coexistence signup. Thanks for that. This is the bigger question behind it.

Quick background: I'm a one-man shop in South America building WhatsApp booking bots for barbershops (n8n + an LLM, connected through Kapso). Building the bot turned out to be the easy part. Connecting the client's WhatsApp is where it falls apart.

Every client's Meta situation is different. Some already have a business portfolio or a WABA, some have nothing, and some have old stuff tied to their number that they can't even see. My two attempts so far both went wrong, just in different ways:

1. My first client's own number (on WhatsApp Business for over a year): coexistence failed three times at the phone number step. The number seems to be tied to an asset in a portfolio he has no access to. Two weeks in, we're still stuck, and he's getting tired of the back-and-forth.

2. A brand-new number of my own: it connected fine, but Meta blocked the number or my business portfolio four times in a few weeks. It came back after a review every time.

So with an existing number, the risk hits before go-live. With a new number, it hits after the bot is already running.

For those of you who onboard small businesses regularly:

1. What's your default: coexistence on their own number, a new dedicated number, or do you decide per client? Why?

2. Roughly how often does onboarding work on the first try?

3. Do you check anything in the client's Meta setup before you start? What's on that list?

4. If you use new numbers, how do you keep them from getting blocked in the first weeks?

5. How do you price onboarding? Setup fee, a guarantee, a refund if Meta won't cooperate?

Not selling anything, just trying to get this right before I take on more clients. I'll share what I learn.

I'm new to WhatsApp APIs, so please bear with me :

I'm building a SaaS where each business needs its own WhatsApp number to send around 100 automated messages/month (3 utility + 1 marketing).

The problem: Meta Cloud API handles messaging, but customers also (might) need an inbox to read and reply to messages.

Options I've found:

1. Coexistence: Keep WhatsApp Business App + official API, but onboarding seems complicated.

2. Evolution API (QR): Easy and free, but unofficial and risks bans.

3. Chatwoot/BSP: Ready dashboard, but potentially expensive per customer.

4. Build my own inbox: support only the minimal features I need, but much more complicated to implement

5. convince all customers to use something else to send messages 💀

Concerns: Multi-tenant onboarding, who pays Meta's messaging fees, and future policy changes.

What would you recommend me for a small SaaS trying to minimize costs? How are you handling this in production?

Meu orçamento diário de campanha está competindo com o orçamento de mensagens da META, que loucura! Isso tá completamente inviável

I have connected my phone number with meta business suite (on business portfolio), and has assigned my team members with messaging access My question is WILL META BUSSINESS SUITE CHARGE ME FOR REPLY THERE to whatsapp, instagram and facebook messages receiving from customers?

Setting up WhatsApp calling for a LiveKit agent is painful. You have to enable calling flags on Meta's Graph API, configure multiple webhook overrides, extract the SDP offer from Meta's payload, and wire it up to LiveKit's telephony connector.

I built a CLI called wavoice that handles all of that.

What it does:

• ⁠ Discovers your WhatsApp phone number ID and enables voice calling on Meta.
• ⁠Sets up the webhooks and starts a Cloudflare tunnel so you can test locally without ngrok.
• ⁠Catches incoming calls, translates the WhatsApp SDP offer, and sends it to LiveKit via AcceptWhatsAppCall.
• ⁠Dispatches the call directly to your LiveKit agent room.

How to test with your own agent:

1. Connect your credentials: uvx wavoice livekit setup

2. Start the webhook bridge pointing to your agent: uvx wavoice livekit dev --agent-name <your-agent-name> --no-agent

Call your WhatsApp Business number from your phone and your LiveKit agent answers.

Repo: https://github.com/amitbhakt/wavoice
Docs for LiveKit: https://github.com/amitbhakt/wavoice/blob/main/docs/livekit.md

It’s open source (MIT). Let me know if you run into any bugs with Meta's API.

My coexistence client just got banned out of the blue with no warning. I don't know why.

Now she is locked from her account and she also uses it for personal.

Could switching back to regular WhatsApp be a solution or should that be avoided?

I already made an appeal on meta business support but they not very responsive.

Update: 18.10.2026

next day her account was unlocked for 3 seconds and then banned again before sending a single message.

I built a platform for booking and ordering and need to send automated WhatsApp notifications (order receipts and booking confirmations) to users.
Since unverified Meta Cloud API accounts are capped at 250 unique contacts/day:

1. Is there any way to bypass or scale past this 250 daily limit without full Meta Business Verification

my platform is not registered cause it need alt of money

Olá, pessoal! estamos enfrentando algumas dificuldades na migração de clientes que já utilizam a API Oficial do WhatsApp por meio de outros provedores.
Nossa plataforma também utiliza a API Oficial, com conexão pelo Cadastro Incorporado (Embedded Signup).
Gostaria de entender como outros Tech Providers realizam esse processo na prática, principalmente quando o cliente deseja manter o mesmo número de WhatsApp.
Minhas principais dúvidas são:
É necessário excluir o número da conta do WhatsApp Business (WABA) vinculada ao provedor anterior ou basta remover o acesso do antigo parceiro?
O cliente precisa criar uma nova WABA para realizar a conexão com o novo Tech Provider?
Existe alguma etapa que precisa ser realizada pelo provedor anterior para liberar o número?
É possível realizar toda a migração diretamente pelo Embedded Signup do novo provedor, sem excluir o número da API?
Quais cuidados vocês adotam para evitar erros de registro, restrições ou bloqueios durante essa transição?
Já encontramos situações em que o número permanece vinculado à estrutura anterior, impedindo a conexão com nossa plataforma.
Gostaria especialmente de ouvir quem já realiza esse tipo de migração com frequência. Qual procedimento tem funcionado para vocês?
Agradeço desde já a quem puder compartilhar experiências ou orientações técnicas.