Most businesses that get a chatbot wrong did nothing wrong technically. The bot works. It just answers the wrong things, in the wrong tone, on the wrong channel, and usually at the exact moment the customer needed a person.
Indian customers mostly reach you on WhatsApp, not on a website chat widget. A bot that lives only on your site asks them to switch context before you have earned it.
Where A Chatbot Actually Helps
Chatbots earn their keep on a narrow band of work: questions with one right answer that get asked over and over.
- Order and invoice status, read from your system rather than guessed
- Business hours, location, which gate to enter from
- Price lists for items that do not change weekly
- Warranty terms, return windows and service conditions written down once
- Anything outside working hours, when nobody is awake to reply
If the answer can be looked up, hand it over.
Where It Annoys People
They are small irritations that stack up until the customer walks away.
The instant greeting. A bot that opens with “Hi, how can I help?” before you have typed anything reads like being put on hold. Wait until the customer sends something first.
The loop. Once the bot has admitted it does not know, three rephrasings of the same answer is worse than silence. After two failures, escalate.
The wrong register. Indian support messages mix Hindi, English and typed shorthand in one breath. A bot trained only on formal English misreads this, and the customer experiences it as not being understood.
The 80% answer. Finishing most of the question and then refusing the last 20% is the most annoying version of all. If it cannot complete the job, escalate before starting it.
The wrong silence. No reply and no visible typing for a couple of minutes, and most people assume you are closed and message your competitor instead.
Put The Bot Where Customers Already Are
Setting up a business number, catalogue and labels is covered in the guide to WhatsApp Business for Indian businesses. Chatbot support on WhatsApp runs through the Business API, which needs an approved account and pre-approved message templates.
One rule: the bot must be able to hand off inside WhatsApp. Sending someone to an email address to complain about WhatsApp support is a guaranteed bad review.
The Handoff Is The Product
Not the answers. The handoff. Design for the assumption that some conversations will fail.
- The customer can ask for a person in plain language, without working through a menu.
- The human sees the full transcript, including what the bot already tried, so nobody restarts from zero.
- There is a stated wait time, and a way to leave a number if the queue is full.
Escalate on mood, not only on topic. Words like “not working”, “refund”, “third time”, or a run of exclamation marks are handoff triggers even when the question itself is routine.
Track handoff rate as your main metric. A bot that escalates almost nothing is probably refusing politely rather than solving anything.
Automate First, and Never Automate This
Pull your top 20 most-asked questions from WhatsApp chat labels and your own call log, not from imagination. Write each answer in under 40 words. Then automate the unglamorous middle: collecting an order number, booking a callback slot, sending the document someone has now asked for twice.
| Question type | Automate it | Notes |
|---|---|---|
| Order status, hours, location | Yes | Pull from a live source, never invent it |
| Callback and visit booking | Yes | Confirm the slot back to the customer |
| Repeat product questions | Yes | Forty words or less |
| Complaint about a person | No | Straight to a human |
| Refund or credit decision | No | Money plus judgement |
| Anything with a filing deadline | No | A person must confirm it |
| Legal, tax or compliance advice | No | Never, at any tier |
The rule underneath the table: if you would not send the reply yourself without checking it, the bot should not send it either.
For the wider picture on AI tooling, see AI tools by job. Running the bot day to day means wiring it to your email and Tally! data, which sits under managed IT services.
FAQ
Should the chatbot be on my website or on WhatsApp? WhatsApp first for an Indian SME, because that is where customers already message. Add the website widget as a secondary channel once the WhatsApp flow is stable.
How long does it take to deploy one? A flow answering your top 20 questions can go live in one to two weeks. Anything that reads live order or inventory data takes longer, because that is integration work rather than configuration.
How do I know whether it is actually working? Watch three numbers: share of conversations completed without a handoff, average handoff wait time, and how many customers message again afterwards. If that last one is high, the bot is sending people away rather than helping them.
Will customers be annoyed that they are talking to a bot? Some will, mostly when it misreads their language or loops. Annoyance comes from failure, not from automation itself.
What if the customer asks something the bot has no answer for? That is the normal case, not the exception. It should say so plainly and pass the conversation to a person with the transcript attached.
Getting A Chatbot Set Up
24Bit System builds AI chatbots for Indian businesses, including the WhatsApp integration, the escalation rules, and reporting on what is actually being handled. Call +91 7840002466 or get in touch to work out what in your case is worth automating.
