Soft Skills for Technicians
Two technicians at Ashgrove Housing fixed the same fault on the same morning for two different housing officers. It was a mapped drive that had dropped off after a password change, a two-minute fix the knowledge base had documented for years. The first technician fixed it in two minutes, said 'there you go', and left. The second technician fixed it in two minutes, said 'that happens to everyone after a password change, here's the one thing to do next time so you don't have to wait for us', and left. One housing officer raised a complaint that week about IT being dismissive. The other one started sending her colleagues to the desk with the words 'ask for Priya'. Same fix. Same two minutes.
This series is about the sentence after the fix. It covers why soft skills outrank technical skills at level one, where the fix is usually already known and the person is not. It covers listening for the problem behind the request, because the request is often wrong. It covers patience without condescension, which is harder than patience. Then comes ownership, meaning the ticket is yours until it is properly someone else's. It covers writing clearly under pressure, for a reader on a phone in a corridor. And it covers teaching and assessing soft skills, because they can be taught. A desk that only hires for them will run out of candidates.
Articles in This Series
- Why Soft Skills Outrank Technical Skills at Level One
The first line's job is the person before the machine, and the fix is usually already known. Covers the sentence that decides trust, two technicians with the same fix, and the skills weighting. - Listening for the Problem Behind the Request
The stated request against the real problem, the repeat-back, and letting the silence sit. Covers the closed question at the right moment, the user who asks for the wrong fix, and the checklist. - Patience Without Condescension: Keeping the Voice Level
The user who clicks the wrong thing six times, the voice that stays level, and the explanation that does not sigh. Covers managing your own frustration, the reset between calls, and the card. - Ownership: The Ticket Is Yours Until It Is Someone Else's
Claim it, update it, hand it over properly, never not-my-job, the follow-through after the fix, the ticket you forgot, claim-based ownership as habit, and the ownership standard. - Writing Clearly Under Pressure: The Reply Read in a Corridor
The reply read on a phone in a corridor, structure first, no jargon, one next step, the apology that is not grovelling, and the reply structure. - Teaching and Assessing Soft Skills on a Support Desk
Role play that is not embarrassing, ticket reviews that read the tone, satisfaction comments as evidence, the coaching conversation, hiring for them, and the review sheet.
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.