Spaces

Weekly chat review for program office conversations

This checklist gives a program office a short weekly routine for reading the chats an AI agent handled. It shows what to check on accuracy, handovers, tone and out-of-date guidance.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Public programs change often. A deadline moves, a form is replaced, a clinic changes its day. Your agent will keep repeating whatever it was last told, so a weekly look at its conversations is the best protection against old information reaching the public. It also shows what people really ask.

Set aside half an hour at the same time each week, ideally with the person who owns the guidance. Open a sample of recent chats, work down the list below and note any change. Keep the notes in one place so you can see what improves over a month.

Tick each one as you go. 0 of 10 done.

[ ] Read a sample of chats from each program, not just the busiest one.
[ ] Check each deadline and date quoted against the current calendar.
[ ] Confirm every form or link the agent shared is still current.
[ ] Look for any answer that sounded like a decision or a promise.
[ ] Check that every sensitive message was handed over quickly.
[ ] Time how long handed-over chats waited for a person.
[ ] Note questions the agent could not answer.
[ ] Read the tone of five replies out loud.
[ ] Check that no one shared sensitive details in the chat unprompted.
[ ] Write down one change and one thing that worked.

Turning chats into better guidance

The review is not about blame. Each odd reply shows where your written guidance is thin. If three people asked whether a neighbour can collect documents, write a short answer once and add it to the guidance. Next week those chats should simply resolve.

Keep a running list of changes with dates. If a complaint ever arrives, you will be able to show what the office told the agent and when you corrected it.

Who should do the review

Pick someone who knows the programs well enough to spot a wrong answer.

  • A team lead for one program, rotating each month.
  • A second pair of eyes for safeguarding and complaints chats.
  • Someone who can edit the guidance the same day.

FAQ

How many chats should we read each week?

A sample is enough. Aim for ten to twenty across your programs, plus every chat that was handed over to staff. If volume is very low, read them all and the habit will still take only minutes.

What should we do if the agent gave a wrong answer?

Correct the guidance first so it cannot happen again. Then, if the person acted on the wrong answer, have a member of staff contact them to put it right and apologise plainly.

Do we need to review chats that went smoothly?

A few, yes. Good chats show you what to keep and give your team a sense of what works. Reading only complaints makes the whole service seem worse than it is.

More free tools for education, health and social program offices

Read the guide: Answer routine program questions in chat, and keep every decision with your staff.