The short answer
Before a remote support session: work out whether the problem affects one person or everyone, note exactly what changed recently and what the error says word for word, close anything private, make sure the machine will not sleep, and have somebody at that desk who can accept the connection prompt. Those five things routinely halve the length of a session.
The three answers that save the most time
Every diagnostic path starts here, and having these ready before the session begins is worth more than anything else on this page.
- One person or everyone? If it is everyone, it is the service, the network or the internet. If it is one person, it is that account, that profile or that machine. This single answer removes half the possibilities.
- What changed? An update, a new starter, a power cut, a new supplier, a move, a password change, a new printer. Faults almost never appear from nothing; something moved.
- What exactly does it say? Not "an error came up" — the actual words. A photograph on a phone is perfect. The wording frequently identifies the fault outright.
Close what you would not show a stranger
Ten seconds of work. Personal banking, private correspondence, payroll, anything confidential that is not related to the problem. Not because anyone is looking, but because it removes the question entirely and means you are not thinking about it during the session. Good practice should not depend on trusting the individual.
Practical bits that stall sessions
- Somebody must be at that desk to accept the connection prompt — sessions do not start without it
- Stop the machine sleeping mid-session; a laptop lid closing ends the connection
- Plug a laptop in if the battery is low
- Know the machine’s name, or which desk it is at, if the office has several
- Have the account password to hand if a sign-in will be needed — though a good technician should rarely need to borrow yours
- If it is a printer or a device, know the make and roughly where it sits
One thing not to do
Do not keep trying fixes you found online while waiting. Half of them change settings that then have to be found and undone, which makes the session longer rather than shorter. If you have already tried things, that is fine — just write down what, so we are not diagnosing your changes as well as the original fault.
If several people are affected
Pick one machine to work on and one person to be the contact. Sessions with four people describing four slightly different symptoms take three times as long and often chase the wrong one. Fix it on one machine, confirm the cause, then apply it across the rest.
After the session
Ask for a note of what was done, and keep it. It matters when the same thing recurs in six months, it matters more if you change provider, and a provider unwilling to write two sentences about what they changed is telling you something. We send one as a matter of course.
If the session ends with a visit being booked, ask what the part is and what it will cost before it is ordered. On remote IT support you should never receive an invoice with a number you have not already seen.
How long does a typical session take?
Most are between ten and forty minutes. Email and account problems are usually at the short end; something that has been quietly wrong for months takes longer because the cause is further back than the symptom.
Do I need to stay on the phone the whole time?
Rarely. Someone needs to start the session and be reachable, but you can get on with other work. Many sessions end with a call to say what was wrong and what changed.
What if the problem does not happen while you are connected?
Intermittent faults are the hard ones. In that case the session is usually spent putting logging or monitoring in place so the next occurrence is captured with evidence, rather than waiting for it to happen while somebody watches.