Monday, before. An agency manages an assistant for a client and does it well. Answers are maintained, conversations are read and problems are fixed.
The client sees none of this. What they see is an invoice each month for something that runs in the background and produces no visible artefact.
At the budget review somebody asks what the fee is for. Nobody at the client can answer, and a service that was working is cancelled because it was invisible.
Monday before: the work is invisible
Maintenance, monitoring and improvement, all real, all unseen, which is the position every recurring service starts from.
Monday after: the work has a number
Enquiries answered, outside hours, that would otherwise have waited, stated as a figure the client can repeat to somebody else.
Tuesday before: the client judges it on impression
Whether they have heard anything about it recently, which is a poor proxy and the only one available.
Tuesday after: the client judges it on outcomes
Conversations that became enquiries, and what happened to them, which is the number that survives a budget conversation.
Wednesday before: the improvements go unremarked
Twelve answers updated and four gaps closed, none of which the client knows happened.
Wednesday after: the improvements are listed
Briefly, as evidence that somebody is actively maintaining something rather than collecting a fee for a thing that runs itself.
Thursday before: the questions the site failed to answer are lost
Which are the most valuable output of the whole exercise, and which sit unreported in a system the client never opens.
Thursday after: they become the next piece of work
A content recommendation with evidence behind it, which is both useful to the client and additional work for the agency.
Friday before: the budget review is a risk
An unexplained line item defended by an account manager describing activity.
Friday after: the budget review is straightforward
A number, a trend and a list of what the client's team no longer does, which is the case in reporting results clients actually care about.
What to lead with
One number. Enquiries handled, or leads captured, depending on what the client cares about, and everything else beneath it.
What to avoid
Dashboards nobody opens and metrics describing the tool rather than the outcome, which is the reporting failure in how to report chatbot results to your boss or.
What to include once a quarter
A handful of verbatim conversations, which do more to justify a fee than any chart and take five minutes to assemble.
What to do when a month is quiet
Report it anyway, with the number and an honest note that volume was low. A skipped report during a quiet month is what starts the client wondering whether anything happens at all.
What the client should be asked once a year
What would make this obviously worth keeping. The answer is frequently a single number they care about that nobody has been reporting, and it costs one question to find out.
Report before they ask
An agency that sends one number, a trend and three verbatim conversations every month, unprompted, keeps a recurring fee that an agency doing identical work silently will eventually lose. The early period matters most, as in proving value in the first thirty days, and the prospect questions sit in what prospects ask an agency before booking a call. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under agencies.