Industries
Restaurants & Food
Take restaurant orders, table bookings and payments in one WhatsApp chat. Auto-reply to common questions and cut support costs with ChatMitra.
Real Estate
Use WhatsApp automation to capture property leads, qualify them automatically, and follow up fast. See how real estate agents close more with ChatMitra.
Travel & Tourism
Use the WhatsApp Business API to capture travel leads, send itineraries, confirm bookings, and keep travellers updated. See how agencies grow with ChatMitra.
Banking & Finance
Run secure KYC, send account alerts and payment notifications on WhatsApp. Cut support load and stay within Meta's rules with ChatMitra.
Beauty & Cosmetics
Sell your catalog, recover carts and win repeat orders on WhatsApp. Auto-reply to product questions and send launches to opted-in customers with ChatMitra.
Education
Answer admission enquiries, fee and timetable questions, and keep parents updated — all on WhatsApp. Cut admin load and costs with ChatMitra.
EduTech
Capture course leads, qualify them and onboard learners on WhatsApp. Automate replies and cut lead-qualification cost with ChatMitra's no-code chatbot.
Events & Webinars
Handle event registrations, reminders and RSVPs in one WhatsApp chat. Cut no-shows, automate FAQs and keep attendees updated with ChatMitra.
Freelancers & Consultants
Capture leads, send proposals and chase invoices in one chat. WhatsApp automation for freelancers and consultants with ChatMitra — from ₹0.20 a chat.
Health & Wellness
Book appointments, send reminders and answer client questions in one WhatsApp chat. Auto-reply to routine queries and cut support costs with ChatMitra.
Home Decor
Share your home decor catalog, take orders and send delivery updates on WhatsApp. Automate FAQs and cut support costs with ChatMitra.
IT Services
Use the WhatsApp Business API to qualify leads, run support over chat, and wire WhatsApp into your stack with webhooks. How IT companies scale with ChatMitra.
Marketing Agencies
Use WhatsApp automation to capture leads, run campaigns and manage multiple client brands from one account. How agencies scale on WhatsApp with ChatMitra.
Offline & Retail
Turn shop footfall into a WhatsApp list. Share catalogs, add a QR-to-chat at the counter and bring buyers back — with ChatMitra from ₹0.20 per chat.
Spas & Salons
Use the WhatsApp Business API to take spa and salon bookings, cut no-shows with automated reminders, and rebook regulars. How salons grow with ChatMitra.
Automotive
Use the WhatsApp Business API for automotive dealerships to qualify buyers, book test drives and send service reminders — automated, on one chat, with ChatMitra.
All Industries
Browse every industry guide
Automation & Chatbots

Live Chat vs Chatbot on WhatsApp: Who Should Answer What

Live chat vs chatbot on WhatsApp: what each does best, what a chat costs since October 2026, and how to hand customers from bot to human at the right moment.

Nirav Chauhan
Written byNirav Chauhan
Read time 18 min
Posted on
Live Chat vs Chatbot on WhatsApp: Who Should Answer What
Summarise this post with:

Short on time? Read this first

  • On WhatsApp, live chat and a chatbot answer in the same chat thread, so the real choice isn't one or the other. It's which messages each one handles, and when the bot steps aside.
  • Bots win on instant, repeatable answers: hours, prices, order lookups, booking slots and collecting details. People win on money, exceptions, complaints, photos and voice notes, and anything that needs judgement.
  • Since 1 October 2026, Meta charges for service messages after 1,000 free per number each month, whether a bot or a person sends them. A chatty bot menu can cost more in Meta fees than a short human reply. The saving from a bot is agent time.
  • WhatsApp's policy requires a prompt, clear and direct escalation path whenever you automate replies. Hand over when the customer asks, when the bot misses twice, when money or a complaint is involved, or when they send a photo or voice note.
  • A good handover pauses the bot, tells the customer who's coming and when, and gives the agent the chat history so nobody repeats themselves.
On this page 0

    Live chat or chatbot? On a website that’s a real choice between two widgets. On WhatsApp it isn’t. A customer writes to one number, and whoever replies, a person or a bot, appears in the same chat thread with the same name and photo. The customer can’t tell which one they’re getting until it goes wrong.

    So the useful question is which messages each should handle, and how to move a conversation from the bot to a person without the customer noticing the seam. This guide compares the two on what matters on WhatsApp in 2026: speed, cost per chat since Meta’s October 2026 pricing change, the 24-hour window and Meta’s escalation rule. Then it shows how to split the work by business size and design a handover that doesn’t lose the customer.

    Using ChatMitra? Live chat runs in the shared team inbox on every plan. Pro adds auto-reply rules, away messages and an AI chatbot, and you can pause all automation for one customer from the chat header, with an automatic resume time. ChatMitra’s fee is ₹0.20 per conversation, not per message. Jump to Running both in ChatMitra.

    Live chat vs chatbot at a glance

    Live chat (a person)Chatbot (rules or AI)
    Who repliesSomeone on your team, from a shared inboxSoftware: keyword rules, button menus, or an AI model
    SpeedMinutes to hours, depending on staffingSeconds
    HoursYour working hoursAround the clock
    Best atExceptions, complaints, refunds, negotiation, reading photos and voice notesRepeated questions, menus, collecting details, order and booking lookups
    Typical failureSlow replies at peak times; silence after hoursWrong or looping answers; no way out to a person
    Cost driverAgent timeSetup and upkeep; Meta charges per message sent
    Scales byHiringBetter answers and more coverage
    What WhatsApp addsThe 24-hour window limits when an agent can reply freelyReplies are limited to text, media, 3 buttons or a 10-row list per message

    There’s also a middle option: AI that writes replies in free text. Our guide to AI agents vs chatbots covers the difference between rule-based bots and AI. This post is about the bigger split, machine or person. For setting up an AI that answers in free text, see our WhatsApp AI agent guide.

    Why WhatsApp changes the comparison

    Most “live chat vs chatbot” advice was written for website chat. Five things work differently on WhatsApp.

    1. One thread, one identity. Bot and agent replies come from the same business number, so the customer sees one continuous conversation. That’s good for continuity, and it means a clumsy handover is very visible: a bot reply arriving after an agent has started typing looks like your business isn’t listening.

    2. Conversations are slow and long. People answer on WhatsApp when they can, sometimes hours later. A website visitor who leaves is gone; a WhatsApp customer comes back to the same thread tomorrow. Your handover has to survive gaps.

    3. The 24-hour window. When a customer messages or calls you, a 24-hour customer service window opens, and it resets each time they get in touch. Inside it, your bot or agent can send anything. After it, you can only send approved templates. Unlike Messenger, which has a separate 7-day human agent tag, WhatsApp offers no extra time for a person to reply. If an agent picks up a handover 23 hours later, they have one hour left to reply freely.

    4. Every reply is billed per message. Since 1 October 2026, Meta’s pricing charges for service messages after 1,000 free per business phone number per month, ₹0.115 each in India. A bot reply and a human reply cost the same. More on what that means below.

    5. Meta’s rules on automation. WhatsApp’s Business Messaging Policy says: “You may use automation when responding during the 24-hour window, but must also have available prompt, clear, and direct escalation paths.” It lists in-chat transfer to a human agent, a phone number, email, web support, an in-store visit or a support form. Separately, Meta’s WhatsApp Business Platform terms bar AI providers from the platform where AI is the “primary (rather than incidental or ancillary) functionality”. That rule is aimed at general-purpose AI assistants. A bot that answers questions about your own products and orders is a support tool for your business, though the terms leave the call to Meta.

    What a chatbot should answer

    A bot earns its place on questions that are frequent, predictable and checkable. On WhatsApp it has a few useful tools: reply buttons (up to 3, each label up to 20 characters), list messages (up to 10 rows, each title up to 24 characters), media and, if your platform supports them, Flows for forms.

    Good bot jobs:

    • The front door. A greeting with three buttons for your top reasons people message, such as “Track my order”, “Book a visit” and “Talk to us”.
    • Fixed answers. Opening hours, delivery areas, prices, return windows and how to pay. The wording you approve is the wording customers get.
    • Collecting details. The order number, the date they want, the product name or their city, before a person sees the chat. This alone saves every agent a message per chat.
    • Lookups. Order status or available slots, but only when the bot reads your live data. A bot that guesses creates a second complaint.
    • After-hours cover. Saying when your team is back and answering what it can in the meantime.

    If you’re building a bot around common questions, our WhatsApp FAQ chatbot guide walks through finding the questions and writing the answers, and our auto-reply examples give ready wording for small businesses. You can also set up to 4 ice breakers, suggested questions shown when someone opens a chat with you for the first time; our guide to conversational components explains them.

    What people should handle

    People are worth their cost wherever a wrong answer is expensive or the customer needs to feel heard:

    • Money. Refunds, failed payments, price matching, discounts outside your rules and anything about a charge.
    • Exceptions. A late delivery for a wedding, an order change after dispatch, a booking outside normal hours.
    • Complaints and upset customers. A menu in reply to “This is the third time I’m asking” makes it worse.
    • Photos, documents and voice notes. A picture of a damaged parcel, a prescription or a voice message in Tamil. Many bots can only read text, so these need a person.
    • High-value sales. A bulk order, a B2B enquiry or a customer comparing you with a competitor. These deserve a person even if a bot could quote the price.
    • Sensitive topics. Health, legal and financial questions, and anything where a customer shares personal details.

    Our WhatsApp customer service guide has a fuller task-by-task list of what to automate and what to keep human.

    Concept illustration of a road splitting in two: a long line of small chat bubbles labelled Store hours, Track order and Book a slot takes the wide branch to a friendly bot, while three bubbles labelled Refund, Damaged parcel photo and Bulk order take the narrow branch to a smiling support agent
    Sort by the question, not by the customer: routine questions to the bot, decisions to a person.

    What each chat really costs

    Cost is usually the reason businesses add a bot, so it’s worth doing the maths properly. On WhatsApp three things add up:

    1. Meta’s charges. Since 1 October 2026, service messages (free-form replies inside the window) are free for the first 1,000 per business phone number each month, then ₹0.115 each in India. Utility templates sent inside the window are also charged, at ₹0.115. Messages inside a Click-to-WhatsApp ad’s free entry point, which can stay open for up to 7 days, are free.
    2. Your platform fee. On ChatMitra’s Starter and Pro plans it’s ₹0.20 per conversation, once per customer per 24 hours, however many messages you exchange. Enterprise (₹2,499 a month) has no ChatMitra fee.
    3. Agent time. Usually the biggest number, and the only one a bot reduces.

    Here’s what that looks like for a business handling 3,000 support chats a month on one number. The agent cost and handling times are example figures to replace with your own.

    LinePeople onlyBot first, people for the rest
    Chats3,0003,000; the bot resolves 1,500
    Business messages per chat (example)4 from an agent6 per bot-only chat; 3 bot + 4 agent per handed-over chat
    Total service messages12,0009,000 + 10,500 = 19,500
    Meta charge (first 1,000 free, then ₹0.115)11,000 × ₹0.115 = ₹1,26518,500 × ₹0.115 = ₹2,127.50
    ChatMitra fee (₹0.20 × 3,000 conversations, Starter or Pro)₹600₹600
    Agent time at ₹2 a minute, 6 minutes a chat (example)3,000 × ₹12 = ₹36,0001,500 × ₹12 = ₹18,000
    Total₹37,865₹20,727.50

    The ₹2 a minute assumes an agent costing about ₹25,000 a month for roughly 208 working hours.

    Concept illustration of a balance scale with a big fluffy cloud of chat bubbles labelled 19,500 bot messages on one pan and a small, heavy stopwatch labelled Agent time on the other, with the stopwatch side sitting lower
    Bots send more billed messages, but agent time is usually the heavier cost.

    Two things stand out. First, the bot raises Meta’s bill: menus and multi-step flows send more messages than an agent’s short reply, and each one is now billed. Design bots to resolve in as few messages as possible: one answer instead of three menus. Second, the saving comes entirely from agent time, so a bot that hands over most chats after five messages costs more than no bot at all. Containment, the share of chats a bot fully resolves, is the number that decides whether it pays. For rates by message category, see our guide to WhatsApp Business cost per message.

    If you’re considering Meta’s own AI, the Meta Business Agent, note that its messages are a separate category since 1 July 2026, charged by tokens at roughly 4 to 5 US cents per message. Meta charges them even inside the free entry point.

    What live chat needs to work on WhatsApp

    Live chat isn’t just “someone answers”. Without a few basics it turns into slow replies and missed messages, and then a bot looks like the fix when the real problem is staffing.

    • A reply-time promise you can keep. Decide what you’ll commit to during open hours, such as a first reply within 15 minutes, and put it in your welcome message. Customers forgive a wait they were told about.
    • Clear hours, stated everywhere. Your WhatsApp business profile, your welcome message and your away message should all say the same hours. Our away message examples cover after-hours, weekend and festival wording.
    • A rota, not “whoever’s free”. With several people on one number, decide who watches the inbox when, including lunch and the first hour after opening, when the overnight queue lands.
    • Saved answers. Agents shouldn’t type the return policy fifty times a day. Approved, saved replies keep answers consistent and fast, and they’re the first step towards a bot: the saved replies used most are your bot’s first rules.
    • A way to see who’s waiting. Unread filters and tags such as waiting-on-us stop chats from falling through the gaps when several people share one number.

    If a business can’t staff live chat well during its own opening hours, a bot will hide the problem for a while but won’t fix it: the handovers will wait just as long.

    The right split by business size

    There’s no single right answer, but your chat volume narrows it down. These are rough guides, not rules.

    Daily chatsRecommended splitWhy
    Under about 20Mostly live chat. A welcome message, an away message for closed hours, saved replies for common answers, and a 3-button menuOne person can keep up; a full bot isn’t worth building yet
    About 20 to 150A bot front door that answers fixed questions and collects details, with people for everything after thatRouting and detail collection save the most time at this volume
    Over about 150, or customers in many time zonesA bot or AI that resolves the top questions end to end, a staff rota for handovers, and weekly reviews of what gets handed overContainment becomes the main lever on cost and wait times

    Whatever the size, keep one person responsible for the bot’s answers. Bots go wrong slowly: a price changes, a policy changes, and the bot keeps saying the old thing.

    When the bot should hand over

    A handover is the moment the customer judges your whole setup. These are the triggers worth building in.

    TriggerHow to spot itExample
    The customer asks for a personWords such as “agent”, “human”, “person”, “call me”, in any language you serve”Can I talk to someone?”
    The bot misses twiceTwo fallback replies in a row, or the same question repeatedThe customer types the same question in different words
    Money is involvedRefund, payment failed, charged twice, discount”I was charged twice for order 4412”
    The customer is upsetComplaint words, capital letters, “third time”, “worst""Still no delivery, this is ridiculous”
    Media the bot can’t readA photo, document or voice note arrivesA photo of a broken product
    High-value intentBulk quantities, business enquiries, comparing quotes”Need 200 units for a corporate event”
    An exception to your rulesRequests outside your stated policy”Can you deliver on Sunday?” when you don’t
    The window is closingA handover still open many hours laterAn agent sees the chat 20 hours after it was handed over

    The cost of getting this wrong is well documented. The US Consumer Financial Protection Bureau’s research on chatbots describes customers stuck in “doom loops” of repetitive, unhelpful replies “without an offramp to a human customer service representative”. On WhatsApp, the customer’s next move is often to block you or post a screenshot.

    Concept illustration of a frustrated customer walking along an endless twisted loop path printed with Sorry, I didn't understand that, while a smiling support agent holds open a door beside the loop labelled Talk to a person
    Two misses, then a person. A bot with no exit is worse than no bot.

    How to hand over without losing the customer

    1. Tell the customer what happens next

    The handover message does more than “Transferring you to an agent”. It says who, when and what to do meanwhile:

    “I’ll pass this to our support team now. Someone will reply here within 30 minutes (we’re open 9 am to 8 pm). You don’t need to send anything else; they’ll see your order number and photo.”

    Out of hours, be honest:

    “Our team is offline until 9 am tomorrow. I’ve noted your order number and the problem, and the first person in will reply here.”

    2. Stop the bot

    Once a person owns the chat, the bot must stay quiet. A bot that answers “Did you know we deliver in 2 hours?” while an agent is handling a refund undoes the agent’s work. Check whether your platform pauses automation automatically when an agent replies, or whether someone has to pause it.

    3. Give the agent the context

    The agent should never ask for something the bot already collected. Before replying, they should be able to see:

    • the whole chat, including button taps;
    • the details the bot collected (order number, date, product);
    • the reason for the handover (asked for a person, missed twice, refund, photo);
    • anything known about the customer: past orders, tags, notes.

    4. Reply inside the window

    Treat handovers as a queue with a deadline. If an agent can’t resolve the issue straight away, they should ask for anything else they need while the window is open, because each customer reply resets it. If the window does close, follow up with an approved utility template about their request, then continue once they reply.

    5. Hand back to the bot

    When the issue is resolved, switch automation back on for that customer, so their next “What time do you open?” gets an instant answer. Some platforms do this on a timer; others need a person to remember.

    Concept illustration of a friendly bot handing a chat bubble labelled Order 4412: damaged item, photo attached to a support agent, who presses a teal cork labelled Reply now into the neck of a large hourglass labelled 24-hour window to hold back the last grains of sand
    Every handover has a deadline: the agent's free replies end 24 hours after the customer's last message.

    Common mistakes when mixing bots and live chat

    • No visible way out. The escalation path is buried, or “agent” isn’t recognised. Put it in the first message and in every fallback reply.
    • Bots that pretend to be people. A bot called “Priya” that says “let me check with my manager” will be found out the first time it misunderstands something. Name it as an assistant and keep your team’s names for your team.
    • Two systems answering at once. A keyword rule and an AI both reply, or a bot replies while an agent is mid-conversation. Customers see two answers and trust neither.
    • Long menus. Four levels of buttons before a customer reaches an answer is slower than asking a person, and every step is a billed message. Keep menus to one or two levels.
    • Handover to an empty room. A handover at 11 pm that says “an agent will be with you shortly” sets an expectation nobody meets. Say when the team is back.
    • Never reviewing the bot. Prices, policies and stock change. A bot that’s right on launch day and wrong a month later does more damage than no bot.
    • Measuring only bot volume. “The bot handled 80% of chats” means little if half of those customers came back the next day. Look at repeat contacts and blocks too.

    How to tell whether the split is working

    Track a handful of numbers each week. You can do this with tags and a spreadsheet if your platform doesn’t report them.

    • Containment rate: chats the bot resolved with no person ÷ all chats the bot started. Tag chats bot-resolved or handed-over at the end.
    • Handover rate by reason: which trigger fired. If “missed twice” is high for one topic, add that answer to the bot.
    • Time to first human reply after handover: the wait customers feel. Long waits here undo the bot’s speed.
    • Repeat contacts: the same customer back with the same problem within 7 days, a sign the bot’s answer didn’t work.
    • Blocks and complaints: a rising block rate after you add automation is the clearest sign something feels wrong to customers.

    Review the handed-over chats every week. They’re the best list of what to add to the bot and what to stop it trying.

    Examples by industry

    BusinessBot handlesPerson handlesHandover trigger to add
    Online storeOrder status, return window, sizes, delivery areasDamaged items, refunds, COD disputesAny photo; “refund”; “charged”
    ClinicTimings, doctor availability, booking a slotSymptoms, reports, prescriptionsAny medical question; any document
    Coaching instituteBatch timings, fees, syllabus, demo-class bookingFee instalments, scholarship requests, parent concerns”instalment”; “discount”; a parent asking about a student
    Real estateProject details, price ranges, site-visit slotsNegotiation, loan questions, booking amountBudget above a set figure; “visit today”
    Travel agencyPackage details, visa checklists, departure datesCustom itineraries, cancellations, refundsDates changed; group of 10 or more
    RestaurantMenu, timings, table booking, delivery areasLarge party bookings, complaints about orders”party”; any complaint words

    Running both in ChatMitra

    ChatMitra puts live chat and automation in the same inbox. Here’s what’s available and how it maps to the setup above.

    ChatMitra featureWhat it doesPlan
    Shared team inboxEveryone on the team works from one WhatsApp number, with the full chat historyAll plans
    Unlimited team members with permissionsAdd agents and set view, create, edit and delete rights per section, per projectAll plans
    Saved repliesType ”/” in the message box to insert an approved answerAll plans
    Welcome messageGreets new chats automaticallyAll plans
    Auto-reply rulesKeyword rules (exact, starts with or pattern) that send text, buttons, lists or mediaPro and above
    Away and fixed repliesAutomatic replies outside your set hours, with a timezonePro and above
    AI chatbotWrites replies from your instructions using your own AI provider key; remembers the last 20 messages of a chatPro and above
    Pause automation per chatStops the AI, rules, away and fixed replies for one customer, and switches back on after 30 minutes, 1, 4, 8 or 24 hours, or when you chooseUse it with any Pro automation
    24-hour window guardBlocks free-form replies once the window has closed and offers a template insteadAll plans
    Customer tags and notesRecord the handover reason, past issues or VIP status on the customerAll plans
    ₹0.20 per conversationOne fee per customer per 24 hours, however many messages the bot and agents sendStarter and Pro; none on Enterprise

    How to set up the split in ChatMitra:

    1. Write your welcome message with how to reach a person, for example “Reply agent at any time to talk to our team.”
    2. Add auto-reply rules for your top questions, and one rule for “agent”, “human” and “person” that sends your handover message.
    3. If you use the AI chatbot, give it a narrow job (your products, hours and policies) and tell it to point people to “agent” when it can’t help. Avoid keywords that overlap with what the AI answers, because a typed message that matches a rule gets a reply from both.
    4. Set away hours and an honest away message.
    5. Agree a handover routine: when a handover message goes out, the agent who picks up the chat pauses automation for that customer from the chat header, choosing a resume time such as 4 or 24 hours.
    6. Tag the outcome (bot-resolved or handed-over, plus a reason tag) so you can count containment each week.

    Good to know:

    • There’s no automatic handover. The handover message tells the customer a person is coming; someone on your team still has to pick up the chat and pause automation.
    • An agent’s reply doesn’t pause the bot. Pause automation for that chat before or right after replying.
    • With both auto-reply rules and the AI chatbot on, a typed message that matches a rule gets two replies. Button and list taps go only to the rules.
    • The AI chatbot reads text only. Photos, documents and voice notes need a person, which is also a good handover trigger.
    • There’s no chat assignment or per-agent reporting. Agree who covers which hours, and use tags to show who’s handling what.
    • Mobile app notifications go to the account owner’s devices; agents see new messages in the web inbox.
    • Away hours use one daily time range and a timezone, with no separate weekend setting.
    • The welcome message isn’t covered by the per-chat pause, so keep it short and general.
    • Check the pricing page for what each plan includes.

    Where to start

    Read your last 100 WhatsApp chats and sort them into three piles: questions with one right answer, questions that needed a decision, and complaints. The first pile is your bot’s job list. The second and third are your team’s, and the triggers for handing over. Build the bot for the top five questions only, add the “agent” exit on day one, and review the handed-over chats every week. That gets most businesses to a split their customers barely notice.

    Sources

    Clear answers

    Frequently Asked Questions

    Live chat means a person on your team reads and answers each message. A chatbot answers automatically, either from rules you set (keywords, buttons and menus) or with AI that writes replies from your information. Live chat handles judgement and exceptions; a chatbot handles speed, volume and after-hours questions. On WhatsApp both reply in the same chat thread.

    Neither is better on its own. A chatbot is better for repeated questions, out-of-hours replies and collecting details such as an order number. Live chat is better for complaints, refunds, unusual requests and anything involving photos, voice notes or sensitive information. Most businesses with more than a handful of chats a day use a bot to answer and route, and people for everything that needs a decision.

    Hand over when the customer asks for a person, when the bot fails to understand them twice, when the conversation involves money (refunds, failed payments, price exceptions), when the customer is upset, when they send a photo, document or voice note the bot can't read, and when the chat is a high-value sale such as a bulk order. Out of hours, say when a person will reply instead of pretending one is available.

    WhatsApp's Business Messaging Policy says that if you use automation during the 24-hour window you must have prompt, clear and direct escalation paths. In-chat transfer to a human agent is one option; the others it lists are a phone number, email, web support, an in-store visit or a support form. So a human in the chat isn't mandatory, but a clear way to reach one is.

    Not always. Since 1 October 2026, Meta charges for service messages after the first 1,000 per business phone number each month (₹0.115 each in India), and it charges the same whether a bot or a person sends the reply. Replies inside a Click-to-WhatsApp ad's free entry point are free. Messages from Meta's own Business Agent are charged by tokens, about 4 to 5 US cents per message, even in the free entry point.

    No. WhatsApp has no equivalent of Messenger's 7-day human agent tag. The customer service window lasts 24 hours from the customer's last message or call and resets each time they get in touch. After it closes you can only send approved templates, so agents should reply, or ask for anything they need, before the window ends.

    Track how many chats the bot resolves without a person (containment), how many it hands over, how long customers wait for a human after the handover, and how many people come back within a week with the same problem. A rising handover rate on one topic tells you what to add to the bot; repeat contacts tell you the bot's answers aren't working.

    Not fully. An AI chatbot can answer free-text questions from your information and handle many routine chats, but it can be wrong, it shouldn't make promises about refunds or exceptions, and many AI bots can't read photos or voice notes. Use AI to reduce the load on your team and to cover off-hours, and keep people for decisions and upset customers.

    Nirav Chauhan

    ChatMitra

    Nirav Chauhan writes for the ChatMitra blog about the WhatsApp Business API.

    Ready to try WhatsApp Business API?

    Start free on the Starter plan — free subscription. Pro is ₹999/month with a 15-day trial when you need automation.