An attended support session should have an agreed purpose and a person authorised to act for the device or account. An unsolicited caller claiming a computer is infected is not a support agreement. Use a previously trusted contact route to verify who is helping and what will happen before opening a remote tool.
Describe the problem without exposing secrets
Record the task that failed, exact time, safe error wording, recent changes and what still works. Explain whether the problem affects one device or several people. Avoid sending passwords, payment details, recovery codes or full customer documents. If a screenshot is useful, remove unrelated personal information and agree the channel first.
Identify any business impact or deadline, but do not assume a supplier offers emergency response because an email address exists. Agree diagnostic scope, charges/cap where applicable, supported device/software and the point at which further work needs approval. Permission to investigate one fault is not permission to reinstall every application or delete records.
Protect the starting state
Check that important information has an appropriate recoverable backup before a change which could affect it. Know whether a work device is managed by an employer or another supplier, and obtain the necessary authority. Do not bypass their security software, policies or credentials to make a connection easier.
Close unrelated private documents and understand which display or application the helper can see. Use the provider’s verified supported tool and read its permissions. Keep control of the attended session and know how to disconnect. Do not share one-time sign-in or recovery codes with a support operator. Enter them yourself in the provider’s verified sign-in or recovery screen. A code created by the remote-support tool to join the agreed session serves a different purpose.
Review the proposed change
Ask what the diagnosis supports and what remains unknown. A routine restart, a software reinstall and a destructive reset have different consequences. The helper should explain material risks, recovery and scope before proceeding. If unsupported hardware, malware or a third-party service prevents a safe fix, an honest finding and next step is better than an invented success.
Afterward, test the original task together, record changes and limitations, and confirm any ongoing support arrangement. Disconnect and remove temporary access according to the agreed process. Check whether a remote agent, account role or token remains; closing a window alone may not end all access.
Keep the safe session/reference record and any follow-up actions. Do not treat payment, a connection log or the operator’s test result as automatic customer acceptance of every outstanding issue. Useful support ends with clear ownership and a controlled exit, not an unexplained permanent foothold.
Sources and review
Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.
Next review: 4 May 2027