WhatsApp chatbot development in India succeeds or fails on platform rules more than on clever conversation. Before you write a single flow, you need to understand message templates and Meta's approval process, the 24-hour customer service window, opt-in requirements and how a conversation passes to a human. Get these right and the bot becomes a dependable channel.
Planning a bot for orders, bookings, support or lead capture? Outline your use case for us and we will map it against WhatsApp's rules before anything is built.
First, the platform realities
Business bots run on the WhatsApp Business Platform (the Cloud API), accessed either directly through Meta or via a Business Solution Provider. The regular WhatsApp Business app on a phone is not designed for automated bots, and unofficial automation of personal or app accounts risks the number being banned.
The 24-hour customer service window
When a customer messages you, a 24-hour window opens. Inside it, your bot can reply freely with text, media, buttons and lists. Once it closes, you can only reach that customer with a pre-approved template message. Every flow you design has to respect this: a bot that promises "we'll update you tomorrow" needs a template ready to do so.
Message templates and approval
Templates are submitted to Meta and categorised as marketing, utility or authentication. Utility templates cover things the customer expects, such as order confirmations, delivery updates and appointment reminders. Marketing templates cover promotions and re-engagement. Templates can be rejected for vague wording, the wrong category, or variables used in misleading ways, so write them clearly, keep placeholders purposeful and submit them early in the project.
Practical template tips
- Create templates for each language you support; Hindi and English versions are approved separately.
- Use buttons in templates so customers can re-open the conversation with one tap.
- Keep marketing and service messaging distinct, because heavy promotional use can hurt your number's quality rating.
Opt-in, quality rating and messaging limits
You must have the customer's consent before initiating messages. Meta tracks a quality rating for your number based on blocks and reports, and new business accounts start with limits on how many unique customers you can message with templates in a 24-hour period, which rise as you use the platform responsibly. Meta also restricts general-purpose AI assistants on the platform; your bot should serve your own business's customer use cases, which is what most companies want anyway.
Designing the human handoff
The single biggest complaint about WhatsApp bots is being stuck with no way to reach a person. Plan handoff as a core feature, not a fallback.
- Triggers: the customer types "agent" or similar, the bot fails to understand twice, the topic is sensitive (complaints, payments, cancellations), or a high-value lead appears.
- Routing: connect to a shared inbox or your helpdesk (Freshdesk, Zendesk, Zoho Desk, a CRM) so agents reply in the same thread.
- Context: pass a summary and collected details so the customer is not asked again.
- Hours: outside staffed hours, the bot should say when a person will reply and collect what they need in the meantime.
What to build first in WhatsApp chatbot development for India
Resist launching with every feature. A focused first release gets through approval faster and teaches you how customers actually behave.
- One high-volume journey, such as order status, appointment booking or lead qualification, integrated with the system that holds the answer.
- Structured inputs, using reply buttons, list messages and WhatsApp Flows for short forms rather than open text wherever the choices are known.
- A grounded answer layer for common questions, drawing only on your approved knowledge base, with a clear "I'll connect you" when unsure.
- Handoff and inbox integration from day one.
- Utility templates for the follow-ups the journey needs.
- Analytics: track drop-off points, handoff reasons and resolved conversations.
Campaigns, catalogue commerce and multi-department routing can follow once the core journey is stable.
Testing before you go live
Run the bot against a script of real customer messages, including rude ones, typos, voice notes, images of receipts and people who ignore the buttons and type anyway. Check what happens when the 24-hour window closes mid-journey, when a template is paused, and when your order system is slow to respond. Invite a small group of staff and friendly customers to use it for a week before promoting the number widely, and read every transcript from that week.
Language, tone and Indian users
Many Indian customers write in Hinglish, transliterated regional languages or short voice notes. Decide which languages you will actively support, test understanding with real customer messages, and consider transcribing voice notes so they can be handled like text. Keep replies short: people read WhatsApp on phones, often between tasks.
How iJurug Soft builds WhatsApp bots
We build conversational assistants as part of iJurug Soft's AI and machine learning services, combining language models, retrieval over your content and the integrations with your CRM, helpdesk or order system. Work runs through fixed milestones, Discover, Design, Build, then Launch and grow, with senior engineers on the project and long-term support afterwards. Our guide to custom AI chatbot development in India covers bots across channels, and our article on conversational marketing automation looks at using chat responsibly for growth.
We don't publish prices. Effort depends on the number of journeys and languages, the systems to integrate, template volume, handoff tooling and your data-protection requirements.
Frequently asked questions
Do we need a Business Solution Provider?
Not necessarily. The Cloud API can be used directly through Meta. A provider can help with onboarding, inbox tools and support; the right choice depends on your internal capacity.
Can we use our existing business number?
Usually yes. Meta now supports coexistence for many numbers already on the WhatsApp Business app, so the app and the platform can share one number with some feature limits. Otherwise the number moves fully to the platform, which is why some businesses choose a dedicated number.
How long does template approval take?
Often quickly, but rejections and resubmissions add time, which is why we draft templates early.
Is customer data safe?
Messages are encrypted in transit; the data your bot stores should be minimised, access-controlled and handled in line with India's DPDP Act.
Share the questions your team answers most on WhatsApp through our project form or at info@ijurugsoft.com. We will reply with a suggested first journey, the templates it needs and a milestone plan.