WhatsApp Charges for Service Messages Starting Oct 1

As of October 1, 2026, Meta is charging again for service messages on WhatsApp Business Platform: the free-form replies a business sends inside the 24-hour customer service window, free since November 2024. The change is specific to Business Platform, the API-based product with a verified number that's typically set up through a provider like 360dialog, not the free WhatsApp Business App any small shop can download. If your team runs support or sales into Latin America over WhatsApp API, and that number also takes traffic from Click-to-WhatsApp ads, this changes two things at once: how much it costs to carry a long conversation, and why it pays to close it fast.

What gets billed, and what stays free, on the same number

The change doesn't touch the messages a business initiates (templates, which were already billed) or the user's message, which was never charged. What starts carrying a price is the free-form reply a business sends afterward, while the conversation is still open inside those 24 hours. The rate matches each market's utility and authentication rate, and Meta only added the pricing detail to its page on September 1, a month before the change takes effect.

There's a cushion: according to 360dialog, one of the official API providers, every business phone number gets 1,000 free service messages a month, and that quota resets with no rollover. For a low-traffic number, that can cover it and close the question. For a number carrying support at scale (multiple agents, a front-line bot, conversational onboarding), 1,000 messages run out fast, and that's where the change stops being theoretical. An account sending 5,000 service messages a month on a single number has 4,000 messages outside the free quota, and those 4,000 messages cost differently by country: about USD 104 in Argentina, USD 80 in Chile, USD 120 in Peru, USD 34 in Mexico, USD 27 in Brazil, and just USD 3 in Colombia, which sits well outside the rest of the table (USD 0.0008 per message, with neither source explaining the gap). The rate is set by the country of the number receiving the message, not by where the business operates: a brand serving customers in Argentina and Brazil from the same team pays almost four times more for each reply to the Argentine customer. None of those totals breaks a business on its own, but for a brand with customers in several countries, support cost per market becomes a line worth tracking separately.

There's also a harder line than the rate itself: accounts that had no payment method on file by September 30 don't move into a bill-later setup. They simply stop delivering service messages as of October 1. That's not a fine or a warning: it's the support conversation going dead on the other end with the customer never told why. If an account is in that situation, that's the first thing to fix, before any rate math.

The 72 hours after a click aren't just better conversion anymore, they're cheaper

The 72-hour window that opens when someone reaches WhatsApp from a Click-to-WhatsApp ad or a Page's "Send Message" button isn't changing: every service message inside that window stays free for delivery, no matter how many get exchanged. Until September 30, that window mostly worked as an intent argument: the user arrived warm from an ad, so it pays to respond fast before the moment cools off. Starting October 1, it also works as a cost argument, and that moves a decision that used to live purely in UX territory into campaign budget territory: whatever a team resolves inside those first 72 hours, no matter how long the back-and-forth runs, doesn't generate a service-message charge. The same conversation, if it stretches past the window or starts because a customer messaged the saved number directly (no ad, no Page button involved), starts counting against the free quota from the first message over the limit.

That hits different flow types differently. Confirming an order or answering a catalog question uses few messages and rarely gets close to the monthly quota. Fintech onboarding with conversational identity verification, a multi-step return negotiation, or any support process that needs real back-and-forth, is exactly the flow type that burns the most service messages per completed conversation, and the first one worth reviewing: not to force it into automation, but to see how much of that exchange could get resolved while the conversation is still inside its originating 72-hour window, instead of after.

One note for anyone using Meta Business Agent, Meta's conversational agent: its messages have been billed by token since August 1, 2026, at USD 2.00 per million tokens according to Meta's documentation (roughly 4 to 5 US cents per message), and that charge applies even inside the free Click-to-WhatsApp window.

Who this actually changes the math for

This matters most for ecommerce and retail brands handling post-sale volume over WhatsApp, for fintech and insurtech using WhatsApp for onboarding or conversational KYC, and for any brand already running Click-to-WhatsApp that until now measured that campaign only on cost per click or cost per conversation started. For those profiles, the per-market rate and the monthly quota stop being a billing footnote and enter the forecast the same way any other customer-service cost line does: it's not purely a flow-redesign exercise, it's new budget that didn't exist before, especially for high-volume operations that will blow through the free quota every month. For a smaller operation running low volume on a single number that hasn't hit 1,000 service messages a month yet, the change matters less right now, though it's worth keeping on the radar for the day that volume grows.

It's another chapter in a pattern this blog keeps tracking: platforms adding new conditions to something an advertiser used to control, or get for free. Before it was Google deciding what text gets added to a Shopping ad description; now it's Meta charging for a reply that had no cost until yesterday.

What's still unconfirmed

Neither source consulted publishes a report showing, ahead of time, how many service messages an account sent last month per number: running the math depends on estimating volume by hand or on whatever the messaging provider's panel shows. There's also no public explanation for why Colombia's rate sits so far below the rest of the region. Finally, Meta only published the full rate detail a month before the change takes effect, so pricing or terms could still shift in the weeks after launch.

This content was developed with AI assistance and reviewed by the Zenda team. Any bad ideas are entirely our own.