For the last year, the rule that mattered was simple: once a customer messaged you, everything you replied for the next 24 hours was free.
That ends on October 1, 2026.
From that date, a reply you send inside the open 24-hour window is a service message, and it is billed per delivered message. So is a utility template sent inside that same window, which until now was free.
This post is the whole pricing model, before and after, what is left that is still free, and who actually takes the money, because there is a real answer to that one and it is not Zavu.
What changes on October 1
Meta announced this on July 1, 2026, which fits its own notice rules: a pricing model add-on requires three months' warning. Three things move.
Service messages become billable. A non-template reply sent by a human agent or by your AI assistant, inside an open 24-hour customer service window, is now charged per delivered message. Support replies, follow-ups, a text confirming something: all billable.
Utility templates inside an open window become billable. This is the one that catches people, because "utility templates are free while the window is open" was the single best cost lever in the old model. It is gone. A utility template now costs whether the window is open or closed.
Rates move for specific markets. Separately, Meta is pulling more countries out of their regional "Rest of" bucket onto their own rate cards: Bangladesh, Iraq, Nepal and Sri Lanka get lower utility and authentication rates, while Kazakhstan, Kuwait, Morocco, Oman and Ukraine get higher ones, all with a new authentication-international rate. Meta says these are "at least" the markets moving.
Two details that decide how much this costs you.
Service messages are priced at the market's utility and authentication rate, so the number depends entirely on where your customers are.
Service messages get no volume tiers. Utility and authentication templates unlock lower rates as monthly volume rises. Service messages do not. A hundred replies and a hundred thousand replies are billed at the same rate per message. If you run high-touch support, that is the line to model first.
The exact numbers are not published yet. Meta commits to publishing October rates by September 1, 2026. Anyone quoting you a precise October figure today is guessing.
The model, before and after
| What you send | Until Sept 30 | From Oct 1 |
|---|---|---|
| A message the customer sends you | Free | Free |
| Your non-template reply, window open | Free | Charged |
| Utility template, window open | Free | Charged |
| Utility template, window closed | Charged | Charged |
| Authentication template | Charged | Charged |
| Marketing template | Charged | Charged |
| Anything inside a free entry point window | Free for 72h | Free for 72h |
The short version of the new world: everything you send costs money, except inside the 72-hour free entry point window. What customers send you is still free.
What the 24-hour window still does
It is easy to read the change as "the window is dead". It is not, it just stopped being a pricing lever and went back to being a permission lever.
The customer service window opens when the user messages you and runs 24 hours from their last message. While it is open, you can send free-form messages: plain text, images, buttons, whatever the conversation needs. When it closes, only approved templates get through.
So after October 1 the window still decides what you are allowed to send. It no longer decides whether you pay. That distinction matters when you design a flow: replying fast is still better product, it is just no longer free.
The free entry point, now the last free door
If someone reaches you through a Click to WhatsApp ad or a Facebook Page call-to-action button, from the Android or iOS app, and you reply within 24 hours, a free entry point window opens for 72 hours. Everything you send inside it is free delivery, any type, templates included.
This was a nice-to-have when replies were free anyway. From October 1 it is one of the only free paths left, which changes the maths on paid social: traffic sent to WhatsApp instead of a landing page now buys you 72 hours of free conversation on top of the click you already paid for.
One caveat: the 72-hour free window and the 24-hour service window are independent. When the service window closes at hour 24, you can only send templates, even though those templates are still free until hour 72.
Template categories, and the trap
A template is a message you registered with Meta and got approved ("type": "template"). Every template carries a category, and the category sets the rate:
- Utility — something happened to an account or an order. Shipping updates, appointment reminders, payment confirmations.
- Authentication — one-time passcodes and login verification.
- Marketing — everything else. Promotions, announcements, re-engagement, and anything Meta decides is promotional.
Here is the trap, and October makes it more expensive, not less. You are charged the rate for whatever category the template carries at the moment you use it. Not the category you meant. A notification that ships as Marketing because someone appended "and check out our new collection" is billed at marketing rates on every send, forever, until you fix the template.
Review the category on every approved template. With the free window gone, this is now the single biggest lever you have.
Do you need a marketing template to start a conversation?
No. This is the most common misreading of the model, and it is expensive.
Any approved template reaches someone outside the window. Marketing is not the "opener" category. It is the "promotional content" category. What decides the category is what you are saying, not whether a window happens to be open:
- An order shipped and the window is closed, so you send a utility template. Charged at the utility rate.
- A login code goes out as an authentication template, window or no window.
- A promotion goes out as marketing, because of what it says.
Meta's own charge example makes this explicit: at hour 30, with no open window, the business sends a utility template with a shipping update and is billed the utility rate. If marketing were required to reach someone again, that example could not exist.
What stops the obvious trick: you pick the category when you create the template, but Meta validates it against the content and can re-categorise it later. Utility has to be non-promotional and either specific to that user, like an order or an account, or genuinely essential. Mixed content, or content whose intent is unclear, lands in marketing.
This is worth money. Marketing rates run several times utility rates depending on the country, and marketing has no volume tiers while utility does. So the cheapest way to reach someone outside the window is a message that is genuinely transactional, written so it stays that way. One promotional sentence appended to an order update can move the whole template into marketing.
Volume tiers
For utility and authentication templates only, rates drop as monthly volume rises. Four things about how they work:
- Tiers are per market and per category. Brazil-utility accrues separately from Brazil-authentication and from Mexico-utility.
- Volume aggregates across your whole business portfolio, every WABA you own, not per number.
- Only charged messages count.
- Tiers reset monthly, at midnight in your WhatsApp Business account's timezone.
Marketing has no tiers. Service messages have no tiers. And when a market moves onto its own rate card in October, its tiers become market-specific too: messages to Ukraine stop accruing toward Rest of Central and Eastern Europe and start accruing toward Ukraine alone, which resets your position on that ladder.
You also get a webhook when you cross a tier: an account_update event with VOLUME_BASED_PRICING_TIER_UPDATE, carrying the category, the tier bounds, the month and the region.
When prices change
Meta may only change pricing on the first day of a quarter: January 1, April 1, July 1, October 1. It commits to minimum notice depending on how disruptive the change is:
| Change | Minimum notice |
|---|---|
| Rate card update, or a market moving to its own rate | 1 month |
| A pricing model add-on, like volume tiers or service message charges | 3 months |
| A pricing model change, like conversation to per-message | 6 months |
Four possible change dates a year, never a surprise mid-quarter. October 1 was announced on July 1, exactly the three months an add-on requires.
Rates are set by the recipient's country calling code, not by where your business is. A Mexican company messaging Brazilian customers pays Brazil rates.
Who charges you what
Now the part that matters for your accounting, and the reason this post exists.
Meta bills you directly. WhatsApp message charges go to the payment method on your WhatsApp Business Account, in Meta Business Suite. Your account, your card, your invoice, from Meta.
Zavu does not touch that. We do not resell WhatsApp messages, we do not mark up Meta's rates, and we will not bill you for service messages when they start costing money in October. There is no line item from us for it, because the money never passes through us.
That is not a policy statement, it is how the product is built. A WhatsApp broadcast in Zavu reserves nothing from your balance and runs no balance check, precisely because the delivery is not ours to charge for. We show you the estimated cost so your Meta invoice does not surprise you, and then we get out of the way.
What Zavu does charge for:
| Zavu charges | Meta charges |
|---|---|
| Your plan, which includes a message allowance | Every delivered message, by category and country |
| Overage past that allowance, at Zavu's own per-message rate | Nothing else |
| WhatsApp connections beyond the ones your plan includes | |
| Other channels you use: SMS, voice, email |
Two bills, two relationships, no markup in between. When Meta's rates move on October 1, your Zavu invoice does not.
How to spend less, after October 1
The old advice was "answer inside the window, it is free". That advice is dead. Here is what replaces it.
Fix your template categories. Still the largest single line of waste, and free to fix. A utility notification miscategorised as marketing can cost several times more per send.
Send fewer, better messages. When every reply is billable, a three-message answer costs three times a one-message answer. This is the first year where "the agent is too chatty" is a line on an invoice rather than a style note. Prompt for brevity and mean it.
Consolidate. Two utility templates that could have been one now cost twice as much. Batch the shipping update and the delivery window into a single message where the customer experience allows it.
Route paid traffic through Click to WhatsApp. 72 free hours per conversation, on traffic you are already paying for. This is now one of the few free paths left.
Deflect what does not need a reply. A status page, a tracking link inside the first message, or a well-placed FAQ removes conversations that used to be free and are about to be billable.
Model service messages separately. They have no volume tiers, so they do not get cheaper with scale. If support is high-touch, that cost grows linearly with your customer base, which is not how the rest of your messaging bill behaves.
How to audit what you were charged
Every status webhook carries a pricing object. Read it and you know exactly why a message cost what it cost.
json{ "billable": true, "pricing_model": "PMP", "type": "regular", "category": "marketing" }
billable is the answer. category tells you which rate was applied, and if that says marketing on something you consider a utility notification, you just found the bug. Historically type came back as free_customer_service when the window covered a message, which is exactly the value you should expect to see disappear from your traffic after October 1.
For per-message breakdowns and tier progress, Meta exposes a pricing_analytics field on template analytics. Tier information is not in the webhooks.
The other dates that matter
August 1, 2026, Meta Business Agent. Messages handled by Meta's own agent product are billed on token usage, around $2 per million tokens, which works out to roughly four or five cents a message. Note that this is charged even inside the free entry point window: free delivery does not mean the whole response is free.
Brazil, BRL billing. Since July 1, 2026, businesses whose Sold-To country is Brazil create new WABAs in Brazilian reais, invoiced by Meta's local entity. Existing accounts must migrate to BRL by June 30, 2027, and after that date Meta stops delivering messages from non-BRL accounts for those businesses.
India, INR billing. The same, one year earlier: localization launched January 1, 2026 and the migration deadline is December 31, 2026.
Both use Meta's WABA currency migration APIs, available since June 1, 2026. If you operate in Brazil or India, those two dates belong in a calendar, not in a blog post you read once.
The short version
Until September 30, you pay to start conversations. From October 1, you pay to have them.
What stays free: messages customers send you, and the 72-hour window that opens when someone reaches you from a Click to WhatsApp ad. Everything else you send is billable, and service messages do not get cheaper with volume.
Get your categories right, say less, and put September 1 in your calendar for the real numbers.
And whatever those numbers turn out to be, the bill comes from Meta. Zavu charges for the platform, not for the delivery.