Password Reset Self-Service
Monday, 08:40. Eleven of the first fourteen tickets are the same ticket: "locked out", "password expired over the weekend", "can't log in". Each takes a technician four minutes, two of which are spent working out who is actually on the phone. By 09:30 the desk has done forty minutes of resets and has not touched a single problem that needed a technician to solve it. This happens every Monday, and on the day after every public holiday, and on the first working day of every month. The desk has long since stopped noticing, the way you stop noticing a fan. The password reset is the most common ticket on almost every desk. It is the one ticket that the user could, with the right project, do entirely by themselves.
This series is that project. It covers why password resets dominate the queue, with the arithmetic that makes the case. It covers the self-service reset project step by step, from requirements to the day the desk stops doing them. It covers the security trade-offs, because a reset is a door and self-service puts a second handle on it. Then comes why enrolment is the whole project, since a reset system nobody enrolled in is a ticket with extra steps. It covers the manual reset done safely for the people who still need one. And it covers measuring the drop and keeping it down. Self-service password reset is a directory and identity feature, not a help desk one. The help desk's job is to run the project, and then to enjoy its Mondays.
Articles in This Series
- Why Password Resets Dominate the Queue: One Desk's Arithmetic
One desk's reset volume worked through, expiry policies, lockouts, Mondays and the day after a holiday, the cost per reset in minutes, and the reset-volume worksheet. - The Self-Service Reset Project, Step by Step
Requirements, choosing an approach, enrolment, pilot, rollout, the desk's role afterwards, and the project plan. - Security Trade-offs: Convenience Against Identity
Verification factors in plain words, account recovery as an attack path, why security questions are weak, a second factor, what to log, and the trade-off table. - Enrolment Is the Whole Project: Getting Everyone Signed Up
The campaign, the new-starter step, the stragglers, the manager nudge, the enrolment number to watch, and the campaign plan. - The Manual Reset, Done Safely, for the Rest
Verifying identity at the desk, the script, handing over a temporary password safely, logging it in the ticket, never over chat or e-mail without verification, and the verification script. - Measuring the Drop and Keeping It Down: The Before/After Sheet
Before and after by month, lockouts versus resets, the residual tickets and what they say, the expiry-policy conversation, and the before/after 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.