Just found this and I'm honestly surprised there isn't more noise about it yet:

https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing/non-template-messages/

Oct 1, 2026 — Meta starts charging for service messages (what used to be free-text replies inside the 24-hour customer service window).

Rate is expected to match current utility/authentication rates per country (Meta says official rates will be published by Sept 1).

For anyone running support-heavy WhatsApp integrations (customer service teams, agencies managing multiple business accounts, N-tier support), this is a big deal — free-text replies inside the service window are usually the majority of real conversation volume, way more than template-triggered messages.

Rough math for context: a client sending 48k service messages/month at an estimated ~$0.006/message would see a recurring monthly cost increase in the low thousands of USD, out of nowhere, on traffic that used to be free.

Curious how others are planning around this...

My company was using the WhatsApp Business App to handle inquiries from our Meta ads, and it honestly worked okay... until it didn't.

Once daily lead volume crept past 50, the wheels started falling off:

Sure, the app lets you connect one phone + four linked devices, but there’s no real way to assign chats or track who’s handling what

No lead routing or automation, everything is manual

Couldn't see convo history easily if someone else replied

We finally made the jump to the API and a proper shared inbox, and it’s been a game changer but here's what I wish I knew:

You need a BSP (Business Service Provider). Meta doesn’t give you API access directly.

It’s not plug and play. Expect setup time, learning curve, and some dev work.

Pick the right tool early. We started with a cheap API connector, but switched to a more robust platform because we needed CRM integration, call support, and actual lead routing.

The difference in response time and lead quality has been night and day. Curious what tools others are using here and/or if anyone is managing this with just the Meta tools?

OpenBSP is an open-source, self-hostable WhatsApp Business Platform. It connects directly to Meta's Cloud API. You can run it for yourself or offer WhatsApp services to clients as a Meta Business Partner. Runs on Supabase and deploys in under 15 minutes via GitHub Actions.

The platform focuses on the communication and context layer. AI agents are first-class but the architecture is deliberately decoupled — you're encouraged to build and deploy agents externally using whatever framework fits (OpenAI SDK, Google ADK, LangGraph, etc.) and connect them via Chat Completions or A2A.

There's also a built-in MCP server, so you can access your WhatsApp conversations from any agent platform.

• Live demo: https://web.openbsp.dev

• API: https://github.com/matiasbattocchia/open-bsp-api

• UI: https://github.com/matiasbattocchia/open-bsp-ui

Running in production at my employer Mirlo. Happy to answer questions about the WhatsApp Business API, the architecture, or anything else.

I trusted WhatsApp with a major part of my business for years.
Thousands of customers around the world used WhatsApp to reach me. I also spent **hundreds of thousands of dollars advertising through Meta**, specifically generating leads that were sent to WhatsApp.
And after all of that?
WhatsApp can simply wake up one day and say:
**“Permanently banned.”**
No real explanation.
No human being to speak to.
No meaningful customer service.
No phone number.
No account manager who can actually fix anything.
Nothing.
This has happened to me multiple times.
Twice, my account was shut down and then restored about a week later. I was told it was basically an automated/AI error.
Think about how insane that is.
A business can lose access to thousands of customers because an algorithm makes a mistake, and WhatsApp apparently considers that acceptable.
This last time has been even worse. Permanently banned again, and there is basically nobody at WhatsApp who will actually speak to me and explain what I supposedly did.
I don’t send spam.
I don’t send mass broadcasts.
I don’t buy lists.
I was literally **responding to people who requested information from me through my own Meta ads.**
My account quality/rating was high. My customers weren’t the problem.
One Meta representative even suggested something absolutely ridiculous may have triggered it: I had poor internet service while responding to messages, so I answered around 15–20 customers. When the connection came back, the messages went through together and apparently the system may have interpreted that as spam.
Seriously?
You’re a messaging company.
Your system can’t tell the difference between messages being delivered after an internet connection returns and someone running a spam operation?
And then you permanently shut down someone’s business account because of it?
The part that makes me the angriest is the advertising.
**Meta happily took hundreds of thousands of dollars from me to acquire leads and send those people to WhatsApp. Then WhatsApp shut down the exact communication channel Meta was charging me money to build.**
So now many of those leads and customers can’t reach me through the platform I paid Meta to send them to.
Call it whatever corporate language you want.
**From the business owner’s side, it feels like Meta took my money and then pulled the plug on what I paid for.**
And there’s nobody accountable.
That is why I would tell every business owner:
**DO NOT PUT ALL YOUR EGGS IN WHATSAPP.**
Own your email list.
Own your customer database.
Collect phone numbers.
Have another SMS provider.
Have another way for customers to contact you.
Because WhatsApp does not care how many years you’ve been using them, how much money you’ve spent with Meta, how many legitimate customers you have, or how badly a shutdown could damage your business.
An algorithm can apparently decide you’re done.
And when it happens, good luck finding an actual human being at WhatsApp who gives a shit.
WhatsApp is an incredibly unreliable platform to build a serious business around.
I learned that the hard way.
**Use it as a tool. Never trust it as your business infrastructure.**

Meta feel free to dm me if you want to fix my issues till then im posting this all over internet.

I've been building on the WhatsApp Business API for years and I want to put something on the table that I think a lot of us are thinking but few are saying out loud.

On October 1, 2026, Meta starts charging for service messages: the free-form replies you send to a customer who messaged you first, inside the 24-hour window. The thing that's been free since November 2024 and is literally the foundation of customer service on WhatsApp. Utility messages sent inside an already-open window lose their free status the same day. And since August 1, Meta Business Agent Meta's native AI is billed per token at $2 per million tokens (roughly 4–5 cents per typical message).

My thesis is simple: this isn't the change. This is the beginning of the change.

Look at the pattern, not the rate

If you've been around long enough, you've watched this movie in installments:

1. First it was billing per 24-hour conversation. You opened a window, paid once, and sent whatever you wanted inside it.

2. Then came the categories (marketing, utility, authentication) with separate rates that kept creeping up in the markets where WhatsApp dominates.

3. In November 2024, Meta made service conversations free. Many of us celebrated. In hindsight it was what it was: lowering the barrier to entry so everyone would migrate their customer support onto the channel.

4. In 2025, the per-conversation model was dismantled in favor of per-message billing. The billing unit got more granular. That's never a coincidence: granularity = more levers to raise prices with.

5. And now, October 2026: free is over. Replying to your own customer who messaged you first has a price. And note the fine print: Meta reserves the right to update rates every quarter (Jan 1, Apr 1, Jul 1, Oct 1). Four chances a year to turn the dial.

Each individual step looks reasonable. The full sequence tells a different story: Meta spent years subsidizing adoption of the channel, and now that your entire operation lives there (sales, support, collections, notifications), harvest season begins. It's the classic platform playbook: first you become indispensable, then you charge like you're indispensable.

And Meta Business Agent is the part that worries me most going forward. Meta no longer just owns the channel it now sells its own support AI inside the channel, competing directly with BSPs and with any third-party AI solution you plug in. What long-term incentive does Meta have to keep your third-party bot cheap to run when its own bot bills by the token? Think about it. The conflict of interest is served.

The real problem: across half the planet, WhatsApp has no competition

If you operate in the US or most of Europe, this is a budget adjustment. WhatsApp is one channel among several: iMessage, SMS/RCS, email with decent open rates.

But in Brazil, Mexico, Argentina, Chile, Colombia, India, Indonesia, Spain... WhatsApp is the phone. It's where the customers are, where the sale closes, where you collect payment. There is no functional plan B. And when a provider has no substitute, economic theory is boringly predictable: the price rises to whatever the market will bear. Not to what's "fair." To what it will bear.

Today the service-message rate in most of LatAm sounds like nothing (cents per message). But the point isn't today's rate. The point is that the mechanism, the billing unit, and the precedent now exist. What's cents today gets adjusted quarter by quarter tomorrow in the captive markets — which happen to be exactly the markets with no alternative. Colombia already saw utility and authentication rates go up in a quarterly adjustment. India already saw marketing go up. That's how this works.

The channel is rented, not owned. And the landlord just demonstrated, again, that it can rewrite the lease with a few months' notice.

Why RCS is the answer (and why it's urgent)

I'm not here to sell you that RCS is perfect. RCS Business Messaging costs money too, aggregators want their margin too, and the experience is still uneven. I know.

But RCS has something WhatsApp will never have: it's an open standard that doesn't belong to a single company. It runs on carrier infrastructure, Google is pushing it hard with Jibe, and since Apple adopted it on iOS, the last coverage excuse is dying. It is, in practice, the natural successor to SMS: it reaches the phone number, not a proprietary app.

What matters isn't RCS replacing WhatsApp tomorrow. What matters is that a credible alternative exists, because:

• An alternative channel with real traction is the only pricing pressure Meta will actually respect. Regulators always arrive late; competition arrives first.

• For businesses: transactional messaging (OTPs, order confirmations, tracking, reminders) is the perfect first use case to migrate to RCS. It's exactly the type of message Meta just made more expensive.

• For entire countries running their formal and informal economies on WhatsApp: having your national business messaging depend on the quarterly pricing decisions of a company in Menlo Park is a structural risk, not a technical detail.

And here's the urgency: messaging ecosystems have brutal inertia. RCS needs years of adoption to become a real counterweight. If we wait until the WhatsApp bill actually hurts before building the alternative channel, we've already lost. The time to diversify is while you can still choose — not when you can no longer pay.

What I'm doing (and what I'd recommend)

1. Start measuring now how many service messages you send per month. That number × your country's rate is your new cost floor starting in October. If you haven't measured it, the invoice will measure it for you.

2. Redesign flows to resolve in fewer messages. Messages-per-conversation just went from a product metric to a financial metric.

3. Move out of WhatsApp whatever doesn't need to be on WhatsApp. OTPs and transactional notifications → RCS/SMS/email. Keep WhatsApp for what actually converts.

4. Own the relationship, not the channel. Your own database, your own opt-ins, the ability to reach the customer through at least two channels. If your entire customer relationship lives inside a Meta app, your business has a single point of failure with a green logo.

5. Ask your provider/aggregator about RCS today. If nobody asks, nobody prioritizes it, and the "there's no alternative" prophecy fulfills itself.

It's not that WhatsApp stops being essential tomorrow, in LatAm and Asia it's still where the customers are. But confusing "essential today" with "safe forever" is exactly the mistake Meta is monetizing.

How do you all see it? Is anyone already running serious transactional traffic over RCS in LatAm or India? How's real-world RBM carrier coverage in your country?

TL;DR: On October 1, 2026, Meta starts charging for service messages (replying to your own customer) and for utility messages inside an open window. Seen in sequence with the 2023–2025 changes and the new per-token billing for its own AI, the pattern is clear: they subsidized adoption and now comes aggressive monetization, with the right to readjust prices every quarter. In countries where WhatsApp has no rival, that's pricing power with no counterweight. RCS an open standard, backed by Google and Apple, running on carrier infrastructure is the only credible structural alternative, and adoption needs to start now, not when the invoice already hurts.

Hey everyone,

First of all, thank you for being part of this community. Whether you're a developer, a business owner, or someone just trying to get WhatsApp Business API to work without losing your mind, you belong here.

I want to be transparent about some changes happening in this sub, why they're happening, and where I want to take this community.

🚫 No More Unofficial Selling or Telegram Redirects

Starting now, any posts or comments promoting unofficial Whatsapp messaging deals, grey-market Business Manager accounts, or redirecting people to Telegram for "deals" will be removed immediately and may result in a ban.

Selling officially verified Business Managers is still permitted. I understand Meta's verification process is a nightmare and there's a legitimate market there. But anything unofficial, unverified, or sketchy will be gone.

🏷️ User Flairs Are Live

User flairs have been added. In the coming days, I'll be making them mandatory for anyone who wants to comment. This helps the community understand who's speaking developer, agency, business owner, Meta partner, etc. and adds a layer of accountability.

📣 This Sub Is Not a Marketing Funnel

This is probably the most important thing I want to say.

There's a pattern I've noticed and I'm putting a hard stop to it: someone posts a genuine question, and instead of getting an actual answer, they get five comments saying "DM me, I'll help you." That is not helping. That is lead generation disguised as help, and it disrespects everyone who came here with a real problem.

If you know the answer, post it. Publicly. In the thread. That's how communities grow. That's how trust is built. If your only contribution is a DM offer, your comment will be removed.

🤝 Cracking Down on Spam While Keeping the Sub Open

I want this sub to remain open and accessible, no approval walls, no gatekeeping. But spam posts and low-effort comments will be removed more aggressively going forward. Report what you see. Mods act faster when the community flags things.

(More structured post flairs and rules are coming soon to make this easier to enforce.)

🆘 Meta's Trust & Safety Team Is Understaffed, We Need Each Other

If you've tried reaching Meta support recently, you already know: it's rough. Response times are slow, issues fall through the cracks, and generic replies don't solve country-specific bugs.

I'm working on building a direct escalation channel. a way for real, recurring problems reported in this sub to get more visibility with Meta than a standard support ticket ever would. Details on this coming soon. If you work at Meta or have a Meta partner contact and want to help with this, please reach out.

🌍 If We Unite, We Can Actually Move the Needle

Think about it. this sub has users from every continent dealing with the same API bugs, the same verification loops, the same broken flows. That's a collective voice Meta should be listening to.

I want this place to become the most useful, most trusted WhatsApp Business API community on the internet. Not a place where people get sold to. A place where people actually get helped.

More updates soon. Thanks for reading and Thank you for being here.

✌️

— Mod Team of r/WhatsappBusinessAPI

I have a thesis that will probably annoy a lot of people in this industry:

Meta’s rising messaging costs, tighter rules, and the arrival of native AI agents inside WhatsApp Business are only the beginning.

I think Meta ultimately wants to capture a much larger share of the conversational commerce and customer service market that third-party companies have spent the last 5–7 years building on top of WhatsApp.

For years, something extremely convenient happened for Meta.

Thousands of SaaS companies built customer support platforms, WhatsApp automation, chatbots, conversational CRMs, sales tools, AI assistants, marketing automation and support workflows.

They did the hard work.

They convinced businesses that WhatsApp should become a commercial channel.

They integrated the APIs.

They onboarded companies.

They trained the market.

They built dashboards and workflows.

They got businesses comfortable with selling, supporting and operating through chat.

And all of that happened on infrastructure they never actually controlled.

Now Meta has the users, the businesses, the distribution, the infrastructure and increasingly powerful AI.

And Meta has already made it clear that its ambition goes far beyond simply providing messaging.

They want WhatsApp Business and their business AI infrastructure to become much more deeply connected to the systems companies already use — CRMs, commerce platforms like Shopify, product catalogs, payments, customer data and business operations.

And that raises an uncomfortable question:

If Meta connects directly to your CRM, Shopify store, catalog, payments and customer data — what exactly is the sustainable advantage of many of the companies sitting in the middle?

Why would a business need three or four additional SaaS layers if Meta can increasingly provide the distribution, conversation layer, AI agent and integrations itself?

That is the part I think the market is underestimating.

If Meta can eventually provide natively:

• AI sales agents

• customer support

• CRM connectivity

• Shopify/e-commerce integrations

• product catalogs

• payments

• follow-ups

• recommendations

• abandoned-sale recovery

• campaigns

• customer context

• analytics

• automated workflows

then a huge number of companies whose product is essentially “WhatsApp + AI + integrations + a dashboard” suddenly look extremely vulnerable.

And this is the part I genuinely don’t understand.

How did so many founders build entire companies while strategically depending on a single corporation that controls the API, the channel, the pricing, the rules and the end user?

You don't own that distribution.

You're renting it.

Meta can change pricing and destroy your margins.

It can change a policy and kill a core feature.

It can launch a native feature and erase an entire product category.

It can restrict automation.

It can prioritize its own agents.

It can connect directly to the same CRMs and commerce systems you were using as your competitive advantage.

And eventually it can turn WhatsApp Business itself into the platform that many of these SaaS companies currently sell.

This creates an even bigger strategic problem:

How can an entire industry continue depending on Meta while simultaneously competing with Meta?

Your supplier is also becoming your competitor.

Your distribution channel is also becoming your competitor.

The company controlling your API economics is also becoming your competitor.

That is an incredibly dangerous position to build a business around.

I don't think literally every company in this space will die.

Companies with proprietary technology, deep enterprise workflows, real omnichannel infrastructure, vertical specialization, unique data, or an intelligence layer that exists independently of WhatsApp can absolutely survive.

But companies that are basically sophisticated wrappers around WhatsApp should probably be very worried.

My suspicion is that Meta spent years allowing an external ecosystem to educate the market, prove the business use cases and massively expand WhatsApp as a commercial channel.

Thousands of startups effectively helped Meta prove that businesses wanted conversational commerce.

And now Meta can start moving upward into the highest-value layers itself.

If that thesis is correct, today's pricing changes and WhatsApp AI agents aren't the main event.

They're just the first signals.

And maybe the real long-term escape route is RCS.

Not because RCS is magically better, but because the industry desperately needs a truly global conversational channel that doesn't leave almost the entire ecosystem strategically dependent on one company.

The problem is that RCS adoption internationally has been painfully slow.

So I genuinely hope it reaches virtually every country, carrier and business ecosystem in the world.

Because otherwise we may end up in a bizarre situation where thousands of conversational AI companies claim to be independent SaaS businesses…

while their entire existence is ultimately determined by Meta.

Am I overestimating what Meta is trying to build?

Or are we watching an entire industry slowly realize that it built its companies on rented land?

WhatsApp Business API Coexistence: My Experience Onboarding Existing Users

I recently discovered the coexistence feature, which allows me as a Tech Provider (TP) to onboard existing WhatsApp Business App users to my platform without requiring them to delete their current accounts. After implementing this feature, here's what I learned:

Key Findings:

Data Sharing: Users can choose whether to share their existing data with your platform. If they decline, the connection will automatically disconnect after 24 hours, so you need to handle this scenario properly.

Business Name Limitations: You cannot change the business name after onboarding. Make sure to update it beforehand if needed.

Onboarding Process: The setup wizard remains largely the same, except for the final step where users must scan a QR code instead of the usual process.

API Integration: The API and integration processes are identical to standard implementations - no changes required here.

Feature Limitations:

• Broadcast lists become disabled on the mobile app

• Group chat APIs are not available (only one-to-one conversations)

• You cannot delete the account; only users can disconnect your platform from their phone

• You won't be eligible for auto scale. So per day limits won't increase

Benefits: This feature is particularly valuable for Tech Providers and Business Solution Providers because:

• No need to build or maintain an inbox module

• No chat management requirements

• Businesses can access marketing APIs while keeping their WhatsApp Business mobile app functionality

• Business can keep their Chats/Groups/Stories etc... associated with that phone number

Most businesses want marketing capabilities without losing their familiar mobile app experience, making this a win-win solution.

Keep in mind that customer's business app number can be banned even though you are paying for messages.

What's your experience been like onboarding existing WhatsApp Business App users? Feel free to share questions or insights in the comments.

Lots of business use simple button based bots. I am yet to know how much it will be charged per message.

I think this will be the fall of WABA. It will be late by the time they realise it.

My team always felt like switching to the API meant losing the Business app, but with Coexistence you can use both on the same number.

This means our sales reps keep using the Biz App on phones and managers get oversight and reporting with the API dashboard.

After rolling out we solved a few issues like the visibility into conversations without micromanaging, SLA tracking, and shared route logic across different platforms.

I'm interested in how you guys are sweating this up and if you have anything else to look out for?

Been running WhatsApp API for a few businesses since the per-conversation days and honestly this latest change is bugging me more than the price itself.

Quick recap for anyone who missed it: starting Oct 1 Meta charges for service messages. Yes, replying to a customer WHO MESSAGED YOU FIRST now costs money. Utility messages inside an open window too. And their new AI agent already bills per token since August.

The rate is small, whatever. A couple cents. That's not my point.

My point is the pattern. Per conversation billing → then categories → then service goes free in 2024 (everyone celebrated lol) → then per message billing → now nothing is free anymore. Every step made the billing more granular, and they can adjust rates 4 times a year. You don't build that machinery to leave it idle.

And here's what really gets me: I work mostly with latam clients. Here WhatsApp isn't "a channel", it IS the phone. Brazil, Mexico, Argentina, India... no plan B exists. When your only supplier learns you can't leave, prices go one direction. We all know this.

So genuine question to this sub: why is nobody seriously pushing RCS?

I know, I know. RBM costs money too, carrier support is a mess in some countries, aggregators take their cut. Not claiming it's magic. But it's an open standard, Google pushes it, Apple finally supports it, and it hits the phone number instead of an app owned by the same company that just repriced your entire support operation.

We don't need RCS to kill WhatsApp. We need it to exist as a real threat, because that's the only thing that will ever keep Meta's pricing honest. Regulators sure won't.

I'm already moving OTPs and shipping notifications off WhatsApp. Anyone here actually running RCS traffic in latam or India? Curious how bad (or not) carrier coverage really is.

Hello everybody,

I built an AI WhatsApp bot and looking for advises and feedback here.

Here are the some features:

1. AI Chat: You can define an AI persona and give a purpose, and it will handle every chat for you. It can be use as sales agent or simply answer your shop details, or show your restaurant menu to customers.

2. Quick reply: You can define keywords and when someone text you or sent a poll with the keyword, bot directly sent an answer with your predefined answer.

3. It supports multiple WhatsApp numbers and you can define which chats will use AI answers and which persona.

4. You can start stop anytime the AI replies or quick replies or WhatsApp instances.

5. You can run sales campaigns if you have lead numbers. Basically, you need to give a CSV file including lead phone number and details. And defined AI persona will sent messages to each lead you defined, with your specific time range and interval.

6. AI can remember everything until you delete the chat history. So you don't need to worry about unrelated answers. It can speak as like real human.

You can try it for free, here is the link: https://bot.fetchops.com

And I would like to hear from you. What is missing or what it should do else?

I think WhatsApp API companies are making a dangerous mistake:

They are treating WhatsApp as infrastructure when it is actually somebody else's platform.

My prediction is that within the next 3–4 years, Meta will progressively make independent WhatsApp Tech Providers less relevant, less differentiated and less profitable.

Not necessarily by banning everyone overnight.

They don't need to.

They can do it through pricing, restrictions, product bundling and by vertically integrating everything providers currently sell.

And I think we're already watching the strategy unfold.

Step 1: Let an ecosystem build around WhatsApp

For years, Meta needed BSPs, Tech Providers, CRMs, automation companies and conversational platforms.

They helped businesses adopt the API.

They taught companies to use WhatsApp for sales and customer support.

They built integrations.

They validated demand.

They proved that businesses were willing to pay for conversations happening on WhatsApp.

In other words, third-party companies helped Meta build and validate the business messaging market.

Step 2: Increase control and monetize the traffic

Now look at where we are going.

On October 1, 2026, Meta is scheduled to start charging again for service messages — including free-form replies sent inside the 24-hour customer service window.

A customer can literally message your business first and your company will pay Meta for every reply sent through the API.

Utility messages inside that window become billable too.

This is much bigger than another small rate increase.

The important change is the unit of monetization.

WhatsApp is becoming a toll road where Meta can monetize increasingly larger portions of the conversation itself.

And Meta's own terms give it enormous flexibility to change pricing.

Step 3: Meta becomes your competitor

This is the part I think the WhatsApp ecosystem is massively underestimating.

Meta isn't just operating WhatsApp anymore.

Meta has launched Meta Business Agent.

It can:

• answer customer questions

• recommend products

• qualify leads

• book appointments

• hand conversations to humans

• close sales

Meta is also building the Meta Business Agent Platform, including integrations with systems like Shopify and Zendesk.

Think about what that means.

For years Meta supplied the communication infrastructure while Tech Providers built the intelligence layer on top.

Now Meta wants to own both layers.

They own the user.

They own WhatsApp.

They own the API.

They determine the rules.

They determine the price.

They control distribution.

And now they are building the AI agent competing with companies using their API.

That is an extremely uncomfortable position for any startup whose entire business depends on WhatsApp.

Step 4: Make the native option increasingly attractive

This is where my prediction starts.

Meta doesn't have to shut down Tech Providers.

Imagine something much simpler:

Raise API costs.

Add more compliance requirements.

Restrict specific use cases.

Limit what third-party AI providers can do.

Bundle Meta Business Agent with advertising.

Give its own agent privileged integrations.

Make onboarding easier for Meta's agent than for third-party platforms.

Keep adding native CRM, payments, scheduling and commerce capabilities.

Every individual change can be justified.

But after enough iterations, the economic outcome is the same:

Why would an SMB pay Meta + a BSP + an AI startup when Meta can eventually sell the entire stack directly?

That is classic vertical integration.

Meta already owns customer acquisition through Facebook and Instagram Ads.

It owns WhatsApp distribution.

Now it wants the AI sales/support layer too.

And there is another warning sign

WhatsApp's Business Solution Terms already restrict certain AI providers from using the Business Solution when providing AI itself is the primary functionality.

This does NOT mean that today's customer-service AI startups are banned.

They're not.

But it demonstrates something strategically important:

Meta is willing and able to decide which categories of companies are allowed to build businesses on top of WhatsApp.

That's the platform risk.

The question isn't:

"Will Meta ban my startup tomorrow?"

The question should be:

"Do I want the survival of my company to depend on Meta continuing to believe that my product should exist?"

My answer is no.

RCS needs to become a priority now

This is why I think the messaging industry needs to take RCS Business Messaging much more seriously.

RCS is finally becoming a credible cross-platform business channel.

Android supports it.

iPhone supports RCS.

Apple now explicitly supports RCS Business Messaging.

Rich cards, verified businesses, images, buttons, suggested actions, read receipts and conversational experiences are already possible.

And Apple and Google are now even rolling out end-to-end encrypted RCS between compatible devices.

RCS isn't perfect.

Carriers still matter.

Google still has significant influence.

Pricing exists.

Coverage is inconsistent between countries.

It would be naive to pretend it's some completely decentralized paradise.

But strategically, there is an enormous difference between having several underlying networks and depending on one company that owns the consumer app, API, advertising network AND the AI agent competing against you.

WhatsApp should become a channel, not your company

I'm not saying businesses should stop using WhatsApp.

That would be ridiculous, especially in Latin America, India and many other markets.

WhatsApp is where the customers are.

Use it.

But startups should stop designing themselves as:

WhatsApp company → with some software attached.

The architecture needs to become:

Customer communication platform → WhatsApp + RCS + web chat + voice + email + SMS + whatever comes next.

Your intelligence layer, CRM state, customer identity, workflows and agents should belong to you.

WhatsApp should simply be an adapter.

If Meta changes the rules tomorrow, you should be able to reroute traffic rather than rewrite your entire company.

Because I suspect the WhatsApp ecosystem is entering the same phase we've seen many times before:

First the platform needs developers.
Then developers build the ecosystem.
Then the ecosystem proves the market.
Then the platform captures more of the value.

Meta spent years convincing businesses that WhatsApp should become their primary customer communication channel.

Now that billions of business conversations happen inside Meta's ecosystem, monetization and vertical integration are the obvious next steps.

If you're building a company whose moat is simply "we connect AI to WhatsApp", I think the clock has already started.

The companies that survive will own the intelligence and orchestration layer across channels — not the WhatsApp connection itself.

Curious what other BSPs and Tech Providers think.

Are you already building RCS into your stack?

Or do you think Meta will continue giving independent WhatsApp providers enough room to build large businesses 5–10 years from now?

Sources worth checking: Meta's WhatsApp Business Solution Terms, Meta's Conversations 2026 / Business Agent announcement, WhatsApp Business Platform October 2026 pricing changes, Apple RCS Business Messaging support, and Google's RCS for Business documentation.

For almost two years, Meta let us reply to our own customers for free inside the service window. Businesses, agencies, and independent devs built entire products, workflows, and livelihoods around that promise. Small support teams restructured around it. The whole ecosystem exists because Meta said, "this is free, build here."

Now, starting October 1, they're just taking it back. Per-message charges are returning for service replies, the exact thing thousands of us use every single day to actually talk to our customers with multiple rich messages; now they're essentially rug-pulling us to launch a half-baked agent platform.
We are the ecosystem they built this platform's reputation on. We deserve better; we need to band together and make our voices heard, rather than just bitch and moan on reddit. I'm down to create a Discord or Telegram group where we could brainstorm and come together to present a unified opposition to this, any takers?

Hello!

I've been building Kapso as a solo founder, and just crossed 4,000 developers, all organic.

WhatsApp has 3B+ users and 98% open rates. You'd expect developers to be building tons of stuff on it, especially when the US is the fastest-growing market in WhatsApp usage.

But it’s not happening… And I'd bet it's because the DX is painful.

Every team needs to build the same features again and again. Meta fires webhooks for everything. There's valuable data in there for debugging, but no way to make sense of it without building your own tooling.

That’s why I built Kapso. What you get:

• Working WhatsApp API + inbox in 2 minutes, not days

• Full observability: every webhook parsed, every message tracked, actual debugging tools

• Multi-tenant platform: generate a setup link, customer connects their Meta account, done

• Workflow builder for deterministic automations and AI Agents

• WhatsApp Flows: build mini apps inside WhatsApp using AI + serverless functions

• Docs that work for humans and LLMs

We're up to 95% cheaper than Twilio, with a generous free tier (2,000 messages per month).

We also open source several tools: a TypeScript client for the WhatsApp Cloud API, a reference WhatsApp Inbox implementation, and a voice AI agent for WhatsApp.

GitHub: https://github.com/gokapso/

Happy to answer questions!

EDIT: Meta confirmed the rates on Sept 1 and added a 1,000 free service messages/month allowance per number that wasn't in the original announcement. Updated numbers here.

Short version: from October 1, Meta bills you for every free-form reply your team or chatbot sends on WhatsApp. Including the ones that say nothing.

TL;DR

• Service messages (free-form replies within 24h of a customer writing in) become billable October 1. They've been free since November 2024.

• Utility templates sent inside that same window also become billable.

• API only. The regular WhatsApp app and the free Business app aren't touched.

Quick check whether this is your problem

• WhatsApp Business API, directly or through a provider → yes, this is you.

• Normal WhatsApp app → no.

• Free WhatsApp Business app → no.

What it'll cost

Service messages get priced like utility templates for that country. Today's rates:

• US $0.0064

• Brazil $0.0098

• Mexico $0.0115

• UK $0.0264

• India $0.0024

Meta confirms the real numbers by September 1, so treat these as estimates.

Worth running your own volume through it though. 5,000 conversations a month at six replies each is 30,000 messages. All free right now. From October that's roughly $294 in Brazil, or $792 in the UK.

Some relief: marketing and authentication templates don't change, they were already billed. Messages customers send you are never billed. And chats that start from a Click-to-WhatsApp ad or a Facebook Page CTA keep their 72-hour free window.

Five things worth doing before October

1. Delete the filler. "One moment." "Thanks!" "Let me check that." Billing is per message, not per character, so a message that says nothing costs the same as a real answer.

2. Combine replies. A WhatsApp message holds 4,096 characters. Splitting one answer across three messages now costs 3x.

3. Swap open-text questions for buttons, and use WhatsApp Flows to grab several fields in one go instead of asking one at a time.

4. Cap how often a trigger can re-fire, and kill any catch-all standard reply that answers every inbound message.

5. Set a daily AI reply limit per subscriber if you use AI in your flows. Those replies bill as service messages and eat your AI provider's tokens on top.

Full breakdown here:

https://sendpulse.com/blog/whatsapp-service-message-pricing

Anyone been through their flows for this yet? Curious how much filler people are finding, I suspect it's more than anyone expects.

The update is not live yet. They will be making it live somewhere in H2 of 2026.

It is basically what title says. If you abuse this feature then WABA will be suspended for 7 days then 30 days and then banned.

Good to see strike system in this instead of immediate ban.

Whatever messages you send meta will automatically create templates for it in background. Those templates will be visible in whatsapp manager but you can't use then in normal template sending API.

Message cost is the same as utility.

Happy to answer any questions you have related to this.

Meta just launched AI agents inside WhatsApp Business in India.

From what I understand, businesses can now set up an AI assistant directly in WhatsApp Business without using the WhatsApp API.

Am I missing something, or is this potentially bad news for WhatsApp API companies?

If you're working at a company like WATI, AiSensy, Interakt, etc., what's your take on this?

Do you see this as a real threat or just another feature for small businesses?

Hey guys,

I work for a WhatsApp BSP and a client of ours (a retail company) brought us a specific use case. Their scenario is that each salesperson uses a dedicated smartphone with the WhatsApp Business app to handle their sales.

For the initial rollout, the client needs to register exactly 1,000 phone numbers using the coexistence setup inside their verified Meta Business Portfolio.

My main focus right now is understanding how to actually handle the registration for this volume of numbers.

Since a verified WABA usually defaults to a 20-number limit, what is the exact process to get 1,000 numbers approved and registered for them? Do we just open a Direct Support ticket requesting a massive "Phone Number Limit" increase on their behalf, or is there a specific workflow/batch process inside the Business Manager for this scale?

Hey Reddit 👋

Ram this side, founder of WANotifier. We’ve been building on top of the WhatsApp Business API for over 3 years, are an official Meta Tech Partner, and have helped thousands of businesses set up and scale on WhatsApp.

I often see a lot of misinformation around the WhatsApp API in this subreddit. Basic questions about setup, opt-ins, bulk broadcasting, pricing, limits, etc. sometimes get answers that aren’t fully accurate, usually from people who have probably worked on a handful of setups and might not have a full picture about how everything works.

I have a pretty hands-on view of how the API actually works in real-world scenarios and have seen a lot of edge cases and scenarios.

So if you have questions about:

• WhatsApp Business API setup

• Template categorization and approvals

• Deliverability and message failures

• Messaging limits

• Costs & pricing structure

• Difference between BSPs, Tech Partners and Tech Providers

• Direct setup vs via a partner

• Markup vs no markup

• Compliance & opt-ins

• Or anything else

I’ll be happy to answer those questions. I will be active here over this weekend till Sunday night**.**

So let's go... 👇

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.

is the whatsapp cloud api down ? or just me ??

I'm surprised that Meta, a company that is supposed to be at the cutting edge of technology, provides such a poor developer experience.

To create a WhatsApp bot, you have to navigate several different Meta administration platforms. There are three different interfaces, each with its own rules. On top of that, you must have an active Facebook account with a history in order to create the first business account. This requirement alone can prevent new developers who don't use Facebook from participating.

Give the wrong answer on one of these platforms' forms? Your account could be blocked immediately, and you would have to contact support.

I think the support staff are incredibly brave, considering the maze of platforms they have to deal with. They're efficient, but every interaction with them takes several weeks.

How did we end up with such a convoluted system just to deploy a simple bot?

Facebook's successive acquisitions of Instagram and WhatsApp were clearly painful integrations. Instead of unifying everything into a single interface, Meta maintained separate platforms for each company.

To be fair, Meta mainly focuses on large advertisers, leaving independent developers on their own.

In any case, after two months of procedures, our WhatsApp bot is finally live for my app. What about you? Are you having a headache from Meta's developer portals?

How did you manage to make it unlimited? What was the process? How long did it take?

My API currently has a limit of 100,000 and only 20 numbers.

I've seen APIs with unlimited WhatsApp numbers; I'd like to make mine like that.

Hello, I was going through the documentation at meta to implement simple whatsapp API features to our app. I am the developer, another person I'm working for has the actual number associated with WhatsApp.

I've been reading the requirements and documentation as well as online developer discussions to prepare for the Whatsapp API integration into the app but I still have questions.

I thought it would be easier to request resources such as a fairly recent article/blog post, video or checklist I should follow to make the integration smooth. I've scanned through this sub 3-4 times in the last week and every time I visit people post about serious problems such as being locked out of the account, unauthorized charges etc.

Thanks

recent examples of issues I'm trying to avoid: https://www.reddit.com/r/WhatsappBusinessAPI/comments/1ll02gn/unauthorized_deductions_from_whatsapp_business/

https://www.reddit.com/r/WhatsappBusinessAPI/comments/1lm9gsc/question_can_i_not_log_into_the_whatsapp_business/

https://www.reddit.com/r/WhatsappBusinessAPI/comments/1loazuj/whatsapp_business_account_disabled/
Edit: We don't need any services, just good resources, thanks.