WhatsApp Service vs Utility Messages: What Gets Charged After October 1, 2026
After October 1, 2026, a non-template WhatsApp reply sent by a person or third-party AI inside an open 24-hour customer service window is a service message and is charged per delivered message. A utility template sent inside that window remains a utility message and also becomes billable. A Meta Business Agent response uses a separate token-based category. The 72-hour free entry point remains the main delivery-charge exception.
Key takeaways
- The 24-hour window controls whether a non-template reply is allowed; it no longer makes that service reply free after October 1.
- A person or third-party AI sending a non-template reply creates a service message. Meta Business Agent creates its own message category.
- A utility template does not turn into a service message merely because it is sent after a customer writes first.
- Meta applies one message category and one Meta delivery charge, never both service and utility charges to the same message.
- The official WhatsApp Business Platform is still the right path for approved templates, campaigns, Meta analytics, and Click-to-WhatsApp attribution.
WhatsApp service vs utility messages after October 1, 2026
Meta’s current documentation separates message type, sender, category, and meter. Keeping those four fields separate prevents most billing mistakes.
| Question | Service message | Utility message | Meta Business Agent message |
|---|---|---|---|
| Message type | Non-template | Approved utility template | Non-template response powered by Meta Business Agent |
| Who sends it | Person or third-party AI | Business automation or agent using the template | Meta Business Agent Platform |
| When it can be sent | Only in an open 24-hour customer service window | According to template and policy rules | In the supported Meta Business Agent flow |
| Meter after October 1 | Per delivered message | Per delivered message | Per token from August 1 |
| 72-hour free entry point | Delivery is free | Delivery is free | Token usage is still charged |
The 24-hour customer service window opens or resets whenever the user sends a message. Until October 1, service replies and utility templates sent in that open window are not charged for delivery. From October 1, Meta says both become billable per message. This is a pricing change, not a removal of the window: non-template messages still require the window to be open.
Meta also says service-message rates will match the market’s utility and authentication rates, without volume tiers. The final rates taking effect on October 1 were not yet published when this article was checked on July 24; Meta says it will publish them by September 1. A forecast should therefore keep message volume separate from the not-yet-final rate.
A five-question classification decision tree
Use this sequence for every business-sent WhatsApp message.
1. Is the 24-hour customer service window open?
If no, a non-template message cannot be sent. The business normally needs an approved template that matches the intended category. If yes, continue; the open window permits a non-template reply but does not determine its final category by itself.
2. Is the message an approved template?
If yes, preserve the template’s category. An order update using an approved utility template remains utility even when the customer messaged five minutes earlier. Starting October 1, that in-window utility delivery is charged again.
If no, the message must be sent during the open 24-hour window. Continue to identify what powers the reply.
3. Is Meta Business Agent powering the response?
If yes, Meta classifies it as a Meta Business Agent message and charges by token from August 1. If a human support representative or third-party AI produces the non-template reply, it is a service message and is charged per delivered message from October 1.
4. Did the conversation start from a free entry point?
When a user enters through a Click-to-WhatsApp ad or Facebook Page call-to-action button, a 72-hour free entry point window can make message delivery free. Meta says this delivery exception remains unchanged. Meta Business Agent token usage is still charged, so “free delivery” does not mean every layer of the response is free.
5. Are you counting only one category?
A message receives one category. A service reply is not also charged as utility, and a non-template Meta Business Agent response is not also charged as service. Keep third-party AI model fees, BSP fees, and Meta message-delivery charges as separate ledger lines; they are different cost sources, not additional WhatsApp categories.
Classification examples for support teams
| Scenario | Classification after October 1 | Why |
|---|---|---|
| Human answers a product question 10 minutes after the user writes | Service | Non-template reply by a person in the open window |
| Third-party AI drafts and sends the same reply | Service | Non-template reply not powered by Meta Business Agent |
| Meta Business Agent answers the question | Meta Business Agent | Separate token-metered category |
| Workflow sends an approved order-confirmation template in the open window | Utility | Template category remains utility |
| Human tries to send free-form text 25 hours after the last user message | Not allowed as non-template | The customer service window is closed |
| Agent replies during a valid 72-hour Click-to-WhatsApp entry window | Category still applies; delivery can be free | Free entry point changes the delivery charge, not the message identity |
For the architecture choice between Meta’s agent and your own AI pipeline, read the Meta Business Agent pricing comparison. For instrumentation, the service-message charge tracking guide shows how to retain the pricing object and reconcile it with Pricing Analytics. The three WhatsApp inbound paths compares Cloud API, BSP, and unofficial interface trade-offs.
Where UnifyPort fits
The classification above applies to messages sent through the official WhatsApp Business Platform. UnifyPort’s unofficial interface is a separate integration path for teams using ordinary messaging accounts or building one inbound queue across WhatsApp, Telegram, LINE, TikTok, Zalo, and X.
An inbound WhatsApp message arrives as a normalized message.received event. When the webhook endpoint has a signing_secret, the receiver verifies X-Device-Timestamp and the HMAC-SHA256 value in X-Device-Signature before processing the raw body. Replies use POST /v1/messages.
That does not reclassify a message sent through Meta or remove an official-platform charge. It means the team has chosen a different messaging path with a different control plane. Keep the two paths explicit in architecture diagrams and billing records.
Limitations and trade-offs
Use the official WhatsApp Business Platform when you need approved outbound templates, official campaign tooling, Meta-native analytics, Click-to-WhatsApp attribution, or a BSP’s managed compliance and support. Its message categories and reporting are designed for those workflows.
UnifyPort does not provide Meta template approval, Meta Pricing Analytics, official ad attribution, or official-platform status. An unofficial interface also carries different operational and policy trade-offs, so it should be evaluated deliberately rather than presented as a billing setting inside Cloud API.
Rates remain time-sensitive. Recheck Meta’s rate card after September 1 and before October 1 instead of copying a planning rate into production forecasts.
FAQ
What counts as a WhatsApp service message after October 1, 2026?
A non-template response sent inside the open 24-hour customer service window by a person or third-party AI, when it is not powered by Meta Business Agent, counts as a service message.
Is a utility template sent inside the 24-hour window a service message?
No. It remains a utility message. Starting October 1, Meta charges for utility messages sent in response to users inside the open window as well.
Are service messages still free in the 24-hour window?
Only until October 1, 2026. The window continues to permit non-template replies, but those service messages become billable per delivered message on that date.
Does one reply receive both a service and utility charge?
No. Meta assigns one category to each message. External AI usage or BSP fees may create separate costs, but they do not add a second WhatsApp message category.
Does the 72-hour free entry point still apply?
Yes for message delivery when the entry conditions are met. Meta Business Agent token usage remains chargeable even inside that 72-hour window.
Next step
If you are comparing the official billing model with a normalized inbound path, review UnifyPort’s webhook delivery and signature reference and test one signed message.received event before changing production routing.
Sources
- Meta: Upcoming pricing updates for non-template messages — checked July 24, 2026.
- WhatsApp Business Platform pricing and message categories — checked July 24, 2026.
- Meta: Be There for Every Customer With Meta Business Agent — checked July 24, 2026.