On 1 October WhatsApp bills the service message: count now
We are five weeks from 1 October 2026: Meta starts billing service messages and in-window utility templates — what since 2025 had felt “free” if the customer wrote first. Country rates are due around 1 September. Anyone without volume by category is blind. On 26 August you can still label templates, cut endless threads, and put the next step in a system.
The same quarter brings another local cutoff: Hacienda asked for 4.4 annex updates (new codes, references, alphanumeric legal IDs) from 1 November 2026. WhatsApp and XML are not the same project, but both punish an operation that lives in chat and email with no rail. Respond.io for the channel; Journal and APIs for the voucher; gateways so collection is not one more message.
A calendar from here to November
- Inventory of in-window messages: how many would be billable on 1 October.
- Move reminders to utility templates that mean it, not to marketing.
- Test the new 4.4 XML in Hacienda’s environment before November.
- A quote with an owner, not a “we’ll see in Q4.”
This is the last post in the fortnightly series that started after June 2025. The rule did not change: real news, a visible process, service pages you can actually go to. On 1 September 2026 the calendar continues; so does the rail.
October bills the chat. November bills the XML. August bills the decision not to count.
If your operation mixes WhatsApp, collection, and Hacienda in one person’s head, ask us for the map. It is the same work as a year ago: systems people use, not seasonal demos.