← BlogIT Help

What to Do Before Calling Tech Support

Published

March 9, 2026

Read time

4 min read

Author

Charlie McKinney

Location

Charlotte, NC

Share

Half of tech support calls end with a simple fix that takes two minutes. Run through this list first — you might save yourself the wait and the bill.

01

Restart everything

It's a cliché because it works. Restarting clears temporary memory, closes hung processes, forces the device to reconnect to the network, and applies any pending updates. Restart your computer, your router, and any device involved in the problem. Not sleep-and-wake — a full shutdown and power cycle. Give each device 30 seconds off before turning it back on.

02

Check the obvious connections

Cables work loose over time. Before assuming something is broken, physically check that every cable involved is seated firmly — power cables, ethernet, HDMI, USB. For Wi-Fi issues, make sure you're connected to the right network and not a neighbor's with a similar name. These feel like obvious checks, but they're the cause of a surprising number of calls.

03

Check if the problem is happening elsewhere

Is a website down for everyone or just you? Visit downdetector.com and search the service. Is your internet slow on every device or just one? Test on your phone over Wi-Fi — if that's also slow, the issue is with your connection; if only one device is slow, the issue is with that device. This narrows down the problem before any diagnosis happens.

04

Write down the error message

When something goes wrong, take a photo of the screen with your phone or write down the exact wording of any error message. Error messages look like gibberish, but they're precise — "DNS_PROBE_FINISHED_NXDOMAIN" means something completely different from "ERR_CONNECTION_TIMED_OUT." Having the exact text cuts diagnostic time significantly.

05

Note what changed recently

Think about what happened before the problem started. Did something update? Did you install new software? Did you move the computer or plug something in? Did it start after a storm or power outage? Timing correlations aren't always the cause, but they're a strong starting point. "It started happening after the Windows update last Tuesday" is useful. "It's been broken for a while" is less so.

Charlotte, NC · On-site & Remote

Still stuck after trying all this?

That's what I'm here for. Remote and on-site support for homeowners and small businesses across the Charlotte, NC area. Fast turnaround, plain language explanations.

Contact me
Share