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

WhatsApp Chatbot Analytics: The KPIs That Show If Your Bot Sells

The WhatsApp chatbot KPIs that matter: containment, handover, drop-off, bot-assisted sales and cost per resolved chat, with formulas and a worked example in rupees.

Hitesh Pathar
Written byHitesh Pathar
Read time 17 min
Posted on
WhatsApp Chatbot Analytics: The KPIs That Show If Your Bot Sells
Summarise this post with:

Short on time? Read this first

  • WhatsApp chatbot analytics should answer three questions: does the bot resolve chats, does it lead to sales, and what does each resolved chat cost? Message counts and session length answer none of them.
  • Ten KPIs cover it: containment, handover rate, unrecognised messages, path completion, repeat contacts, wait after handover, bot-assisted conversion, revenue per conversation, cost per resolved chat and customer reaction.
  • WhatsApp chats are slow and spread out, so decide when a conversation counts as finished, for example no reply for 24 hours, before you calculate anything.
  • In our worked example, a bot-resolved chat costs about ₹0.78 in Meta and ChatMitra charges, while a handed-over chat costs about ₹13 once six minutes of agent time is added. Each percentage point of containment is worth roughly ₹490 a month at 4,000 chats.
  • Most platforms, ChatMitra included, don't produce every KPI as a ready-made report. Tags at the end of each chat, a discount code or UTM link per bot path, and a weekly sample of transcripts fill the gaps.
On this page 0

    WhatsApp chatbot analytics is the practice of measuring what a chatbot achieves in WhatsApp conversations: how many chats it resolves without a person, where customers drop off or ask for help, how many chats lead to an order or booking, and what each resolved chat costs. The KPIs that matter are outcomes, not activity. Track containment, handover rate, drop-off by step, bot-assisted conversion and cost per resolved chat first, and ignore totals such as messages sent.

    Most chatbot reports are full of numbers that go up when the bot gets worse. A bot that asks three clarifying questions instead of one sends more messages. A confusing menu produces longer sessions. A customer who gives up and calls instead shows up as “conversation ended”.

    The question a business owner actually wants answered is simpler: is the bot saving my team time and helping us sell, and is it worth what it costs? This guide sets out the KPIs that answer it, how to calculate each one on WhatsApp, a worked example in rupees, and how to collect the data when your platform doesn’t report it for you.

    If you’re still building the bot, start with our WhatsApp FAQ chatbot guide. This article is about measuring one once it’s live.

    Using ChatMitra?

    ChatMitra shows AI chatbot runs in the AI Chatbot's Executions tab and recent runs of each keyword rule in its Logs view. For containment, handovers and sales, use auto-reply rules that add tags, discount codes or UTM links per bot path, and the Webhooks setting to send every message to your own sheet or BI tool. ChatMitra charges ₹0.20 per conversation, however many messages the bot sends. See How to measure chatbot KPIs in ChatMitra.

    What chatbot analytics should tell you

    Every useful chatbot metric answers one of three questions:

    1. Does the bot resolve conversations? Customers get what they came for without waiting for a person.
    2. Does the bot lead to revenue? Chats that start with the bot end in orders, bookings or qualified leads.
    3. Does it pay for itself? The cost of each resolved chat is lower with the bot than without it.

    A fourth question sits underneath all three: do customers put up with it? A bot that resolves chats by wearing people down, or that triggers blocks, is borrowing against your future sales.

    Metrics that don’t answer any of these questions, such as total messages, total conversations or average session length, describe activity. They’re useful for capacity planning, not for judging whether the bot works.

    Why WhatsApp needs its own definitions

    Most chatbot KPI guides are written for website chat widgets, where a session starts when someone opens the widget and ends when they close the tab. WhatsApp works differently, and the differences change how you should count.

    • Conversations are spread out. A customer can ask about a kurta at lunch and reply to the bot’s answer that evening. Microsoft’s Copilot Studio analytics, for example, treats a conversation as timed out “after 30 minutes of inactivity”. On WhatsApp, that would split one purchase journey into several “abandoned” sessions. Pick a longer rule, such as no reply from the customer for 24 hours, and use it consistently.
    • The customer service window shapes the chat. Meta’s documentation says that “when a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts”, and resets when they message again. Inside it, your bot can send free-form replies; outside it, only approved templates. A bot that hands over at 9 pm to a team that starts at 10 am the next day can miss the window.
    • Read status is a weak signal. Meta’s status webhook marks a message read when it “was displayed in an open chat thread”. That says the customer saw the screen, not that they understood the answer, so treat read rate as a delivery check rather than a success measure.
    • Clicks aren’t reported. WhatsApp doesn’t tell the business when a customer taps a link in an ordinary message. If you don’t tag your links, a sale that started in the bot looks like direct traffic on your website.
    • Every business message has a price. Since 1 October 2026, Meta charges for service messages after the first 1,000 per business phone number each month, and for utility templates sent inside the window. A bot that needs eight messages to answer a question costs more than one that needs three.

    The 10 WhatsApp chatbot KPIs at a glance

    KPIFormulaWhat you want to see
    Containment rateChats resolved with no person ÷ chats the bot startedRising, without a rise in repeat contacts
    Handover rate, by reasonChats handed to a person ÷ chats the bot startedFalling for topics the bot should handle; steady for topics it shouldn't
    Unrecognised-message rateCustomer messages the bot couldn't answer ÷ customer messages to the botFalling as you add answers
    Path completion and drop-offChats reaching the last step ÷ chats starting the path, and the share lost at each stepRising completion; no single step losing most people
    Repeat-contact rateCustomers back on the same topic within 7 days ÷ chats marked resolvedLow and falling
    Wait after handoverTime from the handover message to the first reply from a personShort, and well inside the 24-hour window
    Bot-assisted conversionOrders traced to a bot path ÷ chats that entered that pathRising
    Revenue per bot conversationRevenue traced to bot paths ÷ chats the bot startedRising
    Cost per resolved chat(Meta charges + platform fees + agent time) ÷ chats resolvedFalling
    Customer reactionPositive feedback taps ÷ feedback responses; blocks and opt-outs after bot chatsHigh satisfaction, no rise in blocks

    The sections below explain each one, the trap in each, and how to collect the data.

    Is the bot resolving chats?

    Containment rate

    Containment is the share of chats the bot finishes without a person. It’s the number that decides whether a support bot pays, because agent time is usually the largest cost in customer service.

    Microsoft’s Copilot Studio guidance uses two related definitions: deflection rate, the “percentage of requests completed through self-service”, and resolution rate, the “percentage of sessions ending with a resolved outcome”. The difference matters. A chat where the customer gave up isn’t resolved, even though no person was involved.

    The trap: counting every chat that ended without a handover as contained. Some of those customers left confused and will call, email or come back tomorrow. Check containment against the repeat-contact rate below, and read a sample of “contained” chats each week.

    How to collect it: decide what “resolved” looks like for each bot path, such as the customer received a tracking link, booked a slot or tapped “That helped”. Tag the chat at that point, and tag handovers separately. Then:

    Containment = chats tagged resolved-by-bot ÷ (resolved-by-bot + handed-over + no outcome)

    Handover rate, by reason

    The handover rate is the share of bot chats that end up with a person. On its own it isn’t good or bad: a bot for complaints should hand most chats over. What matters is the reason.

    Record why each handover happened: the customer asked for a person, the bot didn’t understand twice, the topic is one the bot shouldn’t handle (refunds, complaints, medical questions), or the customer sent a photo or voice note. Microsoft counts sessions as escalated when the bot reaches its escalation step or transfers the conversation, and abandoned when the session “ends without being resolved or escalated”. Those three outcomes, resolved, escalated and abandoned, give you a clean split for every chat.

    When one reason dominates, the fix is usually obvious. Many “didn’t understand” handovers on one topic mean a missing answer. Many “asked for a person” handovers at the first message mean the welcome message doesn’t explain what the bot can do.

    Concept illustration of a white robot hand holding out a baton shaped like a rolled chat bubble labelled Order #1042, wants to change size, towards a support agent's open hand, with a small tag reading Handover
    A good handover passes the context too, so the customer doesn't repeat themselves.

    Unrecognised-message rate

    This is the share of customer messages the bot couldn’t match to an answer. Microsoft calls them “unrecognized utterances”: phrases that didn’t trigger any topic.

    On WhatsApp, these messages are easy to miss, because some bots don’t reply at all when nothing matches. The customer just sees silence. Read a weekly sample of chats where the customer’s last message got no bot reply, list the questions, and add answers for the ones that keep coming back. That list is the most valuable output of any chatbot report.

    Path completion and drop-off by step

    Most WhatsApp bots run on paths: a menu leads to a product category, then a size, then a payment link. Completion is the share of chats that reach the end of a path. Drop-off is the share lost at each step.

    A step that loses far more people than the others needs attention. Common causes are a list with too many choices, a question the customer can’t answer (“Enter your order ID” when the ID isn’t in their SMS), or a step that asks for typed input where a button would do. Meta’s reply-button messages allow up to three buttons with labels of up to 20 characters, and list messages allow up to 10 rows in total, so long menus have to be split, and each split is a step where people can leave.

    Concept illustration of a white funnel with rings labelled Menu, Pick a size and Pay, with a crack in the Pick a size ring through which coins and chat bubbles spill out, while a shop owner points at the crack
    Drop-off by step shows exactly where a path loses customers.

    Repeat-contact rate

    If the same customer comes back about the same thing within a few days, the first answer probably didn’t work. Track the share of resolved chats followed by another chat on the same topic within 7 days. It’s the honesty check on containment.

    Wait after handover

    A bot answers instantly, which raises expectations for what comes next. Measure the time from the handover message (“Connecting you to our team”) to the first reply from a person. Long waits here undo the bot’s speed and push customers towards other channels. If your team isn’t available round the clock, say so in the handover message and give a time.

    Answer accuracy, for AI chatbots

    Rule-based bots give the answer you wrote. AI chatbots write their own, which adds a risk the other KPIs miss: a confident, wrong answer that the customer accepts. The chat looks contained, nobody is handed over, and the problem only appears as a return, a complaint or a lost sale.

    Check it with a small audit. Each week, take 20 to 30 AI-answered chats at random and mark each answer correct, partly correct or wrong against your own policies and product data. Track the share that’s fully correct, and look closely at the wrong ones: they usually point to a missing or outdated fact in the bot’s instructions, or a question the bot should have handed over. Treat delivery dates, prices, refund terms and anything medical or legal as topics where the bot hands over rather than guesses. Our comparison of WhatsApp AI agents and chatbots covers when each approach fits.

    Is the bot leading to sales?

    This is where most chatbot reports stop short, and it’s the part owners care about most.

    Bot-assisted conversion

    Bot-assisted conversion is the share of chats on a buying path that end in an order. To count it, each bot path needs a trace that survives the jump from WhatsApp to your store:

    • A discount or reference code per path, such as BOT-KURTA for the kurta finder. Orders using the code are bot-assisted.
    • UTM parameters on every link the bot sends, such as utm_source=whatsapp&utm_medium=chatbot&utm_campaign=kurta-finder, so that your website analytics records the visit and the order.
    • An order or booking reference the bot captures, for services where the sale happens later, by phone or in person.

    For leads rather than orders, use the same idea: count leads that came through a bot path and later became customers.

    Concept illustration of a trail of teal footprints leading from a chat bubble reading Show me kurtas under ₹1,500, past a signpost reading Code: BOT-KURTA and a phone showing a product page, to a shopping bag tagged Paid ₹1,299, with a store owner following the trail with a magnifying glass
    Give every bot path a code or tagged link, so the sale leaves a trail back to the chat.

    The trap: treating every bot-assisted order as revenue the bot created. Some of those customers would have bought anyway. If the number matters for a decision, compare against a group of similar customers who didn’t use the bot.

    Revenue per bot conversation

    Divide the revenue traced to bot paths by the number of chats the bot started. This puts support-heavy bots and sales-heavy bots on the same scale, and it tells you what a conversation is worth when you decide how much to spend on bringing people into WhatsApp.

    Click-to-WhatsApp ads

    When a chat starts from a click-to-WhatsApp ad, Meta provides more data. Meta’s Conversions API documentation describes the click ID (ctwa_clid) as “unique per click” and exposed to the business when the conversation came from an ad, and says it “needs to be sent back to Meta via the Conversions API call” to report purchases. Meta also offers automatic events reporting for purchases and leads it detects in ad-started chats, if you opt in. Messages inside the ad’s free entry point window, which Meta says “may remain open for up to 7 days”, aren’t charged, which also improves the cost side of your numbers.

    Does the bot pay for itself?

    Cost per resolved chat

    Three costs add up:

    1. Meta’s message charges. In India, service messages, the free-form replies your bot and agents send inside the customer service window, are free for the first 1,000 per business number each month and ₹0.115 each after that (rate card effective 1 October 2026). Utility templates sent inside the window are also charged, at ₹0.115.
    2. Your platform fee. ChatMitra charges ₹0.20 per conversation on Starter and Pro: once per customer per 24 hours, however many messages the bot and your agents send. Enterprise has no ChatMitra fee.
    3. Agent time for every chat a person has to handle.

    Here’s a worked example for a D2C clothing brand with 4,000 customer-started chats a month on one number. The handling times, message counts and agent cost are assumptions for illustration; replace them with your own.

    LineContainment 60%Containment 45%
    Resolved by the bot (5 business messages each)2,4001,800
    Handed over (3 bot + 4 agent messages each)1,6002,200
    Service messages12,000 + 11,200 = 23,2009,000 + 15,400 = 24,400
    Meta charge (first 1,000 free, then ₹0.115)22,200 × ₹0.115 = ₹2,55323,400 × ₹0.115 = ₹2,691
    ChatMitra fee (4,000 conversations × ₹0.20)₹800₹800
    Agent time (6 minutes a chat at ₹2 a minute)1,600 × ₹12 = ₹19,2002,200 × ₹12 = ₹26,400
    Total a month₹22,553₹29,891
    Cost per chat (all 4,000 resolved eventually)₹5.64₹7.47

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

    Two numbers stand out. A chat the bot resolves costs about ₹0.78 in Meta and ChatMitra charges (5 × ₹0.115 + ₹0.20, before the free tier), while a handed-over chat costs about ₹13.01 once agent time is included. And the 15-point drop in containment adds ₹7,338 a month, roughly ₹490 for every percentage point. That’s the business case for spending time on the handover reasons and unrecognised messages above.

    Concept illustration of two receipt slots side by side, a short receipt under a small robot reading Resolved by bot, 5 messages, ₹0.78, and a long receipt under a support agent reading Handed over, 7 messages plus 6 min agent time, ₹13.01
    Same question, different receipt: containment is where the savings come from.

    Keep the message count in view too. Bots that answer in one message rather than three menus are cheaper on Meta’s side and quicker for the customer. For the full rate list by message type, see our guide to WhatsApp Business cost per message.

    Do customers like it?

    Customer reaction

    Ask, briefly, at the end of a resolved chat: “Did this answer your question?” with “Yes” and “No” buttons. Keep it to one tap and to a sample of chats, not every one. Count the share of “Yes” taps, and read every “No”.

    Also watch the signals customers give without being asked. A rise in opt-outs, blocks or a falling quality rating after you add or change automation is a sign that something in the bot feels wrong. Our guide to reducing WhatsApp opt-outs and blocks covers what to look for.

    Which KPIs matter most for your type of bot

    The ten KPIs don’t carry equal weight for every bot. Pick the two or three that match the bot’s job and put them at the top of your report.

    Bot typeLead KPIsWatch out for
    Support and FAQ bot (order status, returns, store hours)Containment, repeat contacts, cost per resolved chat"Resolved" chats that come back the next day
    Shopping bot (product finder, catalogue, reorders)Path completion, bot-assisted conversion, revenue per conversationDrop-off at size, variant or payment steps
    Lead qualification bot (real estate, education, B2B)Leads completed, wait after handover, leads that become customersQualified leads waiting hours for a call back
    Booking bot (clinics, salons, test drives)Bookings completed, no-show rate, handover rate for reschedulesCustomers who start a booking and stop at the slot list
    AI assistant (open questions)Answer accuracy, containment, unrecognised or refused questionsConfident wrong answers that look contained

    Reading the numbers: three common patterns

    Numbers only help if you know what to do when they move. These are the patterns that come up most often, and where each one usually leads.

    Containment is high, but so are repeat contacts. The bot is closing chats it hasn’t really solved. Read the “resolved” chats for the topic with the most repeats. Often the answer is technically correct but incomplete, such as a tracking link with no explanation of what “In transit” means or what to do if the date has passed. Add the missing line, or hand that topic over.

    Path completion is good, but conversion is low. Customers reach the product link and don’t buy. The problem is usually after WhatsApp: the link opens a generic category page instead of the product, the price differs from the one the bot showed, or the discount code doesn’t apply. Tap through the path yourself on a phone, the way a customer would.

    Handover rate jumps after a change. Compare the handover reasons from before and after. If “didn’t understand” rose, the new menu wording or keywords don’t match how customers write. If “asked for a person” rose at the first message, the new welcome message probably hides what the bot can do. Roll back one change at a time rather than redesigning everything.

    Whatever the pattern, the next step is the same: read 20 chats behind the number before you change anything.

    Metrics to stop reporting

    • Total messages sent. It rises when the bot gets wordier.
    • Total conversations. It measures demand, not the bot.
    • Average session length. On WhatsApp, long gaps between replies are normal, and a longer chat often means a worse experience.
    • Button taps on their own. A tap only matters if the path ends in an outcome.
    • “Engagement rate” without a definition. If you can’t write the formula, don’t put it in the report.

    Setting up measurement in an afternoon

    You don’t need a data team. You need consistent labels and a weekly routine.

    1. List your bot paths (track order, shop a category, book a slot, talk to a person) and write the “resolved” outcome for each.
    2. Choose your end tags: bot-resolved, handed-over plus a reason tag such as ho-refund or ho-not-understood, and no-outcome.
    3. Add a trace to every buying path: a discount code, a UTM-tagged link or a reference the bot captures.
    4. Write your conversation rule: for example, a conversation ends when the customer hasn’t replied for 24 hours.
    5. Set up the sheet: one row per week, one column per KPI, with the formulas from the table above.
    6. Book 30 minutes a week to fill in the numbers and read 30 to 50 transcripts: handed-over chats, chats with no outcome and a few “resolved” ones.

    A weekly KPI sheet you can copy

    WeekBot chatsResolved by botHanded overContainmentTop handover reasonOrders with bot codesRevenue tracedCost per resolved chat
    1–7 Nov1,00060040060%Size exchange31₹40,269₹5.64
    8–14 Nov

    The first row uses illustrative figures (31 orders at ₹1,299). The point is the shape: a handful of outcome numbers per week, and one sentence on what to fix next.

    How to measure chatbot KPIs in ChatMitra

    ChatMitra doesn’t have a single chatbot analytics dashboard. Here’s what it shows, and how to collect the rest.

    What you needWhere in ChatMitra
    AI chatbot activityAI Chatbot, Executions tab: "Total executions", "Success", "Failure", "Avg duration" and "Avg steps / run" for the last 30 days, with each run's customer question, phone, steps and time taken
    Keyword rule activityAuto Reply: the "Logs" button on a saved rule opens its recent runs (the last 20, kept for 7 days)
    Resolved and handover tagsAuto Reply: "Enable Add Tag" on a rule, for example tag bot-resolved when a customer taps "That helped" or handed-over when they type "agent". Button and list taps are matched like typed text. See auto-reply
    Handover to a personLive Chat: the "Automation ON / OFF" switch in the chat header pauses AI and auto-replies for that customer for 30 minutes to 24 hours, or until you turn it back on
    Counting tagsContacts: filter by tag, or "Export" (emailed) for a spreadsheet with a Tags column
    Every message, for your own reportSettings, Webhooks: subscribe your sheet, CRM or BI tool to message.received, message.sent and message.status.updated
    Click-to-WhatsApp ad dataThe ad referral details, including the click ID, are forwarded to your webhook, so a developer can pass them to Meta's Conversions API
    Customer feedbackTemplate library feedback templates with quick replies such as "Highly Satisfied", "Satisfied" and "Unsatisfied", plus a rule that tags each answer

    A simple setup:

    1. Create one auto-reply rule per bot path that adds a path tag, such as path-track-order, when the customer taps the path’s button.
    2. End each path with “Did that help?” and two buttons. Add rules that tag bot-resolved on “Yes, thanks” and send your handover message plus handed-over on “Talk to a person”. Add the same handover rule for “agent” and “human”.
    3. Ask agents to add a reason tag when they pick up a handed-over chat and pause automation from the header.
    4. Put a discount code or UTM-tagged link in every buying path’s reply, so orders can be matched in your store.
    5. Each week, count tags from the Contacts filter or export, check the Executions tab for AI chatbot failures, and enter the numbers in your sheet.

    Good to know:

    • No ready-made bot KPI report. Containment, handover, drop-off and conversion come from your tags, exports, webhooks and store data, not from a dashboard.
    • Executions covers the AI chatbot only, for the last 30 days, without an export. Keyword rule logs keep only recent runs, so they’re for checking a rule, not for monthly reporting.
    • No reply when nothing matches. If no keyword rule matches and no AI chatbot, fixed reply or away message is set, the customer gets no automatic answer, and the miss isn’t logged. Read chats with no reply in your weekly sample.
    • Pausing automation doesn’t tag the chat. Agents add the handover reason tag themselves.
    • No agent reports, chat assignment or open/resolved status in the inbox. Inbox filters are “All”, “Unread”, “Replied” and tags.
    • No click tracking or revenue report. Use UTM links and discount codes, and get orders from your store. The Shopify Checkouts page’s “Recovered” count shows checkouts that were completed; it doesn’t prove a WhatsApp message caused them.
    • The ₹0.20 fee is per conversation. One credit when a new 24-hour window opens for a customer, whether the customer or your business starts it; bot and agent replies inside that window cost nothing extra. Plans without credits have no fee.

    Common mistakes in chatbot analytics

    • Reporting activity as success. More messages and longer sessions usually mean a worse bot.
    • Counting abandoned chats as resolved. Pair containment with repeat contacts and read the transcripts.
    • Using web-chat timeouts on WhatsApp. A 30-minute cut-off turns one evening purchase into several “abandoned” sessions.
    • Leaving links untagged. Without UTM parameters or codes, bot-driven sales show up as direct traffic.
    • Changing several things at once. Change one path, then compare the next two weeks with the two before.
    • Forgetting the cost side. A bot that hands over most chats after several messages can cost more than no bot.
    • Never reading chats. Numbers tell you where to look; transcripts tell you what to fix.

    A monthly chatbot review checklist

    • Containment, handover rate and repeat contacts compared with last month
    • Top three handover reasons listed, each with one fix
    • Unrecognised questions reviewed and the most common ones answered
    • Drop-off checked for every buying path
    • Orders and revenue traced to bot codes or UTM links
    • Cost per resolved chat recalculated with current Meta rates
    • Feedback “No” answers read, and opt-outs or blocks checked after any bot change
    • One change chosen for next month, with the KPI it should move
    Clear answers

    Frequently Asked Questions

    Chatbot analytics is the measurement of what a chatbot actually achieves: how many conversations it resolves without a person, where customers get stuck or ask for help, how many chats lead to a sale or booking, and what each resolved chat costs. Good chatbot analytics focuses on outcomes, not on activity such as the number of messages sent.

    Start with five: containment rate (chats resolved without a person), handover rate with the reason, drop-off by step in your main flows, bot-assisted conversion (orders or bookings traced to a bot path) and cost per resolved chat. Add repeat contacts, wait time after handover, unrecognised messages and customer reaction once the first five are reliable.

    There is no universal figure. Containment depends on what the bot is allowed to do: an FAQ bot for store hours can contain most chats, while a bot for complaints should hand most of them over. Microsoft's Copilot Studio documentation defines a similar measure, deflection rate, as the percentage of requests completed through self-service. Track your own rate weekly, check it against repeat contacts so that abandoned chats don't count as resolved, and improve the paths with the most handovers.

    Give every bot path that leads to a purchase its own trace: a discount code such as BOT-KURTA, a UTM-tagged link or an order reference the bot asks for. Count the orders in your store that carry that trace, divide by the chats that entered the path, and multiply by your average order value. For a stricter answer, compare against a group of customers who didn't use the bot, because some of them would have bought anyway.

    Add up Meta's message charges, your platform fee and agent time for the month, then divide by the number of chats resolved. In India, Meta's service messages are free for the first 1,000 per business number each month and ₹0.115 each after that, and ChatMitra charges ₹0.20 per conversation on Starter and Pro. Agent time is usually the largest cost, which is why containment drives the result.

    WhatsApp doesn't report link clicks to the business for ordinary messages. Add UTM parameters to every link the bot sends so that your website analytics records the visit and the order, or use a short link service that counts clicks. For click-to-WhatsApp ads, Meta provides a click ID that you can send back through its Conversions API.

    Look at the main numbers weekly and read a sample of transcripts at the same time, especially chats that were handed over or ended without an answer. Do a deeper monthly review of conversion, revenue and cost per resolved chat, and re-check everything after you change a flow, so you can see whether the change helped.

    Partly. The AI Chatbot's Executions tab shows total executions, successes, failures, average duration and average steps per run for the last 30 days, and each keyword auto-reply rule has a Logs view of its recent runs. Containment, handover and sales KPIs are measured with tags, contact exports, webhooks and your store's order data rather than a ready-made report.

    Hitesh Pathar

    ChatMitra

    Hitesh Pathar 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.