WhatsApp Business API Pricing Guide 2026 (India)
How WhatsApp Business API pricing works in 2026 — per-message billing, the four categories, the free 24-hour window, fees, and an India budget example.
Read the guideInfiQ Flows
Draw the conversation. We'll have it.
Build a WhatsApp bot by dragging blocks onto a canvas. It replies in seconds, remembers every customer forever, connects to your systems, and hands to your team at exactly the right moment.
No codeLive in 2 hoursBuilt for Indian businessesapp.infiq.in/flowsOrder-status bot
Live
A real flow: drawn on the canvas, executed on WhatsApp — exactly as drawn.
27
building blocks
Messages, questions, actions, logic — drag them onto the canvas.
10
message types
Text, buttons, menus, media, location and approved templates.
14
built-in reports
Funnels, drop-offs, SLAs and a heatmap drawn on the flow itself.
Unlimited
conversation memory
No session timeout. Reply in 10 seconds or 10 months.
The builder
Build it by dragging
Drag a block from the palette, drop it on the canvas, and the phone preview shows exactly what your customer would receive.
Blocks27
Drag a block anywhere on the canvas — move it any time — then drag from a port to another block to wire them. Enter adds and wires for you.
Flow canvas
0/8 blocks
Live preview
9:41
S
Sharma Electronics
online
TodayMessages are end-to-end encrypted. No one outside of this chat can read them.
Hi 👋9:41
Message
The phone follows the wire — connect a block to see what it sends.
Drag a block, wire it with your mouse — and the phone shows exactly what your customer gets. No code anywhere.
27 blocks
Every block on the canvas
Ten message types, one question, nine actions, five logic blocks, an ending and a reusable fragment — in plain language.
Blocks, working together
A question, a condition, two outcomes.
Four blocks make a lead qualifier: the trigger starts it, a question collects the budget, a condition splits the path, and each branch ends somewhere useful — a brochure for one, your sales team for the other. Tap a branch to route it yourself.
- Trigger
- Ask a question
- Condition
- Hand off
app.infiq.in/flowsLead qualifier
Trigger
New customer message received
Bot asks
“What's your budget range?”
Showing 27 of 27 blocks
Failure drills
Rehearse the failure
Every action has a failure branch. Force it to fail in sandbox and prove your error path works before a real customer hits one.
Sandbox drill
API responding — the flow takes the happy path you drew: delivery status sent, conversation ended at the goal.
Order-status bot
SandboxThe customer’s phone
Happy pathWhat's your order number?9:41
#ORD-48219:41
Order #ORD-4821 is out for delivery today 🚚9:42
The API answered, the status went out, the goal was tracked.
Every action has a failure branch. Force it to fail in sandbox and prove your error path works before a real customer hits one.
Versioned publishing
Publishing can't break a live conversation
Every save is a version; running conversations finish on the version they started — and rollback is one click.
Version history
flow: plan-picker
- v1
- v2
- v3Priya · step 4 of 7 — mid-conversation, started on v3
- v4Rohan · step 2 of 5 — mid-conversation, started on v4
- Livev5Meera · step 6 of 9 — mid-conversation, started on v5
Every save is a version. Publishing never breaks a conversation in progress — and rollback is one click.
Triggers
Keywords in, the right bot out
Four match modes with deterministic priority — the most specific keyword wins, never random.
Customer sends
Rule ladder
checked top to bottom
- Exact“order”routes toOrder tracker
- Starts-with“order status”routes toOrder tracker“order”routes toOrder tracker
- Contains“refund”routes toRefunds desk“order”routes toOrder tracker
- Pattern^tr[ck]+routes toOrder tracker
- Catch-allanything elseroutes toFront desk
“order status” matched starts-with; longest keyword wins the tie — “order status” beats “order”.
Matched: starts-with — Order tracker bot answers.
If several keywords could match, the most specific wins — exact, starts-with, contains, pattern, then catch-all. Deterministic, never random.
Personalisation
Every message knows its customer
Nine built-in variables, every answer reusable in later steps, and a sentiment word-list that routes an unhappy customer to a human.
Pro · renews in 12 days · fast replies
Your message template
tap a variable
Hi ! Your plan renews in days.
$FirstName — a contact field. Fallback if empty: “there”, so the bubble never reads “Hi !”.
Built-in variables
$Name$FirstName$LastName$MobileNumber$Phone$Email$sentiment$patience+ any answer
The customer’s phone
Priya
Hi Priya! Your Pro plan renews in 12 days.9:41
Every variable resolved from the profile and saved answers.
Sentiment routing
$sentiment is positive
Last reply scored by the word-listContinue the flowHand off to a human
Positive or neutral score — the flow continues on the normal path. The word-list is tuned for English and Hinglish.
Preview for Priya: positive sentiment — the flow continues.
Nine built-in variables, every answer reusable — with fallbacks, so an empty name reads “Hi there!”, never “Hi !”.
Analytics
See what's working
Fourteen reports and a drop-off heatmap drawn on the flow itself — measured, not guessed.
Order-status bot · drop-off heatmap
Heatmap on: drop-off concentrates at the List menu step; one dead end found — 3 conversations stuck at Send document.
Every report, built in
14 reports · illustrative figures
Usage vs quota
How much of my plan have I used?
Funnel & drop-offs
Where exactly do people give up?
Version compare
Did my change improve completion?
Retention
Do customers come back within 7 or 30 days?
Answer distribution
What are people actually replying?
Button click-through
Which option does nobody pick?
Completion time
p50, p90, p95 — and which step is slowest?
Peak hours
When do customers message?
Goal attribution
Which entry keyword brings people who finish?
Weekly outcomes
Is completion trending up or down?
Handoffs & SLA
How often do we escalate, and do we hit our SLA?
Re-engagement
Did the follow-up template bring people back?
API health
Is my integration failing, and how fast?
Contact journey
Everything one customer has ever done.
Fourteen reports, and the drop-off heatmap is drawn on the flow itself — the dead end is measured, not guessed.
Pricing
Priced per flow, in rupees
Start with one flow and add capacity when you need it. Prices exclude Meta's per-conversation charges.
Billing term
1 flow: ₹399 per flow per month, billed monthly. Node limits: 2 API, 2 Webhook and 2 Compute — included with every plan.
Node limits
API + Webhook + Compute nodes
2
Every plan includes 2 API, 2 Webhook and 2 Compute nodes.
Node Pack raises the limit when you need it.
Beyond 6 + 6 + 6, add nodes individually at ₹50 per node per month.
- T&C apply.
- All prices in ₹ INR, ex-GST — taxes applicable as per prevailing laws.
- Exclusive of Meta's per-message conversation charges.
Infinite memory
Conversations that never expire
When the bot asks a question it waits indefinitely. Reply in 10 seconds or 10 months — it resumes at the exact step.
The bot asked a question at 9:41. Slide the reply delay — and watch the same late reply land on InfiQ and on a typical session-based tool.
Customer replies after24 hours
At 24 hours: InfiQ resumes at the exact step; typical session-based tools have restarted.
InfiQ FlowsNo expiry
Which plan do you want — Starter or Pro?9:41
24 hours later
Pro, please9:41
Perfect. Picking up where we left off —
Saved answers — restored
- name:Priya
- city:Pune
- team size:12
“replied 24 hours later — resumed at the exact step”
Typical session-based tools24-hour session
Which plan do you want — Starter or Pro?9:41
24 hours later
Pro, please9:41
This session has expired. Let's start again — what's your name?
Session expired — flow restarted
“session window crossed — the flow restarted from zero”
When the bot asks a question it waits indefinitely. Reply in 10 seconds or 10 months — it resumes at the exact step.
Governance
Enterprise-grade by default
A tamper-evident audit chain, four-eyes approval and hard compliance stops — standard, not add-ons.
Audit trail
flow: plan-picker · 5 entries
Tap any entry to tamper with it
5 of 5 links sealed
Four-eyes approval
The person who writes a change cannot be the person who releases it.
- Author
- Awaiting approval
- Approved
- Live
Priya A. drafted the change.
Every change is chained cryptographically — deleting or editing a record is detectable, not just discouraged. One click verifies the whole chain.
- Four-eyes approval
- Full workspace isolation
- SSRF-screened outbound calls
- Opt-out enforced platform-wide
- Every change versioned and reversible
Further reading
Guides from the InfiQ blog
WhatsApp Broadcast: The Complete Operator's Guide
How to run WhatsApp broadcasts that convert — opt-in list building, RFM segmentation, cadence caps, quality-rating protection and follow-up plays.
Read the guideWhatsApp Green Tick Verification: An Honest Guide
What the WhatsApp green tick actually is, who Meta approves, why applications fail, and what to do after a rejection — without the hype.
Read the guide
Send your first message today.
Get live on the official WhatsApp Business API in 2 hours with InfiQ — 7-day free trial, no card required.
7-day free trial Enterprise-grade reliability Live in 2 hours Built for Indian businesses