Denshin / Blog / Engineering
WhatsApp's October 2026 pricing change, from the side that writes the code
From 1 October 2026 WhatsApp charges for service replies past 1,000 a month and for utility templates inside the customer service window. What changed, what it costs at Indian rates, and how we now design order updates and support flows.
Denshin Engineering · Engineering Team · 14 October 2026 · 4 min read
On 1 October 2026 Meta changed which WhatsApp Business Platform messages cost money. If your product sends order updates, delivery alerts or support replies on WhatsApp, the change probably raised the bill a little. If nobody had added a payment method to the account by 30 September, service messages may have stopped going out altogether.
This is what changed, and what we now do differently when we build on it.
How billing works now
Since 1 July 2025 the platform has charged per delivered message, by category, instead of per 24 hour conversation. The categories are marketing, utility (order and account updates), authentication (OTPs) and service (free-form replies to a customer who wrote to you). Messages customers send you are free.
Until this month, two things were free that are not anymore:
- Service messages beyond the first 1,000 per business phone number per month. The 1,000 are still free, and unused ones do not roll over.
- Utility templates sent inside an open customer service window, that is, within 24 hours of the customer's last message.
Messages sent inside a free entry point window, which opens when someone starts a chat from a Click to WhatsApp ad, are still free for the length of that window (up to 7 days, per Meta's docs).
For a sense of scale, India list rates are around Rs 0.86 per marketing message and Rs 0.115 per utility, authentication or service message, before 18% GST. Meta only changes prices on the first day of a quarter, and the Indian card has already moved twice this year, so check the current rate card before you put a number in a proposal. Separately, Indian businesses have to move their WhatsApp billing currency to INR by 31 December 2026.
Cheap until you multiply
Rs 0.115 sounds like nothing. A business shipping 20,000 orders a month with five updates per order (confirmed, packed, shipped, out for delivery, delivered) sends 100,000 utility messages, about Rs 11,500 a month before tax. Three updates per order brings it to Rs 6,900. Not dramatic for one month. It adds up over years, and it is entirely a design decision.
What we do by default now:
- Send only the updates the customer acts on. "Out for delivery" earns its place. "Packed" rarely does.
- Collapse updates that fire close together. If confirmation and packing happen in the same hour, that is one message.
- Keep a message log table: category, template, delivery status, estimated cost. The status webhook tells you when a message is delivered, which is the moment it becomes billable, so the log reconciles against Meta's invoice.
- Move low value notices to email or the app, and keep WhatsApp for the moments that matter.
Support replies have a budget
A support team answering on WhatsApp used to cost nothing. Now it is free for the first 1,000 messages per number per month and charged after that. For a small business that may never matter. For a desk where an AI drafts replies (we wrote about doing that without annoying people), a bot that answers in three short bubbles instead of one paragraph now costs three times as much. Join the bubbles.
Look also for any flow that sends a utility template in reply to an inbound message, for example an order status template when a customer asks where their parcel is. That used to be free inside the window. It now costs the same as one sent cold.
Templates and opt-outs
A template's category is set when it is approved, and Meta can reclassify a utility template as marketing if it reads like a promotion. "Your order has shipped, and here is 10% off your next one" is a marketing message, at roughly seven times the utility rate. Keep utility templates dull and put the offer in a separate marketing send to people who opted in.
Store opt-ins and opt-outs in your own database, not only in your provider's dashboard. When someone replies STOP, the marketing job should respect it on the next run, and you should be able to show where each consent came from, which the DPDP Rules will expect from May 2027 anyway.
Worth checking this week
- A payment method is on the WhatsApp Business account. If service messages stopped on 1 October, start here.
- September's message volume by category, priced under the new rules, so the next invoice is not a surprise.
- Any flow that sends a template in reply to an inbound message.
- The INR billing switch, before December.
Rates and rules above are as of October 2026. They change quarterly, so treat any number in a blog post, this one included, as a starting point and confirm it against Meta's rate card.
Tags: WhatsApp API, Pricing, Notifications, India
All posts · Work with Denshin