Home › Topics › Supporting Remote Workers

Supporting Remote Workers

The desk at Ashgrove Housing had been designed, like most desks, around a building. It had a walk-up window, a cupboard of spares, a technician who could be at your desk in four minutes. Then a third of the staff stopped coming to the building. The desk discovered that none of its best moves worked through a phone. The housing officer in a flat two hours away had a laptop that would not start. They had a broadband connection the desk could not see, and a courier who would not arrive until Thursday. The technician's four-minute walk had become a three-day wait. The ticket, for the first time anyone could remember, had a tracking number in it.

This series is about redesigning the desk for the person who is never in the building. It covers remote-first support design, meaning channels, hours and tools chosen as if nobody has a walk-up window. It covers what the desk supports at home and what it does not, in writing and said kindly. It covers shipping and swapping hardware, where the box is always ready and the spare is already imaged. Then comes remote onboarding and offboarding, for the starter and the leaver who never come in. It covers time zones, coverage and the remote worker's day, which the desk's hours no longer match. And it covers measuring remote support honestly, including the shipping lag that makes a remote ticket slower through no fault of anyone.

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.