Spaces

A weekly chat review checklist for software and IT firms

This weekly checklist shows a software or IT firm what to review in the client chats an AI agent handled, including urgent reports, handovers and prospect enquiries. It takes about half an hour.

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

Before you start

An agent that answers clients all week will make small mistakes, and some of them will repeat. A weekly review is how you find them early. For a software firm the stakes are specific: a missed outage, an answer that overshared a ticket, or a prospect who never got a call back.

Set a regular half hour, ideally the same day each week, and open a sample of chats from the last seven days. Tick each point below as you go. Write down what you change in the agent's instructions, so next week's review can check that the fix worked.

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

[ ] Read every chat that was marked urgent and check the time to a person.
[ ] Check that every incident chat has a ticket with page, time and error text.
[ ] Look for chats that should have been urgent but were treated as routine.
[ ] Check that no password or key was typed into a chat and left there.
[ ] Review the prospect chats and count how many reached a booked call.
[ ] Read a few answers about release dates, hosting and renewals.
[ ] Note any question the agent could not answer.
[ ] Check tone with one client who was frustrated.
[ ] Confirm every handover note told the engineer what they needed.
[ ] Update the instructions with at least one improvement.

A simple routine that works

Set a fixed half hour on a quiet day, perhaps Friday afternoon after the release is out. Open the urgent chats first, then a handful of random ones, then every chat from a prospect. Keep a running note of fixes so patterns show up across weeks.

If you find yourself changing the same instruction three weeks in a row, the rule is probably unclear. Rewrite it with an example, such as a real message from a client at {business}, and the agent will follow it more steadily.

Signs that something needs fixing now

Do not wait for the weekly slot if you see any of these.

  • A client reports the same fault twice and gets two different answers.
  • An urgent chat sat for longer than your agreed response time.
  • The agent promised a date or a price nobody authorised.
  • A client asks whether they are talking to a real person and is unhappy with the reply.

FAQ

How many chats should we read each week?

Read every urgent chat and every prospect chat, plus a small random sample of routine ones. For a small firm that is often fewer than thirty conversations and takes about half an hour.

Who should do the weekly review?

Ideally someone who knows both your clients and your systems, such as the support lead. Rotate it now and then so a second person learns where the agent is strong and weak.

What should we do when the agent gets something wrong?

Fix the instruction that caused it, add a short example of the right reply, and tell the client the correct answer yourself if it affected them. Then check it next week.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.