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 — Pricing for non-template messages). A service message 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, 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 today, and which stop being free?
• What did Meta publish on 1 September 2026, and where do the 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 in the four weeks before the deadline?

Which messages are free today, and which stop being free?

Two dates bracket what is free today, and a third ends it. Meta's pricing documentation states 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" across the platform, replacing conversations with messages as the unit of billing, category by category (Meta — Pricing on the WhatsApp Business Platform).

Two categories were carried through that 2025 change still free, and Meta's non-template-messages documentation gives each one its own sentence and its own date, not one shared date between them. Service messages, it states, "have not been charged since November 2024." Utility messages "sent in response to users within an open 24-hour customer service window," it states separately, "have not been charged since July 1, 2025." Both categories become chargeable on the same date even though they have been free since different points: Meta states plainly, "Effective October 1, 2026, Meta will charge on a per-message basis for service messages," and the same page states Meta "will charge on a per-message basis for utility messages sent in response to users within an open 24-hour customer service window" (Meta — Pricing for non-template messages).

Read the diagram's middle stage carefully — it is drawn deliberately differently from the other two. The "Today" and "1 October 2026" rungs are quoted directly from Meta's own pricing documentation. The checkpoint between them, about confirming a payment method, is drawn as a recommendation rather than a quoted Meta deadline, for reasons the next section explains in full.

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, and nothing about the 1 October 2026 change touches their rate structure — the categorisation rules that do affect them are covered separately at when a template gets recategorised from utility to marketing.

Checked against Meta's documentation on 4 September 2026.

What did Meta publish on 1 September 2026, and where do the rates live?

A specific commitment, not just a change date. Meta's pricing documentation describes its own notice framework directly: "Consistent with the pricing calendar, Meta may update rates up to quarterly," on a fixed cycle — "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." Within that framework, a plain rate card update carries one month of advance notice; adding a new pricing model carries three months; changing the pricing model itself carries six (Meta — Pricing on the WhatsApp Business Platform).

Against that framework, Meta committed to a specific date for the October rates: it will "announce and publish the rates that take effect October 1, 2026, including rates for service messages, by September 1, 2026" (Meta — Pricing for non-template messages). That date has passed as this piece was checked, on 4 September 2026 — meaning the rates for service messages, whatever your market and currency, should already sit on Meta's own rate cards rather than in a future-tense sentence.

We are not reproducing a service-message rate figure on this page, on the same reasoning that already keeps every rupee figure on this site living on one page rather than scattered across every article that mentions cost: a number copied here in six months is a number nobody re-checked against Meta's own quarterly schedule. The dated, currency-specific figures — for templates today, and for service messages once fully reflected in the cards — live at the India pricing breakdown, which is re-checked on its own cycle rather than this one.

Checked against Meta's documentation on 4 September 2026.

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

Every WhatsApp Business Account that connects through the Cloud API is set up with two things: a phone number, and — per Meta's own account documentation — a payment method: "Once created, connect your phone number and set up a payment method" (Meta — WhatsApp Business Accounts). Today that requirement mostly sits in the background, because templates are the only thing being billed and most accounts already added a card to send their first one.

That changes on 1 October 2026, for a structural reason rather than a punitive one. A message that is charged needs an account that can be charged. From that date, an account with no valid payment method attached is not sending free messages any more — it is trying to send messages nobody can bill.

Here is where this piece has to be careful, because a lot of the internet currently is not. In the run-up to 1 October 2026, a wave of vendor blogs and news write-ups covering this same change has been repeating a specific, dated claim: that Meta requires a payment method on file by 30 September 2026, and that an account without one simply stops having its service messages delivered from the following day. We read that claim on more than half a dozen pages while researching this piece, worded closely enough to one another that they read like one source copied many times over.

We could not find that sentence, that date, or that specific consequence on either of Meta's own pricing pages — the general pricing page or the page dedicated to non-template messages — reading both directly on 4 September 2026. Meta's documentation confirms the charging date of 1 October 2026 and confirms rates were due to be published by 1 September 2026; it does not, on the pages we could reach, publish a 30 September payment-method cut-off or describe non-delivery as its consequence. That sentence may exist somewhere inside Meta's Business Help Centre behind a login we could not read, or be communicated directly to larger accounts rather than published — we are not in a position to rule that out. What we can say plainly is that it is not on the developer documentation the rest of this article is sourced from, and a claim repeated by many pages is not the same thing as a claim any of them read at the source.

The practical advice holds regardless of exactly where that sentence lives: from 1 October 2026, a valid payment method is a precondition for every non-template message you send. Confirming one is on file is worth doing this month, rather than finding out the way a customer would — by a reply that never arrives.

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

None, as far as Meta's own documentation states it. We searched the non-template-messages pricing page specifically for a monthly free allowance — for the figure 1,000, and for the phrase "free service messages" — and found neither. What the page does say is a plain before-and-after: service messages are free until 1 October 2026 and chargeable from that date, with no monthly quota carved out on either side of it.

That is worth pausing on, because a specific figure — 1,000 free service messages per phone number, every month — is circulating widely in coverage of this change, phrased almost identically across a number of vendor and news pieces. We are not asserting that figure is false; we are stating what we can verify, which is that Meta's own pricing documentation, read directly on 4 September 2026, does not contain that number, that phrase, or any monthly allowance for service messages at all.

A business planning October's budget around a monthly free block that we could not confirm exists is planning against a figure from an echo, not from Meta. Once the change lands, reading what Meta actually charged you against your own account is a more reliable check than any figure repeated secondhand. If a genuine allowance is announced or documented after this piece was checked, the correction belongs on this page, updated against the source, rather than in a comment thread repeating the same unsourced number.

Are there volume discounts on service messages?

No, and this is one Meta states outright rather than by omission: "Meta does not offer volume tiers for service messages. Meta continues to offer volume tiers for utility and authentication messages" (Meta — Pricing for non-template messages).

Read the two halves of that sentence together and the shape of the new category becomes clear. A marketing template is priced without any volume discount and always has been. Utility and authentication templates get cheaper per message as monthly volume rises. Service messages join neither pattern: whatever the flat rate turns out to be for your market, it does not bend with how many you send in a month.

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 for you in the same sentence that defines a service message: "Any non-template message that is not powered by Meta Business Agent is a service message" (Meta — Pricing for non-template messages). A Meta Business Agent message is the exception that sentence carves out — generated by Meta's own Meta Business Agent Platform, which Meta's documentation describes as 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, not only in amount. Service messages are metered per message. Meta Business Agent messages are metered per token, effective 1 August 2026, at one global rate that does not vary by market. Meta's own documentation is explicit that the cost of any single message is not fixed: it "varies with complexity — simple responses consume fewer tokens and cost less; complex responses consume more tokens and cost more." It also states that a typical message consumes "about 20,000–25,000 tokens" (Meta — Pricing for non-template messages) — meaning two replies that look identical in an inbox, one a short acknowledgement and one a longer reasoned answer, can cost meaningfully different amounts, in a way a flat per-message price never would.

We are not printing the token rate itself here — per-message and per-token figures both move on Meta's quarterly schedule, and a number copied out of this paragraph in six months is a number nobody re-checked. The current published figures are worth reading directly on Meta's own rate cards, alongside everything else Meta charges, at the India pricing breakdown.

If your bots, flows, or AI assistant are calling a model you configured yourself, rather than Meta's own agent platform, none of this token metering applies to them. That traffic is still an ordinary service message under Meta's definition above, billed — from 1 October 2026 — the same as a message a person typed.

Checked against Meta's documentation on 4 September 2026.

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

Not from a formula, because the two numbers a formula needs are not both available in the same place yet: how many service messages you actually send in a month, and the rate Meta charges for one in your market. The second was due by 1 September 2026, under the notice framework covered above. The first is something you can measure today, from your own history, regardless of what the rate turns out to be.

A message log that records every send, its direction, and its status is the input this exercise actually needs. Filtering a month of outbound messages by direction and status, and separating ordinary replies from templates, is what turns "service messages" from an abstract billing category into an actual count you can multiply against a rate once one is confirmed for your market.

Do this before 1 October rather than after. A month's service-message volume, counted from your own logs while replies still cost nothing to send, is the baseline every future invoice gets compared against — and the only way to notice quickly if October's bill looks nothing like what your own traffic would predict.

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 Meta Tech Provider is not permitted to resell Meta's per-message fees at all, a distinction 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's own documentation describes a Solution Partner's credit line being extended to remove that step for their clients.

Practically, that means the payment method Meta bills for service messages after 1 October 2026 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 on your behalf. WabaCRM's own bill covers software: the shared inbox, contacts, campaigns and the rest, visible on its own billing screen. 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 in the next section starts inside Meta's own WhatsApp Manager rather than inside any vendor's dashboard — the platform genuinely cannot check this on your behalf, because it is not the platform's account to check.

What should a business do in the four weeks before the deadline?

Four things, none of which depend on a rate that was not yet published when this piece was checked:

1. Confirm a payment method is on file for the WhatsApp Business Account you actually send from, inside Meta's own WhatsApp Manager, under the account's business settings — not inside your messaging software, for the reasons covered above.
2. Pull a month of your own message logs and count service messages — ordinary non-template replies sent inside the customer service window — separately from templates. That is the number the eventual rate gets multiplied against.
3. Check the rate card once Meta's own published figures are current for your market, on the schedule Meta committed to above, rather than budgeting from a figure quoted on a vendor page with no date beside it.
4. Read what your own bots and automations actually 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 own definition every one of them is a service message from 1 October 2026 onward, whether a person typed it or not.

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. Read alongside this, if your business also sits inside Meta's India billing rules, is the other dated Meta deadline landing this year: migrating a WABA to INR before 31 December 2026.

Checked against Meta's documentation on 4 September 2026.

Every Meta quotation on this page was read from Meta's own documentation on 4 September 2026. Meta changes that documentation without notice; the linked pages are authoritative and this one is not.