Starting October 1, 2026, Meta stops giving WhatsApp businesses free service replies and free in-window utility messages. Every business phone number gets 1,000 free service messages a month; after that, each one bills at the local utility rate. If you run WhatsApp support at any real volume, your monthly bill changes this week, not next quarter.
What changes in WhatsApp service message pricing on October 1?#
Two things, both confirmed in Meta's WhatsApp Business Platform pricing documentation. Service messages — the free-text replies a business sends after a customer messages first — move from unlimited-free to a 1,000-message monthly allowance per phone number, billed at the market's utility rate from message 1,001.
Utility template messages sent inside the open 24-hour customer service window, free since July 2025, lose that exemption too. Meta business partner 360dialog confirms they now bill from the first message, with no allowance at all. Meta's own Meta Business Agent already started charging $2 per million tokens on August 1. Marketing and authentication templates outside the service window were already paid and don't change.
Here's the shape of it:
- Service messages: 1,000 free per phone number monthly, then per-message at the market utility rate
- Utility templates inside the 24-hour window: no free tier, billed from message one
- Meta Business Agent: billing per token since August 1
- Marketing and authentication templates: unchanged
Does this change anything if I barely use WhatsApp?#
If your number sends under 1,000 service replies a month, combined across support and sales, October 1 changes nothing for you. You're inside the free tier and can stop reading here.
It's a different story if you're running templated appointment reminders, order updates, or delivery confirmations inside that 24-hour window — the pattern most SMBs default to because it used to be free and reliable.
We build WhatsApp and voice automation for GCC, European, US, Canadian, and Indian SMB clients, and the accounts that'll feel this first are the ones with exactly that setup: templates firing inside an open conversation, every day, at volume. That lane goes from zero cost to the full rate with nothing to absorb it.
What's actually good about this, and what isn't#
The honest case for Meta here: this closes a loophole businesses have leaned on since July 2025, where a bot could dodge template charges entirely by keeping every reply inside the free-text service category. Categorizing correctly now costs something either way, which removes the incentive to game it.
The honest case against it: 1,000 free service messages a month is nothing for a business running WhatsApp as its main support channel. A mid-size D2C brand can burn that allowance in a few days. My read is this is less cost recovery and more Meta collecting on a lane it opened wide during the platform's 2024–2025 growth push — the new rate is the one utility templates already paid for a year, just applied somewhere it wasn't before.
How we're handling it#
We rebuilt the message-routing layer on every AiSensy- and n8n-based WhatsApp flow we run this month, splitting true service replies from utility-template sends at the workflow level instead of letting both fall through one webhook.
For a wealth-advisory client running appointment reminders as in-window utility templates, we moved that flow to scheduled service replies inside the same open conversation. Same message, cheaper category, and now inside the 1,000-message allowance instead of paying from send one.
We got the routing wrong on the first pass. A couple of flows were still tagged as service replies even though they were firing off a template's timer, which would have billed at the wrong rate. Fixing it took a rebuild of the categorization logic, not a relabel.
We're holding the two higher-volume retail migrations until the first October invoice lands — no point guessing at final per-market rates when real numbers show up in four weeks anyway. It's the same instinct behind routing conversations through a cheaper decision layer before they hit a paid model, just applied to message categories instead of model calls.
What I'd tell a client asking about this#
Pull your WhatsApp send volume from Meta Business Manager for August, split into service replies versus utility templates sent inside the window. Under 1,000 service replies a month means this doesn't touch you — skip it.
If you're sending in-window utility templates at volume, get an active payment method live in the Billing Hub before September 30; Meta isn't running a grace period. And if part of that volume could legally go out as a plain service reply instead of a template, that's the one architecture change worth making before the invoice, not after — the same shift we made on our own WhatsApp automation builds this quarter.
If you want a second opinion on your own numbers before October 1, send me what Meta Business Manager is showing for your account and I'll tell you straight whether this actually costs you anything. Takes ten minutes, no pitch attached. cal.com/webepex/growth-review
