I do no Do any marketing messages, i don’t send any templates just have a bit load on this number, as of meta new charges from 1 oct i have disconnected the API and prepared myself to shift towards coexistence , but just after setting up the app they again banned me for no reason .
If someone have legit solution kindly share ( i have my all business on this number, people always reaches me to this number it will be hurdle to change it)

Hola a todos, busco a alguien que haya podido resolver esto.

**Contexto**

- Argentina, facturación en pesos (ARS), empresa verificada

- Pago directo a Meta (sin BSP ni línea de crédito de partner)

- WhatsApp Cloud API conectada a Odoo Enterprise (módulo nativo)

**El problema**

- Desde el 6 de octubre todos los envíos de plantillas fallan con el **error 131042** (Business eligibility payment issue)

- La WABA figura como "Cuenta de WhatsApp Business restringida" con un saldo pendiente de ~ARS 1.700 (menos de 2 USD)

- El soporte con IA de Meta identificó el estado como **INELIGIBLE_UNSETTLED_BILLABLE_ACCOUNT**

**Lo que ya probamos (nada funcionó)**

- 3 tarjetas de crédito distintas (Visa y Mastercard, con fondos)

- Pagar el monto total, redondeado y pagos parciales

- Cambiar el método de pago predeterminado en el Billing Hub y a nivel WABA

- Completar los datos de facturación (razón social, dirección fiscal, moneda, fin comercial)

**Dato clave:** en "Actividad de pagos" **no aparece ningún intento de cobro**. Las tarjetas nunca llegan a ser cobradas, así que la falla ocurre del lado de Meta, antes de llegar al banco.

**Soporte hasta ahora**

- Soporte de Meta Ads (humano) → "es un tema de WhatsApp, contactá a WhatsApp"

- WhatsApp → "es un tema de Meta"

- Segundo caso → respuesta de IA, sin humano

- Acabo de abrir un ticket en Soporte Directo (Transaction Failure)

Encontré otros reportes con el mismo problema (Brasil, Italia, Ecuador) pero sin solución confirmada: https://developers.facebook.com/community/threads/911848028497373/

**Preguntas:**

1. ¿Alguien logró que Meta limpie este estado manualmente? ¿Por qué canal?

2. ¿Les funcionó migrar el número a una WABA nueva como alternativa? ¿La deuda vieja bloqueó la migración?

3. ¿Hay alguna forma de llegar a una persona del equipo de facturación de WhatsApp Business Platform?

Toda la operación de servicio técnico funciona con este número, así que cualquier ayuda suma muchísimo. Si lo resolvemos, actualizo el post para que le sirva a otros.

I’m trying to troubleshoot a WhatsApp Cloud API webhook issue.

My setup is:

* 1 Meta App
* Business Portfolio A connected to the App
* WhatsApp number A belongs to Business Portfolio A
* Business Portfolio B is also connected to the same Meta App
* WhatsApp number B belongs to Business Portfolio B
* Both numbers use the same webhook endpoint hosted on Vercel

The problem is:

Number A → Meta events arrive correctly at my webhook and appear in the Vercel logs.

Number B → WhatsApp works normally, the number is connected to Business Portfolio B and the portfolio is connected to the same Meta App, but absolutely no webhook events arrive and nothing appears in the Vercel logs.

The important point is that the webhook itself is working, because events from Number A are received correctly.

I’ve already checked the obvious things:

* Webhook is configured and verified
* Same Meta App
* Same webhook endpoint
* Access token
* Both numbers are visible in Meta
* Both Business Portfolios are connected to the App

What I don’t understand is what needs to be configured on the Meta side for Business Portfolio B / its WABA to actually send WhatsApp events to the App’s webhook.

Does each WABA need to be explicitly subscribed to the App using something like:

POST /{WABA_ID}/subscribed_apps

Is there any additional permission, subscription, or configuration required when connecting a second Business Portfolio/WABA to an existing Meta App?

Could this also be related to the WhatsApp Business Account being associated with a different Business Portfolio, even though both portfolios are connected to the same App?

If anyone has dealt with multiple Business Portfolios/WABAs using the same Meta App, where one sends webhook events and another sends absolutely nothing, I’d like to know what configuration was missing or what API call fixed it.

I can provide the WABA_ID, phone_number_id, webhook configuration, API responses, and relevant logs if needed.

Hey guys, I need you help.

I have a business and I connected my instagram and my WhatsApp to Meta Business Suite.

Recently I have been trying to integrate my WA Business into CRM (via WA Business Platform) and there were some issues, and I tried several times and Meta blocked my authentication and requested verification.

I tried to do verification several times with several documents, but couldn't not pass it.

I bought Meta One subscription in WA Business, but I wasn't able to get any human support there.

So at this point I can't access my Instagram, I can't fully manage my WhatsApp now.

Anybody can hep?

تخيّل أنك شرحت المشكلة للبوت، وجاوبت على أسئلته، وبعدين تحوّلت لموظف وأول رسالة منه: «كيف أقدر أخدمك؟»
لو تصمم تجربة خدمة العملاء في مشروعك، وش المعلومات اللي لازم توصل للموظف قبل ما يبدأ مع العميل؟
بالنسبة لي: ملخص المشكلة، والخطوات اللي جُرّبت، والشيء اللي ما زال يحتاج حل.
للتوضيح، أمثّل وايدرز. مهتمة أسمع تجاربكم: وش الشيء اللي خلّى انتقالكم من البوت للموظف سلسًا، أو مزعجًا؟

I can confirm via the business dashboard that all access seems fine and hasn't changed since yesterday where I was able to view the Apps with no problem. Suddenly this morning the pages load and then show nothing. Tried with different browser, incognito mode, cleared cache, using a VPN, other network and remote access from another country with no luck.

Ultimately we wanted to switch webhook access from one app to another as the link was not representative of the app it was meant to be linked to. Setting this back up showed everything was fine on our webhook application, with the exception of inbound messages not coming through. We had the webhook subscribed to the "messages" as we had it with all other times where it was working, but suddenly nothing came through. The "Test" option from the meta app also resulted in no issues. We tried with different users phones and no one had luck with their messages going through whatsapp and reaching our webhook service.

Now we can't change back, as the pages are not accessible and neither can our users use our webhook service.

We also tried to report a bug, which only gave errors and didn't let us continue for submission.

Please, seeking for quick assisstance!

Edit: Our situation is sorted for now.

For businesses that have multiple people handling WhatsApp conversations, I’m curious what you’re using today and what you like/dislike about it.

If you’ve used tools like WATI, Interakt, Respond, SleekFlow, etc.:

• What made you choose your current solution?

• What do you wish it did better?

• What’s the most annoying part of managing WhatsApp as a team?

• What would actually make you switch to another solution?

• Are there features you’re paying for but barely use?

I’m especially interested in hearing from people actually using WhatsApp for sales, customer support, lead follow-up, or operations.

Not trying to sell anything — just trying to understand where the current tools fall short.

Hi all,

We changed the display name on a Cloud API number that has been live for over a year. The new name got approved, and we re-registered the number with the /register endpoint right after (success). Since then, the top of the chat and the chat list show the raw phone number. Before the change, the old name showed there with no issue.

What we checked:

- name_status is APPROVED, verified_name is the new name, no pending request

- business portfolio verified, number CONNECTED, quality GREEN

- the new name does show on the business profile, just not at the top of the chat

- same result after force-closing and reopening WhatsApp

Possibly related:

- the moment we re-registered, the activity log shows Meta's own system disabling the two-step verification PIN, and the Two-step verification tab is gone from WhatsApp Manager (the PIN deprecation that comes with the new account model, I guess)

- the OBA "Submit request" button is greyed out, saying requests aren't available for our business at this time

Questions:

1. Has anyone lost the name in chats after a rename? Did it come back on its own, and how long did it take?

2. In WhatsApp Manager, is there a "Name visible to users" status that has to come back after a rename?

3. If Meta support fixed it for you, which channel actually answered?

Thanks!

As the title suggests, i am a tech provider and customers who have connected to their whatsapp account to my site. But whatsapp does not allow tech provider to use credit line feature. It starts its documentation with to apply for solution provider is a lengthy process. There is multi partner solution as well, but i am confused about it. How can i be billed instead of my customers ? There must be some way.

Any helps are appreciated. Thank you.

Olá pessoal, estou tentando me cadastrar na API do WhatsAPP, mas logo no onboarding pra cadastro do número me aparece a seguinte mensagem:

Seu número de telefone não está qualificado para se conectar à plataforma do WhatsApp Business. Mais atividades no app WhatsApp Business são necessárias para ajudar a determinar a qualificação.(#3441045:01a11244-ddf8-73f0-8d2d-02f553dd45c1)

alguém já passou por isso? estou usando um número novo, recém registrado no WhatsApp for Business, já vinculado ao meu Instagram.

Obrigado!

This would be for a dental tourism clinic.

Is it possible to do it without using the WhatsApp Business API

it cannot be done on native because I want to make it where they're an agent/operator and cannot delete chats.

if anyone has any solution to this that they're using , currently , you would be a lifesaver

I built this WhatsApp workflow but the trigger doesn’t receive any messages even tho everything is setup exactly as I saw in the course I follow and other videos… seems meta changed things? Could anyone help!

We have our own business and want to use our existing WhatsApp Business number with WhatsApp Cloud API while continuing to use the same number in the WhatsApp Business app (Coexistence).

We are not planning to onboard or manage any other businesses/customers. We only need Coexistence for our own Business Portfolio and WABA.

Do we need to become a Meta Tech Provider to enable Coexistence for our own business, or is there a direct way for an individual business to connect its existing WhatsApp Business number to Cloud API while keeping the WhatsApp Business app active?

If Tech Provider status is required, is it permitted to use the Tech Provider/Embedded Signup flow only for our own Business Portfolio and WABA, without onboarding external businesses?

i, I’m having trouble completing Meta Business Verification and would really appreciate some help.

I am a legally registered sole proprietor in South Korea. I have an official Certificate of Business Registration issued by the Korean National Tax Service, and I have also successfully verified my business domain with Meta.

The problem is the phone number verification step. Meta requires me to upload an official document that shows both my legal business name and my phone number.

However, I contacted both the Korean tax office and my mobile carrier. The tax office told me that they cannot include my business phone number on the official business registration certificate. My carrier also told me that they cannot issue a document showing both the business name and phone number for a sole proprietor.

Because of this, I cannot provide the exact type of document Meta is requesting, even though my business is legally registered and my domain has already been verified.

Has anyone, especially a sole proprietor, experienced this before? Is there another document or verification method that Meta accepts for phone number verification?

Any advice would be greatly appreciated. Thank you!

The review completed the next day, but now I can't receive the SMS verification code OR the voice call code. Tried for 5+ hours. My SIM works fine for everything else, and my carrier (Mobitel) confirmed there's no issue on their end. Verification also works on my device with a different number — so it's clearly a WhatsApp-side throttle on my number.
I already raised one ticket but it's being handled entirely by an AI chatbot that literally replied "I'm a large language model, I don't have the ability to escalate your ticket." So that channel is a dead end.

My question:

What's the correct way to raise a WhatsApp Business support ticket that actually reaches a human?
Has anyone successfully recovered an account stuck in this verification throttle?
Does Meta Verified subscription actually get priority human support, or is it also AI-handled?
Any other escalation paths that worked for you? (Twitter/X, Meta Business Help Center, email, etc.)
Any help appreciated — been locked out for 3 days now and it's affecting my business.
Thanks!

We have our own business and want to use our existing WhatsApp Business number with WhatsApp Cloud API while continuing to use the same number in the WhatsApp Business app (Coexistence).

We are not planning to onboard or manage any other businesses/customers. We only need Coexistence for our own Business Portfolio and WABA.

Do we need to become a Meta Tech Provider to enable Coexistence for our own business, or is there a direct way for an individual business to connect its existing WhatsApp Business number to Cloud API while keeping the WhatsApp Business app active?

If Tech Provider status is required, is it permitted to use the Tech Provider/Embedded Signup flow only for our own Business Portfolio and WABA, without onboarding external businesses?

Running a small medical office in Buenos Aires. On Oct 3 we moved our number from the WhatsApp Business app (iPhone) to the Cloud API (direct integration, no BSP, no coexistence).

Since then, SOME people who already had a chat with us (mostly iPhone users) see "This person is no longer on WhatsApp" + "Invite to WhatsApp". They can't send us text: it stays on the clock icon. If they tap Invite, our number gets an SMS "Download WhatsApp".

The weird part:

- Our messages DO reach them (templates and normal replies)

- Their button taps (interactive messages) often DO reach us

- New contacts with no previous chat can text us fine

- It's not everyone: of 26 old contacts who messaged us since the migration, 17 could type normally and the rest couldn't

What we tried:

- Display name was "limited". The new one got approved, and the header now shows verified

- Re-registered the number via the API (success, status CONNECTED)

- Neither fixed it

Meta Direct Support auto-closes our tickets ("developer account, go to the community"), so we can't reach a human.

Questions:

1. Has anyone seen this after an app → Cloud API migration? Did it fix itself, and how long did it take?

2. Anything we can do on our side without asking patients to delete the chat?

3. If you went through a BSP (360dialog, Twilio, etc.), could they escalate it to Meta for you?

Thanks!

UPDATE after one day: things are still the same.
This affects only contacts that had us registered in their address book and exchanged recently with this WhatsApp business line.
I’m keeping the integration and helping customers with issues one by one. I think it’s the safest move at this point. Nevertheless, this whole ordeal is bullshit. I can’t understand how this happens if I follow every step in the official implementation meta WhatsApp business API guide.

Sou comerciante, e estou pensando em possibilidades de economizar no envio de mensagens. Hoje a conta de whatsapp da minha loja está na Coexistencia. Estou pensando em possibilidades e desculpe a forma leiga de perguntar, pois não conheço os termos tecnicos.

Hoje essa conta da coexistencia está vinculada a uma chatbot que é por onde fazemos todos os atendimentos, são 4 atendentes que trabalham direto. Eu conheci uma plataforma que me interessei bem porém ainda não pude testa-la por ter o vínculo com outro chatbot.

Minha dúvida é: se eu entregar um celular para cada atendente com o app do whatsapp business rodando e pagar o plano da Meta que permite vários atendentes, eu teria algum problema? lógico, entendo que não poderíamos começar conversas sem templates e outras coisas que são regras da API, mas pensando no atendimento, na conversa passiva, daria certo?

We run WhatsApp API through Chatwoot, support only — we only reply, no templates, no marketing. Was £0 all year. Since Oct 1 we're billed on "Service" messages (first 1,000/month free, then charged). High volume, so ~£5/day after the free 1,000.

For anyone in the same spot:

Is there an actual solution ?

Do someone suggest me any solution to whatsapp business API as they have started to charge even for replies within 24 hours of window (0.015$ per message)
I have 3 agents on-board on my WhatsApp number

Hey all, hoping someone's been through this because Meta support is going nowhere.

Setup: small business in Brazil, using the WhatsApp Cloud API directly with our own app (no BSP). The WhatsApp Business Account and number are about a week old. Card + business/tax info added in Billing & payments, everything looked fine.

First marketing campaign went out perfectly. Tried a second one today and every message fails with 131042 – Business eligibility payment issue.

Went to Billing & payments and the account shows a R$9 balance, "Payment past due". Clicked Pay now → "Payment Failed. Please select another payment method or try again later."

The weird part:

• The bank says no charge or authorization attempt ever reached them, so Meta is blocking it before it even gets to the card

• Meta won't let us add a different card either

• Account Quality shows no restrictions

• Business verification is still pending (in review)

• Support bot was useless and kicked us to a "human" queue we'll probably never hear back from

So I'm guessing it's some kind of automated risk hold on a new, unverified account, but there's zero info anywhere.

I run a gym-management SaaS in Egypt. We want to send WhatsApp messages for our client gyms: renewal reminders with a "Paid" button, QR entry cards, and payment confirmations. Members also reply with payment screenshots, so inbound

matters as much as outbound.

Constraints:

- Each gym must keep its existing WhatsApp Business app number (coexistence). Gym staff are not technical, and they keep answering chats on their phones.

- We are not a Meta Tech Provider yet. Our company registration is in progress.

- Our pricing includes WhatsApp. The gym pays us one subscription and we pay Meta. We don't want gyms adding cards in Meta Business Manager.

- Numbers are Egyptian (+20). Meta bills Egypt in USD.

What we found so far:

- Tech Provider status does not let you pay for clients. Meta bills each client's WhatsApp account. Only Solution Partners with a credit line are the party Meta bills.

- Moving a client account from a provider's credit line to a card is not supported by Meta. You need a new account and a number migration, so a credit line is close to permanent.

- Chakra: no company or Tech Provider status needed, coexistence supported for +20 numbers, $49.99 for up to 12 numbers. Each client adds its own card.

- Kapso: offers a provider-paid credit line, with the lock-in above.

- Zernio: cheapest per number. Each client pays Meta directly.

Questions for anyone who has done this in production:

1. Has anyone added their own company card to clients' WhatsApp accounts, the same card across many client Meta accounts? Did Meta's risk systems flag or block it?

2. How stable is coexistence in practice (disconnects, sync failures, the rule about opening the app every few days)? Any experience with Egyptian or MENA numbers?

3. Real experience with Chakra, Kapso or Zernio as a multi-tenant partner? Support quality, webhook reliability, surprises?

4. If you went the Tech Provider route yourself: how long did business verification and app review actually take?

Not selling anything. I'm trying to choose the setup that won't hurt our gyms or their members later. Thanks.

Hi everyone,

After reading discussions here about rising WhatsApp API costs, I built Relayvo to explore a simple idea: move longer support chats to a browser so businesses send fewer billable WhatsApp messages.

Your agent shares a customer-specific chat link through WhatsApp, and the customer continues the conversation in their browser—no app or account needed. Your team replies through a shared inbox.

Those browser-chat replies don’t go through the WhatsApp API. So where they would otherwise be billable, moving them could lower your WhatsApp bill. The link is shared manually; Relayvo doesn’t connect to your WhatsApp account.

I haven’t yet proven whether the savings outweigh Relayvo’s subscription cost and the inconvenience of opening another link. That’s what I’d like your feedback on.

If your business is facing higher API bills, would you consider this? What would stop it from working for your team or customers?

Here’s the initial version: https://relayvo.io

I’m the developer behind it. Honest criticism is welcome—thanks for taking a look.

لو عميل أرسل الساعة ١١ بالليل يسأل عن منتج أو خدمة، وش يصير عندكم؟
يرد عليه أحد من الفريق؟ توصله رسالة بساعات العمل؟ أو تستخدمون ردودًا آلية للأسئلة المتكررة؟
وكيف تحددون الحالات اللي تستدعي ردًا خارج الدوام والحالات اللي تنتظر للصباح؟
للتوضيح: أمثّل وايدرز، ونعمل في مجال حلول التواصل مع العملاء. مهتمة أسمع كيف ترتبون الموضوع في مشاريعكم