How to Set Up a WhatsApp Chatbot for Your Business in India (2025 Guide)
Set up WhatsApp chatbots in India with Business App vs API choices, BSP pricing, 5 build steps, automation workflows, and ban risks to avoid now.
- Use the WhatsApp Business App for simple manual replies and the Cloud API or BSP route for automation, routing, and integrations.
- A useful chatbot needs opt-in, template compliance, clear fallback paths, CRM capture, and handoff to a human when intent is unclear.
- Avoid spammy broadcasts because account quality, user blocks, and template policy violations can damage WhatsApp reach.
India leads globally in WhatsApp Business App downloads at 291.6 million (AiSensy, 2026) and 78% of Indian SMBs already use WhatsApp for business communications (WapiKit, 2025). A WhatsApp chatbot automates the responses, lead capture, and follow-ups that otherwise eat your evenings. Here's how to set one up, what it costs, and what actually converts.
WhatsApp Business App vs WhatsApp Business API: which do you need
These are two different products with very different capabilities.
- WhatsApp Business App (free): A single phone or tablet. One person online at a time. Automated greeting message and away message only. No chatbot logic, no multi-agent support, no analytics. Works for shops with under 50 conversations/day.
- WhatsApp Business API: Multiple agents, chatbot flows, automated triggers, CRM integration, analytics, broadcast messaging. Costs: ₹0 for the API itself (Meta doesn't charge) + ₹3,000–₹15,000/month for a BSP (Business Solution Provider) like Interakt, AiSensy, Wati, or Gupshup. Plus per-conversation charges: ~₹0.78 for business-initiated, ~₹0.13 for user-initiated conversations.
For any business getting 100+ WhatsApp inquiries/month, the API is worth it. The app doesn't scale past one person handling messages.
What a WhatsApp chatbot can automate for Indian SMBs
- Lead capture: When someone messages "Hi" or any trigger word, the bot automatically asks for name, city, and requirement — and saves it to your CRM or Google Sheets. No human needed for the first touch.
- FAQ answering: "What are your charges?", "Do you deliver to Bangalore?", "What documents are needed?" — pre-built keyword responses handle the 80% of questions that repeat. Humans only handle the 20% that are unique.
- Appointment booking: Bot shows available slots, customer picks one, confirms via WhatsApp. Integrates with Google Calendar via Calendly or Make automation.
- Order status updates: For e-commerce — order confirmed, packed, dispatched, delivered. Proactive status messages reduce "where is my order" inquiries by 60–70%.
- Payment reminders: Automated WhatsApp message 2 days before invoice due date, and on the due date. More effective than email — open rate is near 98% vs email's 20%.
Choosing a WhatsApp BSP for India
BSP pricing varies significantly. Here's the current landscape for Indian SMBs:
- Interakt: ₹2,756–₹8,258/month. Best integration with Shopify and Indian e-commerce. Good for D2C brands.
- AiSensy: ₹999–₹4,999/month. Most affordable entry tier. Good for service businesses and small retailers.
- Wati: $39–$99/month (~₹3,250–₹8,250/month). Cleaner UI, stronger chatbot builder. Popular with agencies and mid-size businesses.
- Gupshup: Conversation-based pricing without fixed monthly fees. Scales with volume. Better for businesses with irregular messaging frequency.
All four work. The right one depends on your tech stack and how complex your chatbot flows are. For most Indian SMBs starting out, AiSensy or Interakt is the practical starting point.
Setting up a basic WhatsApp chatbot: 5 steps
- Apply for WhatsApp Business API: Apply through a BSP — they handle Meta verification. Takes 2–7 business days. You'll need a phone number not registered on any WhatsApp account, a business display name, and a Facebook Business Manager account.
- Create your chatbot flow: Map out the top 5 questions your customers ask. Build keyword-triggered responses for each. Add a fallback: "Our team will respond within 2 hours" for anything the bot doesn't recognise.
- Set up lead capture: Every new conversation should trigger name + phone + city capture before escalating to a human. Save to Sheets via webhook or CRM directly.
- Get WhatsApp message templates approved: Any business-initiated message (broadcast, follow-up) needs Meta-approved template text. Approval usually takes 24–48 hours. Templates must be non-promotional in tone — "Here's your order update" passes, "Buy now for 50% off" doesn't.
- Test with real numbers: Test every flow with 3–4 real phone numbers before going live. Edge cases (unexpected inputs, wrong language) need fallback handling or your bot will loop and frustrate customers.
What doesn't work
- Sending broadcast messages to people who never opted in: This gets your WhatsApp Business account banned. India's TRAI rules and Meta's own policies require explicit opt-in before broadcast messages.
- 100% bot with no human fallback: Customers who can't reach a human escalate to negative reviews. Build in a "Talk to our team" option at every decision point.
- Promotional language in approved templates: "Special offer", "limited time", "discount" — Meta rejects these in message templates. Use transactional language only.
We build and integrate WhatsApp chatbots as part of our automation stack for Indian SMBs — including lead capture, CRM sync, and handoff to human agents. See our automation services or tell us what you want to automate and we'll scope it out.
What should you verify before using this WhatsApp Automation guide?
Before acting on how to set up a whatsapp chatbot for your business in india, verify the current rules or platform behavior with the n8n Docs. The practical answer depends on your business model, state, turnover, documents, software stack, and whether the decision affects tax, customer data, paid media spend, or a production workflow.
Use this article as a working checklist, then confirm API limits, authentication, webhook payloads, retries, error handling, and hosting requirements. In our audits, most expensive mistakes do not come from ignoring the whole process. They come from one stale assumption, one mismatched address, one missing event, or one automation path that nobody tested after launch.
| Checkpoint | Why it matters | Where to confirm |
|---|---|---|
| Current rule or platform status | Limits, forms, policies, and APIs can change after a blog update. | n8n Docs |
| Your exact business case | A local shop, freelancer, D2C store, agency, and SaaS team rarely need the same next step. | Documents, invoices, campaign data, analytics setup, or workflow logs |
| Implementation evidence | The safest workflow decision is backed by proof, not memory or screenshots from an old setup. | Portal acknowledgement, dashboard export, invoice sample, test lead, or error log |
How do we apply this in real business work?
We start with the smallest decision that can be verified. For compliance work, that means matching PAN, address, bank, invoices, and portal status before filing. For websites, marketing, analytics, and automation, it means testing the real user path from first click to final record. The boring checks catch the costly failures.
A useful rule: if a claim changes money, tax, reporting, or customer communication, keep evidence for it. Save the acknowledgement, export the report, test the form, and note the date you verified the source. That gives you a clean trail when a client, officer, platform, or internal team asks why the setup was done that way.
When should you get expert review?
Get expert review when the next action can create tax exposure, lost reporting data, ad waste, broken customer communication, or production downtime. A simple self-check is enough for low-risk learning. A filed return, new registration, tracking migration, paid campaign restructure, or live automation deserves a second set of eyes before it affects customers or records.
How often should this be rechecked?
Recheck the decision whenever your turnover, state, product mix, campaign budget, website stack, analytics property, or workflow ownership changes. Also recheck it after major portal updates, platform policy changes, annual filing deadlines, and vendor migrations. The guide is useful today only if the facts behind it still match your business.
What is the fastest safe way to decide?
Write the decision in one sentence, list the proof needed for that sentence, and verify only those items first. This keeps the work focused. If the proof confirms the decision, proceed. If one item is unclear, pause and resolve that point before changing filings, campaigns, tracking, website code, or automation logic.
What can go wrong if you skip verification?
The usual failure is not dramatic at first. It looks like a rejected application, a wrong tax invoice, a missing conversion, a duplicate lead, a broken report, or a workflow that silently stops. Those small failures become expensive when nobody notices them until month-end reporting, filing day, or a customer escalation.
What evidence should you keep after making the change?
Keep enough evidence to reconstruct the decision later. For a compliance topic, that usually means the application reference number, registration certificate, invoice sample, return acknowledgement, payment challan, notice reply, or source link checked on the day of filing. For a website, campaign, analytics setup, or automation, keep the before-and-after screenshot, test submission, dashboard export, webhook log, and the exact setting that changed.
This matters because most business fixes are revisited months later, when nobody remembers the original reason. A short evidence trail makes audits faster, handovers cleaner, and vendor conversations more precise. It also keeps the advice in this guide tied to your real operating context instead of becoming a generic checklist that gets copied without review.
- Date checked: record when the official source, dashboard, or portal screen was reviewed.
- Business context: note the entity, state, product, campaign, property, or workflow affected.
- Proof of action: save the acknowledgement, report export, test result, or live URL.
- Owner: assign one person to re-check the item when rules, tools, or business volume change.
Which next step should you take after reading this?
Turn the article into one action list. Mark what is already true, what needs proof, and what needs expert review. If you want to go deeper, compare this guide with Chatbot Integration, WhatsApp Marketing, and Auto Notifications. Then update the decision only after the official source and your own records agree.
Frequently asked questions
What is the short answer on How to Set Up a WhatsApp Chatbot for Your Business in India?
Set up WhatsApp chatbots in India with Business App vs API choices, BSP pricing, 5 build steps, automation workflows, and ban risks to avoid now. The practical next step is to compare the article checklist with your business model, state, turnover, documents, and tools before you act.
What should I verify before using this guide?
Verify the latest API limits, authentication, webhook payloads, pricing, and compliance rules from the official source links on this page. Tax rules, ad platform policies, software APIs, marketplace requirements, and search documentation can change after publication.
When should I get professional help?
Get help when the decision affects GST registration, tax filing, paid media budget, production website performance, analytics accuracy, or business-critical automations. A short expert review usually costs less than penalties, rework, bad data, or failed implementation.
Let's talk about your business.
Tell us what you're working on and where you want to go. We'll put together a plan. No obligation, no sales pitch.
- Free 30-minute call
- A plan built around your goals
- No obligation, no pressure
- Your own account manager