WhatsApp Business API pricing in India: what it costs beyond the message rate

"How much per message?" sounds like a precise question. It still leaves most of a WhatsApp project unpriced.

An institute may need an admissions inbox, reminders and a connection to its student records. A retailer may need order notifications and staff handover. The message rate pays for delivery. It doesn't tell you who maintains those workflows or what the provider charges for the inbox.

There's also a recent change to check before reusing last month's budget. Meta's official FAQ says service messages became chargeable from 1 October 2026, after the first 1,000 service messages per business phone number each month. A budget that assumes unlimited free customer-service replies needs review.

Separate the Business app from the Business Platform#

The WhatsApp Business app and the WhatsApp Business Platform are different products. The Platform provides programmatic access for integrations, either directly from Meta or through solution providers. Meta's FAQ says there is no extra Meta fee to access the Platform directly; partners may charge for their services.

Direct access doesn't include a shared inbox or your workflow. Someone still has to build or supply the screens, permissions and connections your staff use.

If one person handles messages by hand and nothing needs to connect to a CRM, the app may be enough. Ask what problem the API will solve before buying it. For an institute, a useful brief might be: place each enquiry in the admissions system, assign it to a counsellor and show whether the student booked a visit. That is a workflow someone can demonstrate and price.

Know which messages you send#

Meta distinguishes four categories. The examples below illustrate their purposes; Meta's review and current rules decide the actual classification.

Meta's category pages for marketing, utility, authentication and service explain each one.

A payment confirmation with a course discount added isn't the same message as a plain confirmation. Don't forecast by assigning every template the cheapest category. Show the provider the actual text, including buttons and promotional content, and ask for its current classification.

The 24-hour window is a permission rule, not your whole budget#

Under Meta's Business Messaging Policy, a customer message opens or resets a 24-hour service window in which you may reply without an approved template. Outside it, messages must use approved templates. That governs how you may send; pricing is a separate check.

At the time of writing, Meta's documents disagree. The general pricing page still describes service messages in the window as free, while the FAQ explicitly announces per-message service charges from 1 October 2026 with a 1,000-message monthly allowance per business phone number.

For planning, I'd use the dated October announcement and ask the provider to confirm the applied rates and exemptions in writing. Don't infer an INR service rate from this article, and don't reuse the old assumption that a reply inside 24 hours always costs nothing.

Meta also advertises a free-entry period after eligible click-to-WhatsApp ads or Facebook Page entry points. Confirm its current conditions for your account before deducting those messages, and remember the ad spend itself needs a budget.

A calculator you can put in a spreadsheet#

Use one row per recipient market and category, counting delivered, chargeable messages after confirmed exemptions, not contacts or API requests. Define:

• M, U, A and S as chargeable delivered marketing, utility, authentication and service messages;
• rM, rU, rA and rS as their applicable rates;
• P as provider or software charges, and O as monthly operation and integration costs.

For a simple case without volume tiers, the pre-tax monthly amount is:

Meta message charges = M × rM + U × rU + A × rA + S × rS
Monthly operating amount = Meta message charges + P + O

If several countries, tiers or special rates apply, calculate separate rows and add them. Meta says volume-tier rates apply to the messages within each tier, so multiplying every message by the cheapest tier understates the cost.

Count the service allowance per business phone number. With 800 service messages on one number and 1,500 on another, only the second number exceeds the allowance, by 500. Pooling the traffic and subtracting one allowance gives the wrong answer.

A worked monthly budget#

One business phone number. Every rate and charge here is invented for the arithmetic, not Meta's tariff, a provider quote or our price, and no extra exemptions or tiers apply.

Meta message charges

₹10,400

Provider software

₹2,500

Monthly total before tax

₹12,900Excludes setup, ads, staff time and tax

Change the message mix and the total moves. Sending fewer promotions may save more than shortening a handful of support replies, and splitting one helpful answer into several messages may raise a per-message bill. Measure the real flow before redesigning it around cost.

If the provider adds a per-message markup, add a column. If it charges per agent, number or automation run, add rows. Ask whether prices include tax and whether unused prepaid credit expires.

What a provider quote should show#

Ask for a sample invoice built from your own message inventory, separating Meta's charges from the provider's, with the rate-card date and billing currency visible. Then get written answers to these:

1. Which inbox functions, agent seats and phone numbers are included?
2. Are templates, automation runs, API calls or AI usage priced separately?
3. Can we export messages and delivery records for reconciliation?
4. Who owns and administers the business account and phone number?
5. What happens to the number, templates and customer records if we change provider?
6. Who fixes the integration when the CRM or a Meta rule changes?
7. What support is available during admissions season or a campaign launch?

The cheapest software plan may be enough, or it may leave out the exact connection your staff need. Compare every quote on the same workflow, whatever its headline subscription. Our coaching platform comparison uses the same approach.

Cut wasted messages without making support worse#

Start from the events that should send a message. A successful payment might produce one confirmation; a failed payment may need a different action; a reminder should disappear if the booking is cancelled. Those rules need a connection to the system that owns the payment or booking, because a timer can't tell whether the customer already acted.

Use a stable event identifier so a retried notification can't send duplicates, and record the business event, template, recipient, delivery result and the provider's billing information. That makes an unexpected bill easy to investigate.

Keep consent records and honour opt-outs. Meta's policy requires permission for later messages, respect for requests to stop and clear escalation when automation answers customers. A bot that repeats itself while a parent asks for a person is an operational problem whatever the price per message. For the data around these workflows, see our DPDP engineering checklist.

Budget the workflow before the integration#

Export a recent sample of incoming and outgoing messages and group them by purpose and recipient market. Mark which business events should send them, which can be combined and which should stop when the customer opts out or completes the action.

That inventory is enough to request a meaningful quote and estimate a first month. After launch, compare actual delivered-message charges against it, and keep the effective rate card with the spreadsheet so next month's forecast has a clear basis.

If you need an admissions, booking or retail workflow connected to WhatsApp, send us the current process and the systems involved. We'll map the messages and handovers, check the provider requirements and scope the integration separately from the recurring usage bill.

Sources#

Checked 4 October 2026. The current INR tariff was not independently retrieved.

• Meta, WhatsApp for Business FAQ: the per-message model, partner charges and the service-message change from 1 October 2026, with the 1,000-message monthly allowance per number.
• Meta, Business Platform pricing: delivery-based charges, categories, markets, volume tiers and free entry points. Its service-free wording conflicts with the FAQ.
• Meta, pricing documentation and rate cards, linked for you to verify the tariff.
• Meta, Business Messaging Policy, updated 23 September 2026.