Ask your agent for a monthly client report you can check
How AI agents for client work can draft a monthly report from real numbers: every figure sourced and dated, gaps left as gaps, and nothing sent unchecked.
A dentist's practice manager opens her monthly website report on the first Tuesday of the month. It says visits are up and the site is "performing strongly". She has a board meeting on Thursday and wants to quote a number. Which number? Up from what? Where did it come from? She emails the designer, the designer digs through three dashboards, and a two-minute report turns into an hour of work for both of them.
Now picture the same report with four lines: search clicks this month and last month, from Google Search Console, for these dates; the two contact form tests you ran and whether they passed; the three changes you made; and one line saying phone calls from the site weren't measured this month. She can quote that on Thursday.
AI agents are good at drafting the second kind of report, as long as you set them up to. Give your agent the month's real exports and your work log, a fixed format, and one firm rule: every number names its source and dates, and anything missing is written as missing. Then check the draft against the sources before it goes out. That's the whole method. The rest is how to make it stick.
Can AI write my monthly client reports?
It can write a good draft. It shouldn't be the last one to read it.
A language model is very good at turning a pile of exports and notes into three plain paragraphs a business owner will read. It's also capable of filling a gap with something that sounds right. A report is exactly the place where a confident, wrong number does damage, because the client may repeat it to someone else.
So split the job:
- The agent drafts. It reads the files, pulls out the numbers, compares them with last month and writes it up in your format.
- You check. You spot-check numbers against the source, read the wording as the client would, and send it.
That split is the same one that works for having your agent draft client replies: the agent does the typing, you keep the judgement.
What should the agent work from?
Only what you give it. Put the month's files in one folder per client and tell the agent to use nothing else.
A typical folder for a local business on a care plan:
| File | Where it comes from | What it gives the report |
|---|---|---|
| Search performance export | Google Search Console, Performance report | Clicks and impressions from Google Search, this month and last |
| Visitor stats export | Your analytics tool | Visits and the pages people viewed |
| Work log | Your own notes | Updates, backups, changes made, requests handled |
| Form and booking tests | Your own notes | Which tests you ran and whether they passed |
| Open items | Your own notes | Anything waiting on the client |
A few details about the numbers are worth knowing before you ask for them.
Search Console counts four things. Google's help page for the Performance report lists clicks (people who clicked through to the site from Google Search), impressions (how often the site appeared in results), click-through rate (clicks divided by impressions) and average position. For a local business, clicks are the one to lead with; the others are context.
The newest days can change. Google's help page says the most recent data can be preliminary, still being collected. Export a full, finished month rather than "the last 30 days" on the first of the month.
AI Overviews aren't a separate line. Google's guidance on AI features says sites that appear in AI Overviews and AI Mode are counted in the overall web search traffic in Search Console. If a client asks how many visits came from Google's AI answers, the honest answer is that this report doesn't split them out.
What rules should the agent follow?
Write them once and reuse them for every client. A short instruction file is enough:
- Use only the files in this folder. Don't use anything you remember or can look up.
- Beside every number, write where it came from and the date range, for example "(Search Console, 1 to 31 August)".
- If a number isn't in the files, write "not measured this month". Never estimate.
- Compare with last month only when both months are in the files.
- Describe changes plainly: "up from 212 to 240", not "strong growth".
- Keep it under 200 words, in this order: what we did, what we checked, the numbers, what we need from you.
- Don't recommend new paid work unless it's in the open items file.
Rule 3 matters most. A report that says "calls from the website: not measured" is more useful than one that guesses, because it shows the client exactly what they'd need to measure it. It also keeps you honest: a care plan never promised a number you can't show.
If you've already given your agent your prices so every quote matches, this is the same idea: the agent works from the facts you hand it, not from what sounds plausible.
What should the report look like?
Short, in the client's words, the same shape every month. Here's a format that works for most local businesses:
Your website in August
What we did: Updated the site's software after a backup. Added the new hygienist to the team page. Fixed a broken link on the fees page.
What we checked: The contact form and the booking link, on 4 and 25 August. Both reached you.
The numbers: 240 clicks from Google Search, up from 212 in July (Search Console, 1 to 31 August and 1 to 31 July). Calls from the website: not measured this month.
What we need from you: Your holiday opening hours, when you have them.
Four headings. The client can read it on a phone, and every number can be traced. If you want more on what a small business actually reads, the website monthly report template goes further on layout and tone.
How do you check the draft quickly?
Five minutes per client, in the same order each time:
- Pick three numbers and find each one in the source file. If one is wrong or missing from the file, send the draft back with the rule it broke.
- Check the dates. Full month, and the comparison month is the one before.
- Read the "what we did" list against your work log. Nothing extra, nothing missing.
- Look for vague words. "Strong", "healthy", "significant". Swap each for the number or cut it.
- Read it as the client. Would they know what to do next?
If a client disputes something next month, you have the source file, the date range and the draft. That's a much better conversation than "I think it was about that". The same habit applies to anything your agent writes for a client: approve what your agent sends before it leaves, every time.
Where do reports fit in a care plan?
Put the monthly report in the plan itself, with what it covers and what it doesn't. Your service recipe is the right place: list the files you'll collect, the format, and the day of the month it goes out. Then the report stops being a favour and becomes part of the service, and the agent's instructions come straight from the recipe.
Where Volant fits
Volant builds period reports from the records you already keep for each client: the work done, the requests handled, the payments and the numbers you've added. Reports show what happened, where each number came from, and what is missing. To see how each client's work and promises sit together, start with keeping track of clients.
Whatever your AI agency uses, keep the rule: every number has a source, every gap is written down, and a person reads it before the client does.