WhatsApp service vs utility pricing change: 1 October 2026

Meta has announced that, starting 1 October 2026, two categories of WhatsApp Business Platform messaging that have been free will start carrying a charge: service messages — the free-form replies a business sends inside the open customer service window, described in detail in our guide to the 24-hour window — and utility template messages sent inside that same window. Utility templates sent outside the window are already billed under the per-message model that took effect on 1 July 2025, covered in our guide to WhatsApp pricing and message categories; what changes on 1 October is that the free ride these two message types have had until now ends.

This is a dated policy announcement, not a rumour or a leak. It is worth treating it exactly as what it is: a confirmed effective date with an unconfirmed price.

The rates for service messages and in-window utility templates have not been published. Meta has said they will be published by 1 September 2026 — one month before the change takes effect. Until that rate card appears, any number attached to this change is a guess, and a guess dressed up as a fact is worse than admitting the number is unknown.

This matters because the temptation, especially in a sales or marketing conversation, is to fill the gap with a plausible-sounding figure so the sentence sounds complete. We are not going to do that here. If a rate card, a blog post, or a partner deck hands you a specific rupee figure for this change before 1 September 2026, treat it as an estimate at best and ask where it came from.

It is also worth being explicit about what is confirmed versus assumed. Confirmed: the effective date, and that these two specific message types move from free to billed. Assumed by absence of evidence otherwise, and therefore not something to repeat as fact: the actual rate, whether it will vary by country the way template pricing already does, and whether it will differ between the two message types or treat them the same. Every one of those is a reasonable question to ask Meta directly or watch for in the rate card — none of them has a public answer yet.

Meta's own disclosed practice, described in our pricing and categories guide, is to give advance notice scaled to how disruptive a change is: as little as a month for a rate card update, longer for a new pricing tier, and the longest runway for a change to the pricing model itself. Moving service messages and in-window utility templates from free to paid is closer to a model change than a rate tweak — it changes which message types are billable at all, not just what an existing billable message costs.

A roughly six-week gap between the rate card landing (1 September) and the change taking effect (1 October) gives a business exactly one billing cycle to see the actual numbers before they apply. That is a narrow window for adjusting a messaging budget, which is the practical reason to start planning for this now rather than waiting for the rate card to appear.

Do not publish an estimated per-message cost for service messages or in-window utility templates anywhere a customer or a prospect might read it as fact. Do not restructure a messaging workflow around a guessed number, since a workflow built to dodge a rate that turns out different from the guess is wasted work in either direction. Do not assume the new charge will mirror the existing per-message rate for utility templates sent outside the window — a service message and an outside-window utility template are functionally different sends today, and there is no public basis for assuming they will be priced the same once both are billable.

Also resist the urge to pre-emptively cut off free-form replies inside the window before 1 October arrives. The window's core behaviour — described in our 24-hour window guide — is not changing on this date; only its billing status is. A business that starts refusing to reply for free inside a window that is, as of today, still free is giving up a real customer-service capability against a policy that has not taken effect yet.

The one thing worth doing now is making sure you know, for your own number, roughly how many service messages and in-window utility template messages you actually send in a typical month. That is a real, checkable figure available today, and it is the input the eventual rate card will need multiplied against it.

Two things are worth confirming before 1 October regardless of what the rate turns out to be. First, that whatever platform sends your WhatsApp messages actually distinguishes a service message and an in-window utility template from a free-form session reply the way Meta's billing will, since a platform that treats all three as one undifferentiated bucket cannot tell you which of your sends are about to start costing something. Second, that your team has a habit of checking Meta's published rate card directly once it lands, rather than waiting for the number to arrive secondhand through a partner or a vendor's summary — the same discipline our pricing and categories guide recommends for the rate card in general.

A platform that already separates messages by category and window status, the way ours does for its own billing-guard logic, does not need to change its plumbing when the rate card lands — updating a number is a formula change, not a redesign. A platform that has never made that distinction has more work ahead of it than a pricing update; it has a data-modelling problem to fix first.

This article states what is confirmed as of its publish date: the effective date, the two message types affected, and the fact that the rate is not public yet. It does not state a number, because there is not yet a real one to state. Once Meta's rate card is published, expect the actual figures to be checkable directly against Meta's own documentation rather than against a summary written before the number existed.

Until then, the responsible position for any business budgeting WhatsApp messaging is the same one worth repeating: the effective date is real, the affected message types are named, and the rate is not yet known. Anyone telling you a specific number before 1 September 2026 is telling you their guess, not Meta's rate card.