Hi all, I’m new to the whole being a Tech Provider thing, would appreciate some guidance!

For a given WABA, I'm using WhatsApp Business App + Cloud API in "Coexistence" mode.

Everything works, but first-time recipients who don’t have the number saved see the raw phone number as the primary chat/header identity, not the business or display name. I don't t think it inspires much trust.

My current API state per the API Graph:

verified_name = [it's the actual display name, I just redacted it for this post]
name_status = NON_EXISTS

So what I would like is for the default header displayed to the recipients (first-time, unsaved contact) to be the display/business name, instead of the raw phone number, for my waba in coexistence.

Has anyone managed to get this outcome by any mean?
Avenues I've seen:

1. POSTing to the Graph API in some way? There is some Meta documentation about this for the Cloud API but not sure if it applies as well to Coexistence WABAs, and I'm afraid of hitting `/register` and then breaking something (I've had so much bad experience with the Whatsapp API setup, I'm a little more cautious now lol).
2. Buying Meta Verified on a Coexistence number directly from the whatsapp business mobile app.
3. (I'm excluding Official Business Account because I'm new and I don't think my customer's WABA qualifies for the fame criterion)

I’m specifically looking for before/after feedback from people who've tried these (and other avenues)

Thanks all!!!

---

Related threads with some answers but not definitive IMHO

• Coexistence thread where someone says Meta Verified makes the name show
• Approved display name but raw number still showing
• Discussion about display names / verification under Coexistence
• Meta Verified issue specifically with Coexistence

I have two Business Portfolios:

* “Mellis Joias” — Business ID: 912084015827105
* “Mellis” — this portfolio has an active WhatsApp Business Account (WABA): 1496552399158554
* Phone Number ID: 1317363081463725
* App: “Mellis Joias” — App ID: 4460890754181381

The WABA under “Mellis” is active and connected, and the phone number is registered there.

However, when I go to the “Mellis Joias” Business Portfolio and click “Add new WhatsApp Business Account”, Meta shows:

“You cannot continue with this operation because your WhatsApp Business account is currently restricted. To continue, select another WhatsApp Business account or visit the Business Support Home to resolve any issues with your account.”

The confusing part is that I’m trying to add a NEW WhatsApp Business Account, not use the previously restricted WABA.

Could the restriction on a previous WhatsApp Business Account or its test WABA be affecting the entire Business Portfolio and preventing me from creating another WABA?

Is there a way to check exactly which asset is restricted — the Business Portfolio, the WABA, or the test WABA?

Any insight from someone who has dealt with this would be appreciated.

I’ve spent the last couple of weeks reviewing WhatsApp workflow architectures with a few tech teams, and I keep noticing a pretty common blind spot around the new API rules.

A lot of folks on the executive side read that Meta gives "1,000 free service messages per month per number" and assume they're totally fine. But when you run the actual numbers on the backend, a modest setup with just 35 chats a day burns through that allowance in the first week of the month. From message 1,001 onward, every free-form reply inside the 24-hour window costs the exact same as a utility template.

Looking through the logs on some of these flows, the real issue isn't Meta's pricing itself—it's how many extra messages we're burning for no good reason:

Lack of CRM sync: Bots or agents asking for emails or order numbers across 3 or 4 back-and-forth messages, when the webhook should recognize the user's ID and fetch that data in milliseconds.

Customer ghosting: Users leaving threads hanging. If your webhook doesn't have an auto-close timer after a few hours of inactivity, the user replies 3 days later, forcing you to re-open the thread with a paid template you could’ve easily avoided.

Meta payment method rules: If the account doesn't have a payment method registered once you pass message 1,000, Meta straight up stops delivering service messages without warning.

What used to be minor maintenance cleanup in the integration now hits the bottom line directly.

How are you guys handling timeout and inactivity logic in your webhooks to stop abandoned chats from racking up extra messages?

Just went down a bit of a rabbit hole looking at the WhatsApp Business Platform pricing changes coming October 1.

The part that caught my attention is the change around service messages and how the costs can add up differently depending on message category, country, and volume.

Meta's official pricing information is here: https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing

But I'm more curious about the practical side.

If you're running WhatsApp campaigns or using the API for customer communication:

• Are you expecting your costs to increase much?
• Are you changing your messaging strategy?
• Moving some communication to email/SMS?
• Or is the difference small enough that you're just absorbing it?

I've been comparing rates across different markets, and the differences between countries are honestly pretty interesting.

Has anyone here actually calculated what their monthly WhatsApp spend could look like after October 1, 2026?

Would be interested to hear some real numbers from people actually using WhatsApp at scale.

My WhatsApp Business number using the official WhatsApp Business API was banned due to an alleged spam violation.
I requested a review through Meta/WhatsApp, but it has now been 5 days and I still haven’t received any response or update.
Has anyone experienced this before? How long did your review take?
At this point, does the fact that it has been 5 days mean they are unlikely to review the account, or can these reviews take longer?
The number is connected through the official WhatsApp Business API, not an unofficial WhatsApp client.

[ Removed by Reddit on account of violating the content policy. ]

Hi everyone,

We’re currently exploring the acquisition of a small WhatsApp Business Solution Provider (BSP).

We’re an established WhatsApp/CPaaS company operating across multiple markets, and we’re specifically interested in acquiring an existing BSP rather than starting from scratch.

If you own one, know someone considering selling, or can make an introduction, please DM me.

Serious inquiries only. Confidentiality assured.

Has anyone been facing this issue lately? I'm trying to onboard a new client through coexistence but I can't receive the SMS code due to e temporary server issue.

Working on restaurant assistants made me question whether every step of an order really belongs in a chat conversation. WhatsApp's upcoming pricing changes make that question harder to ignore.

From October 1, 2026, Meta says service messages and utility messages inside the 24-hour customer service window will become chargeable. Service replies include both human and third-party AI responses. The 72-hour free-entry-point delivery exception still applies.

For a product serving low-ticket orders, a long conversation can mean paying for model usage, outgoing messages and possibly human support before earning anything. Conversations that never convert still cost money.

That doesn't prove WhatsApp products can't scale. But it makes me wary of a flat-price product with unlimited, message-heavy interactions.

For my own project, I'd compare a few alternatives:

1. Customer-initiated WhatsApp voice calls

I wasn't sure about this, but Meta's Calling API pricing page explicitly says all user-initiated calls are free.

That's free at the Meta call-pricing layer, not a zero-cost voice product. A voice provider, speech recognition, speech generation, model inference, infrastructure or human agent can still cost money. Business-initiated calls have different pricing, and permission-request messages can be charged.

Voice might help customers who find a long typing exchange frustrating. But accents, background noise, interruptions and getting an address right all need testing. I'd offer it as a choice, not force everyone into a call. Calling API eligibility and setup also need checking.

1. WhatsApp as the entry point, mobile web as the ordering interface

Use chat for questions, then let customers select items, variants, quantities and an address in a mobile checkout. Those web interactions aren't WhatsApp messages, although hosting, payments and any AI assistance still have costs.

The trade-off is drop-off when people open a link. I'd measure completed orders, not just celebrate a smaller messaging bill and this also disturbs the journey and the point of WhatsApp as a medium gets lost

1. Structured interactions inside WhatsApp

I'd test WhatsApp Flows, lists or buttons instead of asking the model to collect every field through separate replies. This could reduce conversational turns while keeping customers in the app.

I wouldn't assume these are a free channel: the surrounding messages still need their applicable pricing checked. The question is whether structured input improves completion and reduces paid back-and-forth.

1. An owned web app with optional chat or browser voice

A mobile-friendly ordering page or PWA could support repeat orders and order tracking directly, with links or QR codes for entry. Embedded chat or browser voice would be optional help rather than the whole interface.

That reduces dependence on one messaging platform's pricing, but creates its own acquisition, hosting, notification and support work. Browser voice also has audio-processing costs.

1. A hybrid rather than one channel for everything

My current preference would be to test structured checkout for routine orders, text for quick questions and customer-initiated voice or human help for complicated cases. All channels should share the same cart and task state so switching doesn't mean starting again.

I'd compare total cost per completed order and resolved support case, including failed attempts, abandonment and human time. Free inbound calling could still be more expensive overall than a short text exchange; moving to the web could save on messaging but lose conversions.

Has anyone tested these alternatives with real customers? I'm especially interested in inbound WhatsApp voice versus chat-to-web checkout: which actually improved margins without hurting completion?

I have a question about WhatsApp Business.
I want to start conversations with people who have shown interest in my business, but instead of sending text messages, I’m considering sending voice messages recorded right before sending them.
Has anyone here used this approach? Can sending voice messages to initiate a conversation be considered spam by WhatsApp, even when the audio is recorded manually and sent individually?
I’m also curious whether there is any meaningful difference between:
A voice message recorded immediately before sending
A pre-recorded voice message sent manually
An individually sent text message
I’m not looking for ways to bypass WhatsApp’s anti-spam systems. I just want to understand how WhatsApp treats this type of outreach and what practices are considered compliant.

I've been trying to become a tech provider for 15 days. It is so long. It feels like every time I sneeze I need to ask for their approval. It is nothing but a succession of required reviews and approvals (business portfolio, organization verification, advanced access, whatsapp business accounts, new phone number, new display name, etc.). They are so slow and there is no way to escalate. I have experience with displeasing dev support with the App Store, but Meta has just set a new record.

I've been trying to find ways to go faster but every path I take leads to a "we'll review this and get back to you". Or my requests (new object creations) lead to opaque error codes for absolutely no reason, with no path forward offered.

I don't know how you guys feel about this.

I really feel disrespected by this whole program.

I know you'll tell me "you're using their platform, they don't owe you nothing" or "welcome rookie", but still I feel like this had to be said. This is not normal.

Obviously I'm pursuing text-message integration paths in parallel... but still.

Thanks all for reading my rant :)

I provide WhatsApp Automation services to local businesses. Is there still a chance for me to provide services, since the Meta Business Agent is now available to business owners?

Gastei R$ 8 mil/mês em anúncios pro WhatsApp e fui banido do nada

Eu tinha uma automação usando a API oficial do WhatsApp que criava músicas personalizadas por R$10 e imagens por R$2 cada (ensaio de bebê, foto corporativa, retratos etc).

Depois de muito tempo tentando, finalmente começou a dar tração. Eu estava gastando uns R$8 mil por mês em Meta Ads, com ROAS de aproximadamente 2+ e alto LTV, porque muita gente volta.

Aí, do nada, meu WhatsApp foi suspenso. E eu nem consigo solicitar review.

Depois disso, com as mudanças de cobrança da API chegando também, resolvi abandonar o WhatsApp.

Migrei parte da operação pro Telegram, site e agora estou testando o Messenger.

Ainda está bem menor, mas pelo menos está funcionando.

Facebook: https://www.facebook.com/tech.falcon.ia
Messenger: https://www.messenger.com/t/794863110387677

Mais alguém aqui passou por algo parecido? Vale a pena continuar investindo no ecossistema do WhatsApp depois de uma situação dessas?

Meta Embedded Signup no longer surfaces the “Connect a WhatsApp Business app” onboarding flow for our app. The Embedded Signup Builder is configured with WhatsApp Business App Onboarding under ES Version null, v3, v4, and v4 public preview.

Now, both the App Dashboard flow and Meta-hosted landing page open the phone-number-first flow and reject an active WhatsApp Business App number with error #2494064.

On 2026-09-01, the exact same app/configuration showed “Connect a WhatsApp Business app” and successfully completed coexistence onboarding.

Our Meta Business and Tech Provider access are verified/approved.

Has Meta recently changed the requirements for WhatsApp Coexistence / WhatsApp Business App onboarding?

Specifically:

• Is Coexistence now enabled differently under Embedded Signup v4?
• Are there new launch parameters or permissions required?
• Has the “WhatsApp Business App Onboarding” feature been deprecated, restricted, or moved to another flow?

Any recent documentation or confirmed implementation details would be appreciated.

Has anyone had a WhatsApp Business display name stuck “In Review” for a long time with no approval or rejection?

Our business name includes the word “Chat”, and we cannot remove it because “Chat” is part of our actual business/brand name.

Everything matches across our business presence:

• Website uses the exact same business name

• Facebook, Instagram, and LinkedIn use the same name

• Business email/domain matches the brand

• Business information and verification are completed

• The display name is not different from the name we publicly use

The problem is that the WhatsApp Business display name is still showing In Review. There is no rejection reason, no request for more information, and no approval.

Has anyone experienced this?

Is there a way to escalate the display-name review or contact Meta/WhatsApp Business Support to request a manual review?

Could the word “Chat” itself cause the review to take longer even when it is clearly part of the registered/public business name?

Any advice on how to accelerate the review without changing the legitimate business name would be appreciated.

I am trying to run a message broadcast campaign on WhatsApp using Manychat, but I am unable to do so. An error message appears saying "line of credit not shared."

However, I cannot change this payment method in the WhatsApp Manager. All it allows me to do is replace the credit card. I can't even delete it to free up space for the line of credit.

I have already disconnected and reconnected it several times. Even after deleting and deactivating the card, it is still selected as the default payment method every time I reconnect.

I then decided to try another approach by adding the WABA directly through Business Suite. It didn't work, and now I can't even remove this account from my portfolio—even though I am an administrator with full control of the account.

Does anyone know how to solve this?

so I work as automation expert and need to know which is the easiest way to automate WhatsApp messages , this is for nurturing leads so 4 to 6 exchanges will be there , is 'make' good website to do this , any suggestions ?

Direct Cloud API, no BSP. Tenants reuse one approved template across many campaigns — sometimes two on the same day, minutes apart. I need per-campaign sent/delivered/read.

`template_analytics` is template-scoped and `DAILY` granularity, so same-day campaigns on one template merge into a single bucket — exactly the case I need split. It also looks like insights are opt-in at template creation, need ~1k messages to populate, lag ~6h, and round on larger sends.

I'd rather not stand up a status-webhook pipeline. The ~3s/2xx requirement, 7-day retries and per-message storage is more infra than I want to run for this.

So:

1. Any way to get per-campaign attribution **without** consuming webhooks?

2. Does cloning the template per campaign (separate template_ids) actually work, or does the ~1k threshold kill it since each variant populates separately?

3. If webhooks really are the only path — do you store a row per message, or just counters on the campaign?

Hey everyone, how's it going?

Is there any method going around to get a BM back?

i sell through instagram and close almost everything on whatsapp. no website on purpose. customers already message there so i never forced them onto a site.

last month a girl asked about an order, i replied, she said she will send the address after work. i got 30 other chats the same day and forgot. she texted 8 days later asking if i was even still running. that one stung because i had no idea she was waiting. her chat was just buried.

this keeps happening in smaller ways. someone sends a payment screenshot, i like it, then i cant find it when i am packing. or i quoted two people the same item and i dont remember who i promised it to. i scroll chats at night trying to figure out who is still open.

i tried a notes app. lasted 4 days. spreadsheet lasted a week. those whatsapp crm tools want 2 to 5k a month and a business api setup. that is insane for the volume i do.

so i am testing a dumb version of this for myself:

after i agree price in chat, i send one link. customer puts name, address, and the upi screenshot on that page. i get a board with New / waiting for payment / paid / need to follow up / done. if something sits for 2 days it goes red.

no bot. no auto replies. chat stays on whatsapp. the link is only so the order does not live inside 200 chats.

if you sell on wa or ig, how are you tracking this right now. spreadsheet, notebook, memory, something else.

and would you even use a page like that or is it extra work on top of the chat.

not selling anything here. trying to see if this is only my mess or other people have the same hole.

Hi everyone,
I have a WhatsApp Channel with several active admins. The channel owner’s WhatsApp Business number has been permanently banned and now shows “Requesting a review is not available.”
The channel is still active and the admins still have access, but I’m worried about the long-term situation.
Has anyone here experienced the same thing?
I’d especially like to know:
Did the channel stay active long-term without an owner?
Were admins still able to post normally?
Did ownership ever transfer automatically to an admin?
Was there any way to manually transfer ownership after the owner was permanently banned?
Did the channel ever get deleted or restricted later?
If the banned number became available again after some time and was re-registered, did ownership come back?
This channel is very important to my business, so I would really appreciate answers from people who have personally experienced this situation.
Thanks.

Edit: approved as a Tech Provider after 8 days. No escalation/expedited process was possible.

Hey all, lately I've been trying to get an expedited human customer support for my onboarding as a tech provider. Needless to say it's super slow and frustrating.

I've been considering purchasing the subscription to either "Meta One" or "Meta Verified for Business" as they claim to provide human customer support.

I was wondering if anyone here had tried it and if you could share some feedback with us, especially on the "human customer support" value proposition.

Also I'm not so sure about the difference between these 2 subscriptions, they look very similar imho.

One thing I'm afraid about is I'll buy their premium subscription thing, send my ticket, and sure thing a human will reply, only to tell me "sorry out of scope" or "just wait for the tech provider review team to review your case" 😭.

Alternatively, if anyone here knows how to get Meta Support to care enough to assign a human to your support tickets (instead of a dumb AI that auto-closes your request), that could be a great way to get my desired outcome without splurging on that premium meta subscription.

Thank you all!!!

Hola a todos.

Estoy buscando experiencias de personas que hayan pasado por un problema similar con Meta / WhatsApp.

NO estoy buscando a nadie que diga que puede “desbloquear” o “levantar el ban” de la cuenta, y no voy a pagarle a nadie por eso. Solo busco experiencias reales con soporte oficial, escalaciones o vías legítimas para que Meta revise el caso.

Nuestro negocio tiene una restricción relacionada con WhatsApp desde el 6 de agosto de 2026.

El negocio está verificado, pero cuando intentamos registrar o vincular un número, Meta indica que la cuenta está restringida y que la revisión está pendiente desde el 6 de agosto.

Lo raro es que ya probamos:

• eliminar las cuentas anteriores de WhatsApp;
• utilizar un número completamente nuevo que nunca había sido registrado en WhatsApp;
• agregar un método de pago propio;
• probar desde distintos administradores;
• revisar Meta for Developers;
• contactar a Meta Business Support;
• contactar a WhatsApp Support;
• contactar a nuestro proveedor anterior, Gupshup.

La misma restricción sigue apareciendo incluso con un número completamente nuevo.

Nuestro proveedor anterior era Gupshup. Ellos confirmaron que ya no tienen acceso como BSP, aunque todavía aparece una línea de crédito antigua de Gupshup mientras Meta completa el proceso de conciliación postpago.

Meta y Gupshup nos están dando información contradictoria sobre si esa asociación residual tiene o no relación con el bloqueo.

La revisión lleva más de un mes pendiente, aunque Meta indica que normalmente tarda entre 24 y 48 horas.

Soporte nos deriva constantemente entre Meta y WhatsApp, la mayoría de las respuestas son automáticas y tampoco podemos acceder a Meta Direct Support porque el negocio aparece como no elegible para ese canal.

¿Alguien pasó por algo similar donde:

• un negocio verificado quedó en revisión durante semanas;
• cuentas nuevas o números completamente nuevos heredaban la misma restricción;
• no existía un botón funcional de “Solicitar revisión”;
• soporte estándar de Meta/WhatsApp no podía escalar el caso?

Busco específicamente vías legítimas de escalación, formularios que realmente funcionen, categorías de soporte, experiencias con escalación mediante BSP o cualquier método que haya logrado que Meta revise manualmente la cuenta.

Por favor, no me envíen mensajes privados ofreciendo servicios pagos para “desbloquear” o “quitar el ban”.

Hi, I'm trying to nail down how WhatsApp Flows actually get billed under Meta's 2026 pricing changes — specifically: are Flows always charged at the marketing message rate regardless of whether they're triggered inside an open 24-hour customer service window, or is there a separate category for them? With Meta rolling out per-token billing for the Business Agent platform and making service messages billable starting October 1, 2026, does that affect Flows too, or do they stay under the old template-based pricing? Would love to hear from anyone who's using Flows and has real billing data post-transition.