The caller can see more than the problem
Notifications, documents, saved passwords, account names and personal messages may become visible during the session.
Technology, platforms and channels
Should I give a caller remote access to my device?
Remote access can allow another person to view the screen, control the pointer, open files, change settings and observe information. The risk depends on who initiated support, how identity was confirmed and what permissions are granted.
Page P-017Guidance pageReviewed 29 August 2026
Key Guidance
Do not give remote access to an unsolicited caller. If you genuinely need support, start through the provider’s official route, confirm the technician inside that process and keep the access limited, visible and removable.
Start with Key Guidance for the short answer. Then read the sections that match what happened and what you need to do.
Understand the issue
Why this matters to you
The software may be genuine and widely used. The danger comes from giving powerful permissions to a person whose identity and purpose have not been independently confirmed.
Control can extend beyond viewing
Depending on permissions, the other person may type, open applications, download files, change settings or install extra software.
Banking may be obscured
A scammer can distract you, blank the screen or ask you to hide information while transactions or account changes happen.
Access may be configured to persist
Unattended-access settings, saved sign-in details or secondary software can allow later reconnection.
Consequences and movement
What may happen next
A safe support process should confirm identity before access, explain the exact purpose and let you end and remove the connection.
Connection-code request
The caller asks for a number shown by the remote-access tool, which can authorise the session.
Escalating permissions
Viewing changes to control, file transfer, administrator access or unattended access.
A financial detour
The caller asks you to open banking, process a refund, buy something or check whether money arrived.
A secrecy instruction
You are told not to speak to the bank, family, employer or another support provider while the session continues.
Practical response
What you should do
Treat remote access as a high-authority permission, not a routine phone instruction. The safest decision is made before the connection begins.
- Decline unsolicited accessEnd the call or chat. Do not download the tool or provide a connection code.
- Start support independentlyUse the genuine app, website, contract or device settings to open a new support case.
- Confirm the scopeAsk what the technician needs to see or control, how long access lasts and how it will be removed.
- Close sensitive servicesDo not open banking, email, password managers, identity documents or private work systems during the session.
- Keep control of the sessionWatch the screen, reject unexpected permissions and end access at once if the task changes.
- Follow recovery if access beganDisconnect the device and use the dedicated recovery steps if the person connected, files moved or sensitive services were opened.
Look more closely
Remote access gives practical control, not merely technical help
Once connected, another person may view activity, alter what appears on screen and direct actions inside accounts. Grant access only through a support process you initiated and independently verified.
A technical, banking or investment problem creates a reason for assistance.
Urgency and relief make access feel like the fastest safe option.
Professional language, genuine software and a familiar organisation name imply authority.
The connection provides direct visibility and control over the device.
Independent initiation, bounded permissions and immediate disconnection restore user control.
Selected history
Historical cases and lasting lessons
Remote-access support scams
Unsolicited callers have used genuine remote-access software within false technical, banking and investment stories.
Lasting lesson: Assess the person, initiation route and permissions separately from the software brand.
Account and malware escalation
A remote session can expose sign-in details or install extra software, creating effects after the visible call ends.
Lasting lesson: Ending the conversation may not be sufficient once access has been granted.
Transferable understanding
Patterns over time
The tool inherits the caller’s story
Familiar software feels safe when presented as part of a repair, refund or investment process.
Permission grows gradually
A view-only request can expand into control, files, administrator rights or financial access.
Visible activity can hide invisible change
The person may focus attention on one window while altering settings or accounts elsewhere.
A genuine need does not verify a caller
Even when the device has a real problem, the present contact and proposed route still require independent confirmation.
Plain-language answers
Common questions
Is remote-support software itself dangerous?
Not necessarily. These tools have genuine uses. The risk is unauthorised access, excessive permission and misuse by the person controlling the session.
What if I called the support number first?
Confirm that the number came from the genuine provider. Search results and adverts can direct people to impersonators.
Can I safely show only one window?
Screen-sharing modes differ, and notifications or permission changes can expose more than expected. Verify the person and use the narrowest possible access.
What if the caller becomes angry when I refuse?
End the contact. Pressure, threats or resistance to independent verification are reasons not to continue.
Start legitimate support through a route you control
If the connection never began, block and report suspicious contact. If access was granted, act as though information or settings may have been exposed and follow the remote-access recovery page.
Scamology Insights
Treat access as the Path, not merely a technical step
These learning resources can help identify how a request for help becomes direct control over evidence, accounts and action. Links are intentionally withheld in this production version.
Continue understanding
Explore related guidance
Evidence and currency