Here is a belief that many new tech-support agents pick up in their first week: “Internet problem? Ask them to restart the router and the device. That solves 90 per cent.” Whether the number is right, I do not know, because I have not seen reliable data for it. What I can say is that restarting is a fine step but a poor strategy, and agents who rely on it alone end up with long calls and repeat contacts.
Why guessing costs time
A home internet connection is a chain. A device talks to the Wi-Fi router, the router talks over a cable or fibre line to the provider’s equipment, and the provider connects to the wider internet. A fault can sit at any link. If you try fixes in random order, you may fix the problem by luck and learn nothing, or you may change settings on a healthy link and create a second problem.
The disciplined way is to isolate: start from the customer’s side, test one link at a time, and move outward. Each test should split the possibilities in two.
Layer one: how big is the problem?
Before touching anything, ask questions. Is it one device or all of them? One app or every website? Did it ever work, and when did it stop? Did anything change, such as a new router, a power cut, a plan change or a thunderstorm? A single phone that cannot connect while a laptop works points at that phone. Every device failing points at the router or beyond.
Also ask whether the customer is connected to the right Wi-Fi network and whether airplane mode is on. This sounds silly. It is regularly the cause, and checking it politely costs ten seconds.
Layer two: the device to the router
If one device fails, ask it to forget and rejoin the Wi-Fi network, restart the device and check that it is not set to a manual IP or proxy it should not use. A useful question is whether the device is connected to Wi-Fi but shows “no internet”. That means it reached the router but the router is not passing traffic out. A device that cannot see the Wi-Fi at all suggests distance, router Wi-Fi switched off, or a hardware issue.
Layer three: the router and its lights
Ask the customer to read the router’s indicator lights to you. Labels vary by model, so do not assume. Typically one light shows power, one the Wi-Fi, and one the line or internet status. A line or internet light that is off or red, or blinking in a way the manual calls a fault, tells you the router is not getting a signal from the provider. Now a restart is justified: switch the router off, wait about a minute, switch it on and wait a few minutes for it to reconnect. Make sure cables are firmly seated. If a wired laptop works but Wi-Fi does not, the problem is the Wi-Fi part of the router.
Layer four: the line and the provider
If the router is healthy but the line light stays down, or the router shows connected yet nothing loads, the fault may be outside the home: a cut or damaged fibre or cable, a local outage, an unpaid bill leading to suspension or a problem with the provider’s account configuration. Here the agent’s tools matter. Check for known outages in the customer’s area, check account status and the line diagnostics visible on your system, and raise a ticket with a field technician when needed, giving the facts you have already collected so the engineer does not start again.
One more check at this stage: “connected but slow” is a different complaint. Ask whether the slowness is at certain times (evening congestion), on certain devices or only far from the router, and consider whether many devices are using bandwidth at once. A wired speed test next to the router separates a line problem from a Wi-Fi one.
Call habits that help
- Explain what you are about to do and why, in plain words, so customers can follow and not fear pressing the wrong thing.
- Never ask for the Wi-Fi password beyond what the process requires, and never ask for banking details during a technical call.
- Do not ask a customer to factory-reset the router without warning: it erases their settings, and some need provider details to set up again.
- Record each step and result in the ticket, so the next person, or the same customer calling back, does not repeat everything.
- Confirm the fix with the customer before closing: ask them to load a page and a video, not just to say it seems fine.
So was the belief wrong?
Not entirely. Restarts clear many temporary glitches, which is why they appear in every script. The error is the belief that it replaces thinking. Used at layer three, with a reason, a restart is a test. Used as the first and only move, it is hope. And the questions at layer one are what let you pick the right test, because they take you from “internet not working” to a specific link in about a minute.
The same method carries over to many other faults: email not sending, an app that will not open, a printer not responding. Break the chain into links, test the middle, and decide which half to examine next.
Leave a Reply