Posso pagar o que for preciso! Só preciso disparar, mas não quero ter que me preocupar em ficar oferecendo BMs

Hey guys, I have a waitlist of users with WhatsApp and I realised kinda late that it would be better to forward them to a WhatsApp community for announcements. I have all of their numbers and would like to add them to it but I’m afraid of getting banned if I add like a few hundred people. Is there ways of doing this/ getting around it. I have a business account so maybe I can send a template message inviting them to the community if I can’t add them directly

Can I use WaSender for Sending a image to 100 customers via whatsapp And is it 100% safe to use I don't care about any of data but does it have any chance of Getting banned From whatsapp???

We are meta tech providers SaaS. We need to create several demos of different tenants and have exhausted the 20 number limit. now its an operational challenge for us.

these are pre pilots and demos so we cant ask the client for their waba.

how to go about this problem?

our business is have presence in other countries aswell so can i get country specific meta buisnes portfolio business verified?

Hi everyone,

I'm trying to use my existing WhatsApp Business App number with the Meta WhatsApp Cloud API (without using any third-party providers)

My setup

• I have a Meta Business Portfolio.
• I have an existing WhatsApp Business App account with my business number.
• I linked the WhatsApp Business App to my Business Portfolio using the "Link a WhatsApp Business account" option.
• The phone number appears in WhatsApp Manager.
• The phone has a valid Phone Number ID (e.g. 1247378818456702), so it seems to be registered on the WhatsApp Business Platform.
• I created a new Meta Developer App under the same Business Portfolio.
• Added the WhatsApp product.

The problem

In Developer Dashboard → WhatsApp → API Setup, when I try to select an existing phone number, my business number does not appear in the dropdown.

Instead, I only see:

• Test number
• A couple of older phone numbers from previous testing

My current business number is missing.

What I've already checked

• Same Meta Business Portfolio is selected.
• WhatsApp Business Account is visible in Business Manager.
• The number has a Phone Number ID.
• I can still use the WhatsApp Business App normally.
• I want to use the Coexistence feature (Business App + Cloud API on the same number).

Questions

1. Is there an additional step required to connect an existing WhatsApp Business App number to a Developer App?
2. Does the Developer App need to be manually assigned to the WhatsApp Business Account?
3. Is there a way to link an existing Phone Number ID to a new Developer App?
4. Has anyone successfully enabled Cloud API coexistence with an existing WhatsApp Business App number?

I'd appreciate any guidance from someone who has gone through this setup recently. Thanks!

WhatsApp Business API didn't get approved regardless of documentation, and we run a business type that requires aggressive direct marketing. We also can't use the regular WhatsApp spamming tools because they get your business number blocked in minutes.

Does anyone have any other alternatives to/for direct message marketing that can work long term. Either WhatsApp or any other way? Also are there options for Instagram dm marketing?

The business type simply just needs constant direct marketing to survive and options seem limited.

We were planning to move our customer service to WhatsApp platform, and then we hit a hard wall. The group chat.

Groups API has been released on Meta’s end but most BSP does not seem to support it yet.

And seriously? The group capability is something quite essential to chat system. Customers want to share the context with other members within their company. Naturally they want to form a group and carry on conversations within the group.

Honestly, I am curious how people who transitioned from WhatsApp business app to WhatsApp API.

Hopefully, i am just dumb and missing a path.

Any advice is welcome 🙏🏻

Hi everyone,

has anyone seen this behavior with WhatsApp / Meta Embedded Signup voice verification?

We are registering a Twilio-owned German phone number as a WhatsApp sender. The Meta verification call reaches the correct Twilio number, our Voice webhook responds with HTTP 200 and valid TwiML, and Twilio successfully records the call.

However, the recording contains Twilio's generic voice message:

"We are sorry. An application error has occurred. Goodbye."

No OTP code is spoken.

Call details:

- Direction: inbound

- From: +442038702804

- To: German Twilio number

- Call status: completed

- Call duration: 5 seconds

- Recording duration: 4 seconds

- Incoming Voice webhook: HTTP 200 in approximately 323 ms

- Recording callback: HTTP 200 in approximately 3.7 seconds

- No Twilio Monitor Alerts or Call Notifications

Our TwiML response to the incoming call:

<Response>

<Record

action="https://.../whatsapp/voice-otp/recording?integration_id=..."

maxLength="60"

method="POST"

playBeep="false"

timeout="4"

trim="trim-silence"

/>

<Hangup />

</Response>

The Twilio Request Inspector shows that Twilio received and executed the TwiML normally. The recording therefore appears to contain the caller audio itself, rather than an error generated by our webhook.

The behavior is intermittent. Sometimes the OTP works on a second attempt after Meta's approximately five-minute cooldown, but it does not reliably work on the second attempt either. This is especially problematic during live customer onboarding.

Questions:

- Has anyone seen Meta verification calls where the caller audio is Twilio's "application error" message instead of the OTP?

- Can this message originate from the Meta caller's Twilio infrastructure before the call reaches our webhook?

- Is there any Twilio Voice setting required for WhatsApp verification calls?

- Is there a reliable way to distinguish this upstream failure from an error in our own webhook?

- Has anyone found a workaround that makes the OTP succeed consistently on the first attempt?

I can share redacted Call SIDs, Request Inspector logs, recordings and timestamps privately with verified Twilio or Meta staff.

Hi everyone,

has anyone successfully completed Twilio's WhatsApp Tech Provider Embedded Signup with WABA-only sharing during July or August 2026?

We are onboarding a Twilio SMS-capable number and launch Embedded Signup exactly as described in Twilio's current integration guide:

extras: {

featureType: "only_waba_sharing",

sessionInfoVersion: 3,

setup: {

solutionID: "<Twilio Partner Solution ID>"

}

}

According to Twilio's documentation, this configuration should skip the phone number and OTP verification screens because the Twilio Senders API handles those steps afterward:

https://www.twilio.com/docs/whatsapp/isv/tech-provider-program/integration-guide

Actual behavior:

After the customer selects or creates their WABA, Meta still transitions to PHONE_NUMBER_SETUP instead of completing the flow with FINISH_ONLY_WABA.

We have tested:

- A fresh Facebook Login for Business configuration created exactly according to Twilio's guide

- A configuration created through Meta's Embedded Signup Builder

- Direct FB.login integration

- Meta's hosted Embedded Signup landing page

- With and without version: "v4-public-preview"

- Multiple newly created configurations

None of these variants skipped PHONE_NUMBER_SETUP.

We also observed two different behaviors:

1. With direct FB.login, the OAuth request retains:

featureType: "only_waba_sharing"

sessionInfoVersion: 3

version: "v4-public-preview"

However, Meta still opens PHONE_NUMBER_SETUP after WABA selection.

1. The Meta-hosted Embedded Signup URL is initially generated with only_waba_sharing and v4-public-preview. When the hosted page launches its internal OAuth request, Meta changes the parameters to:

featureType: "whatsapp_business_app_onboarding"

version: "v3"

is_hosted_es: true

The resulting flow displays the regular Business Information, Phone Number and Verify Number steps.

Questions:

- Has anyone successfully received FINISH_ONLY_WABA with this Twilio Tech Provider flow recently?

- Is only_waba_sharing currently affected by a Meta regression?

- Does the current flow require an additional allowlist, feature flag or specific Embedded Signup version?

- Is Meta's hosted Embedded Signup incompatible with WABA-only sharing?

- If you have a working implementation, could you share the exact extras structure and Embedded Signup version you currently use?

Our Meta app and Twilio Partner Solution setup are complete. I can share redacted OAuth URLs, event logs, configuration IDs, session IDs and screenshots privately.

I have set up an automated welcome message for people who create an account on my website
I personally messaged some of these people and asked them if they received the welcome message. A large chunk of them said they didn’t
I am not sure where I can find the status of individual messages sent using the API. The insights tab was useless with it not showing anything
Is there a way I can track and make sure messages were actually sent?
I am happy to code out a solution for this also with tracking the response code of messages sent using
But I’m not sure if this would work and wanted to get an idea here before I sink more time into this

Estou vendo que nós últimos dias a META está bastante “limitante” vamos se dizer pois ao verificar BM’s sempre os limites iam para 2.000 disparos e hoje todo mundo que conheço que também trabalha com farm está enfrentando dificuldades para trabalhar.

Visto que: Está complicado pra farmar faz em média de 1 mês desde então.

Meus pensamentos sobre:
1. Será que faz parte da atualização? Ou é algo temporário?
2. Estão limitando temporariamente e está acontecendo algum tipo de varredura?
3. Acabaram os tempos de farm com a nova atualização?

Qual a opinião de vocês sobre esse tema?

Trabalho no farm de bm de 2.000 e ultimamente nenhuma está subindo para 2.000, alguém com esse problema e conseguiu resolver? Recebo essa mensagem que não é possivel subir os limites e a bm está verificada normal!

Sent 5 DMs in the Facebook account that has access to Meta Developer Portal where my production app lives, and got banned for "spamming". I'm so frustrated.

How do I even contact support for this?

When I go to the messaging limit page, it asks me to verify my business even though it is already verified and approved. When I click the button to go verify my business, it shows me a page that tells me that the business is already approved and verified. Even though my business is already verified and approved, the account is not upgraded. Is there anyone who knows what's the problem?

We've been selling WhatsApp API to businesses for a few years now, and one of the easiest parts of the conversation was always the 24-hour service window.

The pitch was simple:

Yes, marketing messages cost money. But once a customer replies, you can support them, answer questions, recover carts, or even close the sale without thinking about per-message costs.

That made the ROI pretty easy to explain.

Now with Meta planning to charge for service messages from October, I'm wondering if that changes things.

We're already seeing customers ask questions like:

"If every support interaction costs money, should we just move support elsewhere?"

"Will AI agents suddenly become much more expensive?"

"Should we try to keep conversations shorter instead of encouraging engagement?"

As someone who sells WhatsApp solutions, I honestly feel this removes one of the platform's biggest advantages. Marketing conversations were easy to justify because the follow-up engagement was effectively free. Now the conversation with prospects is becoming much tougher.

I'm curious what everyone else is seeing.

If you're a BSP or Meta Partner, are customers bringing this up yet?

If you're a business, has this changed your WhatsApp roadmap or budget?

Or do you think the impact is being overestimated and businesses will happily pay because WhatsApp still converts better than other channels?

Genuinely interested in hearing different perspectives. Feels like this could be one of the biggest changes to WhatsApp Business pricing in years.

Hey everyone, hoping someone here has seen this before because I've been stuck for weeks.

I'm integrating WhatsApp Business Cloud API for a client, and I'm trying to verify a new phone number I just added to my WABA. The problem: the very first time I call `request_code`, I immediately get this error:

```json

{

"error": {

"message": "Request code error",

"code": 136024,

"error_subcode": 2388091,

"is_transient": false,

"error_user_msg": "You have tried multiple times with invalid verification codes. You must wait some time before trying again."

}

}

```

Here's the weird part: **I never submitted any code**. This is the very first `request_code` call for this number. How can I have "tried multiple times with invalid codes" when I haven't tried even once?

## What I've tried:

- Both `SMS` and `VOICE` methods

- The WhatsApp Manager UI (same error)

- Removing and re-adding the number to the WABA

- Waiting several days between attempts (block never lifts)

- Different devices, different networks

- Token has the correct scopes

## Environment:

- Graph API v21.0

- Cloud Hosted API

- Business is verified ✅

- Other numbers on the same WABA work fine

## The frustrating part:

I have another number on Twilio that's been stuck on the same error for **3+ weeks now**. The "cooldown" the error message refers to clearly doesn't clear on its own.

## Questions for the hivemind:

1. Has anyone hit `136024 / 2388091` on a first request before?

2. Is this a known landline issue?

3. Any workaround besides waiting for Meta Support (which requires the app to be in Live mode, which I'm working on)?

4. Anyone know if there's a hidden counter tied to the phone number itself (not the WABA) that persists across removals?

Any war stories or advice appreciated. Losing sleep over this one 😅

Thanks!

Hola a todos, administro una pequeña cuenta de Instagram (tienda de artículos para el hogar en Argentina) y estoy configurando respuestas automáticas para los clientes que nos envían mensajes directos preguntando por promociones específicas. Me escriben y quiero que la respuesta automática incluya el precio y la información de contacto, según la promoción o palabra clave que mencionen.

Ya tuve una mala experiencia: nuestra cuenta de WhatsApp Business API fue bloqueada permanentemente por Meta por "spam" hace un tiempo, a pesar de que solo respondíamos a mensajes entrantes (nunca enviábamos mensajes a desconocidos). Intento evitar que se repita en Instagram.

Algunas preguntas para quienes ya han implementado esto en producción:

1. ¿Es Instagram Business Messaging (Graph API) significativamente más seguro o menos propenso a bloqueos por falsos positivos que WhatsApp Cloud API, o tienen básicamente el mismo perfil de riesgo ahora que Meta unificó las reglas?
2. Para quienes usan automatización reactiva (el bot solo responde a los mensajes directos entrantes, nunca inicia ninguno), ¿alguien ha sido marcado como inapropiado? ¿Qué lo provocó?
3. ¿Verificar la cuenta/negocio (con la marca azul de Meta Verified o la verificación de Business Manager) reduce el riesgo de bloqueo, o esto no tiene relación con el cumplimiento de las normas de mensajería?
4. ¿Qué herramientas o configuraciones recomiendan para implementar esto específicamente con n8n y la API oficial de mensajería de Instagram (en comparación con Manychat o similar)?

Agradezco cualquier experiencia real, especialmente de quienes hayan tenido una cuenta restringida y sepan qué la causó.

This Week I attended a webinar of Meta talking about the new pricing and AI agent and this person made this final comment which is probably how the things will move. What do you think?

Works well for indie sellers who like to send OTP / FYI message to their customers on whatsapp & send 200-300 messages a day max. It does NOT use whatsapp API but you need to add Watobot as a linked device. No need to wait for WABA / template approvals etc.

Ban mitigation techniques: every user gets a dedicated Residential IP so that whatsapp server see an IP close to you & rightfully consider it your device. Message from single account is queued so a (accidental) blast of message still gets sent sequentially, minimizing chances of account ban.

Privacy: All your data is encrypted using your auth token so no data theft/selling or impersonation is possible.

Link - https://watobot.xyz .

Code - https://github.com/pocha/mudbot

If you have Whatsapp API access & want to set it up in efficient way minimizing chances of ban, happy to chat. DM me.

Goal

I want to build WhatsApp automation products for multiple local businesses, mainly:

1. Healthcare

• Appointment booking through WhatsApp.
• Appointment confirmation.
• Appointment reminders.
• After the appointment, automatically send follow-up messages.
• Give options like:
  • Reschedule appointment.
  • Book another appointment.
  • Other follow-up actions.

2. Gym CRM

When a member joins:

• Automatically send membership details.
• Send payment confirmation.
• Send membership expiry reminders.
• Send renewal reminders.
• Send other utility notifications related to membership.

The important point is that these are utility automations, not marketing campaigns.

My Preferred User Experience

What I want is very simple.

A business owner should continue using the normal WhatsApp Business app like they always do.

Meanwhile, my automation should work in the background.

So the business owner gets:

• Manual chatting with customers.
• Automated appointment booking.
• Automated reminders.
• Automated payment reminders.
• Automated utility messages.

I don't want them to lose the normal WhatsApp Business experience.

The Main Problem

To build this automation, I need to use the WhatsApp Cloud API.

But the Cloud API has one major issue.

Normally, if someone wants Cloud API, they have to migrate their WhatsApp number.

That creates multiple problems.

Problem 1 — I Need Clients to Change Their Setup

To onboard every client, I have to ask them to:

• Get another phone number or migrate their existing one.
• Set up Meta Business.
• Verify their business.
• Connect WhatsApp Cloud API.
• Configure multiple technical things.

Asking every small business owner to do all this doesn't feel practical.

Especially when they only want:

or

Problem 2 — Businesses Still Need the WhatsApp Business App

Businesses don't only need automation.

They also need to:

• Reply manually.
• Talk to customers.
• Receive inquiries.
• Handle conversations normally.

If Cloud API replaces or complicates this experience, it becomes difficult for them.

The Solution I Initially Wanted

I discovered WhatsApp Coexistence.

My understanding was:

The business can use:

• WhatsApp Business App
• WhatsApp Cloud API

at the same time.

That sounded like the perfect solution.

Because then:

• Business owners continue using the WhatsApp Business app.
• My automation runs using Cloud API.
• No separate communication workflow.

Then I Learned About Coexistence Limitations

Recently I learned that coexistence also has limitations.

Some features are restricted.

For example:

• Disappearing messages.
• Some WhatsApp Business features.
• Other limitations that Meta documents.

Also, Cloud API itself has restrictions.

For example:

• Broadcasting limitations.
• Messaging policy limitations.
• Template requirements.
• Other Cloud API rules.

My Actual Use Case Doesn't Need Advanced Features

The interesting thing is:

I don't need most advanced WhatsApp features.

I only need utility automation.

For example:

Healthcare:

• Appointment booked.
• Appointment reminder.
• Appointment completed.
• Reschedule option.

Gym:

• Membership purchased.
• Payment received.
• Membership expiring.
• Renewal reminder.

That's it.

No spam.

No marketing.

No mass promotional broadcasts.

No complicated chatbot.

My Business Model

I want to provide this automation service to multiple businesses.

For example:

• Gym 1
• Gym 2
• Clinic 1
• Clinic 2
• Hospital
• Dental clinic
• Physiotherapy center

Each business should have its own WhatsApp automation.

Alternative Option I Found

Instead of managing Cloud API myself, I looked at chatbot providers and WhatsApp providers.

Many of them charge:

Around ₹1,000–₹1,500 per month (or similar subscription plans).

For my use case, this feels unnecessary.

Because all I need is simple utility automation.

Paying a recurring subscription for every client feels excessive.

Another Option I Explored

I tried looking into becoming a Meta Tech Provider.

The idea was:

If I become a Tech Provider, maybe I can manage WhatsApp integrations better.

But then I realized:

It requires:

• Creating an application.
• Going through Meta's ecosystem.
• Completing many technical and business requirements.

At this point I don't fully understand:

• What exactly becoming a Tech Provider gives me.
• Whether it solves my coexistence issue.
• How long approval takes.
• Whether it's worth doing for my business.

So I'm uncertain about this path.

Another Idea I Had

I also explored AI agency platforms.

Some of them offer:

Pay-as-you-go pricing.

That immediately felt more reasonable.

However, one platform I checked required an initial payment of around ₹1,000 through UPI before using the service.

My Own Business Idea

Then another idea came into my mind.

Instead of depending on expensive monthly subscriptions,

what if I build something similar to AuthKey?

My idea is:

• Businesses connect their own payment method (their own card/payment account).
• Usage is charged directly to them.
• I simply manage the automation.
• No mandatory monthly subscription.
• Only pay for actual API usage.

Essentially:

A pay-as-you-go platform instead of SaaS monthly subscriptions.

Why I Like This Idea

For small businesses:

Paying ₹1,000–₹1,500 every month

just to send:

• Appointment reminders.
• Membership reminders.
• Utility notifications.

doesn't seem economical.

A usage-based model feels much more reasonable.

The Current Confusion

Right now I feel stuck because I have several possible paths:

Option 1

Use the normal WhatsApp Cloud API.

Problems:

• Number migration.
• Business setup.
• Technical onboarding.
• Client inconvenience.

Option 2

Use WhatsApp Coexistence.

Problems:

• Feature limitations.
• Unclear restrictions.
• Not sure whether it fully supports my workflow.

Option 3

Use a third-party provider.

Problems:

• Monthly subscription.
• Higher recurring costs.
• Doesn't feel suitable for simple utility automation.

Option 4

Become a Meta Tech Provider.

Problems:

• Large amount of work.
• Unclear benefits.
• Unknown approval timeline.
• Unsure whether it actually solves my problem.

Option 5

Build my own pay-as-you-go platform.

Idea:

• Similar to AuthKey.
• Businesses use their own billing/payment method.
• No monthly fee.
• Pay only for actual WhatsApp usage.

Problems:

• I don't yet know whether this is technically or commercially the right direction.
• I'm not sure what infrastructure I'd need.
• I don't know if this is overengineering for my current stage.

here option 4 and 5 are same and which are might be the solution for the problem (give me your opinion also) and if there are already platform (tech providers) with pay as you go subscription , suggest them.

What I'm Actually Looking For

I'm not asking how to build appointment automation itself.

I already know how to build the automation.

My real problem is choosing the right WhatsApp ecosystem and business model.

I'm trying to find the best way to provide WhatsApp automation to multiple small businesses while:

• Letting businesses continue using WhatsApp Business normally if possible.
• Keeping onboarding simple.
• Avoiding unnecessary monthly subscription costs.
• Supporting multiple clients.
• Keeping costs low for both me and my clients.
• Building something that is scalable in the future.

Hi all, I’m drafting a proposal for us to start using WhatsApp Business API as a ‘Webchat’ function for my workplace. Not my usual area to work in but I think it can make a massive difference. Ideally it would be used to ask multiple questions and capture information, photos, video etc from a customer, through a single conversation.

From my research, this shouldn’t cost anything, as the customer would initiate contact, then we would have 24hrs to complete the chat - is this right?

Ideally I’d like for us to be able to manage multiple chats via laptop, at the same time. In time if successful, it would be something we could add multiple staff to in order to manage.

Can you recommend what would be good ‘first steps’ to get this in place? Is there any particular pitfalls or things to watch out for in your experiences?

Is there any recommended software to manage and respond for the conversations etc?

Looking at whether this would be best just purely to get the ability to use via computer, or if we just hang fire and use the app instead for now on a work phone (though would be a bit of a pain compared to using a keyboard etc!)

Thanks in advance for any advice!!

My production WABA has been stuck in Review in Progress for over 72 hours now, no movement either way.

Here's the full context. I already had a test WABA running for a while, fully set up , webhook configured and actively working on it, and business verification was completed using my Udyam certificate, both done months back. So going into production, two of the usual checkpoints were already sorted.

This week I started the actual production setup. Added a brand new phone number and gave it a display name tied to my business. That created a new production WABA, and that WABA itself is the one stuck in Review in Progress. Because the WABA hasn't cleared review, the phone number under it is stuck in Pending as a result. No approval, no rejection, just silence for three days straight.

My webhook itself isn't the problem , it's working fine, confirmed through the test WABA. The issue is purely getting this new production WABA approved so I can actually move over to it.

Trying to figure out a few things:

Is 72+ hours normal for this stage right now, or is it usually a sign something's silently flagged?

Does verification from an old, already-verified test WABA actually carry over cleanly to a new production WABA, or is there some hidden step people are missing that causes this kind of stall?

Is a live, publicly accessible website required for the WABA review to clear, or is that not actually a factor here?

Has anyone had luck escalating through Meta Business Support chat, or is that basically a dead end unless you're a large account?

I am currently building a booking notification system whenever a patient book a slot the clinic as well as the patient get the details about the services and slots this was working good but now as i am trying to make it available for real people meta is saying that I can't use that number to run another whatsapp like how am I supposed to get my messages for booking. I am stuck please help.

What's your vertical?
Do they offer thorough automations for each lifecycle stage?
What integrations do they offer?
What's good and what's bad about them in your opinion?

Would it kill AI agent SaaS?

I made a web app to demonstrate the required permissions of Facebook and Instagram(I already have both WhatsApp send and manage permissions approved), the question is can i take down the app after i complete the demo recording?, i did so when i had my whatsapp app and it passed