Ask five vendors what a WhatsApp chatbot costs and you will get five numbers that cannot be compared, because each is quoting a different layer of a three-layer cake. The layers are Meta's per-conversation fee, the platform or BSP fee on top, and the cost of building the bot itself. Once you separate them, the pricing pages stop being confusing and start being merely optimistic.
Here are all three layers in rupees, what moves each one, and the cases where the honest answer is that you do not need the bot yet.
Layer one: Meta's per-conversation fee
Meta charges per 24-hour conversation window, and the rate depends on who started it and why. Marketing conversations — you message the customer first with a promotion — cost the most, roughly ₹0.78–₹0.88 in India. Utility conversations — order updates, appointment reminders — run lower. Service conversations — the customer messages you — are cheapest, and user-initiated windows have a free tier. Rates adjust; Meta publishes the current card, and any quote you get should name which categories it assumes.
The practical consequence: a bot that mostly answers inbound questions costs a fraction of one that blasts promotions. The conversation mix is the single biggest driver of the monthly bill, and it is the one most pricing pages leave out.
Layer two: the platform or BSP fee
You do not talk to Meta's API directly; you go through a Business Solution Provider or a platform built on one. Their pricing takes three shapes: a flat monthly fee (₹1,000–₹10,000+ depending on contacts and features), a per-message markup on Meta's rates, or a per-agent-seat model borrowed from helpdesks. Wati, AiSensy, Interakt and their peers all land somewhere in this space, and the advertised price is usually the entry tier that assumes you will not read the overage table.
The trap to avoid: per-message markups look tiny until you multiply by real volume. A ₹0.15 markup on 50,000 monthly conversations is ₹7,500 of pure margin for the platform. Flat-fee-plus-Meta-at-cost is the structure to push for, and the one we use.
Layer three: the build
A template bot that answers five FAQs from a menu costs almost nothing and is worth it. A bot that qualifies a lead, checks real order status from your system, books a slot, hands to a human with full context when it is stuck, and logs everything — that is a custom build, priced once as a project. The range is wide because the work is wide, but it is a fixed number you agree before anyone writes code, not a subscription that grows with your success.
When a WhatsApp bot is the wrong spend
If your customers do not already message you on WhatsApp, a bot does not create the habit — it automates an empty queue. If your volume is a handful of conversations a day, a human with the Business app is faster to deploy and free. And if the honest goal is broadcast marketing to cold lists, the economics and Meta's quality rating will both punish you within weeks. The bot pays when the conversations already exist and the humans answering them are drowning.
What we charge
We build the custom layer and pass Meta's fees through at cost — no per-message markup. The build is a fixed project price sized to the workflows, and a third of our fee rides on the number the bot is supposed to move. The audit prices your actual conversation mix, not a tier on a pricing page.