Helping a relative with their computer, remotely, without making it worse

The hard part is never the technical problem. It is the ten minutes of getting connected with someone who cannot describe what they are seeing — and doing it in a way that does not train them to accept the next request from a stranger.

Getting connected with the fewest steps

Every instruction you give over the phone is a chance to lose the thread. Optimise ruthlessly for the number of things they have to do, not for elegance.

1. Send the download link by message, not by voice. "Go to r, e, m, o..." is where these calls die. Send a link they can tap, then talk them through what happens after they tap it.
2. Prefer a tool with no account on their side. Every signup is a password they will have to create, mistype and then reset, on a call, under pressure. If it can be a code, make it a code.
3. Ask them to read you the code, digit by digit. Do not ask them to type anything on your behalf. Reading is much easier than typing for most people, and the failure mode is obvious rather than silent.
4. Stay on the phone while it connects. The moment of "is it working?" is when people close the window.

Before you change anything

• Ask what they were doing when it started. Not what the problem is — what they were doing. The description of the problem is usually a theory; the sequence of events is data.
• Look before clicking. Take in the whole screen. The answer is frequently visible immediately: an unread dialog behind the window, a disconnected cable icon, a full disk warning, a browser toolbar that arrived with something else.
• Ask before you close things. Windows you consider clutter may be work they have not saved. This is the single most common way remote help causes damage.
• Say what you are doing as you do it. Partly so they are not watching the cursor move on its own in silence, which is unnerving; partly so they might learn the path.

Fix the cause, then reduce the next call

Solving the immediate problem is the smaller half. The larger half is making the next three calls unnecessary:

• Turn on automatic updates rather than promising to check in later.
• Remove the toolbars, "cleaners" and startup clutter that arrived bundled with something. These generate a steady stream of alarming pop-ups that in turn generate calls — and they train exactly the wrong reflex.
• Make text bigger. A surprising share of "I cannot find the button" is "I cannot read the button". Display scaling at 125% or 150% solves more support calls than most software.
• Set up a printer, a backup and a password manager once, properly, while you are already connected. These are the three recurring calls.
• Write down what you changed and send it to them. Partly a record for you, partly so they can see that changes are documented rather than mysterious.

Do not teach the habit a scammer needs

This is the part most guides skip. Every remote support session teaches something, and the wrong lesson is "when someone says they are helping, install what they tell you to install".

1. Establish that they initiate, always. You will never phone them out of the blue asking to connect. If someone does, it is not you.
2. Use one tool consistently. An unfamiliar name is a signal they can act on. If they only ever see one, anything else stands out.
3. Point out that you never ask for passwords or card numbers, and that nobody legitimate will.
4. Tell them to end any session where they feel rushed, including one with you. The instinct to not be rude is the instinct scammers rely on.

That last group takes two minutes and is worth more than the fix. The full anatomy of the fraud is in how the support scam works — worth reading before you set someone up with remote access for the first time.

When remote is the wrong answer

Be willing to stop. If the machine will not boot, if the network is down, if a drive is failing, or if the screen is black, there is nothing to connect to and the call is only going to frustrate both of you. Hardware problems need hands. So does anything requiring a BIOS screen, which exists before any operating system is running and therefore before any remote tool exists.

More guides