Most "computer repair" calls start with a problem a restart would have fixed. That is not meant to sound dismissive, it is genuinely good news: the highest-volume issues - slow machines, dropped Wi-Fi, printers, email - follow the same short script, and it takes about fifteen minutes to run.
Here is the first-15-minutes checklist I would want anyone in Sacramento to run before deciding whether they need a tech at all.
The first 15 minutes
Restart the thing, fully. Not sleep mode, not "close the lid and reopen it." Power it all the way off, count to ten, power it back on, and let the updates finish. A surprising percentage of issues are just a machine that has run for weeks.
Write down the actual error. "It broke" is not diagnosable. The exact message on the screen - the blue screen code, the popup text, the printer error - tells a competent tech what it is in seconds. Your note may be the difference between a remote fix and a truck roll.
For anything network-related, restart the router. Unplug the router and modem, wait 60 seconds, plug the modem in, wait for solid lights, then the router. Most dropouts and "the internet is slow" moments are stale routing tables, and this fixes them in five minutes with no risk to your data.
Check the obvious physical layer. Is the power cable seated at both ends? Does the outlet actually work (plug in a lamp)? Is the printer on the right network? The cheapest fixes in IT are the ones you can see.
Full step-by-step versions of all of these live in the free troubleshooting guides - six of the most common problems, written in plain language.
Three things that never fix it
While we are here, three things to avoid, because they make paid repairs more expensive:
Random button mashing. Every guess at a password can lock an account out longer. Use the official reset path instead.
"Free cleaner" and "driver updater" downloads from search results. Those download buttons are usually the problem, not the solution. Real tools come from the manufacturer's site.
Popup virus warnings. "Your computer is infected, call this number" is a scam script, not a diagnosis. Close the browser, don't call, don't pay anything. Legitimate alerts come from antivirus you installed.
When calling a tech is the right call
The checklist above is for the ninety percent. Call someone when you hit these:
- Hardware symptoms. No power after the checks above, grinding or clicking noises from a drive, smoke or burning smells, a cracked screen.
- Data loss. If files are missing and you have no backup, stop using the drive immediately and get help. Continued use lowers the odds of recovery.
- Recurring problems. The same thing every few weeks, whether it's a restart loop or a network that keeps dying. That is a root cause, not bad luck.
- Business downtime. If your team cannot work, timebox your own attempts, then delegate. Remote support is usually the fastest route.
The goal of good support is that you never have to become a tech - just know when your ten minutes of free fixes are up.
What good support looks like
When you do call, the provider should price it flat before starting, explain what they found in plain English, and tell you what happens next. No meter running, no jargon, no surprise line items. That is how I run it: flat-rate quotes per project in IT services, a one-time remote tech support option, and free first-15-minutes on every session.
Run the checklist first. If it still misbehaves, you'll arrive with a note instead of a shrug, and that makes the fix faster for everyone.