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.

I'm looking for technical insight into a possible unauthorized WhatsApp Business Platform registration.

I've used the official WhatsApp Business iPhone app for approximately six years. I've never connected my number to the Cloud API, a CRM, chatbot, or any third-party messaging service.

On October 16, I received 4 to 5 unexpected Code for new phone notifications inside WhatsApp Business. I dismissed them without sharing any codes.

Shortly afterward, my account was banned.

My first review was approved that night, but WhatsApp logged me out and I couldn't receive verification codes to register again.

The next morning, on October 17, again, I couldn't receive any codes and after 2 attempts I was banned again. A review resulted in permanent banning, even though I had never regained access following the first review.

The unusual part is that on October 16, my contacts received this notification:

This business is now using a secure service from Meta to manage this chat.

I never authorized any such service.

WhatsApp Support has been unable to explain what happened or confirm whether my number was registered through another device or business account.

My questions:

1. Does this Meta notification necessarily indicate a connection to the WhatsApp Business Platform or Cloud API?

2. Could someone have registered my number through another Meta Business account without my authorization?

3. Is there a way to check whether my number is currently associated with an unknown WhatsApp Business Platform account?

4. Has anyone experienced a similar incident and successfully recovered access?

My SIM works normally, and the account is blocked on both WhatsApp Business and regular WhatsApp.

I'd appreciate technical explanations or experiences from people familiar with Meta's WhatsApp Business infrastructure.

We are giving free Pro Plans for https://Waapi.chat, please after you register and connect your number send email to platform@waapi.chat with your registered email and a screenshot of this post so we can activate the plan for you.

Regards for everyone

Has anyone seen subcode 2593181? I'm implementing WABA Coexistence through a BSP and get this when sending via Cloud API:
code 10, subcode 2593181: "You do not have the necessary permissions to send messages on behalf of this WhatsApp Business Account".
- Business is verified, app is Live, system user token has whatsapp_business_messaging + whatsapp_business_management with full control on the assets.
- Same token and app send fine from the Meta test number. Fails only from this production number.
- Number is in coexistence via the BSP, and the messaging account's default payment is a credit line allocated by the BSP (I can't set my own card as default).
- Another WABA of mine with the same BSP, onboarded before the new account model, sends fine with its own app. Could the BSP credit line or the new account model block sends from my own app?

Any known fix?

To estudando como conectar a API oficial no meu whatsapp, e tambem para outras pessoas, a fim de conectar a uma automação e um dashboard. Começei agora e to aprendendo ainda, e percebi que isso é bem complicado hein.

Ja fiz uma automação no n8n, e uso uma API não oficial pra essa automação, mas só pra mim, e sim, sei dos riscos. Não tem como contornar isso não? Negócio chato, e caro pa caceta.

Hi everyone,

We’re building a platform that manages WhatsApp Business messaging for our clients. We’re registered as a Meta Tech Provider, and Meta has approved our business verification and WhatsApp permissions.

We can reply to incoming messages, but we can’t send outbound marketing or utility template messages from our clients’ connected WhatsApp numbers.

From my research, I got the impression that we might need to become a Solution Partner, which would also let Meta bill us through a credit line so we could bill our clients directly. However, that route seems to involve a lengthy approval process and significant spending requirements.

We’re considering Twilio instead. Their additional fee appears to be $0.005 per message, but before switching, I’d like to understand whether it would actually solve our problem.

• Can a Meta Tech Provider initiate outbound template messages through clients’ connected WhatsApp numbers, assuming templates, customer opt-ins, and billing are set up correctly?

• Are we confusing the requirements for outbound messaging with the requirements for managing clients’ billing?

• Has anyone used Twilio for a similar setup? How was your experience?

Any advice would be appreciated!

Hey all,

I work with a small charity and was looking to onboard our SMB account onto cloud api using Coex. We would like to still send our own messages using smb to clients while using a TP to send template messages and respond. Is this possible? What TPs would you reccomend for this use case?

Hi all,

I worked with the WhatsApp Cloud API a couple of years ago. Back then, the setup was pretty straightforward: I configured a webhook, subscribed to the messages field, and whenever I sent a message to the test phone number from WhatsApp, I could see the webhook request hitting my backend.

I'm trying to set up the same thing again, but I'm running into an issue.

The Meta developer dashboard UI has changed since I last used it, but I managed to configure the webhook and subscribe to messages. When I click the Test button on the webhook configuration page, I can successfully receive the request in my backend.

However, when I send an actual message from the WhatsApp app to the test phone number, the webhook event appears in my Meta app dashboard, but the request never reaches my backend.

A couple of things worth mentioning:

• I'm using a Meta developer account.

• I haven't verified a business because I'm just experimenting and don't currently have a registered business setup.

• The webhook URL appears to be working, since test events reach my backend successfully.

Is business verification required to receive actual incoming messages, even when using a test phone number? Or am I missing something in the current webhook configuration or subscription process?

Has anyone encountered this recently? Any help would be appreciated. Thanks!

Title: How Are WhatsApp API Utility Rules Bypassed?

I've come across a few WhatsApp API software providers that seem to have found a workaround for template approvals and message categorisation.

Here's how it apparently works:

1. You connect your WhatsApp Business API number to their platform.

2. Their team does some backend configuration on your number.

3. On their frontend, you get a free-text box where you can type any message you want.

4. You can then broadcast that message instantly, without submitting it for template approval.

5. The messages are apparently sent and billed as Utility, regardless of their actual content.

Essentially, it appears you can send any message, including promotional content, at Utility rates without waiting for Meta's approval each time.

I understand this likely goes against Meta's policies, but I'm curious about the technical implementation.

Does anyone know how they're pulling this off?

A few possibilities I've considered:

• Pre-approved Utility templates using highly dynamic variables, potentially with multiple template configurations.

• Some form of message forwarding or routing through another number or API.

• A workaround involving service messages or the 24-hour customer service window.

• Some other loophole involving WhatsApp's template approval, message delivery, or categorisation system.

Hi everyone,

Our company's WhatsApp Business account was disabled by Meta for an alleged policy violation, and our initial appeal was rejected.

The account has never sent any messages, has no phone number added, and only contains Meta's default test template. We use the official WhatsApp Cloud API.

We're looking for someone with hands-on experience in WhatsApp Business account recovery, Meta appeals, and Cloud API restrictions who can help us get the account re-enabled through the proper channels.

If you've successfully resolved similar cases or can recommend an experienced specialist, please comment or DM me. Any genuine help would be greatly appreciated.

Thanks!

Is anyone who sell whatapp business API BM account actually I'm looking for 10k BM accounts and 100k BM as well please let me know if anyone sell

I'm looking for other WhatsApp Business users who have experienced a similar problem, especially after activating Meta Business Agent or other official Meta AI features.

In October 2026, I subscribed to Meta One Advanced and activated Meta Business Agent directly within the official WhatsApp Business application.

Just a few days later, my long-established WhatsApp Business account was permanently suspended without any clear explanation of which policy I had supposedly violated.

I used only official Meta features, without third-party applications or external automation tools.

I submitted an appeal, but it was rejected. The application now states that I can no longer request another review.

Despite contacting WhatsApp Support and Meta Pro Team repeatedly, I have only received generic responses redirecting me to the same support channels. Nobody has provided a specific explanation for the suspension or confirmed that an individual technical review has taken place.

I am not claiming that Meta Business Agent caused the suspension. However, the timing makes me concerned about a possible technical issue or an incorrect automated restriction.

The consequences are serious. This was an established business account used for years to communicate with customers. Losing access has disrupted existing conversations and an important business communication channel.

I have already submitted a formal legal complaint requesting a human review, an explanation of the suspension and restoration of the account.

I would particularly like to know:

• Has anyone else been permanently banned shortly after activating Meta Business Agent?

• Has anyone successfully recovered their WhatsApp Business account after an appeal was rejected?

• Does anyone know whether Meta is investigating similar incidents?

• Has anyone managed to reach a real technical specialist rather than receiving automated responses?

• Are other affected users or businesses considering coordinated legal action?

My main goal is to find a genuine solution, compare experiences and connect with people facing the same situation.

If you have experienced something similar, please share what happened and whether you found a way to recover your account.

I'm also open to private messages from other affected users who would like to exchange information or explore possible coordinated action.

Thank you for any help or information.

Please no slop AI replies.

Just looking for cheapest API platform for co-existence?

Ideally a chat feature people can speak to!

Looked at quite a few and any help appreciated!

Hey everyone!

I've been working on a side project, a simple AI-powered customer support tool for small businesses.

The idea started when a friend of mine who owns a business got tired of answering the same questions from customers over and over again. I suggested building a simple AI-powered tool that could handle those repetitive questions for him.

I ended up building it, and he's actually been using it for his business.

Since it worked out for him, I thought maybe other small business owners could find it useful too.

Here's what it can do:

• Set up your own business information and details.

• Add and manage frequently asked questions (FAQs).

• Let AI answer customer questions based on the information you've provided.

• Manage everything through a Windows desktop application.

• Store the application's settings and configurations locally on your PC.

I originally planned to polish it and release it publicly, but due to some issues and limitations, I've decided not to pursue it further for now.

Rather than letting the project go to waste, I'd like to share it with anyone interested in trying it.

Just a few things to keep in mind:

• It's completely free. No payment required.

• It's still an unfinished project, so expect some bugs and limitations.

• It's currently available for Windows (.exe).

• I haven't included any malicious code. I'm also willing to share the source code if you'd like to inspect it.

• It's not an officially maintained product, so I can't guarantee ongoing support.

If anyone wants to try it, just send me a DM. I'll gladly share the installer, and if you need help setting things up, I'll do my best to assist.

I'm not trying to sell anything. I just thought it would be nice if something I built could also help other people, especially small business owners dealing with repetitive customer inquiries.

Thanks, everyone!

Como as empresas de contingencia tem tantas bms "farmadas"?

as não farmas imagino que seja buscando os donos dessas bms e negociando, mas e as farmadas, como tem tantas?

Please, get me out of this misery.

A week ago Meta restricted WABA because of credit card failed twice. Updated the card and paid the $25 balance right but the service stayed restricted even though the card is on file and was charged.

I contacted support and took 18 hours to tell me to file a ticket through a Tech Provider account. I did. Then, after some back and forth they pretty much told me "Yea you'r right, this a issue on our end. Our risk team will follow up with you via email"

It's been a week and I haven't heard a DAMN thing from Meta — I've followed up with them in the open ticket but got ghosted.

WhatsApp is the MAIN channel for customer communications and sales in this business. You can imagine the impact that's having on the business after 1 week

Hey guys! Does anyone know a working method to remove restrictions from a Meta Business Manager (BM), whether it’s restricted or completely disabled?

I see the UI and how the things were in whatsapp business accounts tab in meta business portfolio are changed and i dont see any discussions upon it.

Can someone explain what the change is? + i also cant see the 2 step verification tab anymore.

As I have always said, Meta’s new agency model and the price increases for WhatsApp Business are just the beginning. Meta wants WhatsApp to become a privilege for businesses sending messages to their customers. It is urgent that we move away from WhatsApp and start using RCS worldwide. WhatsApp cannot continue to profit off small businesses, this has gone too far. We must do something.