What changed in WhatsApp business message pricing on 1 October 2026?
WhatsApp business message pricing changed on 1 October 2026: you now pay for service replies past 1,000 a month per number, and for utility templates in an open window.
| Date | What | Before: what you paid | After: what you pay |
|---|---|---|---|
| 1 Oct 2026 | Service replies you send | Free since 1 Nov 2024 | 1,000 free per number per month, then billed |
| 1 Oct 2026 | Utility templates you send in an open window | Free | Billed |
| 1 Jul 2026 | Meta Business Agent | Not a category | Billed by tokens |
| 1 Jul 2026 | Singapore | Inside "Rest of Asia Pacific" | Own row; utility and authentication rates higher |
Meta's pricing update page, read on 26 October 2026, says Meta "resumed charging, on a per-message basis, for messages that were previously free". "Each business phone number has one free tier of 1,000 delivered service messages per month." Unused messages do not roll over, and utility templates get no free tier. Your paid social team now carries a bigger message budget line than in September.
Our WhatsApp insurance playbook covers use cases and consent; here we cover your unit economics only. Meta schedules pricing changes on 1 January, 1 April, 1 July and 1 October; rate-card updates come with at least a month's notice. Diarise the next three for your team.
How the 24-hour window and the 7-day free entry point window work together
Two clocks decide what your lead costs: a 24-hour customer service window that opens when the person messages you, and a free entry point window of up to 7 days.
| Message | You pay inside the free window | You pay outside it |
|---|---|---|
| Service reply | Free | Free to 1,000 per number per month, then billed |
| Utility template | Free | Billed per delivered message |
| Marketing template | Free | Billed per delivered message |
| Authentication template | Free | Billed per delivered message |
| Meta Business Agent | Billed by tokens | Billed by tokens |
The 24-hour window is the permission clock. When a user messages you, "a 24-hour timer called a customer service window starts" (Meta's pricing page), and each new user message resets it. Inside the 24-hour customer service window you can send non-template messages as well as templates; outside it, templates only.
The free entry point window is the money clock. You open it when a person messages you "via an ad that clicks to WhatsApp (CTWA) using a device running our Android or iOS app" and you reply inside the customer service window. It "may remain open for up to 7 days" from your reply. "Meta continues to charge for Meta Business Agent messages in the FEP window."
The window belongs to the business and the person: Meta tracks it "for the business and WhatsApp user pair, not for an individual Messaging account". If your lead uses desktop or web WhatsApp, or finds you through search, you never open one.
Will your next WhatsApp message be billed?
Four facts decide it: where your lead came from, how fast you replied, how long ago, and what you send. The checker is an illustrative heuristic, not Meta's billing engine.
Your reply came within 24 hours and fewer than 7 days have passed, so your free window is open. Meta does not charge for marketing, utility, authentication or service messages inside it.
What the change does to cost per bound policy
The bill lands on your slowest funnel stage: the days between quote request and bound policy, when your agents answer in free-form messages.
| Flow design | Messages you send per lead | Your leads inside the 7-day window | Index per policy |
|---|---|---|---|
| A. Late first reply, or follow-ups after day 7 (40% is a blend) | 6 service, 2 utility, 1 marketing | 40% | 170 |
| B. Reply within 24 hours | 6 service, 2 utility, 1 marketing | 80% | 50 |
| C. As B, capped script, no cold marketing | 4 service, 1 utility, 0 marketing | 80% | 14 |
Your cost per lead will not show this. Meta says each Messaging account keeps its own billing relationship and payment method, so check whether anyone on your team joins message cost to policies bound. Meta's 21 October 2026 results put average price per ad across its apps up 14% year on year; that is not a click-to-WhatsApp figure, so you should treat it as pressure. Our cost per bound policy post explains why you should put messaging cost inside that unit.
Design A is a desk where insurance leads wait for an agent and renewals go out as marketing templates. Design C leaves your ad, audience and bid alone and changes your reply time and script; the index falls from 170 to 14 on these placeholder inputs. We expect the direction to hold wherever marketing costs more than service, but the size will not. The index is not a price. Swap 1, 2 and 5 for your recipients' rates from Meta's rate card (a separate download) and see what your own gap is.
Leapbuzz builds a cost-per-bound-policy model from your own message counts: ask for the model.
A cost-per-bound-policy worksheet for your own flow
Load a design, then change the counts to your own. This is an illustrative heuristic, not Meta's billing engine.
Billable messages: 6,200 service, 2,400 utility, 1,200 marketing. Cost index 17,000 over 100 bound policies, or 170 per policy.
Rules: messages inside the 7-day window are free; service messages outside it are free up to 1,000 per number per month; utility and marketing templates outside it cost your rate index. Meta's page does not say whether free in-window service messages count toward your 1,000, so we assume they do not. Authentication and Meta Business Agent messages are left out.
Billable service = leads x service messages x (1 minus window share), less 1,000 per number, floored at zero. Utility and marketing follow the same pattern without the free tier. Index per policy = billable counts x rate indices, divided by leads x bind rate.
Four flow-design fixes that beat switching channel
Fix your reply queue and script before you touch the channel. The new WhatsApp business message pricing charges you for slow replies and cold templates, and you control both.
- Reply inside 24 hours, every time. No reply, no free window. Set your team a first-response target on the ad lead queue. A templated acknowledgement counts as the reply, so an off-hours auto-reply opens the window. Meta lists marketing, utility, authentication and service messages as the opening reply, not Business Agent messages, so confirm before you rely on an agent auto-reply.
- Finish qualification inside 7 days. Send the quote, documents and bind link inside the window your reply opened, compliant with your consent record. A day-9 follow-up is a billed template; on day 6 it is free.
- Keep acquisition and service on one phone number. Every Messaging account on that number shares the window. Splitting numbers fragments your customer record, and Meta's page does not tell you how a window carries across numbers.
- Decide in writing who may use Meta Business Agent. Count tokens per resolved conversation before an agent answers your ad leads.
Volume tiers will not rescue you: Meta says "Volume tiers only apply to utility and authentication messages." Service and marketing volume earns nothing.
Renewal reminders sent as marketing templates are billed at the marketing rate on every send and never touch the free tier. Aim for utility-template approval where Meta's category rules allow it (our renewal outreach post covers the sequence). Category is Meta's call, so build the fallback cost into your forecast.
Do this today
Pull October's message volume by category and phone number from each Messaging account's pricing analytics, and set it beside October's bound policies. That join shows what the new pricing did to your cost per bound policy.
| Check | You pass if | If you fail |
|---|---|---|
| A payment method on every Messaging account | You see one on each account | Add one; delivery stops after the free tier |
| Billing currency on each account | It matches your finance currency | You choose it at account creation; changing it means migrating through Meta's Currency Migration API |
| Your first-response time on ad leads, last 30 days | Over 24 hours for under a tenth of your leads | Design A is your flow, and you fix it operationally |
Then run the worksheet with your counts. If your index per bound policy sits above the Design B figure, fix the reply queue before you touch the bid. Leapbuzz builds that cost-per-bound-policy reporting for insurers in Singapore and Malaysia. Re-check Meta's pricing page on 1 January 2027, the next date a rate can change.
