WhatsApp Service Message Pricing: What Changes on 1 October 2026

What is a WhatsApp service message, and how is it different from a template?

Meta draws this distinction in its own pricing documentation, in a single sentence worth reading exactly as written: "Any non-template message that is not powered by Meta Business Agent is a service message" (Meta — Upcoming pricing updates for Meta Business Agent, service and utility messages). A service message, Meta says, can be "powered by a person, like a customer service representative, or by a 3rd-party AI solution."

A template is the opposite in every respect that matters for billing. It is pre-approved content, sent whether or not a customer service window is open, and it is what a business uses to reach someone outside the 24-hour window Meta opens whenever a customer messages first. A service message only exists inside that window: it is the ordinary reply — the answer, the confirmation, the follow-up question — that a business sends back to someone who has already written in. The fuller breakdown of what Meta charges for outside that window, and what it never has, is at is the WhatsApp Business API free?

That single distinction, template versus non-template, is what has decided pricing on this platform since 1 July 2025, when Meta replaced conversation-based billing with a per-message model built around exactly this line. Everything else in this piece — what is free, what stops being free, how much stays free, and on what date — is that one distinction applied to two categories that were, until now, still on the free side of it.

• What is a WhatsApp service message, and how is it different from a template?
• Which messages are free, and which stopped being free?
• Where do the service rates live?
• Why does a payment method on file decide whether your messages arrive?
• How many free service messages does each number get every month?
• Are there volume discounts on service messages?
• What is a Meta Business Agent message, and why is it metered by tokens?
• How do you work out what October will cost before it happens?
• Who adds the payment method on a Tech Provider platform, you or the vendor?
• What should a business do before 1 October 2026?

Which messages are free, and which stopped being free?

This change has now happened. It took effect at midnight on 1 October 2026 in each Messaging account's own timezone, and Meta's pricing page was updated on 30 September 2026 to describe the new regime in the present tense. Everything below was re-checked against that page on 2 October 2026. If you are reading a page elsewhere that still says replies inside the window are free, check its date.

Two dates bracket what used to be free, and a third ended most of it. Meta's pricing page records that "Effective November 1, 2024 – Service conversations are now free for all businesses" — the moment ordinary replies inside the window stopped being billed under the old conversation model. Then, "Effective July 1, 2025, Meta charges on a per-message basis" for messages businesses deliver, replacing conversations with messages as the unit of billing (Meta — Pricing on the WhatsApp Business Platform).

The same page now states the third date in one line: "Effective October 1, 2026 – Meta will charge on a per-message basis for service messages." Meta's page dedicated to the change gives the two affected categories a sentence each, because they have been free since different points. Service messages: Meta "will charge on a per-message basis for all service messages, consistent with how Meta charges for template messages. These messages have not been charged since November 1, 2024." Utility templates sent as replies: Meta "will charge on a per-message basis for utility messages sent in response to users (within an open 24-hour customer service window). These messages have not been charged since July 1, 2025" (Meta — Upcoming pricing updates).

The two categories do not end the same way. Service messages keep a monthly free tier, covered below; in-window utility templates do not get one. Read the middle stage of the diagram as the one step with a deadline attached: a payment method on the WhatsApp Business Account before charging starts.

Two cells changed when the rules landed. In-window utility templates now sit under the ordinary utility volume tiers, because Meta's tier rule is that "only messages that are charged count toward the tiers" and these are now charged — an earlier version of this page recorded the answer as "not stated", which it was until the regime went live. And the free entry point window is up to 7 days, not the 72 hours this page and Meta's own documentation both carried for the previous two years; the string "72 hour" no longer appears on Meta's pricing page at all (checked 2 October 2026). Messages inside that window stay free regardless — with one exception that is new: Meta Business Agent replies are charged inside it.

Marketing and authentication templates sit outside all of this. They have been charged per delivered message since 1 July 2025, with no in-window exemption to lose — the categorisation rules that do affect them are covered at when a template gets recategorised from utility to marketing.

Re-checked against Meta's documentation on 2 October 2026.

Where do the service rates live?

The rates themselves. Meta's pricing documentation describes its own notice framework: "Meta may update pricing only on the 1st day of each quarter, thus up to 4 times per year: January 1, April 1, July 1, and/or October 1," with a minimum of one month's notice for a rate card update (Meta — Pricing on the WhatsApp Business Platform). Within that framework Meta committed that it would "announce and publish the rates that take effect October 1, 2026, including rates for service messages, by September 1, 2026."

It did, and the rate cards have since moved into place: Meta's pricing page now publishes rates "across all 5 categories x 47 markets", effective 1 October 2026.

One claim from the announcement no longer appears — but the rate card settles it anyway. Before the change, Meta's notice stated that "By market, rates for service messages will be the same as the rates for utility and authentication messages", which this page quoted on 19 September 2026. That sentence is not on Meta's live pricing page as of 2 October 2026; the page now only groups service with utility and authentication as "fixed, per published rates" while saying rates "vary by market–category".

So we read the card itself. Meta's USD workbook dated "effective October 1, 2026" carries a Service column alongside Marketing, Utility, Authentication and Authentication-International, and in all 47 markets the service rate is identical to the utility and authentication rate — India $0.0014, Brazil $0.0068, Germany $0.0550, Kuwait $0.0440, and so on down the sheet.

Treat that as a measurement with a date on it rather than a promise, because Meta deliberately stopped making the promise. Today you can price a service message at your market's utility rate and be exactly right; the day Meta separates them, nothing will announce it, and the only way to notice is to read the service column rather than copying the utility one. One difference already exists and is not about the rate: volume tiers apply "for utility and authentication messages only", so the utility rate steps down as you scale and the service rate never does.

The figures above are illustrations, not a rate card. They are there to establish one thing — that Meta's service column matches its utility column today — and four markets is enough to show that. We deliberately do not reproduce a full rate table on every article that mentions cost, on the reasoning that a number copied across a dozen pages is a number nobody re-checks against Meta's quarterly schedule. The dated, currency-specific figures live at the India pricing breakdown and in the cost calculator, which are re-read on their own cycle; Meta's own USD, INR and 14 other currency cards are linked from its pricing page and are the only authority.

Why does a payment method on file decide whether your messages arrive?

Every WhatsApp Business Account is set up with two things: a phone number, and — per Meta's account documentation — a payment method: "Once created, connect your phone number and set up a payment method" (Meta — WhatsApp Business Accounts). Until this change that requirement sat in the background, because templates were the only thing billed and most accounts added a card to send their first one.

Since 1 October 2026 it decides delivery, and Meta says so in writing — now in both of the places that used to disagree. The current pricing page carries each statement in its own section:

Read together they are consistent rather than contradictory: the free tier still goes out, and everything past it does not. The practical consequence is unchanged and now unavoidable — if that deadline passed without a payment method on your account, your replies are being cut off at 1,000 a month per number, and the fix is a card in Billing Hub rather than anything a messaging platform can do for you.

Two corrections to earlier versions of this page. On 4 September we reported that the 30 September deadline and the non-delivery consequence were not in Meta's developer documentation; they were added afterwards, and the table above replaces that. And Meta has dropped the word "shared" from the free tier, which this page previously quoted — the live wording is "one free tier of 1,000 delivered service messages per month" per business phone number.

How many free service messages does each number get every month?

One thousand a month, and it is live. Meta's pricing page states it twice, in the same words both times: "Each business phone number has one free tier of 1,000 delivered service messages per month. Meta charges as of the 1,001st service message per month, after the free tier has been used." The rules around it are short and specific:

• Per number, not per account. Two numbers on one Messaging account get 1,000 each.
• Delivered, not sent. Meta charges only on delivery, and the tier counts deliveries.
• No carry-over, and it resets on your own clock. "Unused service messages in the free tier do not roll over to the next month... This reset happens at 12am by Messaging account timezone."
• Eligible governments and non-profits are exempt. For those cohorts "service messages remain free beyond the monthly free tier", a policy Meta says runs "through December 31, 2027".

The allowance covers service messages only — utility templates sent inside the window get no equivalent tier, so every one of those is charged from the first.

A correction. An earlier version of this page quoted Meta on how the tier counts a group send: "A 1:1 delivery consumes one unit; a group send consumes one unit per delivered recipient." That sentence is not on Meta's live pricing page as of 2 October 2026, so it is no longer quoted here. Since the tier counts deliveries, a group send plausibly still consumes one unit per recipient — but that is now inference, and this page does not present inference as Meta's words. The same version reported that no monthly allowance existed in Meta's documentation; it did not on 4 September, and it does now.

You can tell which side of the tier a message fell on from the status webhook: inside the tier it stays "type": "free_customer_service" with "billable": false, and past it Meta switches the same category to "type": "regular" with "billable": true.

Reading what Meta actually charged you is the reliable check, because the status webhook tells you which side of the tier each message fell on.

Are there volume discounts on service messages?

No, and Meta states it outright: "Meta will not offer volume tiers for service messages. Meta continues to offer volume tiers for utility and authentication messages" (Meta — Upcoming pricing updates).

Read that beside the rate rule and the shape of the category is clear. A service message costs the same as a utility template to the same market, but where utility and authentication rates step down as monthly volume rises, the service rate does not bend. The first 1,000 each month on each number are free; every one after that is charged at the flat rate.

For a support-heavy business that lives inside the customer service window — a shop answering order questions, a clinic confirming appointments people asked for, the kind of setup a shared team inbox exists to run — that absence of a volume discount matters more than it would for a business sending mostly marketing templates, which were never discounted by volume in the first place.

What is a Meta Business Agent message, and why is it metered by tokens?

Meta draws the line in the same sentence that defines a service message: anything not powered by Meta Business Agent is a service message. A Meta Business Agent message is the exception — generated by Meta's own Business Agent Platform, which Meta's documentation describes launching on 1 July 2026, rather than by a person, a bot you configured, or a third-party AI model you brought yourself.

Meta charges for it differently in kind. Service messages are metered per message. Meta Business Agent messages are charged per token, since the category was introduced on 1 July 2026, at one global rate that does not vary by market. Meta is explicit that the cost of a single message is not fixed: "Simple responses consume fewer tokens and cost less; complex responses consume more tokens and cost more." It also states that "One message typically consumes 20,000–25,000 tokens" (Meta — Upcoming pricing updates). Two replies that look alike in an inbox can therefore cost different amounts, which a flat per-message price never would.

A non-template message is charged as one or the other, never both. We are not printing the token rate itself — it moves on Meta's schedule like every other figure. If your bots, flows or AI assistant call a model you configured yourself rather than Meta's agent platform, none of this token metering applies: that traffic is an ordinary service message, drawing on the free tier and then billed like a message a person typed.

How do you work out what October will cost before it happens?

Count, then subtract, then multiply. The rate is now published; the count is something only your own history can give you.

A message log that records every send, its direction and its status is the input this exercise needs. Filter a month of outbound messages by direction, separate ordinary replies from templates, and count the replies per sending number, because the free tier is per number. Anything above 1,000 on a number is the part being charged. In-window utility templates are counted separately and in full, since they get no tier.

After the change, the status webhook shows the split directly. Meta's pricing page lists the pricing object for each case: a service message inside the free tier keeps "type": "free_customer_service" with "billable": false, and one delivered after the tier is used arrives as:

"pricing": { "billable": true, "pricing_model": "PMP", "type": "regular", "category": "service" }

If you still have September's message log, count it: a month's reply volume per number from before the change is the baseline every later invoice gets compared against, and it is the only month you will ever have where the same traffic cost nothing. Failing that, count the current month and treat the first 1,000 per number as the part that stays free.

Who adds the payment method on a Tech Provider platform, you or the vendor?

You do, and the distinction is not a technicality — it is the reason a Tech Provider can describe this change plainly instead of quietly marking it up. WabaCRM is a Meta-verified Tech Provider, verified 30 July 2026, and that tier carries a specific restriction: a Tech Provider is not permitted to resell Meta's per-message fees at all, covered in full at BSP vs Tech Provider. There is no credit line a Tech Provider extends on a customer's behalf, in the way Meta describes a Solution Partner's credit line removing that step for their clients.

Practically, the payment method Meta bills for service messages sits on your own WhatsApp Business Account, inside your own Meta business portfolio — not inside WabaCRM's billing, and not something a platform screen can add or remove for you. WabaCRM's own bill covers software: the shared inbox, contacts, campaigns and the rest. Meta's bill for messages is a second, separate invoice that goes directly to whatever card is on file with Meta, at whatever rate Meta publishes for your market.

That split is why the checklist below starts in Meta's Billing Hub rather than in any vendor's dashboard: the platform cannot check this on your behalf, because it is not the platform's account to check.

What should a business do before 1 October 2026?

Four things, in this order:

1. Confirm there is a working payment method in Meta's Billing Hub, for the WhatsApp Business Account you actually send from — not inside your messaging software, for the reasons above. The deadline was 30 September 2026; if it passed without one, your replies are already being cut off at 1,000 a month per number.
2. Count last month's replies per sending number. Replies above 1,000 on a number are what is charged; in-window utility templates are charged from the first.
3. Read your market's service rate from the service column of Meta's own rate card, rather than budgeting from a figure on a vendor page with no date beside it. On the card effective 1 October 2026 it matches the utility and authentication rate for the same country — but read the column rather than assuming that, because Meta removed the sentence promising the two would stay equal.
4. Read what your own bots and automations send. A keyword bot's canned answer, a flow's text step, an AI assistant's drafted reply — none of these are templates, so under Meta's definition every one is a service message, and each draws on the same 1,000 as the replies your team types.

None of this changes what your software vendor charges you. It changes what Meta charges you, on an account only you control the billing for. The other dated Meta deadline this year, if your business sits inside Meta's India billing rules, is migrating a WABA to INR before 31 December 2026.

Re-checked against Meta's documentation on 2 October 2026.

Quotations on this page were read from Meta's own documentation on 19 September 2026 and re-checked against it on 2 October 2026, after the change took effect; where the two differ the page says so. Meta changes that documentation without notice; the linked pages are authoritative and this one is not.