Spaces

Weekly chat review for broadband, mobile and satellite providers

This checklist gives telecom owners a weekly routine for reading the chats their AI agent handled. It helps you spot wrong answers, repeat faults and gaps in your written information in about half an hour.

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

Before you start

A telecom business changes all the time. Plans move, an area gets new coverage, a router model is replaced, a billing date shifts. An agent that answered well last month can quietly drift out of date. A short weekly read keeps its facts matching the real business.

Set a fixed half hour, for example Friday morning. Open last week's chats and go down the list. Mark anything odd, then fix the written information the agent relies on. Do not try to read every chat; look at a sample and at every chat that was handed to a person.

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

[ ] Read five chats about faults from start to finish.
[ ] Read every chat that was handed to a person.
[ ] Look for customers who wrote twice about the same problem.
[ ] Check that every coverage answer carried the line about differences by address.
[ ] Check that no chat asked for a password, a PIN or full card details.
[ ] Find the three most common questions and check the written answers still match your plans.
[ ] Note any question the agent could not answer.
[ ] Check how long customers waited for a person after a hand-over.
[ ] Write down one change to make before next week.

What to look for in a fault chat

Read as the customer. Did the agent say sorry once and move on? Did it ask for the address and the service in the first couple of lines? Did the customer end the chat knowing what happens next? If not, the fault steps need rewriting.

Also watch for a pattern in one place. Several customers on the same street writing about the same drop in speed is not a chat problem, it is information your network team should hear about quickly.

  • Count how many chats mention the same area.
  • Mark any chat where the customer sounded worried about safety.
  • Share patterns with your engineers by the end of the week.

FAQ

How many chats should I read each week?

A sample is enough: around ten, plus every chat handed to a person. Pick a mix of faults, plan questions and bill queries so you see the full range of what customers ask.

Who should do the review?

The owner or a support lead who knows the plans well. Have a second person look now and then, because fresh eyes catch wording that sounds fine to the person who wrote it.

What if the review shows lots of mistakes?

Fix the most common one first, then check the rest next week. Most problems trace back to a missing or out-of-date fact, which is quick to correct once you find it.

More free tools for broadband, mobile and satellite providers

Read the guide: Answer customer messages for telecommunications providers.