Starting October 1, 2026, every reply a business sends on WhatsApp inside the 24-hour service window — free-form, not a template, written by a human agent or generated by an AI like Agentforce — stops being free. Meta will charge per service message, at the same rate it already charges for utility and authentication templates in each country, with no volume discount.
That changes the math for any company that has already decided to integrate WhatsApp with Salesforce — and it changes more for whoever put Agentforce answering customers inside that window. That's exactly where, in the routine reply inside an open service conversation, the operation today pays nothing beyond the channel's license.
What a service message is — and why it was free until now
A service message is any reply that combines three things at once: it's free-form (not a pre-approved template), it happens inside the 24-hour window a customer opened, and it wasn't generated by Meta's own AI agent. Order-status checks, appointment confirmations, a billing question — most of a WhatsApp service conversation is, technically, a service message.
That kind of message has been free since November 2024, when Meta eliminated the per-service-conversation charge that existed before. That's what made WhatsApp cheap to operate at scale: a Brazilian company already using the app as its main channel — 82% of the country's micro and small businesses, according to market research, often with no system behind it at all, just the app and whoever's memory happens to be answering — pays nothing for the message exchange itself, only for the license or the tool that connects the channel to the system. It's the same double-entry symptom we already mapped in small-scale operations, where a salesperson notes it down on WhatsApp and transcribes it into the CRM later because the manager requires it — except here the hidden cost isn't the process, it's the messaging itself that Meta has been charging zero for until now.
With 82% of WhatsApp users in Brazil having already talked to a company through the app and 88% reporting they've already been served by a bot in that conversation, the scale of service messages exchanged every day in the country isn't small. That scale is exactly what makes the October change weigh on the budget — not the per-unit price, which is low, but the volume that multiplies it.
What changes on October 1, 2026
Four points sum up the change, straight from Meta's own documentation on non-template message pricing:
- Service messages stop being free. They start being billed per unit, at the same rate Meta already charges today for utility and authentication templates in that country — without the volume discount (tier) utility and authentication templates get.
- Utility templates lose their in-window waiver. Today, a utility template sent inside an already-open service conversation isn't charged. That ends alongside the October change.
- It isn't the same thing as the Meta Business Agent. Meta's own AI inside WhatsApp — a distinct product from Agentforce — already gets billed by token ($2.00 per million tokens, roughly 4 to 5 cents per reply) starting August 1, 2026, on a separate timeline. A message generated by Agentforce or any other third-party AI falls under the service-message category, billed per unit starting in October — not under Meta's token scheme.
- The exact rate per country lands by September 1, 2026. Meta's own documentation uses, as an illustrative example for Brazil, a charge around $0.0068 per service message — an order of magnitude below the marketing template (around $0.0625), but still a value that's zero today.
The message that costs zero today inside the service window becomes a budget line in October — the per-unit price is low, the volume is what decides the bill.
None of the four points depends on a company's own decision — it's Meta's rate card changing, and it applies to any business running the WhatsApp Business Platform, with or without Salesforce in the middle.
What this changes for anyone already running Agentforce on WhatsApp through Salesforce
Today, the cost of a WhatsApp support conversation inside Salesforce has two layers: the Service Cloud Digital Engagement license — around $75 per user per month — and Agentforce's own consumption, billed in Flex Credits or per conversation depending on the contracted model. Starting in October, a third layer enters: every reply Agentforce sends inside the service window — the same routine reply that's free for Meta today — starts carrying a per-message cost billed directly by Meta itself.
That stacks on top of any use case that already depends on long conversations in the channel. It's the same pattern already showing up with the Buyer Agent closing recurring B2B orders straight through WhatsApp: every SKU confirmation, every revised contract price, every clarifying question becomes a separate service message — free today, billed per unit starting in October.
The risk isn't the isolated per-message cost, which is low. It's the same variable-consumption risk we already broke down in Agentforce's own pricing: it looks small on the proposal and turns unpredictable in operation when nobody measures, beforehand, how many service messages a typical conversation actually consumes.
Four questions before October 2026
The change already has a date on the calendar — what's left is deciding how the operation prepares before it lands:
- How many service messages does the operation exchange per conversation today, adding up human agents and Agentforce? Without that number, there's no way to estimate the change's impact — only to react to the invoice once it arrives.
- How many of those turns can be resolved with a single-shot collection — a WhatsApp Flow, an embedded form — instead of several back-and-forths? Every avoided message exchange is one fewer service message billed per unit.
- Which structured updates — order confirmation, status, reminder — make more sense as a template than as a loose reply? Utility templates also start getting charged inside the window, but they still keep the volume discount service messages don't have.
- Who on the team — Salesforce, service, finance — becomes the owner of the monthly messaging spend ceiling after October? That ceiling doesn't exist today because the bill is zero. Starting in October, someone needs to own it.
None of the four answers live in Meta's or Salesforce's price sheet in isolation — they live in the conversation pattern the operation already has, measured before the change takes effect.
The free window turned into the exception, not the rule
For nearly two years, the service message on WhatsApp was the free piece of a bill that already charged for templates, channel licenses, and agent consumption. That changes in October 2026, and it changes for every company operating the channel — with Salesforce, with another CRM, or with no CRM at all.
Whoever already measures today how many service messages a typical conversation consumes walks into the change knowing the real size of the impact. Whoever only discovers the change on October's invoice will spend the following month trying to reconstruct a number that could have been measured in September.
Questions that keep coming back
To close, the most common doubts about WhatsApp's service-message billing.
What is a WhatsApp service message, and when does it stop being free?
A service message is a free-form reply — not a pre-approved template — sent inside the 24-hour service window a customer opened, by a human agent, a rules bot, or third-party AI like Agentforce. It's been free since November 2024, but stops being free starting October 1, 2026, when Meta begins charging per unit, at the same rate it already charges for utility and authentication templates in each country, with no volume discount.
Are the Meta Business Agent and Agentforce's service messages billed the same way?
No. They're different products on different timelines. The Meta Business Agent is Meta's own AI inside WhatsApp, billed by token — $2.00 per million tokens, roughly 4 to 5 cents per reply — starting August 1, 2026. A message generated by Agentforce or any other third-party AI falls under the service-message category, billed per unit starting October 1, 2026, at the rate equivalent to that country's utility and authentication template.
How much will each service message cost in Brazil?
Meta's own documentation uses, as an illustrative example for Brazil, a charge around $0.0068 per service message — well below the marketing template, which sits around $0.0625. The final rate by category and volume only closes with the official table Meta publishes by September 1, 2026, so the final number may differ from the example.