- Community
- Question
Hi Meta Team,
I run a WhatsApp automation/chatbot platform serving 300+ businesses of various sizes in multiple countries. I want to raise a genuine concern about the Oct 1, 2026 change that makes service messages (chatbot/human replies inside the 24-hour customer service window) chargeable per message.
Why the free 24-hour window matters so much: This window was one of the few genuinely fair, win-win parts of the Cloud API pricing model.
Businesses already pay for:
- Marketing template messages
- Utility template messages
- Authentication template messages
- WhatsApp BSP/platform provider charges
- Chatbot/automation development & maintenance cost
The free 24-hour reply window was the balance to all that — it let businesses actually have a conversation with a customer once they'd already paid to start it. It didn't cost Meta a business goodwill hit, and it didn't cost businesses extra to simply respond to their own customer. Removing it turns every single reply — "Hi," "thanks," "here are the details," "sure, let me check" — into a billable event, stacked on top of everything above.
This isn't happening in isolation — Cloud API already has real operational pain: On top of this pricing change, businesses running Cloud API already deal with:
- Accounts getting restricted during onboarding
- Business Manager getting stuck in verification for 15+ days
- Daily messaging limits not increasing even for genuine, compliant usage
- Display names getting flagged as "violating policy" for normal business names
- Templates getting auto-recategorized even when they're clearly utility, not marketing
- Numbers getting banned for policy violation even on small marketing campaigns sent to a business's own opted-in client data
Because of these issues, we've already stopped actively promoting Cloud API for Marketing use-cases for the last 10+ months. Adding per-message charges on top of an already-free, already-fair conversation window will likely push the same hesitation into support/service use-cases too.
The unintended consequence:
The free 24-hour service window was one of the biggest reasons businesses chose WhatsApp Cloud API over other channels — it made automation and real-time support genuinely affordable at scale. Removing it will push:
- Small/mid businesses to cut chatbot usage or reduce reply quality (shorter, fewer, less helpful responses) to save cost
- Some businesses to explore alternative channels (SMS, in-app chat, other messaging platforms) where conversational replies remain free
- Developers/BSPs like us to face client churn or resistance to onboarding new automation use-cases
Respectfully — this risks shrinking the very use-case (proactive, automated customer engagement) that made Cloud API attractive in the first place. It may increase short-term revenue per message but reduce total message volume and platform stickiness longer-term. Where this leads: If the free reply window disappears on top of these existing friction points, we expect:
- Businesses scaling back chatbot/automation investment
- Slower Cloud API adoption from new businesses evaluating WhatsApp vs. other channels
- Overall decline in WhatsApp Business usage over time — not because businesses don't want to use WhatsApp, but because the cost + operational friction combined stop making sense
Ask: Please keep the 24-hour service window free, as it stands today. It's the one part of this pricing structure that doesn't need fixing. If monetization is the goal, we'd rather see that addressed through template pricing or tiered plans — not by charging for a business simply replying to its own customer within a conversation it already paid to open.
Thanks for reading.
I'm trying to understand the reasoning behind this pricing model.
How is it practical for businesses to be charged even when they are simply replying to customers? Customer support often involves thousands of replies every day, and charging for every service message could significantly increase operating costs.
If businesses have to pay for marketing templates, service replies, utility messages, and potentially AI usage as well, the total cost becomes very high. At that point, it's difficult to see the incentive for businesses to continue using the WhatsApp Cloud API.
Another concern is that WhatsApp marketing message pricing is already substantially higher than SMS in many markets. In some cases, SMS can cost around five times less while still reaching customers effectively.
Could you explain the business rationale behind these changes and how Meta expects businesses with high customer support volumes to absorb these additional costs?
Fully support this. As a WhatsApp Business solution provider, we've seen how the free 24-hour service window enables businesses to provide fast, meaningful customer support. Charging for every reply will discourage automation, reduce customer experience, and slow adoption. Hope Meta reconsiders this decision.
Agree 100%. The free service window has always been a fair balance in the pricing model. Businesses already invest in templates, chatbot development, and BSP costs. Adding charges for every support reply will especially impact SMEs. Please keep the 24-hour customer service window free.
This is a genuine concern. Many small and medium businesses rely on WhatsApp for customer support because it's affordable and efficient. Charging for every message within the service window will increase costs without adding value. I hope Meta listens to the community.
Strongly support this request. Please preserve the free 24-hour service conversation window. It benefits businesses, customers, developers, and ultimately strengthens the WhatsApp ecosystem.
We from CommuniQate also vouch this. We are based in The Netherlands. It's already hard to convince customers to pay 13.9 euro cent for marketing messages and 4.1 cent for utility messages while the business app is free.
Until now the advantages were outweighing costs, but when you also charge 4 cents for service messages we cannot defend that anymore with our customers, many of them will stop using WhatsApp Cloud API altogether.
This is a really big impact change, i hope you guys will take your time to reconsider if this is really a good idea.
We all are so passionate about this because we want to help make the Cloud API succeed, in The Netherlands WhatsApp Cloud API was just starting to get traction and popular, but this ruins it honestly.
Glassix has over 1K customers and nearly 3K WhatsApp numbers. I told the team to remove the dust from the RCS and Apple Business Messaging channels on our platform, as enterprises are starting to look for alternatives after this announcement. One of my customers told me last night, "Meta acts like a drug dealer. Giving you free shots until he gets you."
As someone who has spent years building solutions on the WhatsApp Business Platform, this decision is difficult to understand.
Meta invested years in building a strong BSP and Tech Partner ecosystem. Thousands of partners have invested heavily in products, infrastructure, onboarding, support, and customer success to help businesses adopt WhatsApp at scale.
Now, if every service message is billable, businesses will naturally start asking:
"Why should we pay a BSP when we can build directly with Meta?"
This doesn't just increase costs for businesses—it reduces the value proposition of the entire partner ecosystem that Meta itself encouraged over the years.
Partners don't just provide API access. We provide onboarding, automation, CRM, AI, integrations, analytics, compliance, and ongoing support. But if the cost of simply replying to customers keeps increasing, convincing new businesses to adopt the platform becomes significantly harder.
I hope Meta reconsiders this decision or introduces a pricing model that protects customer support use cases while keeping the partner ecosystem sustainable. A healthy ecosystem benefits everyone—Meta, partners, businesses, and most importantly, customers.
Hi META we are your TECH partner provide services to 150+ clients in Pakistan. The Margins are already quite low. Just this year people started taking interest in the Cloud API and now with this per service message pricing. 99% of my client will churn. It will hurt you and ours revenue too. Please rethink this decision.
We express our concerns regarding the WhatsApp Cloud API pricing changes planned for October 1, 2026, specifically the introduction of message-based charges for service conversations within the existing 24-hour customer service window.
The proposed pricing model raises significant questions, particularly around charging businesses for service messages exchanged while responding to customer-initiated conversations within the 24-hour support window. This period was designed to facilitate seamless customer engagement, and support interactions often involve numerous exchanges such as confirmations, clarifications, troubleshooting, and follow-up responses. Applying per-message charges to these conversations could substantially increase operating costs for organizations handling high volumes of customer inquiries
The 24-hour customer service window has long been one of the defining strengths of the WhatsApp Business platform, enabling businesses to provide timely, efficient, and responsive customer support. Preserving this capability without introducing additional per-message costs would help maintain the platform's value for businesses while continuing to encourage high-quality customer engagement.
Considering the potential impact across businesses, public institutions, and high-volume customer support environments, we respectfully request that Meta reconsider the proposed pricing approach. If changes to the commercial model are necessary, we encourage the introduction of a fair usage allowance or an exemption for service messages exchanged within the 24-hour customer service window. Alternatively, pricing adjustments could remain focused on template-based messaging rather than applying charges to conversational replies that occur during active customer-initiated interactions.
We've got 7k customers that use an ERP on a daily basis. We've been working on automating the customer service using Meta Business API. We were just about to launch our product when this sad news came to public. Please reconsider the amount as this is going to ruin our business. Already considering switching to Telegram, but the preferred tool by customers is Whatsapp. So sad to see this happening!
Adding my support to this thread. As an independent developer building custom integrations for e-commerce platforms, I see firsthand how crucial the free 24-hour service window is for merchants.
My clients rely on automated integrations to provide expected, real-time updates—like order confirmations, shipping statuses, and basic support replies. Under the current model, the 24-hour window allows them to provide excellent customer service without being penalized for being responsive.
If every service message becomes a billable event, the math simply stops working for small and mid-sized e-commerce businesses. Instead of encouraging the adoption of the WhatsApp Cloud API, this pricing change will force merchants to scale back their automated support or move to cheaper, less integrated channels. This directly hurts the ecosystem of developers building solutions on top of Meta's platforms, as our clients will be forced to reconsider their tooling and churn.
Please reconsider this change and protect the 24-hour service window. It is essential for the survival of automated, high-quality customer service for SMBs.
I strongly urge Meta to reconsider charging businesses for service messages inside the 24-hour customer service window.
This window exists because the customer has already started the conversation. Businesses are not sending unsolicited marketing; they are simply replying to users who asked for support, pricing, order updates, or help.
Adding per-message fees to normal customer support will hurt SMBs, increase operational costs, and may discourage businesses from providing complete and helpful replies on WhatsApp.
Please keep the 24-hour customer service window free for service replies, or at least protect SMBs with a fair free allowance or capped pricing model.
Customer-initiated support should remain accessible, predictable, and affordable.
Adding a perspective from Pakistan, because the impact of this change is not evenly distributed across markets.
I run an e-commerce business here. In Pakistan, WhatsApp is not "a support channel" — it is effectively THE way commerce talks to customers. When a customer messages us, we reply: order status, delivery questions, cancellations, a simple thank-you. Under the current model those replies inside the 24-hour window are free, which was the fair part of the deal — the customer starts the conversation, and answering them costs nothing extra.
From October 1, every one of those service replies becomes a billable event. For a business like ours that means tens of thousands of replies a month — a bill of hundreds of US dollars, charged in USD while revenue is earned in local currency. That is a very different burden in an emerging market than it is in the EU or US.
Nobody objects to paying for marketing messages. But charging for support replies punishes exactly the businesses that answer their customers fastest, in the markets where WhatsApp holds a near-monopoly on customer communication. We already pay to bring customers to WhatsApp — often through Meta's own ads — and now we will pay a second time for every reply.
+1 to the OP's ask: keep customer-initiated service replies free. If monetization is the goal, address it through template pricing, tiered plans, or a meaningful free tier for SMBs with emerging-market rates — not by making "your order is on the way" a billable event.
Dear Meta Team,
As a technology provider serving transportation and logistics companies, we are extremely concerned about the decision to charge for service messages on WhatsApp.
Today, our customers exchange more than 2 million service messages every month through our platform. These are not marketing campaigns or promotional messages. They are operational conversations: delivery updates, tracking information, proof of delivery, customer support, shipment status, driver communication, and other essential interactions between transportation companies and their customers.
WhatsApp has become a critical communication channel for these businesses, especially in Brazil, where customers naturally expect companies to be available through WhatsApp.
Charging for every service message completely changes the economics of these operations. At our current volume, even a relatively small cost per message can create a significant monthly expense for both technology providers and their customers.
Over the years, companies like ours have invested heavily in building solutions around the WhatsApp Business Platform: integrations, automation, AI, customer service tools, infrastructure, compliance, support, and development.
We helped bring thousands of business interactions to WhatsApp because Meta encouraged the creation of this ecosystem.
Now, this pricing model risks making many of these automations financially unsustainable.
The biggest concern is that businesses may begin reducing their use of WhatsApp, limiting automated customer service, or actively searching for alternative communication channels simply because responding to their own customers has become too expensive.
We understand that Meta needs a sustainable business model, but service conversations should not be treated the same way as marketing communication.
We strongly encourage Meta to reconsider this decision or introduce a pricing model based on volume, monthly tiers, or significantly reduced rates for service messages.
With more than 2 million service messages per month already flowing through our platform, this is not a theoretical concern for us. It will have a direct and measurable impact on our customers and on the solutions we have spent years building around WhatsApp.
We want to continue investing in the WhatsApp ecosystem, but the ecosystem also needs to remain economically viable for the businesses and technology partners who helped build it.
I strongly support keeping the free 24-hour customer service window.
Charging businesses for every reply within an active customer conversation will significantly increase the cost of customer support, especially for small and medium-sized businesses.
This change may discourage businesses from using the official WhatsApp Business Platform and push them toward unofficial alternatives, which is not beneficial for the WhatsApp ecosystem.
The current pricing model has been fair and has encouraged businesses to adopt the official API. I respectfully ask Meta to reconsider this decision and keep the 24-hour customer service window free.
Thank you for
I completely agree. The free 24-hour service window was one of the biggest advantages of the WhatsApp Cloud API. It allowed businesses to provide fast, responsive customer support without worrying about being charged for every reply. Charging for all messages within the customer service window will especially impact small and medium-sized businesses. I hope Meta reconsiders this decision and finds a better balance between monetization and supporting businesses that rely on the platform.
Please reconsider this. It will destroy a lot of businesses depends on WhatsApp Api
For me if service window is gonna be billeable is not gonna be profitable anymore, might go back to phone or even thinking about giving curstomer support in telegram
Dear Meta team,
I'm the founder, CTO and managing Director of OrderLemon, based in Belgium. Our platform currently supports more than 500 shops and WhatsApp numbers across Belgium, the Netherlands, Austria, and Turkey, and our sales team is about to begin onboarding in the UK and France.
Every month, we handle over 5 million messages on behalf of small local businesses: bakeries, butchers, sandwich shops, pizzerias, restaurants, and independent traders. For most of them, margins are thin and every euro counts.
This is where the current model breaks down for them. These businesses cannot realistically pay for Instagram and Facebook ads to bring customers onto WhatsApp, and then pay again for each conversation once those customers arrive. The combined cost simply doesn't add up at their scale, and OrderLemon carries both their engagement volume and their millions of active users.
We've built something that, to our knowledge, hasn't existed in Europe before: full e-commerce over WhatsApp in a single solution, payment included. It's working, and it's growing fast. Our concern is that the current pricing direction risks undermining one of the most promising commerce channels emerging for European SMEs.
We'd welcome the chance to discuss a pricing structure that works for micro-businesses, and to share the data we're seeing on the ground. We think there's a strong shared interest here in keeping these merchants on WhatsApp.
Kind regards, Ruvenss Founder, OrderLemon
I am writing to formally submit a consolidated objection and concern regarding the upcoming WhatsApp Cloud API pricing changes scheduled for October 1, 2026, particularly the introduction of charges for service messages within the 24-hour customer service window.
We operate a WhatsApp automation and chatbot platform serving more than 300 businesses across multiple countries, including government-related platforms, public service systems, and large-scale commercial clients. WhatsApp is a core communication channel within these ecosystems, supporting customer service, operational workflows, and automated interactions at scale.
We are trying to understand the business rationale behind charging per message for service replies, especially within the 24-hour window where businesses are responding directly to customer-initiated conversations. Customer support environments typically involve thousands of daily interactions, including simple acknowledgments, clarifications, and follow-ups. Introducing per-message billing in this context would significantly increase operational costs and complexity.
In addition, businesses already bear multiple layers of costs, including marketing templates, utility and authentication messages, platform or BSP fees, and chatbot development and maintenance expenses. Adding per-message charges for basic service responses may create a cumulative cost structure that becomes difficult to sustain, particularly for high-volume support operations.
We also note that WhatsApp marketing messaging is already priced significantly higher than SMS in many markets, in some cases multiple times more expensive, despite SMS remaining an effective and lower-cost alternative. This raises concerns about competitiveness and long-term adoption of WhatsApp as a primary business communication channel.
Furthermore, we operate under long-term contractual agreements with clients, some extending up to five years, which include strict service level obligations and contractual penalty clauses. Any substantial increase in messaging costs may directly impact our ability to fulfill these obligations. This could potentially expose our organization and our clients to financial penalties, compensation claims, and legal disputes arising from unmet service expectations.
We are also concerned about the broader impact on government-related services and regulated institutions that rely on our platform. Any sudden increase in communication costs at the messaging level may disrupt service continuity and force organizations to reduce the quality or scope of customer support, which would have wider operational consequences.
Given the scale of impact across high-volume support environments, we respectfully request Meta to reconsider this change, or at minimum introduce a fair usage model or exemption for service replies within the 24-hour window. If monetization adjustments are required, we would suggest focusing on template-based pricing structures rather than charging for conversational replies initiated within an existing customer interaction.
We believe the 24-hour service window is a fundamental part of the WhatsApp Business API value proposition, enabling efficient, real-time customer engagement.
Businesses will find this very expensive and will surely look now for other channels like RCS /SMS/telegram. This was one of the major factor for a business to be convinced on using API. Meta should reconsider this
This is a surprising decision by META . In 24 hours window is so much expensive. Should be rethink about it.
Thanks
Really bad decision.
My platform is offering Meta services in Iraq and I do have more than 100 clients using WhatsApp api service. However, I highly believe this decision will negatively impact us. At the same time I believe there must be a consideration that other social media platforms are offering relative services with reasonable pricing.
Please reconsider this... It will kill a lot of businesses.
