Remote IT Support Checklist for Freelancers and Solo Consultants

A freelance IT helper has a rare job: strangers let you look at their private files, their email and their business, and expect you to fix a problem without making a new one. Trust is your product. The tools you use and the habits you build around them decide whether clients call you again. This checklist covers the whole life of a remote support session.

Before the session

1. Agree on the problem and the time. A short message such as "the printer stopped working after Tuesday's update, can we look at it at 3 pm?" saves time later.
2. Agree on the price and what is covered. Say whether you charge by the hour, by the session or by the fix.
3. Tell the client what to prepare. Ask them to close private documents they do not want you to see, and to have any passwords you will need ready, but not to send them in writing.
4. Check that they can run the tool. For control of a Windows computer, they need the PeerFlow Windows app installed. Do this once, ahead of time, to avoid wasting billable minutes.

Starting the session

1. The client opens PeerFlow and chooses Share this device, and reads you the code by phone.
2. You open PeerFlow remote desktop and enter it.
3. The client allows control. Confirm out loud: "I can see your screen. May I take control?"
4. Say what you plan to do, in one sentence.

During the session

• Narrate. "I am opening the printer settings." Clients relax when they know what is happening.
• Stay on topic. Do not browse folders unrelated to the problem. A visible badge on their screen shows that someone is connected, and they can see your pointer.
• Use the tools. Copy short text between the two computers when needed, and send files in either direction. Draw on their screen to point at something rather than describing it.
• Take screenshots at key moments, such as the error message before and the working state after. They go into the PeerFlow folder.
• Never ask for passwords by chat if a phone call will do. Let the client type their own passwords on their own keyboard whenever possible.

Closing the session

1. Ask the client to test. Do not leave until they confirm that the problem is gone.
2. End the connection and tell the client that the code is now useless.
3. Remove anything you installed for the session unless the client wants it.
4. Send a summary by email: what was wrong, what you did, what to watch for.

Documentation that pays

Recording sessions

Recordings can be useful for training and for settling disputes, but they capture a client's private screen. Always say that you are recording, why, and how long you will keep the video. Store recordings in the PeerFlow folder, protect them like any other client data, and delete them when they are no longer needed.

Protecting yourself

Write down what your service covers and what it does not. Do not touch data you were not asked to touch. Keep your own computer updated, since a client's problem should never pass through your machine into the next client's. For more on safe habits, see is remote desktop safe?.

Growing from one client to many

When the list grows, a repeatable routine saves you. A template message, a saved note and a standard summary make your work look professional. If you later work with others, read about remote support workflows for small IT teams. Get the Windows and Android apps for yourself and walk each new client through the one-time set-up.