Measuring Self-Service ROI
The knowledge base took a technician three weeks to build, spread over a quarter. A manager, reasonably, asked what it had been worth. The desk said "a lot", and then "it's hard to measure". Then, under pressure, it produced a number with a percent sign that nobody believed, including the desk. The truth was available in the ticket system the whole time. The password article alone had been opened four hundred times. The reset tickets had fallen by two-thirds. The mapped-drive runbook had turned a forty-minute fix into a six-minute one for every technician on the desk. Nobody had added it up, because adding up felt like marketing.
This series is the adding up, done honestly. It covers what ROI means for a help desk, in hours rather than in anything with a currency sign. It covers deflection math without fooling yourself, in ranges, with the effort subtracted. It covers reading knowledge base usage so you know which articles earn their keep. Then comes the time saved by technicians, which is usually larger than the deflection and almost never counted. It covers proving it to management in one page. And it covers when self-service does not pay, because some tickets should be tickets and some articles should never be written. Every number in this series is a worked example from a fictional desk. Yours are in your ticket system, waiting.
Articles in This Series
- What ROI Means for a Help Desk: Hours as the Honest Currency
Cost per ticket in plain words, hours as the honest currency, what to count and what not to, and the cost-per-ticket worksheet. - Deflection Math Without Fooling Yourself or Your Manager
Tickets avoided times cost per ticket minus the effort to write and maintain, the counting rules, ranges rather than points, a worked example, and the calculation sheet. - Reading Knowledge Base Usage: Which Articles Earn Their Keep
Views, searches, failed searches, helpful votes, articles opened from tickets; which articles earn their keep and which to retire; and the usage report layout. - The Time Saved by Technicians: The Return Nobody Counts
Faster resolution with an article open, consistency, onboarding a new technician in days instead of weeks, measuring it honestly, and the technician time worksheet. - Proving Self-Service ROI to Management in One Page
Before and after, the hours, the ask, the brief a manager reads in two minutes, and the ROI one-pager. - When Self-Service Does Not Pay, and Where to Stop
Small desks, rare tickets, the article nobody reads, the request that must be a ticket anyway, knowing where to stop, and the stop-doing list.
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.