WhatsApp Business Service Messages Now Cost Money: What Indian SMBs Should Do

If you run a clinic in Pune, a D2C skincare brand out of Bengaluru, or a tuition centre in Lucknow, there is a fair chance WhatsApp is where your customers actually talk to you. Appointment confirmations, order updates, payment receipts, delivery OTP follow-ups: these are the messages that keep a small business running. Until now, many Indian SMBs have treated these "service" conversations as effectively free once they were on the WhatsApp Business API. That assumption is about to cost you money.

From October 1, Meta is moving to per-message charges for service messages sent through the WhatsApp Business Platform, with a rate of roughly Rs 0.115 per message for India. On paper that looks trivial. Multiply it by 40,000 order updates a month and you have a line item of around Rs 4,600 that did not exist before. Scale to a few lakh conversations and you are negotiating a new budget head. Most SMB owners we speak with have not yet run that multiplication, and that is the gap this article is meant to close.

Below, we walk through what the change actually is, how to audit your own message volume, how to think about the category system that determines what you pay, and how to put together a realistic budget. If you are searching for WhatsApp Business API pricing India 2026 to plan next quarter, this is the working version of that answer, not a summary of Meta's pricing page.

Key Takeaways

• Service messages on the WhatsApp Business API move to per-message billing from October 1, at roughly Rs 0.115 per message in India.
• Messages inside an open 24-hour customer service window are the main exception, so the timing and triggers of your messages matter as much as their volume.
• Audit your last 90 days of outbound traffic by template category before you change anything. Most SMBs find that 20 to 30 percent of their volume is avoidable or misclassified.
• Marketing and utility messages are priced differently from service messages, so mis-tagging a promotional message as a service message is the most expensive mistake you can make.
• Budget per conversation outcome, not per message, and build a 25 percent buffer for seasonal spikes like Diwali, Eid, and the financial year-end rush.
• Pick a provider whose invoicing you can reconcile with your GST filings, because the new line items will need to show up cleanly in your books.

WhatsApp Business API pricing India 2026: what actually changes on October 1

Before this change, the WhatsApp Business Platform charged for template messages (the pre-approved messages you send outside a customer's active window) and for some conversation types, but a large share of customer-initiated, service-oriented conversations were not billed. The new structure extends per-message charges to service messages on the same logic that already applied to other conversation categories. The practical effect is that more of your traffic now shows up on an invoice.

Three things are worth separating in your head. First, the rate: Rs 0.115 is the headline figure for service messages in India, and it is per message rather than per conversation, which matters when a single exchange involves several outbound notifications. Second, the window: a customer who messaged you recently opens a 24-hour customer service window, and replies you send inside that window have historically been treated differently from proactive outbound messages. Third, the tax layer: the amounts you see in your dashboard are typically exclusive of GST, so your effective cost is higher once the 18 percent is added where applicable. Confirm with your provider how they present this, because a budget built on pre-GST numbers will be short.

Do not assume that every rate and rule is frozen. Meta revises pricing, and provider-level markups differ. Treat any figure in a blog post, including this one, as a starting point to verify against the current rate card in your Business Manager before you commit spend.

How do I audit my WhatsApp message volume before the billing change?

The audit is the most valuable thing you can do this month, and it takes an afternoon. The goal is to answer one question for every template and every automated flow: what triggers this message, who receives it, and was that customer already in an active service window when it went out?

Here is a working procedure we use with clients:

1. Export 90 days of outbound logs. Pull message-level data from your provider's dashboard or from your BSP (Business Solution Provider) portal. You want template name, send timestamp, recipient, and delivery status. If your provider only gives aggregate counts, ask for the raw export now; it is a reasonable request.
2. Group by template and by trigger. Build a simple sheet with one row per template: order confirmation, OTP, appointment reminder, payment failed, abandoned cart, review request, and so on. Add a column for the business event that causes it.
3. Tag each template by its real purpose. Is it a reply to something the customer asked? A transactional notice tied to an action they took? Or is it a nudge that would have gone out regardless of any action? Be strict. Most "service" messages that are really promotions get caught here.
4. Measure the window share. For each template, estimate how often the message is sent inside an open customer window versus cold. Cold, proactive sends are where costs concentrate.
5. Calculate exposure. Multiply monthly volume by the applicable rate, then add GST. Do this for the current month and for a projection assuming 15 percent growth.

Worked example: a 15-person logistics company in Gurgaon

A logistics firm we worked with in Gurgaon runs dispatch for about 900 deliveries a day across NCR. Their WhatsApp program sends a pickup confirmation, an "out for delivery" notice, a delivery OTP, and a feedback request for every shipment. That is four messages per delivery, roughly 108,000 messages a month before anyone looked closely.

The audit showed three things. The feedback request was going to every customer, including those who had already rated the delivery in-app, so about 30 percent of those sends were duplicates. The "out for delivery" notice was firing even for same-hour deliveries where the OTP message arrived seconds later, making it redundant. And the OTP was correctly a transactional, necessary send, so it stayed. After removing the duplicate feedback sends and merging the two dispatch notices for same-hour routes, their volume dropped to about 71,000 messages a month. At the Rs 0.115 headline rate, pre-GST, the exposure fell from roughly Rs 12,400 to about Rs 8,200 monthly, and their feedback response rate actually went up because the surviving request reached customers who had not already answered.

The lesson is not that every company can cut 35 percent. It is that the audit surfaces decisions you were making by accident.

Which message categories should I use to keep costs down?

Meta classifies templates into categories, and the category you choose at template creation determines how the message is billed and whether it is approved. Choosing the wrong one is not a clerical error you can ignore. Mis-categorising a promotion as a utility or service message can get the template rejected or flagged, and in some cases it means you are paying the wrong rate on every send.

In practice you are deciding among marketing, utility, and authentication messages, with service conversations handled through the customer window. Authentication covers OTPs. Utility covers transactional updates tied to a specific customer action or account, such as order status, appointment changes, or payment reminders for an existing invoice. Marketing covers anything promotional, including offers, re-engagement, and cross-sell.

Pro tip: the most common expensive mistake we see is a "payment reminder" that is really a discount nudge. If the message says "pay now and get 10 percent off," it is marketing, regardless of what you call it internally. Write the template copy so it reads like what it is, and categorise it honestly from the start. A utility template that drifts into promotional language will eventually be reviewed and either rejected or repriced.

Choosing a provider: what to compare

Your provider choice affects how easily you can see and control spend. The table below compares the criteria that matter most to Indian SMBs. Treat the qualitative ratings as a framework to fill in with current quotes, not as fixed facts.

Criterion	Direct Meta onboarding	Tier-1 BSP (enterprise-focused)	Indian BSP / SMB-focused provider
Setup complexity	High; requires Business Manager and verification	Moderate; handled for you	Low; guided onboarding
Per-message transparency	Direct from rate card	Rate card plus platform fee	Varies; ask for itemised invoice
Platform or markup fees	None beyond message rates	Typically present	Typically present, sometimes bundled
GST-ready invoicing	You manage it	Usually supported	Usually supported; confirm the GSTIN on invoice
Support for SMB volumes	Limited hands-on help	Often priced for larger accounts	Strong fit for small teams
Best for	Technically strong in-house teams	Large, multi-market programs	Indian SMBs needing support and rupee billing

Whichever route you take, ask every provider the same four questions in writing: what is the all-in per-message cost in rupees including platform fees, how are messages inside the customer window billed, can the invoice carry my GSTIN and show per-category line items, and what happens to my templates if the rate card changes mid-contract.

How should an Indian SMB budget realistically for customer engagement?

Budgeting per message is the wrong unit. It produces a number that looks small and then surprises you in February. A better unit is cost per successful outcome: cost per confirmed appointment, per completed order, per recovered cart. That framing lets you compare WhatsApp spend against SMS, email, or a phone call on the same terms.

Start with your monthly outcome targets. Suppose a diagnostic clinic in Jaipur targets 1,200 booked appointments a month and needs about three WhatsApp touches per booking (confirmation, reminder, and a post-visit follow-up). That is roughly 3,600 messages, or about Rs 414 pre-GST at the headline rate, which works out to around Rs 0.35 per booking. Set that against the value of a booking and the decision is easy. But if you have 40 percent no-shows and a reminder that is not converting, the cost per attained visit is the number to watch.

Build your budget in four steps:

1. Forecast message volume by template for the next six months, using the audited baseline.
2. Add a 25 percent buffer for seasonal peaks. Diwali, Eid, Christmas sales, and the March financial year-end all push volume up, and so do festive campaigns from competitors that raise the noise your customers ignore.
3. Add GST and any platform fee to get a true landed cost.
4. Divide by expected outcomes to set a cost-per-outcome ceiling you will review quarterly.

If you are weighing WhatsApp against bulk SMS for reminders, the comparison belongs on this same per-outcome basis. Our bulk SMS services team regularly helps clients run that side-by-side, and it often shows that the right answer is a mix rather than a switch.

Common mistake: budgeting only for new sends

The mistake we see most often is budgeting for the messages you intend to send and forgetting the ones your systems send without you thinking about them. Retries on failed deliveries, webhook-triggered notifications, and duplicate sends from two integrated tools (a CRM and an e-commerce platform both firing the same order update) can add 10 to 20 percent to your real volume. Pull a week of raw logs and count every outbound message, not every template you designed. The gap between the two numbers is usually where your budget leaks.

What should my implementation checklist look like before October 1?

If you are running WhatsApp through a provider, you do not need to rebuild anything. You do need to make sure the change does not catch you mid-campaign. Work through this list with your team or your vendor:

1. Confirm your Meta Business Manager is verified and that the payment method on file is current, so sends do not fail on a billing hiccup.
2. Export and archive your current template library with categories, since you will want a record if a template is recategorised.
3. Re-tag every template against the audit. Remove or merge duplicates, and rewrite any promotional copy hiding inside a utility template.
4. Add a suppression rule so that customers who have already acted (rated, paid, confirmed) are not sent the follow-up.
5. Set a daily spend alert in your provider dashboard so a runaway flow is caught in hours, not at invoice time.
6. Get written confirmation of the invoice format, including GSTIN and per-category breakdown, and brief your accountant before the first October invoice arrives.
7. Run a two-week dry period in late September where you log what the new billing would have cost against actual sends, so the first real bill is not a surprise.

Your accountant matters here more than people expect. Ask them how the new line items will be recorded and whether the input GST on platform charges is claimable under your registration. Getting that right in October saves a reconciliation headache in the quarter-end close.

Is WhatsApp still worth it for an SMB after the pricing change?

For most businesses that rely on it, yes, but the case has to be made on outcomes rather than convenience. A WhatsApp message that gets read within minutes and drives a booking or a payment is still among the cheapest high-attention channels available. The change does not make it expensive; it makes it visible. That is a good thing, because a channel you cannot see the cost of tends to be over-used.

If you are still deciding how WhatsApp fits alongside advertising and paid acquisition, our earlier write-up on WhatsApp marketing ROI in 2026 for Indian SMBs walks through how to measure return on that spend. For a broader view of tools that help small teams spend efficiently across channels, see AI advertising tools for Indian SMBs in 2026.

If you want background on how the per-message model is shaping up across providers, two related posts go deeper: WhatsApp Business API per-message pricing: what Indian SMBs will pay now and WhatsApp Business API per-message costs in India. For the latest rate-change timeline, see WhatsApp Business API pricing changes in 2026.

Frequently asked questions

How much do WhatsApp service messages cost in India from October 2025?

Service messages move to per-message billing with a headline rate of roughly Rs 0.115 per message in India, typically quoted before GST. Check the current rate card in your Meta Business Manager, since rates and provider markups can change.

Are messages sent within the 24-hour customer window free?

Replies sent inside an open 24-hour customer service window are treated differently from proactive outbound sends. Design your flows so that as many customer-initiated conversations as possible stay inside that window, and verify how your provider bills them.

Do I need to pay GST on WhatsApp Business API charges?

Platform and messaging charges generally attract GST at the applicable rate for your provider's invoice. Confirm with your provider and your accountant, and make sure invoices carry your GSTIN so input credit can be claimed where eligible.

What is the cheapest way to send WhatsApp messages for a small business?

The cheapest message is the one you do not send. Audit your volume, remove duplicate and redundant notifications, keep messages inside the customer window where possible, and categorise each template honestly. Compare cost per outcome rather than cost per message.

Can I switch WhatsApp providers without losing my templates?

Templates are tied to your WhatsApp Business Account, so migration is usually manageable, but it requires planning. Export your template library first, confirm the new provider will re-register the same templates, and avoid switching during a peak sending period.

How do I stop WhatsApp costs from spiking during Diwali or sales?

Forecast peak volume using last year's logs, add a 25 percent seasonal buffer, set daily spend alerts, and cap any promotional flows with a volume limit. Review campaign performance daily during peaks so you can pause underperforming sends quickly.

Should I use WhatsApp or SMS for appointment reminders?

It depends on your cost per attended appointment, not on message price alone. Run both channels for a few weeks, track no-show rates and cost per confirmed visit, and choose the mix that performs best for your customer base.

Where eDarpan can help

If you would rather not run this audit alone, eDarpan works with Indian SMBs on exactly this kind of cost review: pulling message logs, re-tagging templates, and building a budget your accountant can sign off. Our WhatsApp Business API team can handle setup and migration, and our IT consulting engagements cover the broader question of which channels to fund. For teams that also need help with the systems behind their messaging, see our cloud migration and managed services and custom software development offerings.

Ready to see where your WhatsApp spend is going before the first October invoice arrives? Contact eDarpan for a no-obligation message audit, or read more about who we are and how we work.

The bottom line

The October change is not a reason to abandon WhatsApp. It is a reason to stop treating your customer messaging as a free background utility and start managing it like any other cost line. Audit what you send, categorise it honestly, measure cost per outcome, and build a buffer for the seasons that will test your budget. Do those four things in September and the first bill will hold no surprises.

Image credit: Out of business by kevin dooley via flickr (BY 2.0), sourced through Openverse.