Spaces

First-reply checklist for phone, mobile and broadband customers

This checklist shows what the first reply to a new customer message should hold when the question is about a dead line, a weak signal, a plan or a bill. It is made for carriers, mobile providers and resellers.

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

Before you start

A customer who writes to a carrier is rarely relaxed. The router light is orange, the phone shows no bars, or the bill looks bigger than last month. They want to hear that someone has understood the problem and knows the next step. The first reply sets that tone, and it often arrives while your team is busy with a wider fault.

Read down the list and tick what your replies already do. Each gap is a place where customers write a second and third time, which costs you more time than one good answer. Share the list with whoever replies, whether that is you, your support desk or your AI agent, and fix the gaps in order.

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

[ ] Name the problem back to the customer in one line.
[ ] Ask which service the message is about: home broadband, mobile or a business line.
[ ] Ask what the lights or the phone screen show right now.
[ ] Ask for the service address or the number, but not for passwords or full card details.
[ ] Check whether a known outage covers the area before giving steps.
[ ] Give one or two simple steps, such as a restart, and ask them to report back.
[ ] Say plainly if the matter needs a person, such as a bill dispute or a number move.
[ ] Offer a technician window if the basics fail.
[ ] Ask how they would like to be contacted and when.
[ ] End with what happens next and when they will hear from you.

A first reply that does the job

Picture a customer writing at seven in the morning that the broadband is down. A good first reply sounds like this: Sorry about that, I know it is a bad start to the day. I do not see a fault on your street. Could you tell me what colour the router light is?

It names the problem, says what you checked and asks one question. That is enough. The second message can carry the steps.

Slips that cost you extra messages

These habits send customers back to you again and again.

  • Pasting a long fault guide into the first reply.
  • Asking for the address, the account number and the date of birth in one go.
  • Saying a technician will "be in touch" without any window.
  • Telling someone to restart the router when you can already see an outage.

FAQ

Should the first reply try to fix the fault straight away?

Give one simple step if the fault looks small, but start by showing you understood. If your outage map shows a known problem, say so first and skip the restart steps.

What should I not ask for in a first reply?

Do not ask for full passwords, card numbers or security answers in chat. Ask for an address or number to find the account, and let a person do identity checks.

How long should a first reply take?

During a fault, faster is better, because customers are often offline and anxious. A short acknowledgement within minutes beats a perfect answer an hour later.

More free tools for phone, mobile and broadband providers

Read the guide: Answer line, signal and plan questions for your phone and broadband customers.