Home › Topics › Remote Support Tooling

Remote Support Tooling

The technician connected to the finance director's laptop to fix a printer, which took two minutes. The session was still open, and the technician was curious about a slow-drive complaint from the week before. So they had a look around for another ten. The director, who had gone to make coffee, came back to find a cursor moving on their screen through a folder called "Board". Nothing was taken and nothing was meant. The desk spent the next month explaining to the whole organisation why remote control was safe. It is, when it is done with consent, in view, and for exactly as long as the job takes.

This series is about doing it that way every time. It covers remote control done securely, with the five principles in plain words. It covers consent, every time, including what to say and what the user sees. It covers logging and session records, in the ticket, where a question a month later can be answered. Then comes unattended access policy for servers and the out-of-hours job. It covers remote support for people working from home, with the phone-and-photo fallback for the day it fails. And it covers choosing and reviewing the tool by criteria rather than by name. A remote session is a technician standing at someone's desk, except that they cannot see you. Behave as if they could.

Articles in This Series

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.