Before remote IT support:
prepare the useful details.

1. Describe the problem in ordinary language

Start with the task: “I need to open a shared document,” “The printer stopped responding,” or “I cannot sign in to my work account.” Then explain what happens instead, when it started, and whether it happens every time.

Record the application or device involved and the exact error wording when possible. A cropped screenshot can be useful, but first remove names, email addresses, account numbers, customer records, and any visible secrets.

2. Confirm the person and the appointment

Before allowing remote access, confirm who will help, which device is involved, and what access has been authorized. Use a contact route you already know is genuine—not a number or link from an unexpected warning.

The FTC warns that tech-support impersonators use calls and alarming pop-ups to obtain payment or remote access. An unexpected message is not a reason to hand over control of your computer. Read the FTC’s tech-support scam guidance.

3. Prepare the working environment

Keep the device connected to power and have a way to communicate if the connection drops. Close unrelated documents and private applications. Confirm that any work in progress is saved before a session that might require closing an application or restarting the device.

For changes that could affect important data or services, confirm the backup and recovery responsibilities in advance. Do not assume a backup exists because a folder is synchronized to a cloud service.

4. Stay in control of access

The support plan should explain what will be reviewed, which actions require approval, and whether a restart or temporary interruption may be necessary. Enter your own credentials when needed; do not put passwords or recovery codes into the inquiry message.

Do not disable protection, install an unfamiliar remote-access tool, or grant unattended access simply because a caller insists. An organization’s authorization and security process should determine the method used.

5. Finish with a clear handoff

Ask what was changed or checked, what now works, and what remains unresolved. Test the original task together when practical. Confirm that the remote session is closed and whether any temporary access or tool needs to be removed.

A useful summary records the issue, actions, outcome, and next owner. It should distinguish a completed fix from a workaround or a diagnosis that still needs confirmation.

A suspected incident needs a different response. This checklist is for an ordinary, authorized support session. Where compromise, data exposure, or a serious incident is suspected, follow your organization’s incident process rather than experimenting with settings.