A monthly chatbot report for clients: DMs, leads and bookings in one page
Short answer: A monthly chatbot report for a client should fit on one page and answer three questions: how many people messaged, how many became leads, and how many of those booked or bought. ManyChat, a tool that automates replies to messages on Instagram, Facebook Messenger, WhatsApp and TikTok, gives you conversation and contact counts, but it does not give you a finished client report, so you add the lead and booking numbers from the client's calendar or CRM (the system where they keep customer records). Show five or six numbers, one short note on what changed, and one decision for next month. Be plain about what you cannot prove.
You run DM automation for clients, and each month you have to send something that proves it is working without overwhelming them with charts.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A good monthly report is one page, six numbers and a short story. The numbers: conversations started, leads captured, leads qualified, bookings or sales, average first reply time, and handoffs to a human. The story is two sentences on what moved and why, plus one thing you will change next month. Clients do not read twelve-page decks. They read the top third of the first page.
This guide gives you the metrics, a layout you can copy, a worked example with made-up numbers, and the limits of what you can claim. It is written for an agency that runs ManyChat for clients, but the layout works for any chat automation tool. A DM is a direct message, a lead is a person who gave you a way to contact them and showed interest, and attribution means deciding which action caused a sale. A flow is the set of automated chat steps a client's account follows. Instagram, Facebook Messenger and WhatsApp are chat apps run by Meta, the company behind Facebook, and Meta sets the rules for what automation may do on them. TikTok is the short-video app that also has business messaging.
This page may contain affiliate links from which Blur Studio earns commissions.
Metrics that matter
Pick numbers that follow the path a customer takes. Every number should answer "so what" for a business owner.
| Metric | Plain meaning | Where it comes from |
|---|---|---|
| Conversations started | People who sent a message or replied to an automated one | The chat tool's contact or conversation view |
| Leads captured | People who left an email, phone number or booking intent | Data collected in the flow, a Google Sheet or the CRM |
| Leads qualified | Leads that meet the client's own test (area, budget, service) | A tag or field your flow sets, checked by the client |
| Bookings or sales | Appointments held or orders paid | The client's calendar, CRM or shop. Not the chat tool. |
| First reply time | Minutes from the first message to the first answer | Inbox timestamps, or a sample you check by hand |
| Human handoffs | Chats a person had to take over | A "needs human" tag or the Inbox assignments |
Two extra numbers help when the client asks why a bill changed: active contacts used and the plan allowance. As of November 2026, ManyChat's pricing page counts an active contact as a real person you interact with during the monthly billing period, counted once however many messages they send. Anyone who messages you counts, not only people you reached by automation. Add one line to the report showing used versus included, so a busy month never surprises the client. For how that count works, see contacts count and billing surprises. Plans and prices vary by billing country, so check the pricing page for your own numbers.
Numbers to leave out
- Total messages sent. It rises when you add steps. It says nothing about business value.
- Open or read rates. Read data differs by channel and tool, so check what your channel reports before you quote it. Clients also misread it.
- Follower growth credited to the bot. A giveaway or a post did that, not the flow.
- Vendor marketing percentages. Never quote a tool's own claims about lead capture or conversion lift. They are not your client's results.
Layout: one page, four blocks
Use the same layout every month so the client learns where to look. Here is the one I would use.
- Headline strip. The six numbers with last month beside each. Use plain labels like "People who messaged us" instead of "inbound conversations".
- The path. One simple funnel line: 412 messaged, 138 left details, 61 qualified, 19 booked. Four numbers in a row beat any chart.
- What changed. Two or three sentences. "Replies after 6 p.m. rose because the story campaign ran Thursday. We added a pricing question to the flow on the 12th."
- Next month. One test, one fix and one thing you need from the client, such as updated opening hours.
Put a short notes strip at the bottom for the three or four things that went wrong: a flow that failed, a platform problem, a human who did not answer within the target. Clients trust reports that include bad news. If you need a general reporting layout for non-chat work, the agency client reporting template covers the wider shape, and client reporting software for agencies compares tools that build it for you.
Worked example (made-up numbers)
These numbers are invented to show the method. They are not benchmarks and not results from any real client.
Client: a dental clinic. Channels: Instagram and WhatsApp. Month: October. Your fee: a monthly care retainer.
| Metric | September | October |
|---|---|---|
| People who messaged us | 340 | 412 |
| Left their details | 104 | 138 |
| Qualified (right area, wants a check-up or whitening) | 49 | 61 |
| Booked a first visit | 14 | 19 |
| Median first reply time | 3 min | 2 min |
| Handed to a person | 38 | 44 |
| Active contacts used of 2,500 included | 340 of 2,500 | 412 of 2,500 |
The story in two sentences: "Messages rose by about a fifth after the Thursday story series, and bookings rose from 14 to 19. Eight of the 44 handoffs were about insurance, so we are adding an insurance answer to the flow next month."
Notice what the example does not say. It does not say the bot made 19 bookings. It says 19 people who messaged booked. The next section explains why that wording matters.
Where each number comes from in practice
- Messaged and left details: the chat tool's contact list filtered by date and tag. ManyChat has no single full export of all contacts, so the simplest route is to have the flow write each lead to a Google Sheet or a CRM row as it happens. Its Help Center describes exports via collected data, Google Sheets or an external request.
- Qualified: a tag your flow sets after the qualifying questions. Agree on the test in writing with the client first. See lead qualification questions.
- Booked: pull from the client's calendar. If the flow sends people to a booking link, add a "source" field to that form so the booking can be matched back. Sending chat leads to a CRM and calendar shows the setup.
- Reply time: check a sample of 20 chats by hand if the tool does not report it. State that it is a sample.
Honest limits of attribution
Attribution is the hard part, and where agencies overclaim. Here is what you can and cannot say.
- Last touch is not cause. A person may have seen an ad, visited the website, then messaged. The chat was one step. Say "these bookings started in a DM", not "the bot generated these bookings".
- Offline and phone bookings are invisible. If someone messaged, then phoned the clinic, your report misses it. Ask the front desk to ask "how did you hear about us" and log it.
- People who go quiet are not counted as lost. A missing booking might be a no, or a booking made a month later. Use a fixed window, such as bookings within 30 days of the first message, and state that window in the report.
- Platform gaps. Follow to DM, which messages new followers, has an open Meta-side problem on ManyChat's status page as of November 2026, so a dip in that trigger may not be your flow. Check the status page before you explain a drop. Platform outages belong in the notes strip.
- Do not promise a rate. Do not write "a 20 percent lift" as a forecast. Report what happened, with the dates.
- Privacy. A client report should not include names or message text. Share counts and, if needed, a few anonymised examples. This is information, not legal advice: check local law and the platform's current rules on storing message content.
Copy-ready monthly checklist
- Export or copy the month's leads into one sheet on the 1st.
- Check the status page and your own flow log for outages and failed steps.
- Count the six metrics and write last month beside them.
- Add the used-versus-included contact line.
- Ask the client for booking and sales numbers by the 3rd.
- Write two sentences on what changed and one decision for next month.
- List what went wrong in plain words.
- Send the report by the 5th with a 15-minute call offer, not a long meeting.
A test for your own report
Before you send the first one, hand it to someone who does not work in marketing. Pass: they can say in one sentence what happened and what you will do next. Fail: they ask what a term means or which number matters. Fix the labels until it passes. Repeat once a quarter, because clients change.
Who should skip this style of report
- Clients who sell through the shop or phone, not chat. If DMs are a small side channel, fold two lines into a wider marketing report.
- Agencies with only a few chats a month. The numbers are too small to trend. Report counts and examples instead.
- Clients who need live dashboards. A monthly page will not satisfy them. You need a connected dashboard, which is a bigger build.
How I'd approach this
I would agree the six numbers in the contract before launch, so nobody argues about definitions in month three. I would make the flow write every lead to a sheet from day one, because rebuilding history later is painful. And I would use the same one-page layout for every client, so a new hire can produce a report in an hour.
If you are still choosing a tool, start with ManyChat's Free plan to test your reporting setup on a demo account. As of November 2026 the Free plan includes 25 active contacts, enough to test the flow but not to run a client. Check ManyChat's pricing page for what you need. For how to price the reporting into your retainer, see how to price chatbot work for clients, and for the service itself, adding DM automation as an agency service.
If you want the numbers to feed a live dashboard instead of a monthly page, Blur Studio builds the custom version: connections between your chat tool, CRM and calendar, plus ongoing care. See what that includes.
Questions people ask
What should a chatbot report for a client include?
Six numbers: conversations started, leads captured, leads qualified, bookings or sales, first reply time and human handoffs. Add last month beside each, two sentences on what changed, and one plan for next month.
Can ManyChat produce a client report for me?
It shows contacts and conversation activity inside the tool, and the Help Center describes exports through collected data, Google Sheets or an external request. It does not give you a finished client report with bookings, so you add those from the client's calendar or CRM. Check the current features in your plan.
How often should I send the report?
Monthly is enough for most small clients. Send it by the fifth, once the client has given you booking numbers. Send a short alert in between only if something breaks.
How do I show bookings came from DMs?
Add a source field to the booking form or tag the lead in the CRM when the flow sends it. Then count bookings within a fixed window, such as 30 days after the first message. Say that other channels may also have played a part.
Should I show message text to the client?
Counts are safer than text. If you show examples, remove names and contact details. This is not legal advice, so check local privacy law and the platform's current rules.
What do I do if numbers drop one month?
Report the drop, and check causes in order: a failed flow step, a platform issue on the vendor's status page, a change in the client's posting, then seasonality. Write the cause and the fix in the notes strip.
How do I explain contact counts and billing to a client?
Add one line showing active contacts used against the plan allowance. On ManyChat, an active contact is a person you interact with during the billing month, counted once. Read ManyChat pricing explained for the current plans.
More in this topic: ManyChat: for agencies (8 guides) →