Service, utility, marketing and authentication: what WhatsApp actually charges for

WhatsApp has three template categories, marketing, utility and authentication, and one category that is not a template at all, service. The category looks like a line on an invoice. It is a permission first and a price second: the category decides whether Meta will deliver the message, and only then what it costs.

The four names, and which axis each one sits on

Meta’s Template fundamentals page, updated May 21, 2026, is exact about the three that are template categories: “Each template must be categorized as authentication, marketing, or utility.”

Service is the fourth name and it sits on a different axis. It is not a category you assign to a registered template. It is what Meta calls the free-form message you send while a customer service window is open, and the Service messages page records where it lands in billing: “Service messages are billed under the SERVICE pricing category.”

The map therefore has two questions in it, not one.

Category	Registered and approved in advance	Can be sent with no open window	Volume tiers available
Marketing	Yes	Yes	No
Utility	Yes	Yes	Yes
Authentication	Yes	Yes	Yes
Service	No	No	No

The volume tier column comes from Meta’s own restriction of the mechanism: “You can unlock lower utility and authentication rates based on the number of messages you send in a month.” Service is excluded by name on the pricing update page, which says that Meta “continues to offer volume tiers for utility and authentication messages” and not for service.

Which categories need Meta’s approval before you may send

All three template categories. Template fundamentals states the gate on reach, “Template messages are the only type of message that can be sent to WhatsApp users outside of a customer service window”, and again on status:

Templates must have a status of APPROVED before they can be sent in template messages.

Service messages are the one category with no such step, and Meta draws the contrast itself:

Unlike template messages, service messages do not require pre-approval - you can compose and send them as needed in response to a WhatsApp user’s message or call.

Which categories can only be sent inside an open window

Exactly one: service. The pricing page puts the restriction on the message type rather than on the price: non-template messages “can only be sent within an open customer service window”. The Service messages page says the same from the other end: “When the window closes, you can only send pre-approved template messages.”

The three template categories are not window-gated at all. A utility template in particular can go either way, and Meta says so when describing what changes in October: a business can use one “to either reach out to or respond to users”. The window changes what a utility template costs. It does not change whether it is allowed.

Service is gated by time and needs no approval. Templates are gated by approval and need no open window.

What is free, and the three different reasons why

There are three separate free cases, each with its own date and its own scope, and no single sentence of Meta’s covers all three.

The first is the whole non-template category: “As of November 1, 2024 - Meta does not charge for non-template messages”. The second is narrower, one template category in one situation: “As of July 1, 2025 - Meta does not charge for utility templates in response to users (delivered within an open customer service window).” Marketing and authentication templates get no such treatment.

The third is the free entry point window, and it is the only case where a marketing template is not billed. Meta’s rule is otherwise flat, “All marketing template messages are charged”, and this window is what overrides it:

Free entry point window - All messages, including template messages, are free for 72 hours, if sent within an open free entry point window.

It opens only from a specific origin:

If a WhatsApp user messages you via a Click to WhatsApp Ad or Facebook Page Call-to-Action button using a device running our Android or iOS app (our desktop and web apps are not supported)

Two of those three cases end on 1 October 2026. Meta will charge per message for service messages from that date, and for utility templates sent in response to users inside the window. Meta also records a monthly allowance on its own platform from the same date: “Each business phone number has one shared free tier of 1,000 delivered service messages per month.” That is Meta’s allowance, on Meta’s platform. It is not an offer of ours, and nothing on this page is a statement about what we send.

Per message, not per conversation, since July 2025

Anything you read about WhatsApp conversations as billing units describes a model Meta retired. The pricing page is unambiguous: “Conversation-based pricing is deprecated. It was replaced with per-message pricing on July 1, 2025.” The unit is now a delivery, and only some deliveries count: “You are only charged when a template message is delivered”.

What sets the amount is three things together, not the category alone. Meta lists them as “template category, volume tier, and country/region rate”, and elsewhere ties the geography to the recipient rather than to you: “Charges for messages are based on the country calling code of the recipient WhatsApp phone number.”

There is no United States row to quote you. Meta groups the United States with Canada in a market it calls North America, both under calling code 1, and the per-market amounts live in downloadable rate card CSVs and PDFs per currency rather than in the page text. Any figure handed to you as the American utility rate is one reading of one CSV on one day, so we will not print it as a US rate. The most specific published line about that market is a direction of travel, effective January 1, 2026: “North America - Lower utility and authentication rates.”

The category is Meta’s decision, and it can change after approval

You propose a category at creation; Meta rules on it. From the Template categorization page, updated Sep 15, 2026: “WhatsApp validates the category you indicated per the contents of the template and the guidelines.” Disagreement is a rejection, not a re-label:

REJECTED status indicates that WhatsApp disagreed with the category you designated in your template creation request.

Approval is not final either. Meta runs a recurring sweep, and “Automatic category updates can apply to any approved template that does not meet the template category guidelines”. A utility template that should have been marketing gets moved, with thin notice: “A 1-day advance notice is provided before the template category is updated to marketing.” The pricing consequence is stated as your responsibility, on the pricing page: “Whenever a template is used, a business accepts the charges associated with the category applied to the template at time of use.”

Two content rules sit behind those moves. Utility has to clear a bar the guidelines state as “Must be non-promotional, not containing any promotional or persuasive intent”, and anything mixed or vague falls to marketing, including “Templates where contents are unclear”. Authentication is narrower still: “Only authentication templates can be used to send a one-time passcode for identity verification. Marketing and utility templates cannot be used for this purpose.”

The answer, in one paragraph

If a customer messaged you and the window is open, the service category becomes available to you: free-form, no approval, and free until 1 October 2026. An open window does not put everything you send in it into that category, though. A template sent inside an open window is still a template message and is charged on its own category, which is the reason a utility template delivered in the window needed a free case of its own and a marketing template never got one. Direction and category are two different axes. If the window is shut, service is not merely expensive, it is refused, and your only route is a template whose category Meta assigned and can reassign. Category answers the permission question before it answers the price question.

For the same shape of problem elsewhere, where a reply is rejected and the reason is only legible through an API, the Google review reply case is documented here.