WhatsApp's 1,000 free service replies: what changes for you

Updated 2026-09-24 · 4 min read · By the Convo360 team

What counts as a service conversation

Meta divides WhatsApp conversations into categories, and the distinction decides what you pay. A service conversation is one the customer started by messaging you. Marketing, utility and authentication conversations are ones you started with an approved template.

The critical detail, and the one most businesses get wrong, is that a conversation is a twenty-four hour window rather than a message. If a customer writes at 10 am and you exchange thirty messages over the next few hours, that is one service conversation, not thirty.

This is why the number 1,000 goes further than it first appears. A thousand free service conversations means a thousand separate customers writing in during a month, or the same customer writing on a thousand different days, not a thousand messages.

For a typical Indian small business handling twenty to thirty customer enquiries a day, the allowance covers the whole month with room to spare. For a busy D2C brand at a festive peak it will not, and that is what this change is really about.

What actually changes on 1 October 2026

Until now, service conversations have effectively been free in most circumstances. From 1 October 2026 each business phone number receives 1,000 free service conversations per calendar month, and conversations beyond that are billed.

In India the rate after the allowance is roughly ₹0.115 per service conversation, which is small per unit and worth understanding at volume.

Even at twenty thousand conversations the cost is modest compared with the salary of a single support executive. The risk is not the amount, it is being unaware of it.

The part that catches businesses out

The charge itself is manageable. The failure mode is not.

If your WhatsApp Business Account has no valid payment method attached, Meta does not send you an invoice and wait. It stops delivering messages once the free allowance is exhausted. Your bot appears to break, customers receive nothing, and the error your logs show is a billing error rather than anything to do with your setup.

This happens silently and usually at the worst time, because the allowance runs out fastest in a busy month. A brand that sails through September comfortably can hit the limit on the fourth day of a Diwali campaign.

The fix is dull and important: add a payment method in Meta's Billing Hub before you need it, and check it is attached to the correct WhatsApp Business Account rather than to a different asset in the same Business Manager.

How Convo360 keeps you ahead of it

Convo360 counts service conversations for each connected number and shows how much of the monthly allowance has been used. A warning appears as you approach the limit rather than after you have crossed it, which is the only point at which the information is useful.

If Meta does start refusing messages because no payment method is attached, Convo360 recognises that specific error and tells you what it means in plain language, instead of leaving you to decode an error code while customers wait.

Because Convo360 is a bring-your-own-keys platform, this is billed by Meta to you directly with no markup added. You see exactly what Meta charges, which also means you can verify the numbers against Meta's own reporting rather than taking anybody's word for it.

Should you try to reduce service conversations?

Mostly, no. A service conversation exists because a customer wanted something, and discouraging that to save eleven paise is poor economics.

There are two exceptions worth acting on. The first is repeat conversations caused by your own silence: a customer writing on three consecutive days because nobody replied is three conversations that should have been one. Faster first response genuinely reduces the count.

The second is questions caused by missing information. If hundreds of customers write to ask where your returns policy is, fixing the page removes those conversations permanently. That is worth doing for reasons that have nothing to do with the bill.

What is not worth doing is making yourself harder to reach. Businesses that hide the WhatsApp number to reduce volume reliably discover that the enquiries simply become lost sales instead.

A short checklist before 1 October

Four things, none of which take long.

1. Add a payment method in Meta Billing Hub and confirm it is attached to the right WhatsApp Business Account.
2. Check your current volume. If you are already above 1,000 service conversations a month, budget for it rather than being surprised.
3. Watch the meter in Convo360 for the first month so you learn your own pattern, particularly around festivals.
4. Tell whoever pays the bills that a new charge will appear, so nobody cancels a card that is now keeping your customer support running.

The last one causes more outages than the technical steps. A small recurring charge from Meta on a company card is exactly the kind of thing a finance team queries and blocks, and the consequence lands on your support queue three days later.

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.