Customer communications

WhatsApp charges service messages from 1 October 2026

Twinny Team · · 7 min read
Mobile phone on a table with a messaging app open

If your customer service, reminders or sales depend on WhatsApp, there is a date worth putting in the calendar: 1 October 2026. According to the official WhatsApp Business Platform pricing documentation, on that day Meta starts charging service messages (the non-template messages a business sends inside the 24-hour customer service window) per message, when until now they were free. In Meta’s words, "any non-template message is charged as of October 1, 2026", at per-country rates equal to those of utility and authentication messages. It is the most relevant change since, on 1 July 2025, the model moved from charging per conversation to charging per delivered template message.

What exactly changes (and what does not) according to Meta

Until 30 September 2026, when a customer writes to you a 24-hour window opens in which your non-template replies (from human agents, chatbots or automated flows) cost nothing. From 1 October, each of those service messages is charged individually, "consistent with how Meta charges for template messages", at the rate each country has for utility and authentication. Per-country rates also change in several markets. What stays free are conversations opened from click-to-WhatsApp ads or from the message button on a Facebook Page during their 72-hour window.

  • Until 30 September 2026: service messages inside the 24-hour window are free.
  • From 1 October 2026: every service message is charged per unit, at each country’s utility and authentication rate. Five replies in one conversation cost five times more than one.
  • The 72-hour window of conversations that start from a click-to-WhatsApp ad or the Facebook message button stays free.
  • Recommendation: check Meta’s official rate card for your country; conditions change often.

The lesson is not the date: it is the dependency

With per-message billing of service messages, every reply on WhatsApp now has a direct cost: a twenty-message support conversation costs twenty times more than a one-message one. And every pricing or policy adjustment by a third-party platform is a reminder of the same thing: the larger the share of the customer experience that happens inside a channel you do not control, the more exposed your operating cost and conversion are to someone else’s decisions. It is not about abandoning WhatsApp, which remains the preferred channel of many customers, but about deciding at every moment of the customer journey which channel is the most efficient.

WhatsApp is changing. Your customer journey should too.

How Twinny solves it: one number, every conversation

Twinny’s customer communications solution starts from a single business number from which the company handles phone calls, WhatsApp calls and WhatsApp messages, plus email, SMS, web and social, all on the same customer context. An AI voice or messaging agent resolves the first layer and executes in your systems; when needed, it escalates to a person with the full history. A call does not start from scratch because the customer wrote on WhatsApp earlier.

WhatsApp as an entry point, not the whole experience

The second piece is deciding where each interaction continues. A conversation can start on WhatsApp and continue in a personalised web experience, generated by Twinny, in which the customer keeps talking to the AI, looks up information, selects options, completes forms, books, buys, provides documentation or executes actions, keeping identity, context and conversation. WhatsApp becomes an entry point and a notification channel; the rich part of the experience happens in an owned channel, with no per-message cost and better conversion.

  • Fewer service and template messages on WhatsApp: lower cost per conversation.
  • Voice and AI where a call resolves better than twenty messages.
  • Owned web experiences for forms, bookings, payments and documentation.
  • Shared context across channels thanks to the Company Memory.

What to review before 1 October

  • How many service messages you send per conversation each month and in which countries: from 1 October each one has a cost.
  • Which interactions could start on WhatsApp and continue on the web or by voice.
  • Whether your business number is already ready for voice, WhatsApp calls and messages on the same context.
  • Which actions a digital worker could execute without human intervention (bookings, changes, status enquiries).

If you want to know how much of your current WhatsApp operation could move to owned channels without losing context, tell us about the process and we will send you an initial proposal within 24 hours.

Frequently asked questions

Will Meta charge for service messages from 1 October 2026?

Yes. According to Meta’s official documentation, from 1 October 2026 every service (non-template) message a business sends is charged per unit, at the same rate as each country’s utility and authentication messages. Until that date they were free inside the 24-hour window.

What stays free?

Conversations that start from a click-to-WhatsApp ad or from the message button on a Facebook Page, during their 72-hour window.

Do I have to stop using WhatsApp?

No. The point is to use it as an entry point and notification channel, and to continue in voice or in an owned web experience the interactions that allow it.

How does Twinny keep context across WhatsApp, voice and web?

Every interaction is recorded against the same customer identity in the Company Memory: history, intent, actions taken and process in progress.

References

  1. Meta — Pricing for service (non-template) messages, updates from 1 October 2026 (official documentation)
  2. Meta — WhatsApp Business Platform pricing and per-country rate cards
  3. Twinny — AI customer communications

Want to see how much you could save in your case?

Calculate my ROI Book a demo

Orchestrate every channel
from one intelligent
layer.

In 30 minutes we'll show you how Twinny connects to your operation and starts delivering results from week 1.