On this page
Too long? Read this
- The bots that pay first answer the ten questions that make up most enquiries, qualify leads in three questions, book slots, report order status and cover the hours nobody is at the phone
- Thirty use cases across nine industries, each with the trigger, the flow outline and the payoff
- Every bot needs a human path, a stop when a person joins, and templates for anything after the 24-hour window
- What a chatbot costs (nothing per message for inbound replies) and the metrics to judge it by
A WhatsApp chatbot pays for itself when it does one of five jobs: answers the questions that make up most enquiries, qualifies a lead before a person spends time, books a slot, reports a status, or covers the hours nobody is at the phone. Everything below is one of those five, applied to an Indian business, with the trigger, the flow outline and what it saves. All of them run inside the 24-hour window that a customer's message opens, so they cost nothing per message at Meta; templates are needed only for what the bot starts later. Every one needs a human path and a stop when a person joins.
Salons and spas
- Price and service menu. Trigger: "price", "services", or any first message. Flow: list of services with prices, "Book" button. Saves the desk from typing the price list forty times a day.
- Booking. Trigger: "book". Flow: service list, day and slot (a WhatsApp Flow form), confirmation template, 24-hour reminder. Saves phone tag and no-shows.
- Rebooking after a visit. Trigger: appointment completed plus 6 weeks. Utility template with a "Book again" button. Recovers lapsed clients.
Clinics and dental
- Appointment booking and triage. Trigger: any first message. Flow: new or existing patient, department, slots. Emergencies get the emergency number immediately.
- Pre-procedure instructions. Trigger: appointment stage "confirmed" for procedures. Utility template with instructions and a "questions" button.
- Report ready. Trigger: report uploaded (webhook). Utility template with a reply button to receive it in chat.
- Recall. Trigger: 6 months since the last visit. Utility template offering slots.
Coaching and education
- Course enquiry qualifier. Trigger: "fees", "batch", any first message. Flow: class, subject, mode; batch details; counsellor callback slot. Saves counsellors from unqualified calls.
- Fee reminders. Trigger: instalment due minus 3 days. Utility template with a payment link. Improves on-time collection.
- Class reminders and materials. Trigger: timetable. Utility template with the day's material attached.
- Result sharing. Trigger: result published. Utility template with the score and a "doubt session" button.
Real estate
- Configuration and budget qualifier. Trigger: any first message, click-to-WhatsApp ad. Flow: project, configuration, budget, timeline; brochure; site-visit slot. Saves agents from cold calls.
- Site-visit booking and directions. Trigger: "visit". Flow: day, slot, pickup; utility confirmation with a map link.
- Document checklist. Trigger: stage "booking". Utility template listing documents with a reply-to-upload instruction.
- Price and availability update. Trigger: inventory change. Utility template to enquirers of that unit type.
D2C and e-commerce
- Order status. Trigger: "order", "where is my order". Flow: order number, lookup via webhook, status; hand to a person if not found.
- Size and fit help. Trigger: "size". Flow: product, height and weight, recommendation from a size table.
- Returns and exchanges. Trigger: "return". Flow: order number, reason, eligibility from policy, instructions; hand to a person for exceptions.
- Abandoned cart recovery. Trigger: cart event via Zapier or webhook. Utility reminder, utility follow-up, one marketing step. Details.
- Back in stock. Trigger: "notify me" plus restock webhook. Utility template.
Restaurants and food
- Menu and ordering. Trigger: "menu", "order". Flow: menu as a list or catalog message, items and quantities via a WhatsApp Flow form, payment link, confirmation.
- Table reservation. Trigger: "table". Flow: date, time, guests; utility confirmation; a reminder on the day.
Travel
- Enquiry qualifier. Trigger: any first message. Flow: destination, dates, travellers, budget; hand to a consultant with the summary.
- Itinerary and documents. Trigger: booking confirmed. Utility templates for itinerary, document checklist and check-in reminders.
Finance and services
- Loan or policy enquiry. Trigger: click-to-WhatsApp ad. Flow: product, amount, city; eligibility basics; advisor callback. Keep to facts; no guarantees.
- EMI and renewal reminders. Trigger: due date minus 5 days. Utility template with a payment link.
Gyms, tuition, jewellery
- Trial booking (gym). Trigger: "trial". Flow: branch, day, slot; utility confirmation.
- Batch timings (tuition). Trigger: class number. Flow: subject, timings, fee; callback.
- Order ready for pickup (jewellery). Trigger: order stage. Utility template with store hours.
Any business
- After-hours cover. Trigger: message outside business hours. Flow: acknowledge, FAQ menu, capture name and need, promise a reply by a time, create the lead, assign for the morning.
Picking the first three
Rank your last 200 enquiries by the question asked. The top three questions are the first three bots: usually a price or menu answer, a booking or callback request, and a status or availability question. Build those, measure containment for two weeks, then add the next three. Institutes and clinics typically reach 60 percent containment with five bots; D2C stores with order status and size help alone.
What every bot needs
- A human path on every menu ("Talk to a person").
- A stop when a person replies (VGraple CRM pauses automation automatically).
- One fallback, then a handoff; never a loop.
- Templates approved for anything the bot starts after 24 hours (reminders, follow-ups).
- Consent recorded for anything marketing.
- A weekly read of twenty conversations; every fallback is a branch to add.
What it costs and what to measure
Inbound replies inside the 24-hour window are free at Meta; templates the bot starts cost Rs 0.115 (utility) or Rs 0.8631 (marketing) in India. VGraple CRM's flow builder, automation rules and WhatsApp Flows are on the free plan; the AI chatbot is on Growth and above. Measure containment, handoff rate with context, time to first reply, fallback rate, and the outcomes the bot exists for: leads created, bookings confirmed, orders placed, hours covered. How to build one without code is the next step.
Frequently asked questions
What is the most useful WhatsApp chatbot for a small business in India?
An FAQ and lead-capture bot: a menu of the six questions that are most of your enquiries, each answered with a short message and a 'talk to a person' button, plus two questions that capture the enquiry for a human. It contains 40 to 80 percent of inbound volume and takes under an hour to build.
Do chatbots work in Hindi and regional languages?
Yes. Flow messages can be written in any language, a first question can ask the customer to choose, and the AI chatbot answers in the language the customer writes in. Test each language before going live.
Can a chatbot take bookings?
Yes. A flow collects service, date and slot through lists or a WhatsApp Flow form, creates the appointment, and sends a utility confirmation and a reminder. Reschedule requests land with a person.
Can it check order status?
Yes, if the order system is connected through a webhook, Zapier or the API so the bot can look up the order number. Without a connection, it collects the order number and hands to a person.
What does a chatbot cost?
Replies to inbound messages inside the 24-hour window are free at Meta, so the bot costs nothing per message. Templates the bot starts later (reminders) cost Meta's rate. VGraple CRM's flow builder is on the free plan; the AI chatbot is on Growth and above.
How do I keep a chatbot from annoying people?
Offer a person on every menu, stop when a person joins, never loop more than once, keep messages short, and read twenty conversations a week.
Should I use AI or a scripted flow?
Both. The flow gives structure (menus, bookings, data capture); the AI handles the questions the flow did not script, from your documents, with escalation rules.
How fast can I launch one?
The FAQ bot in under an hour; a booking bot in an afternoon; an AI bot in a day including uploading documents and testing.