Can it be fixed without a visit? What remote support genuinely can and cannot do

About half the faults people ring us about have nothing physically wrong with the machine at all. The hardware is fine; something in the software, the settings or an account has gone sideways. And for that half, a visit is often the slow way to get help, because the fault can be fixed over a secure link, while you watch, from wherever you are.

This guide is the honest split: what remote support genuinely can do, what it never will, and how to tell which side of the line your problem sits.

What genuinely works over a link

The pattern is simple: if the fault lives in software, it travels down a link. The common ones we see:

• Pop-ups and scare pages. The full-screen warning with a phone number on it is almost always a website pretending to be your computer, not a real infection. Over a link we can close it down and check whether anything real was left behind. If you have one on screen right now, read the scam guide first, because the number on that warning is not who you should be calling.
• Email that will not connect, on a computer or a new phone, especially the kind that keeps rejecting a password you know is right.
• Printers that say offline while sitting there, plugged in, mocking you.
• A computer that has slowed to a crawl, which is best looked at while it is actually being slow, on the machine, not from a description of it. What we look for is covered in the honest speed-up guide.
• Settings that have wandered: the screen that looks wrong, the browser that changed itself, the thing that moved and cannot be found.
• Setup and show-me-how: new machines, new accounts, moving to a new phone, and the questions you would rather be shown once than guess at for an hour.
• Parental controls and family devices: screen time, app limits and safe search, set up properly rather than fought over.

What never will, and why the honesty matters

If the fault lives in the hardware, no link reaches it. A cracked screen, a dead battery, a charging port, a machine that will not power on at all, a drive making clicking noises: those need hands on the machine, every time. No honest person will fix a cracked screen down a link, and anyone who says otherwise wants something other than your screen fixed.

There is a second category worth naming: faults that are technically software but should not be handled remotely. A drive that is failing is the big one. If your files are at risk, the safe move is to stop and treat it as a recovery job, not to run tools over a link on a drive that may have limited reads left in it.

The point of the free phone call is exactly this split. Describe the fault, and we tell you straight which kind you have, before anything is agreed. If it is not remote-suitable, the call costs nothing and you have a straight answer about what it actually needs.

How a session actually runs

You call, we listen, and if remote can fix it you get one fixed price for the session before we connect. Then the connect page walks you through it, device by device: one small open-source app, two boxes to fill in, and we stay on the phone throughout. The session runs through our own server in the EU rather than a rented middleman. You watch everything we do, at watching speed, you can end it with one click, and when it closes nothing stays behind: no access, no software running, nothing watching.

And if the session cannot fix it after all, the fee is credited in full against the visit that follows. Nobody pays twice for one fault. That is the whole model, and it is written into our terms rather than left as a nice sentence on a blog.