Every family has one. You are reading this, so it is probably you — the person who gets called when the printer stops working, when an email looks suspicious, when the tablet is "doing something weird." The calls come at inconvenient times and the problem is usually described in terms that make it impossible to diagnose remotely.
Most of this is avoidable. Not by making relatives more technical, which does not work and is faintly insulting as a goal, but by setting things up so the common failures stop happening and the remaining ones are fixable without a car journey.
What changed in 2026
- Remote access got easier and safer. Built-in screen sharing in mainstream operating systems and messaging apps removed the need to install and maintain third-party tools.
- Passkeys started replacing passwords, which is genuinely good for people who struggle with password managers — but the recovery story changed, and that recovery story is what you will be dealing with.
- AI-assisted scams got much more convincing. Impersonation calls using cloned voices moved this from an occasional worry to a standing risk, particularly for older relatives.
- Subscription sprawl became a support burden. Devices increasingly stop working because a subscription lapsed, not because anything broke, and diagnosing that over the phone is its own category of frustrating.
Set up remote access first
This is the highest-leverage thing on the list and most people do it in the middle of a crisis rather than in advance.
Being able to see the screen turns a twenty-minute call into a two-minute one. Without it you are asking someone to read menu items aloud while they describe a dialog box, and they are stressed, and neither of you is enjoying it.
Use whatever is built in where possible — mainstream operating systems and video-call apps all offer screen sharing now, and something already installed is something you will not be maintaining. Set it up while you are physically present, run through it once together so it is familiar, and make sure they know how to start it without you.
One boundary worth setting explicitly: unattended access, where you can connect without them accepting, is convenient and worth discussing rather than assuming. Some people are fine with it and some are not, and the conversation matters more than the setting.
Document the accounts
Most genuine family tech emergencies are not device problems. They are account problems — locked out of email, phone replaced and two-factor codes gone, a password changed and forgotten, an account recovery that needs information nobody has.
Write down, for each important account: which email address it uses, where the recovery codes are, what phone number is attached, and whether there is a password manager and how to reach it. Store that record somewhere durable — a password manager's shared vault, or genuinely on paper in a safe place.
The scenario to plan for: their phone is lost or dead. If two-factor codes live only on that phone and recovery codes were never saved, some accounts become unrecoverable. That is not a hypothetical, it is the most common serious tech loss families experience, and fifteen minutes of preparation prevents it entirely.
Passkeys change the details but not the principle — recovery still depends on having access to some other trusted device or account. Passkeys vs 2FA covers the mechanics, and the best password managers covers shared vaults, which are ideal for exactly this.
Reduce the surface
Every application, subscription, and gadget is something that can break and become your problem. The most effective support strategy is having less to support.
Turn on automatic updates everywhere. Deferred updates are a large share of recurring problems, and the postpone prompt gets postponed indefinitely.
Remove what is unused. Software nobody opens still generates prompts, notifications, and confusion.
Standardise where you can. Two people on the same platform is dramatically easier to support than two people on different ones. Not worth forcing, worth nudging at replacement time.
Prefer defaults. Every customisation is something you will have to remember and re-apply after a reset.
Write down the subscriptions. What renews, when, on which card. Failed payments break things in ways that look like faults.
Scam protection is part of the job
The most damaging thing that happens to family members is not a broken device. It is a convincing impersonation — a call claiming to be a grandchild in trouble, or a support agent needing remote access to fix a problem that does not exist.
Two rules cover most of it. Nobody legitimate asks for remote access after calling you unexpectedly; support you did not initiate is not support. And any urgent request involving money gets verified by hanging up and calling back on a known number, no exceptions.
Agree a family code phrase, out loud, and make sure the people most likely to be targeted know it. Deepfake scam protection covers why voice recognition is no longer sufficient verification, which is the part that surprises people.
Common mistakes
- Fixing without explaining. Not to teach them everything — just enough that a recurrence is recognisable.
- Installing tools you will maintain forever. Every addition is a permanent obligation.
- Not setting up remote access in advance. You will want it during the crisis, which is the worst time to configure it.
- Assuming recovery information exists. It usually does not, until someone writes it down.
- Treating the symptom. The same call every month means the underlying cause is untouched.
- Being condescending about it. People who feel stupid asking stop asking, then handle a scam call alone.
FAQ
How do I stop the same question recurring?
Ask what they were trying to do rather than what went wrong. The recurring question is usually a workflow problem — a shortcut that is hard to find, a step that is easy to skip. Fix the workflow and the question stops.
What if they live far away?
Remote access plus documented accounts covers most of it. For the rest, a local contact for physical problems — a neighbour, a nearby relative, a paid service for hardware — is worth arranging before it is needed.
Should I manage their passwords for them?
A shared password manager vault is usually better than either extreme. They keep control, you have access when something goes wrong, and nobody is writing passwords in a notebook that gets lost.
How do I handle a device that should be replaced?
Time it around a support deadline rather than a fault. A device no longer receiving security updates is a concrete reason with a date attached, which is easier to act on than "it is getting old."
Where to go next
For the account layer that most emergencies actually involve, read the best password managers and passkeys vs 2FA. For the scam side, deepfake scam protection, and for making sure family photos survive all of this, photo backup strategy.