Spaces

Weekly chat review checklist for telecom and utility teams

This checklist gives a telecom or utility owner a weekly routine for reviewing the conversations an AI agent handled. It helps you spot wrong answers, slow hand-overs and new questions before they grow.

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

Before you start

In telecoms and utilities, questions change with the weather, the network and the billing calendar. An answer that was right on Monday can be wrong by Thursday after a fault clears or a plan changes. A short weekly review keeps the agent and your notes in step with what is really happening.

Set aside forty-five minutes at the same time each week. Open the week's chats, read a sample, and work down the list. Write down what to change in your notes, and who will change it. Small, regular checks beat a big clean-up after something goes wrong.

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

[ ] Read at least twenty chats, including the longest and the angriest.
[ ] Check every outage answer against what the status note said at that time.
[ ] Count how many chats were handed to a person and how long each waited.
[ ] Look for any billing or account answer the agent should have passed on.
[ ] Check all safety and medical-need chats were passed on in minutes, not hours.
[ ] List the five questions customers asked most and see if you have a ready answer.
[ ] Note any customer who wrote again about the same fault.
[ ] Check the tone: calm, short and kind, with no jargon.
[ ] Remove or update any old status note, closure or price note.
[ ] Write three changes for next week and give each an owner.

Turn the review into action

The aim is not to grade the agent. It is to improve your notes. When you find a wrong answer, ask what the agent was told, and fix that. When you find a good answer, copy its wording into your ready answers.

Share one short summary with your team each week: what went well, what we changed and what is coming. It keeps everyone calm about the agent and gives frontline staff a voice in how it behaves.

  • Keep a simple log of changes.
  • Review more often during storms or big faults.
  • Ask your team what customers said that the agent missed.

FAQ

How many chats do I really need to read?

Twenty to thirty a week is a good start for a small team. Choose a mix: some long ones, some that were handed over, and a few that look routine. Larger providers can sample more.

Who should do the weekly review?

Someone who knows the service well, like a customer care lead or the owner. Ask one frontline person to join now and then, since they hear what customers say on the phone.

What should I do if I find a serious mistake?

Contact the customer through a person, put it right, then fix the note and tighten the hand-over rule behind it. Write the lesson down so the whole team learns from it.

More free tools for telecom and utility providers

Read the guide: Answer outage and service questions with an AI agent.