WhatsApp Business pricing India changed on 1 October 2026, but businesses did not lose every free customer-support reply. Meta now gives each Business Platform phone number 1,000 free delivered service messages every month. It charges for the 1,001st and subsequent service messages. If a business has no payment method, Meta says it will still deliver messages within that free allowance; delivery stops only after that number uses its monthly allowance.
Key takeaways
- Meta’s dated developer documentation says the 1,000-message monthly free tier applies per business phone number, not per company or account.
- A business without a payment method can use that free tier. Once it is exhausted, Meta says further service messages will not be delivered until billing is available or the allowance resets.
- The change concerns the WhatsApp Business Platform used through an API. It is not a claim that the separate WhatsApp Business mobile app now charges its users per reply.
- Meta bills service messages when they are delivered, and unused free messages do not roll into the following month.
The distinction matters to Indian retailers, startups and customer-service teams that built their support workflow around a previously free conversation window. A blanket warning that an account without a card can no longer answer any customer is incorrect. The actual operational risk is narrower and measurable: a phone number can keep replying within its allowance, then run out of deliverable replies later in the month if the business has no payment method. That makes usage visibility and billing readiness more important than a generic warning to stop using the channel.
Meta’s WhatsApp Business Platform pricing documentation, updated for 1 October, is the primary source for the rule. Moneycontrol, Business Standard and Mint each reported the pricing change. Some secondary coverage compresses the billing warning into a total cutoff; the narrower rule in Meta’s dated developer document governs the explanation below.
WhatsApp Business pricing India: what changed?
Meta began charging for service messages on the WhatsApp Business Platform from midnight in a messaging account’s time zone on 1 October 2026. A service message is generally a business’s free-form response inside an open customer-service window after a person contacts it. Such replies had been free. Meta now provides 1,000 free delivered service messages per business phone number each month, then applies its service-message rate to further deliveries.
That is different from saying that every customer question now triggers a fee. A customer sending a message to a business is not itself a Meta-billed business message. Nor is every message a service message. The category, whether Meta delivers it, the open customer-service window and the phone number’s remaining free allowance all matter. A finance or operations team should separate these events before forecasting costs.
Meta says the free allowance resets monthly according to the messaging account’s time zone. Unused messages do not carry forward. The first thousand are not a one-time promotional balance and are not pooled across all numbers owned by a business. A company with multiple numbers therefore needs a count for each number, while a business using one shared number cannot borrow unused allowances from another number after that shared line crosses its threshold.
What happens without a payment method?
Meta’s developer guidance is unusually explicit: if a business has no payment method, Meta will deliver service messages within the free tier and will not deliver them after the tier is used. The phrase “without a payment method” therefore does not mean immediate suspension at the first reply. It means the business cannot continue delivering service messages beyond the 1,000-message monthly allowance unless it arranges payment or waits for the next monthly reset.
Consider an illustrative support line that sends 900 delivered service messages in a month. Under Meta’s stated rule, all 900 fit inside the free tier. If it sends 100 more, those also fit. The next deliverable service message would be number 1,001: a line without a payment method would not deliver it, while a line with billing would incur the applicable charge. These are arithmetic examples of the published threshold, not predictions about any particular company’s bill or traffic.
Another example shows why a month-end count is not enough. Imagine a retailer with two API phone numbers: one has delivered 1,100 service messages, while the other has delivered 700. Meta assigns each number its own allowance, so the first number has crossed its threshold while the second has not. A company-wide sum of 1,800 would conceal which line faces delivery interruption. This matters when separate numbers handle sales, returns and after-sales help.
Businesses should also avoid describing the post-threshold outcome as a silent drop. Meta’s documentation states the delivery rule, but the precise response visible to a company depends on its API implementation and provider. Teams should inspect delivery status and billing alerts in their own tools, rather than assuming every failed message appears in the same way. Customer inquiries can still arrive even when the business has exhausted deliverable outgoing service replies.
Which WhatsApp product does the change cover?
The pricing document addresses the WhatsApp Business Platform, the API-based product used by companies and software partners to integrate chat with customer-support desks, sales tools and automated workflows. This is the product in which businesses manage templates, phone numbers and a messaging account. It should not be conflated with the WhatsApp Business mobile app installed by a local shopkeeper to speak with customers from a phone. The 1,000-message API rule is not evidence that the free mobile app has adopted an identical per-reply fee.
This distinction is especially relevant for Indian small businesses. A merchant may start on the mobile app and later move customer conversations to an API provider to distribute chats among staff or connect them to an order system. The change in commercial terms attaches to the Platform workflow, not simply to the WhatsApp name on the phone screen. A provider’s dashboard or invoice may contain charges beyond Meta’s network fee; the business should distinguish provider service fees, taxes and Meta message fees rather than treating one displayed price as universal.
Meta’s categories matter as well. The service-message allowance is for service messages, not a free pool for marketing templates. Utility and authentication templates have their own rules and rate cards. A business should verify the category of each outgoing template before it assumes that a message can use the service allowance. A wrongly classified campaign may produce a very different cost pattern from an agent replying to an existing customer.
What can an Indian business do now?
The first task is to identify whether it uses the WhatsApp Business Platform at all. Teams running only the Business mobile app should not apply API billing instructions to themselves. Platform users should list their business phone numbers, messaging accounts and providers, because the allowance is tracked by number and the reset is tied to the account’s time zone. If a software provider manages billing, its terms may determine which payment method Meta sees and how charges appear on the customer’s invoice.
Second, measure delivered service messages, not only chats opened, users served or messages attempted. Meta’s rule is attached to delivered messages. A support interaction with several separate business replies may consume several units. Conversely, an inbound customer message is not a billed outgoing service message. Build a weekly view by phone number and a daily alert near the monthly threshold so a support team can respond before its busiest number loses delivery.
Third, test the contingency before the allowance runs out. A team should know who can add or update the payment method, whether a provider pays Meta and rebills the company, and what operational alert appears when a delivery is refused. Do not ask agents to send fewer helpful replies merely to game the meter; an abrupt interruption to returns, banking or delivery support can damage the customer experience. The better choice is to forecast normal volume and secure a working billing route where traffic routinely exceeds the free allowance.
Fourth, examine templates separately. Campaign teams may use marketing, utility or authentication categories, each with separate rates and conditions. An open service window does not turn every outbound template into a free service message. Meta’s pricing page and the relevant rate card, rather than an old spreadsheet or a provider’s sales summary, should govern budgeting. Rate cards can vary by country and message category, and provider charges may be layered on top.
Finally, review the experience from the customer’s side. A person who writes to a brand does not see its billing dashboard. If the business exceeds the allowance without a payment method, the customer may simply wait for a response that cannot be delivered. A support leader can prepare an alternative contact path on the website, update internal escalation procedures and examine the API’s actual delivery-status signals. Those are prudent operational steps, not claims that Meta has prescribed a particular help-desk design.
Why the free allowance changes the business case
The allowance is a material difference between two stories: “all support becomes paid” and “support remains free until a per-number monthly threshold.” The first overstates the exposure of a low-volume company; the second identifies a discontinuity for a busy number. A startup with a few hundred support replies may remain within Meta’s free service tier. A larger retailer whose teams send thousands of replies on one line must plan for usage-based charges and billing continuity. Neither outcome can be generalized from the company’s headcount or revenue alone; delivered message volume is the operative measure.
Moneycontrol, Business Standard and Mint each reported the broader shift in Indian business-messaging costs. Their reports are valuable context, but the operative free-tier and no-payment language should come from Meta’s dated technical documentation. That distinction also matters because Meta’s general WhatsApp Business pricing landing page may lag an effective developer-policy update. When the two descriptions conflict, businesses should consult the dated Platform documentation and their account billing interface for the current rule.
There is a wider platform lesson for companies treating messaging as core infrastructure. A channel that looks free during early adoption can acquire a marginal cost as usage scales. It is sensible to model the customer-support workflow in the same way a company models cloud usage: identify the unit charged, who controls it, the point at which a free tier ends, and what happens when payment fails. The calculation belongs beside service quality, not in place of it. Reducing messages at the expense of solving customer problems may cost more than the messaging fee saved.
Lapaas Voice has previously covered Meta’s separate WhatsApp Business Agent pricing. That AI-agent product is a different commercial layer from the service-message allowance described here. We have also examined Meta’s small-business AI tools and their geographic limits; neither story should be read as a substitute for the Platform’s current messaging rate card. The key comparison for an Indian business is its own mix of service replies, templates and any separate agent or provider fees.
Frequently asked questions
Are all WhatsApp Business replies paid from 1 October 2026?
No. For the WhatsApp Business Platform, Meta says each business phone number receives 1,000 free delivered service messages per month. The 1,001st and subsequent service messages are chargeable. This rule concerns service messages, not every type of outbound message or the separate Business mobile app.
Will an account without a payment method stop replying immediately?
No. Meta says it will deliver service messages within the free tier even without a payment method. After that phone number has used its 1,000 free messages for the month, further service messages will not be delivered without billing. The threshold resets monthly in the messaging account’s time zone.
Can unused free messages be carried into the next month?
No. Meta’s documentation says unused service messages do not roll over. The allowance is also attached to each business phone number, so an unused balance on one number cannot be treated as a shared balance for another.
Does this change the free WhatsApp Business mobile app?
The announced pricing rule is documented for the API-based WhatsApp Business Platform. It should not be presented as a per-reply charge for every shop using the separate mobile app. Businesses should confirm which product and provider they actually use before making changes.
Source note: This article follows Meta’s developer pricing document updated for 1 October 2026. Independent coverage consulted: Moneycontrol, Business Standard and Mint. Examples are illustrative; they are not company bill estimates. This report was updated to clarify the 1,000-message free tier and correct an earlier overbroad description of payment-method requirements.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.



