WhatsApp Business API to Charge Per Message in India Starting October 1: Rates, Free Tier, and Enterprise Impact

Starting October 1, 2026, Meta is updating the commercial structure of its WhatsApp Business Platform (API), ending the era of unlimited free customer support conversations. Under the revised pricing model, enterprises and Business Solution Providers (BSPs) in India will be billed on a per-message basis for service-related replies at an effective cost of approximately 14 paise per delivered message (including 18% GST and typical platform routing fees) after exhausting a monthly free allowance of 1,000 messages per business phone number.

The pricing change applies exclusively to commercial enterprises operating through the paid WhatsApp Business Platform (Cloud and On-Premises API)-the developer gateway integrated with CRM systems, customer support desks, and automated AI routing engines. The change does not affect consumer WhatsApp accounts or the standard, free-to-use WhatsApp Business app utilized by local merchants and small business owners.

Understanding the 1,000-Message Free Allowance

For the past two years, Meta allowed brands to send unlimited free-form customer service replies at zero platform fee, provided the replies occurred within an active 24-hour Customer Service Window (CSW) opened by an inbound user query. The new update brings this open-ended period to a close:

• 1,000 Free Messages Per Phone Number: Each individual business phone number linked to a WhatsApp Business Account (WABA) receives an allocation of 1,000 free delivered service messages per calendar month.
• No Account-Level Pooling: The free allowance is bound strictly to the specific registered phone number; high-volume lines cannot pull unused quotas from secondary or dormant numbers within the same business manager.
• Use-It-or-Lose-It Allocation: Unused quotas do not roll over into subsequent billing cycles and reset automatically at midnight on the first day of each calendar month.
• Shared Across Human Agents and Bots: The 1,000-message buffer is consumed collectively by all live support agents, rule-based chatbots, and integrated AI assistant responses. Once message 1,001 is delivered in a given month, every subsequent outbound reply is billed.

India Rate Card & What Changes on October 1

Alongside customer service replies, Meta is also removing the free status of utility templates sent inside active conversation windows:

Message Type & Interaction Scenario	Pricing Before Oct 1, 2026	Pricing from Oct 1, 2026 (India)
Service Messages (Replies in 24h Window)	Free & Unlimited	First 1,000 Free/mo; then ~₹0.1150 + GST (~14 paise total)
Utility Templates (Sent Inside 24h Window)	Free	Billable at ₹0.1150 + GST (~14 paise total)
Utility Templates (Sent Outside Window)	₹0.1150 + GST	Unchanged (₹0.1150 + GST)
Authentication / OTP Templates	₹0.1150 + GST	Unchanged (₹0.1150 + GST)
Marketing Promotional Templates	₹0.8631 + GST	Unchanged (₹0.8631 + GST)
Incoming Customer Messages	Completely Free	Always Free (Zero inbound platform charge)
Click-to-WhatsApp (CTWA) Ad Chats	72-Hour Free Window	Always Free (72-hour window fully preserved)

Enterprise & BPO Impact: The End of “Chatty” Multi-Part Replies

The shift directly impacts customer-support-heavy industries, direct-to-consumer (D2C) brands, logistics aggregators, and Business Process Outsourcing (BPO) centers:

• Cost Multipliers on Fragmented Chats: Previously, customer support agents and automated bots frequently split answers across multiple separate bubbles (e.g., sending “Hello,” followed by “Let me check that,” followed by “Here is your link”). Under the new structure, a three-bubble interaction that previously cost nothing will now cost roughly 42 paise if delivered outside the monthly free tier.
• D2C Order Confirmations & Tracking: Brands running continuous Cash-on-Delivery (COD) confirmations, address verifications, and delivery queries within open chat windows will see line-item additions on their monthly Communication Platform as a Service (CPaaS) invoices.
• Disincentivizing Conversational Spam: Meta’s strategic rationale centers on streamlining communication. By assigning a nominal per-message cost to service interactions, the platform discourages automated multi-message bloat, incentivizes concise responses, and aligns WhatsApp support costs more closely with alternatives like transactional SMS and Rich Communication Services (RCS).

How Enterprises Are Adapting Ahead of the Deadline

To avoid ballooning communication expenses, companies and product managers are restructuring their conversational architecture:

1. Deploying WhatsApp Flows: Instead of running sequential multi-step chat questionnaires that consume 5 to 8 billable replies, companies are shifting to WhatsApp Flows-native, interactive forms that capture user intent, address modifications, or return requests in a single structured interaction.
2. Consolidating Bot and Agent Logic: Engineering teams are reprogramming conversational bots to synthesize answers into a single, comprehensive text bubble accompanied by rich cards, menus, or document attachments.
3. Multi-Channel Fallback Pipelines: For non-urgent operational updates (such as shipment dispatches or routine invoice links), enterprises are configuring automated routing rules that prioritize transactional SMS or RCS, triggering WhatsApp delivery only when primary channels fail or when an active engagement is established.
4. Mandatory Billing Thresholds: CPaaS aggregators such as Gupshup, Wati, Exotel, and Sinch are actively urging enterprise clients to add valid payment instruments and configure automated budget capping before October 1 to prevent automated customer support lines from unexpectedly pausing mid-conversation.

Via