Define one small task clearly
Fictional example: Claudia wants to change a printer setting. Her brother offers to help remotely. They agree on a time and that particular task. He explains, and Claudia performs the steps herself where possible. Beforehand she closes email and health-related windows. Their agreement is “help me select this printer”, rather than “fix my whole computer”. The scope and finish remain understandable, while any extra work can be discussed separately. This also gives Claudia a useful process she can repeat instead of leaving her unsure what has changed.
Check identity and software independently
Call the arranged helper using an already known number if an unexpected new message arrives. A name, profile photograph or familiar-sounding voice should not alone justify surprise access. Use a supported tool obtained from its official source and read its permission notices. Microsoft’s Quick Assist documentation distinguishes viewing a screen from control that the user allows. Other software can behave differently. Do not install a remote-support file sent to you merely because someone claims an urgent security fault requires immediate intervention. Pause and verify before connecting.
Reduce visible information before sharing
Close documents, conversations and browser windows unrelated to the job. Consider notifications and extra monitors. Where supported, share only the necessary window instead of the entire display. Inspect the preview or explicitly ask what the helper can see. Do not display a password collection. If a confidential entry becomes necessary, end sharing for that step and resume afterwards. Password dots do not hide every other account detail around them. The goal is to expose only what the agreed task needs, even when the person helping is trustworthy.
Grant control deliberately and narrowly
Seeing the display and operating the mouse or keyboard are separate permissions. Allow only what the task requires and remain present. Before deletion, a purchase or an important account change, ask about effects and alternatives. Being related does not replace consent for those actions. If the process moves faster than you understand, interrupt it; this is a normal part of good assistance. For a managed workplace device, involve the responsible IT team instead of installing private remote access around organisational rules. Stop if the tool’s actual scope is unclear.
Make the ending explicit
End sharing within the tool and verify that the connection is closed. Review changed settings and any unresolved task together. Do not set up unattended permanent access simply because one session was convenient. A short note explaining the solution may be sufficient next time. If you already allowed an unknown person access, treat that as a separate security incident and seek official assistance. These steps describe voluntary support; they do not guarantee that every tool or remote-support situation is safe under every circumstance.
Your checklist
The checkboxes are for your own reference. No entries are sent to us. To keep a copy, print the page or save it as a PDF using your browser menu.
Common questions
Must I allow complete control?
Not automatically. Explanations or screen viewing may be enough. Decide according to the task and tool rather than approving every extra permission without review.
Can I leave the room?
Remain present so you can follow changes and end the session. Unattended ongoing access is a different arrangement with more extensive consequences than a single assisted task.
What if the helper suddenly wants my banking page?
That does not fit an ordinary printer or device adjustment. Stop and clarify independently. Do not transfer money or reveal codes to supposedly complete technical assistance.
Sources and further information
Primary sources from public authorities, consumer organisations and providers. A source may be in another language; follow the guidance that applies to your service and where you live.
- Microsoft: Remote help with Quick AssistSource review date:
- FTC: Technical-support scamsSource review date:
