Before Remote IT Support: A Practical Checklist

A useful first message helps a technician understand the problem and agree the next step. This checklist works for Windows, Mac and Linux computers, website problems, documents and spreadsheets. You do not need to diagnose the fault before asking for help.

Gather the useful details

• What are you using? Note the device, operating system and affected application or website.
• What were you trying to do? Describe the expected result and what happened instead.
• What does the error say? Copy the wording or take a screenshot. Hide passwords, account numbers, private messages and other people's information.
• When did it last work? Mention a recent update or change if you know one; it is fine to say you do not know.
• How widespread is it? Is one file, one device or everyone affected?
• What have you tried? A short list avoids repeating work.
• What matters most? Say whether there is a deadline, important data or a limit on the time or budget available.

Before anyone changes the device

Save your work. Tell the technician whether important files are backed up and whether you have checked that a backup can be opened. Agree what may be changed, what requires a separate decision and how the remote session will end.

A message you can use

I need help with [device/application]. I expected [result], but [problem] happened. It last worked [when/unknown]. The error says [text]. I have tried [steps]. My main priority is [priority]. Please confirm the scope before work begins.

Ask Linux Stewards

Linux Stewards helps with Windows, Mac and Linux, websites, documents, spreadsheets and practical AI automation. Small jobs are welcome. We confirm the scope and price before work starts, including whether remote support is suitable.

Start with a short text description in the contact form. If a screenshot would help, follow the email instructions on the contact page.