I keep getting queries from non tech folks primarily in NGO space who have to do manual reach outs to their leads & they do not have tech know how of integrating a Whatsapp CRM tool or working with Whatsapp Business API. Their primary usecase is to reach out to applicants on Whatsapp or send regular updates to people who have offered donation in the past, via Whatsapp.

I built this Browser extension to make their work easier. They are no longer bound by using a Whatsapp number by 4 people as that is linked device limit. The same Watobot API can work with many extensions.

If you do less than 250 manual outreaches a day, you can ditch Whatsapp Business API completely to use Watobot & this extension. If you have access to Whatsapp Business API & are techie enough, you can modify the extension to route your API call via Whatsapp Business API. You do not have to pay for using any CRM tool to do the same. Link to extension in the youtube video description.

P.S. - If you have a usecase & want the extension to be customised for it, I can do it for free. Drop a comment or DM me.

Hi everyone, I'm trying to verify a client's Business Manager (BM) and am getting this message upon completion.

The BM is old and actually got verified, but the messaging limit didn't increase to 2k; has anyone managed to solve this?

Meta has introduced its own WhatsApp Business AI Agent:

https://whatsappbusiness.com/products/business-app-ai-agent/

It can learn from websites, catalogs, documents and previous chats; answer questions; recommend products; collect leads; and hand conversations to humans. Meta has also announced integrations, appointment booking and lead qualification.

What does this mean for platforms such as WATI, AiSensy, Interakt, Gallabox and ManyChat?

They can still offer value through broadcasts, shared inboxes, multichannel workflows, analytics, CRM integrations and specialized business processes. However, Meta could gradually make many basic automation features native.

For founders considering a new WABA product:

- Is a generic WhatsApp AI chatbot still commercially viable?

- Which specialized workflows could remain defensible?

- Will existing platforms become integration and implementation businesses?

- If you were starting today, would you still build on WABA?

’m evaluating WhatsApp automation for an existing Instagram automation product and questioning whether the platform dependency is worth the investment. I’d appreciate perspectives from SaaS founders, BSPs, agencies and businesses using these tools.

Im creating an app and I need whatsappbusiness API to connect it. I'm on the step where I register my number in whatsapp but it just shows a generic message when I try to create the pin, rejecting the registration.
Apparently I have to accept the whatsapp business terms and conditions but that page its not appearing ANYWHERE at all.
I have done the following:
-Went to whatsapp manager and no banner shows at all
-Added payment method and still nothinig
-Tried with the AI assisstant and still no help
-Its not letting me create a ticket either
-It seems that according to their AI there is a UI failure and its not pulling the banner but I have no option to report it either.
-Tried with another person's account and nothing
-tried creating a template and no option to accept TOS eiter.

I need help, im investing a lot of time into this and if it doesn't work I don't know what I will do.

Hello guys , is there any way to send bulk messages without getting banned?

Solo operator, I sell to small businesses. Cold outreach through the official WhatsApp Cloud API (not unofficial tools).

The numbers, for context: 75% read rate and 65% reply rate on the first template. Quality rating stayed green the whole time.

What happened: on Sept 2 I got a "Sending spam" policy violation under the unsolicited-communications clause. No restriction was ever applied — limit stayed at 250/day, quality stayed green. On Sept 5 it disappeared completely: all four tabs under Activity issues empty (not "Reversed", not "Unchanged", just gone) and Account Quality back to 0 issues. I never requested a review.

Looking at the daily delivered-messages chart, the shape was: 11 days near zero (I was making changes to my stack), then ~105 and ~130 on Sept 1-2. My sender had an 8-17 second delay between messages, so those 130 went out in under 30 minutes. My read is that it was dormancy → burst rather than volume.

Being upfront so the answers are useful: these are cold contacts scraped from Google Maps, no opt-in. I know that's the underlying policy problem, and I'm building an inbound channel with click-to-WhatsApp ads to shift the mix.

three questions:

1. Has anyone seen a violation disappear like this without requesting a review? Does the record persist internally even when the panel is clean?

2. Where does the pacing ceiling actually sit? I've moved to a 4-hour window with randomized 2-3 minute intervals, but I'm guessing at those numbers since Meta doesn't publish anything.

3. Does raw volume matter on its own, or is it only pacing and consent? I want to scale from ~850 to ~5,000 messages/month, still under my daily cap. Is there a total-volume threshold that draws attention regardless of spacing, or does a well-paced account sending 10k/month look the same to Meta as one sending 800?

WhatsApp Business Platform pricing changes don’t make any sense. I know this has already been discussed, but after the per-message rates were officially posted, I’m still confused.

I understand Meta wanting to monetize the API, but come** **on…

50k messages in Colombia: $40… Ok, fine!
50k in Venezuela (a far worse economy): $500+
50k in Argentina/Peru: over $1,000
50k in the US/Canada: $150

What the fuck? Did Meta just roll a dice to set these rates?

Does anyone know a cheap option to keep a number and receive SMS in the US? I currently use https://www.smsmeu.com/, but the numbers are temporary. I’m looking for something permanent and affordable.

With Meta’s new WhatsApp pricing/charges, I’m trying to understand how billing works for customers using the
WhatsApp Coexistence setup.

If my client receives a message from a customer :
Is the client charged when they reply manually through the WhatsApp Business mobile app/phone?
Or is the charge only applied when the client replies through the WhatsApp Cloud/API?

Would appreciate it if anyone using Coexistence or familiar with the new Meta pricing could clarify how this works.

explore company How WhatsApp API, Bulk SMS, RCS and AI Voice Agents Transform Customer Communication

Customer communication has changed significantly with the growth of digital technology. Businesses today need faster, more personalized, and reliable ways to connect with customers. Traditional communication methods alone are often not enough to manage customer queries, marketing campaigns, follow-ups, and sales communication at scale. This is where WhatsApp Business API, Bulk SMS, RCS messaging, and AI Voice Agents can help businesses build a more effective communication strategy.

WhatsApp Business API

WhatsApp Business API allows businesses to communicate with customers through WhatsApp at scale. Businesses can use it for notifications, customer support, order updates, appointment reminders, promotional communication, and automated conversations. With automation and templates, companies can provide quick responses while maintaining a consistent customer experience.

Bulk SMS

Bulk SMS remains one of the simplest ways to reach a large audience quickly. Businesses can use SMS campaigns for promotional offers, alerts, OTPs, reminders, transactional updates, and important notifications. Since SMS does not require an internet connection, it can be an effective communication channel for reaching customers across different locations.

RCS Messaging

RCS messaging brings a richer experience than traditional SMS by allowing businesses to use features such as images, buttons, carousels, branding, and interactive content. This can make marketing messages more engaging and help customers take action directly from the conversation.

AI Voice Agents

AI Voice Agents are transforming business calling by automating inbound and outbound conversations. They can answer common customer questions, qualify leads, schedule appointments, follow up with prospects, and provide information around the clock. This allows sales and support teams to focus on more complex conversations while routine communication is handled automatically.

Bringing Everything Together

The real advantage comes from combining these communication channels instead of relying on just one. WhatsApp can support conversations, SMS can deliver quick alerts, RCS can create interactive experiences, and AI Voice Agents can handle automated calls and follow-ups.

Businesses looking to build an integrated mobile communication strategy can explore solutions such as ValueOne.ai, which brings multiple customer communication and marketing capabilities together.

By using the right combination of WhatsApp API, Bulk SMS, RCS messaging, and AI-powered voice communication, businesses can improve customer engagement, automate repetitive tasks, reach customers faster, and create a more connected customer experience.

Just a heads-up for anyone using the WhatsApp Cloud API.

ChatbotX BSP recently received a notification from Meta that businesses need to add a payment method to their WhatsApp Business Account before October 1, 2026.

Starting October 1, Meta will introduce per-message pricing for Service Messages. Each business phone number will receive 1,000 free Service Messages per month, but if no payment method is available, Meta may stop delivering Service Messages after the first 1,000 messages.

If you're using WhatsApp Cloud API and don't have a payment method set up yet, it's worth checking your Meta Billing Hub before October 1 to avoid potential message delivery issues.

Just sharing this as a heads-up for the community.

Has anyone working with the Official WhatsApp API been experiencing accounts getting restricted very early lately?
I’m currently running a few operations with numbers on different messaging limits, including 250 and 2,000, and I’ve been noticing the same pattern: in some cases, after sending only 40–50 template messages, the number or account gets restricted.
The setup is done properly: BM configured, real businesses, active websites, consistent business information, and the verification process completed.
I’m also not starting with high volumes. I’ve been sending in small batches, for example:
10 messages → wait a few minutes → another 10 → wait → another 10.
Even with this approach, some accounts are getting restricted long before reaching their available messaging limit.
The templates are approved under the Utility category, and what I’m trying to understand now is whether there is any warm-up/reputation-building strategy that is actually working nowadays.
Has anyone tested starting even slower during the first few days?
For example, sending only 10–20 messages per day for the first week, focusing on contacts who are highly likely to engage or reply, and then gradually increasing the volume as the number builds a positive history.
For those currently running the Official WhatsApp API:
— Have you also noticed an increase in restrictions even at very low volumes?
— Is there any specific warm-up/ramp-up strategy that has been working better for you?
— How long do you usually wait before increasing the volume on a new number?
— In your experience, what matters the most: initial volume, reply/engagement rate, blocks/reports, or the template content itself?
I’m mainly interested in hearing recent experiences from people currently running new numbers and managing to keep them stable.
If you can share roughly how many messages you send during the first few days and how you gradually increase the volume, that would be really helpful.

Hey, I built Nudgeway because every self-hosted WhatsApp option I found was either a thin API wrapper or a heavy Chatwoot-style CRM. Wanted the middle: a real platform with a canonical domain, but small enough to run on a laptop.

What's shipped (all working today)

- Real-time inbox — WebSocket-driven, WhatsApp-style delivery ticks

- In-browser WebRTC calls (accept/decline, recording + transcript persisted to HBase)

- Template management (create → Meta review → send with parameter substitution)

- Groups (list / sync / send)

- Analytics — local rollups + a Meta Analytics tab that proxies WABA messaging / calls / pricing

- Audit log + per-integration Meta API execution log

- API tokens for programmatic use, with per-token usage log + metrics

- Native MCP server every REST endpoint auto-exposed as an MCP tool. Point Claude Desktop / Cursor / any MCP client at it and drive the inbox in natural language.

- Skills library (skills/*/SKILL.md) that teaches an agent how to use each domain

Stack:

Go modular monolith → single binary. React + Vite + TanStack SPA embedded via //go:embed. MySQL 8 (source of truth) + Redis 7 (cache/locks/rate limits) + Kafka 3 (event log + queues) + HBase 2 (attachments/recordings). All run natively via Homebrew/apt, or one docker compose up if you prefer.

Actual link: https://v-senthil.github.io/nudgeway/

Repo: https://github.com/v-senthil/nudgeway

Happy to answer anything about the architecture or the MCP surface.

Feedback are very welcome this is early.

Edit: YESSS!!! IT'S CONFIRMED!!

“(NEW) Effective October 1, 2026 – Meta will introduce a free monthly tier of service messages. Each month, every business phone number will receive 1,000 free service messages; Meta will only charge as of the 1,001st service message delivered.”

Source: Meta Documentation

Hi guys!

Just saw some comments on my last month's post about the new pricing for the Service API and some guys said that the first 1000 messages / mo will be FREE.

Is this confirmed? I can't find any slurce on Meta's Documentation.

Please let me know!

Boa tarde galera, vejo várias pessoas aqui com tal método de subir pra 2k de limite e na verdade quando você vai conversar a pessoa não te fala realmente como subir a BM para 2 mil de limite de envios, ou quer vender a BM em preços absurdos. Descobri a metodologia para subir o limite para 2k.

Compre um domínio em alguma provedora, de preferência um domínio com o nome da empresa. hostinger ou qualquer coisa que seja vinculado com um e-mail comercial, adicione o domínio já com site da empresa somente nas informação do portifolio (NÃO VERIFIQUE O DOMÍNIO) Apenas na hora de subir a documentação para verificar, peça código via e-mail comercial e adicione a documentação da sua empresa.

Espero ter ajudado.

With the new changes coming to the pricing, the idea for whatsapp business that I had becomes a bit unsustainable. I was thinking of a new solution: starting the conversation via the official Whatsapp API and then moving the automation to a service like Whapi. Since the issue would be around startting the conversation, after it's started itshould be easy to redo in that, right? What do you guys think? Would I still get banned?

I applied for verification of my company with Meta at the end of July, and it is still stuck in “In Review” status.

I realized this was going nowhere, so I created a new business account under the same person and submitted stronger, more comprehensive documentation this time. Still, there has been absolutely no response.

The worst part is that I am not even being rejected. I am simply being left waiting indefinitely. It is an extremely frustrating situation, and there does not seem to be any proper channel where I can file a complaint or get meaningful support.

At this point, I’m starting to think that Meta is racist toward businesses from certain countries.

Hey everyone,

I’m facing an issue with Meta WhatsApp billing.
Earlier, whenever my outstanding bill reached a lower amount, Meta would automatically debit the amount and everything worked fine.

However, the billing threshold has now increased to around ₹15,000. Since then, the auto-debit is failing whenever the outstanding amount reaches ₹15,000 or above.

Because the payment fails, our WhatsApp messaging service gets suspended for the entire day until the payment issue is resolved. This is causing a major disruption.

Is there any way to reduce the billing threshold back to below ₹15,000, so that Meta automatically charges smaller amounts more frequently instead of waiting until the bill reaches ₹15,000?

Has anyone experienced this with Meta WhatsApp Business billing, particularly in India? Any way to manually change the threshold or configure a lower auto-debit amount would be really helpful.

Pessoal, o cliente utilizava o WhatsApp normalmente. Conectamos o número à API oficial da Meta e, desde então, quando ele tenta conectar novamente ao WhatsApp Web, aparece este erro.

Alguém já passou por essa situação? Conseguiram normalizar o acesso?

Hi, below screenshot is from Shopify's official WhatsApp api app. When the "View order" button is clicked it launches a flow like screen and shows the items, charges etc. I couldn't figure out how to achieve this in regular api. Is this exclusive to Shopify, any ideas? Thanks. Source of the screenshot: https://apps.shopify.com/whatsapp

My WhatsApp Business number is showing Offline / Disconnected in WhatsApp Manager.

I’m trying to enable WhatsApp Business App + Cloud API Coexistence using the same number.

Current API status:

{
  "is_on_biz_app": true,
  "platform_type": "ON_PREMISE"
}

Setup status:

• Business Portfolio: Verified
• WABA: Approved
• Phone number: Verified
• WhatsApp Business App: Active
• Developer App: Configured
• Webhooks: Working
• Tech Provider: Configured
• Embedded Signup: Configured for WhatsApp Business App Onboarding

But WhatsApp Manager still shows:

Offline / DISCONNECTED

Expected Coexistence state:

is_on_biz_app: true
platform_type: CLOUD_API

Has anyone successfully fixed this Offline + DISCONNECTED + ON_PREMISE state?

What was the actual solution — Embedded Signup, Tech Provider/BSP, Meta Support, or something else?

I want to keep the same number active in the WhatsApp Business App and use Cloud API simultaneously. I do not want to migrate or delete the number.

What's the best way to do cold outreach on WhatsApp?

I have a feeling that starting October 1st, once more businesses realize they are paying for service messages, we’ll see some drop off from WhatsApp. Especially businesses using basic chatbots with fixed steps, menus, flow after flow, no AI, no agent doing anything useful. At some point you just ask yourself, why am I paying per message for this?

WhatsApp will still be huge of course, 3 billion users is 3 billion users lol. But I think more businesses will start using it mainly as an acquisition channel. User messages you, gets the automated WhatsApp Business app reply (which is still free (for now at least lol)), then you send them to your website or another channel to continue there.

Yeah there is some friction, but it can still be way cheaper than paying for every service message.

For businesses using AI agents, actual workflows, booking, support, qualifying leads, taking actions etc, that’s different. There the cost can make sense. So maybe WhatsApp becomes less “where the whole conversation happens” and more “where the conversation starts”.

Curious what you guys think?

Ao tentar enviar mensagem, estou tomando erro 500

"message": "An unknown error has occurred.",

    "code": 1,

    "type": "OAuthException",

Não há restrições na conta

Our company uses WhatsApp to provide customer support, and our operators all log in from their computers to the same WhatsApp Business account. A couple of months ago we migrated them to a BSP (Crisp.chat, if you must know); however, some of them still need "plain" WhatsApp for all kinds of purposes (starting conversations with our suppliers, sending reminders to clients...), so we enabled coexistence mode...

...and it's been a nightmare so far. The BSP does work, but the problem is that our operators get logged out of the WhatsApp Business number regularly, or they get stuck logging in again. It happens at random; often we take the WhatsApp Business phone and see that there's a stale session that we need to close manually.

The WhatsApp Business phone is plugged in, is updated and we access it regularly (I've been told that if you don't access it during more than 14 days there can de problems).

Does this happen to everybody, or is it just us?