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

The technical problem is rarely the hard part. The hard part is the ten minutes of getting connected with someone who cannot tell you what is on their screen — and doing it in a way that does not train them to say yes to the next stranger.

Getting connected with the fewest steps

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

1. Send the store link by message, not by voice. "Go to the Play Store and search for..." is where these calls die. Send a link they can tap.
2. Prefer a tool with no account on their side. Every signup is a password they will create, mistype, and then need to reset — on a call, under pressure.
3. Ask them to read you the code, digit by digit. Do not ask them to type something you dictate. Reading is far easier than typing for most people, and mistakes are obvious rather than silent.
4. Stay on the phone while it connects. "Is it working?" is the moment people close the app.
5. Tell them what the permission screen will say before it appears. If they meet the accessibility warning without warning, they will either panic or accept it blindly, and neither is what you want.

Before you change anything

• Ask what they were doing when it started. Not what the problem is — what they were doing. The problem description is usually a theory; the sequence of events is data.
• Look at the whole screen before touching it. The answer is often visible immediately: a dialog waiting behind another window, a full-storage warning, an app that updated and moved its buttons.
• Ask before you close or delete anything. What looks like clutter to you may be the only copy of something to them.
• Say what you are doing as you do it. Watching a cursor move on its own in silence is unnerving, and narrating gives them a chance to learn the path.

Fix the cause, then reduce the next three calls

• Turn on automatic app updates rather than promising to check later.
• Make text and icons bigger. Settings → Display → Display size and text. A surprising share of "I cannot find the button" is "I cannot read the button", and this one setting closes more support calls than any app.
• Clear storage properly if the phone is full. A phone at 100% storage misbehaves in ways that look like a dozen separate faults.
• Remove the "cleaner" and "booster" apps. They generate a steady stream of alarming pop-ups, which generate calls — and they train exactly the reflex a scammer needs.
• Set up the things that recur: a backup, the photo sync, and how to check the storage. Then write down what you changed and send it.

Do not teach the habit a scammer needs

This is the part most advice skips. Every remote support session teaches something, and the wrong lesson is "when someone says they are helping, install what they say and press accept".

1. Establish that they initiate, always. You will never call them out of the blue asking to connect. If someone does, it is not you.
2. Use one app consistently. An unfamiliar name then becomes a signal they can act on.
3. Point out that you never ask for passwords, card numbers or codes, and that nobody legitimate will.
4. Turn the accessibility permission off when you are done, together, so they see where the switch is. This is the single most useful thing you can show them.
5. Tell them to end any session where they feel rushed — including one with you.

That takes two minutes and is worth more than the fix. The full anatomy of the fraud is in the call that asks you to install something, and it is worth reading before you set someone up with remote help for the first time.

When remote is the wrong answer

Be willing to stop. If the phone will not turn on, has no network, has a broken screen, or is stuck before Android has started, there is nothing to connect to. Hardware problems need hands, and so does anything requiring the recovery menu — which exists before any app does.

More guides