For many NGOs, WhatsApp has become much more than a messaging channel. It is where programmes reach people, collect information, send reminders, answer questions and increasingly, have ongoing conversations with communities.

That last part is important.

A simple programme message can quickly turn into a conversation: a user responds, a chatbot replies, the user asks another question, an AI assistant responds, and the interaction continues.

Until now, service messages in these conversations have been free. From 1 October 2026, Meta will start charging for service messages on WhatsApp.

For organisations that rely heavily on two-way conversations, the immediate question is obvious: how much is this going to cost?

The answer depends much more on your programme than on a single pricing number.

What is changing with WhatsApp service messages?

WhatsApp already charges for certain template messages, including marketing and utility messages. The change is that service messages, which were previously free, will also become billable from 1 October.

In practical terms, service messages are outbound, non-template messages sent as part of an ongoing conversation. These can include:

• Responses from a programmed chatbot
• Interactive messages, such as messages with buttons
• AI-generated responses
• Other non-template messages sent to users

That means the cost impact will look very different for different organisations.

A programme that mainly sends periodic updates may have relatively few service messages. A chatbot-led programme or helpline, where users and bots exchange several messages in a single interaction, could have a much higher volume.

And that is why the first step is not to change your programme. It is to understand your numbers.

How much could the WhatsApp pricing change cost your organisation?

There is no single answer.

In a recent Glific webinar on the pricing change, the team shared an early estimate based on the previous month’s data across the organisations they analysed. For most organisations in that sample, the estimated increase in monthly cost was less than ₹1,000.

That is useful as an indication, but it is not a universal benchmark.

The estimate was based on a single recent month, and programme volumes can vary significantly with seasonality and scale. During the webinar, organisations also pointed out that in some cases service messages can vastly outnumber marketing and utility templates, particularly for programmes involving extensive chatbot or AI conversations.

So the important number is not ₹1,000.

It is your number.

Glific’s Data Analytics → Message Overview provides a good starting point. It shows inbound and outbound message volumes, including the split between template and service messages, and gives an approximate cost based on current volumes. This calculator can help you arrive at an approximate cost based on those indicative message volumes.

For organisations that have been running Glific for longer, historical message data can also be analysed to understand how volumes change over time and what costs might look like as programmes expand.

This matters particularly for seasonal programmes. A quieter month may give you a very different picture from a month when your programme is operating at full capacity.

Once you know the cost, look at the conversation

The pricing change is also a useful opportunity to look at how your programme conversations are designed. Not every task needs a long back-and-forth on WhatsApp.

For example, if a user needs to provide several pieces of information during registration or data collection, WhatsApp Forms can bring those inputs together in a single interaction, reducing the number of messages needed to complete the task.

For programmes that mainly involve updates and reminders, WhatsApp Groups could be another option. Instead of sending the same information through individual conversations, some broadcast-heavy programmes may be able to reach their communities through groups.

And where a programme depends on deeper, two-way conversations, it may be worth asking whether WhatsApp needs to be the only channel involved.

The point isn’t to move everything away from WhatsApp. It’s to look at each interaction and ask: does this conversation need to happen in the way it does today?

Does every programme conversation need to happen on WhatsApp?

For many organisations, WhatsApp will continue to be an important channel. People already use it, understand it and are comfortable interacting with organisations there. A change in pricing does not change that overnight.

But it does create an opportunity to think beyond a single channel.

This is where the Glific Web Channel comes in. It brings the Glific conversation experience to a browser, giving organisations another way to engage users without relying entirely on WhatsApp. Organisations can continue to build and manage their conversations in Glific, while users can access them through a web-based chat experience.

We’ll soon be ready to begin beta testing the Web Channel with NGO partners. If you’re interested in being part of the beta, keep an eye on our

If you’re interested in being part of the beta, keep an eye on our LinkedIn and Instagram channels for updates.

The question, then, becomes less about WhatsApp or something else and more about which channel makes sense for which conversation.

A pricing change can be a useful prompt

The WhatsApp pricing change is ultimately a cost change. But for organisations running programmes through conversational technology, it can also be a useful prompt to take a closer look at how those programmes work.

Start with the data. Understand your message volumes and the proportion that are service messages. Look at when your volumes peak and how they might change as the programme grows.

Then look at the conversations themselves. Where is the back-and-forth essential? Where could a Form make an interaction simpler? Where might a Group work better than one-to-one messaging? And where could another channel provide a better experience?

WhatsApp is not going away from the way organisations engage communities. But the economics of using it are changing.

And that makes this a good time to rethink not whether we use WhatsApp, but how we use it.

The conversation comes first. The channel should follow.