Remote tech support for parents without breaking their privacy

Your parent calls. The printer won't connect. A website looks wrong. An error message appeared and won't go away. You're three states away.

The instinct is to fix it remotely. Install software that lets you take control of their computer, see their screen, move their mouse. Problem solved in five minutes instead of an hour of phone instructions that end with "never mind, I'll figure it out."

But that remote access software creates a permanent backdoor into their machine. It runs in the background. It stores credentials. It becomes the tool scammers use when they call pretending to be from Microsoft or Apple, and your parent, accustomed to letting people into their computer to help, clicks yes.

The tradeoff isn't theoretical. Tech support scams cost older Americans hundreds of millions annually, and remote access tools are the mechanism that makes the fraud work. You're trying to help. The scammer is trying to steal. The software can't tell the difference.

Here's how to provide real help without creating the vulnerability that makes your parent a target.

The problem with permanent remote access

Remote desktop software, TeamViewer, AnyDesk, LogMeIn, Chrome Remote Desktop, works by creating a persistent connection between two computers. Install it once, and you can access that machine anytime, from anywhere, as long as both devices are online.

That's the feature. It's also the risk.

The software runs continuously in the background. It listens for incoming connections. It authenticates using a password or PIN that, if your parent writes it down or reuses it elsewhere, becomes a single point of failure. If that credential leaks in a breach, or if your parent accidentally gives it to a scammer, the attacker has the same access you do.

CISA's guidance on multifactor authentication emphasizes that any persistent access point should require strong authentication. Most remote desktop tools offer two-factor authentication as an option, not a default. Your parent probably didn't enable it. You might not have either.

The bigger problem is habituation. Once your parent gets used to the idea that "someone can see my screen and fix things," they stop questioning who that someone is. The scammer calls, says there's a virus, asks them to open the remote access software and read the ID number. Your parent does it because that's what happens when they need help. The scammer is inside in under a minute.

This isn't a hypothetical edge case. It's the primary mechanism behind tech support scams targeting older adults. The FBI warns specifically about remote desktop software in fraud alerts. The FTC has recovered hundreds of millions from companies whose tools enabled these scams.

Permanent remote access is a tool designed for IT professionals managing fleets of machines. Using it to help your parent fix their printer is like giving them a loaded gun to hang pictures.

Screen sharing through video calls: the safer alternative

You don't need persistent access to help someone. You need to see what they see, in the moment, while you're both actively engaged in solving the problem.

That's what screen sharing does, and every major video calling platform includes it: FaceTime, Google Meet, Zoom, Microsoft Teams, Skype. Your parent is probably already using at least one of these to talk to you.

Screen sharing requires active participation from both people. Your parent starts a video call with you, then clicks a button to share their screen. You see what they see. You walk them through the fix. When the call ends, the sharing stops. There's no background process, no stored credentials, no way for someone to access their computer when you're not on the line together.

The security model is fundamentally different. Remote desktop software says "this person can access this computer anytime." Screen sharing says "this person can see this screen right now, during this call, with my active consent."

If a scammer calls and asks your parent to share their screen, your parent has to initiate a video call with the scammer first. That's a much higher bar than "open the program and read me the number." It creates friction. Friction stops fraud.

Here's how to set it up.

Setting up screen sharing on your parent's device

The goal is to make screen sharing easy enough that your parent will actually use it when they need help, but not so automatic that they forget it requires their active consent.

If your parent uses an iPhone or iPad and you use an Apple device:

FaceTime includes screen sharing. Your parent calls you, you answer, they tap the screen sharing icon. That's it. No installation, no setup, no credentials to manage.

Walk them through it once while you're on the phone:

1. Start a FaceTime call with you
2. Look for the screen sharing button (it looks like two overlapping rectangles)
3. Tap it, then tap "Share My Screen"
4. You'll see their screen on your device

Practice this when nothing's broken. Let them initiate the call, find the button, share their screen while you're both looking at something neutral like their home screen. Make it routine before it's urgent.

If your parent uses an Android device or a Windows computer:

Google Meet works across platforms and doesn't require software installation. Your parent opens meet.google.com in their browser, starts a meeting, sends you the link, and shares their screen once you join.

The first-time setup takes longer because they need to understand the flow: open browser, go to Meet, start meeting, copy link, send link to you (via text or email), wait for you to join, then click "Present now" and choose "Your entire screen."

That's a lot of steps for someone who's already frustrated. Simplify it:

Create a bookmark in their browser for meet.google.com. Label it "Video call for help." Write down the steps on an index card and tape it near their computer:

1. Click "Video call for help" bookmark
2. Click "New meeting"
3. Click "Copy joining info"
4. Text me the link
5. When I join, click "Present now"
6. Choose "Your entire screen"

The card isn't condescending if you frame it as a reference, not a crutch. You have checklists for things you do rarely. So do they.

If your parent uses Zoom regularly:

Zoom's screen sharing is straightforward once you're in a meeting. The setup is the same as Google Meet: they start a meeting, send you the link, wait for you to join, then click "Share Screen."

Zoom has one advantage: you can schedule recurring meetings. Set up a weekly or monthly meeting link that's always the same. Your parent saves it. When they need help, they click the saved link, and you join. No new link every time.

The tradeoff is that Zoom requires an installed application, not just a browser. If your parent already has Zoom for other reasons (book club, family calls), use it. If not, browser-based Google Meet is simpler.

Walking through fixes without taking over

Seeing their screen is half the solution. The other half is guiding them through the fix without making them feel like you're doing it for them.

This matters more than you think. The goal isn't just to solve today's printer problem. The goal is to build their confidence so they can solve tomorrow's problem, or at least attempt it before calling you.

Describe what you see, then ask them to do it:

Wrong: "Okay, I need you to click the thing in the top right corner."

Right: "I see a gear icon in the top right corner of the window. That's the settings menu. Can you click on that for me?"

Naming what you see gives them a reference point. Asking them to do it, rather than telling them, preserves agency.

Pause after each step:

You can see the next five steps. They can't. If you rattle off instructions faster than they can execute them, they'll feel rushed and incompetent.

One step. Wait for them to complete it. Confirm it worked. Next step.

Explain why, not just what:

"Click 'Forget this network' so the computer stops trying to connect to the old WiFi and will search for the new one."

The extra sentence takes three seconds. It transforms the fix from magic you're performing into a process they understand. Next time the WiFi acts up, they might remember "forget the network" as a thing to try.

Celebrate small wins:

"Perfect, you got it. That's exactly what we needed."

You're not patronizing a child. You're acknowledging that they just successfully navigated an interface that was designed by people who don't think about accessibility or clarity. That's worth recognizing.

Creating written guides for repeat problems

Your parent will encounter the same problems multiple times. Printers lose connections. Passwords get forgotten. Updates break settings. You can solve it fresh every time, or you can document the solution so they can try it themselves first.

Written guides work if you make them specific to their exact setup.

Take screenshots during the fix:

While you're walking them through the solution, take screenshots of each step. Most screen sharing tools let you do this. If not, use your phone to photograph your screen.

Write the steps in their language:

Not "Navigate to System Preferences > Network > Advanced > TCP/IP."

Instead: "Click the Apple icon in the top left corner. Click 'System Preferences' (it looks like a gear). Click 'Network' (it has a globe icon). Click 'Advanced' in the bottom right. Click the 'TCP/IP' tab at the top."

Use the words they use. If they call it "the internet settings thing," write "the internet settings thing" in parentheses next to the technical name.

Store the guides where they'll find them:

A Google Doc they can't locate helps no one. Create a folder on their desktop called "Tech Help Guides." Put PDFs or printed pages in there, labeled clearly: "Printer won't connect," "Forgot password," "Computer running slow."

Better yet, print them and put them in a three-ring binder next to the computer. Physical beats digital for someone who's already frustrated with digital.

Update the guides when things change:

Software updates change interfaces. Your carefully documented steps stop working. When that happens, update the guide during the next fix. Don't let outdated instructions erode their trust in the system.

The cultural reference that fits

In Sherlock Holmes, Watson isn't just a sidekick. He's the person who sees what Holmes sees and writes it down so others can follow the reasoning later. Holmes solves the case. Watson makes the solution teachable.

You're Watson. Your parent is the reader who gets the case file after the fact. The goal isn't to be the only person who can solve the mystery. The goal is to document the process so the next time a similar problem appears, they have a reference.

The best Watson doesn't just record what happened. He explains why it happened, in language the reader understands, so they can apply the method to new situations. That's what your written guides do. That's what your patient explanations during screen sharing do.

Holmes wouldn't be Holmes without Watson. Your parent's tech independence won't exist without your documentation.

Setting boundaries around availability

Helping your parent remotely is generous. Becoming their 24/7 help desk is unsustainable.

You need boundaries, and boundaries require explicit conversation.

Set specific help hours:

"I'm available for tech help on Tuesday and Thursday evenings after 7, and Sunday afternoons. If something breaks outside those times, write down what happened and we'll fix it during our next session."

This isn't cruel. It's sustainable. Urgent tech problems are rare. Most things can wait 48 hours.

Triage over text first:

Before you jump on a video call, ask them to text you a description of the problem. Sometimes the fix is simple enough to explain in a message. Sometimes the problem resolves itself before the scheduled call.

Texting also creates a record. If the same problem keeps recurring, you have documentation of the pattern.

Teach them the "restart first" rule:

A shocking number of problems vanish after a restart. Make that step one of every troubleshooting attempt.

"Before you call me, try restarting the computer. If that doesn't fix it, write down exactly what you were doing when the problem started, and we'll look at it during our next help session."

Know when to escalate to paid support:

You're not a professional. Some problems require professional diagnosis: hardware failures, virus infections, complex network issues.

It's okay to say "This is beyond what I can fix remotely. Let's find a local repair shop." Trying to solve everything yourself leads to frustration on both sides.

Consumer Reports' Security Planner includes guidance on finding trustworthy local tech support. Verify credentials, check reviews, and avoid anyone who cold-calls offering help.

Protecting your parent from scammers who impersonate you

Once your parent gets used to screen sharing with you, scammers will try to exploit that trust.

The attack works like this: Scammer calls, claims to be from Microsoft/Apple/their bank, says there's a problem, asks them to share their screen so "we can fix it together." Your parent, accustomed to screen sharing as the way to get help, complies.

You need a verification protocol.

Establish a call-back rule:

"If anyone calls and asks you to share your screen or download software, hang up and call me first. Even if they say it's urgent. Even if they say they're from Apple. Hang up, call me, and we'll figure out if it's real."

Write your phone number on a sticky note and put it on their monitor. Make calling you the automatic response to any unsolicited tech support offer.

Practice recognizing scam patterns together:

Show them examples of tech support scam calls. YouTube has recordings. The FTC's tech support scam guidance includes transcripts.

Go through the tactics together: the fake urgency, the claim that their computer is infected, the request for remote access, the demand for payment in gift cards.

Make it a conversation, not a lecture. "Here's what these scams sound like. If you ever get a call like this, here's what to do."

Set up two-factor authentication on their accounts:

If a scammer does get into their computer, two-factor authentication on email, banking, and other critical accounts creates a second barrier. They can't reset passwords or transfer money without the second factor.

Use an authenticator app, not SMS. SMS can be intercepted through SIM swapping. Google Authenticator, Microsoft Authenticator, or Authy work across platforms.

Walk them through the setup during one of your help sessions. Test it together so they understand the flow.

When remote help isn't enough

Sometimes the problem can't be solved remotely. The computer won't turn on. The internet is completely down. The screen is physically cracked.

Have a backup plan.

Identify a local contact:

Is there a neighbor, friend, or family member who lives nearby and has basic tech skills? Not someone who can solve complex problems, but someone who can physically check if cables are plugged in, restart the router, or drive your parent to a repair shop.

Introduce them to each other. Exchange phone numbers. Make it clear this person is the "in-person backup" for problems that can't be solved over video.

Keep a list of trustworthy local services:

Research computer repair shops in your parent's area before you need them. Check reviews, verify they don't have complaints with the Better Business Bureau, confirm they offer in-home service if your parent can't transport the computer.

Store the list in the same place as your written guides. When something breaks that you can't fix remotely, you're not Googling "computer repair near [parent's city]" in a panic.

Consider annual in-person maintenance:

If you visit your parent once or twice a year, use part of that time for hands-on tech maintenance. Update software, clean out old files, check that backups are working, verify security settings.

In-person access lets you do things that are painful over video: physically cleaning dust from vents, checking cable connections, replacing aging hardware before it fails catastrophically.

The setup that respects both of you

Remote tech support for parents works when it's built on mutual respect. You respect their autonomy by teaching instead of taking over. They respect your boundaries by following the protocols you've established.

Screen sharing through video calls gives you the visibility you need without creating the persistent access that scammers exploit. Written guides give them independence. Scheduled help hours give you sustainability. Verification rules protect them from fraud.

The alternative, installing remote desktop software and becoming their always-available IT department, helps in the short term and creates dependence in the long term. Worse, it trains them to accept remote access as normal, which is exactly what scammers need to succeed.

You're helping them stay independent in a world that's increasingly hostile to people who didn't grow up with this technology. That's worth doing right.

The next time they call with a problem, you'll know exactly what to do: start the video call, share the screen, solve it together, document the solution, and end the call knowing you didn't leave a backdoor open behind you.