Password & Lockout Tickets

On the first working day after the long weekend, the desk at Meridian Parts logged thirty-one tickets before ten o'clock. Twenty-two of them were the same ticket wearing different names. Forgot it. Locked out. Changed it on Friday and now the phone will not stop asking. Locked out again, twenty minutes after being unlocked, for the third time, by something nobody could see. The two technicians on shift did not do anything that morning that could be called support. They did resets, in a row, like a bakery doing bread, while the ticket about the finance server waited behind them.

This series is about the ticket that is never interesting and never goes away. It covers why password tickets dominate the queue and how to count them honestly. It covers the lockout that keeps coming back, and the six places a stale password hides. It covers verifying identity before you reset anything. The reset request is the easiest door into an organisation and the desk is standing in it. The series covers the reset itself, done properly, so it does not generate the next ticket. It covers the layered plan that makes password tickets rare rather than merely faster. And it covers measuring the problem month by month so you know when you have won. None of it is clever. All of it is the difference between a desk that does support and a desk that does bread.

Articles in This Series

• Why Password Tickets Dominate the Help Desk Queue
  The anatomy of the password ticket, the several credentials per person, the password cached on a phone, the Monday and post-holiday peaks, and the census that counts them honestly.
• The Lockout That Keeps Coming Back Every Twenty Minutes
  The account that locks again twenty minutes after every unlock, the six places a stale credential hides, the diagnostic order from most likely to least, and the lockout diagnostic sheet.
• Verifying Identity Before You Reset Anything
  The reset request as the easiest door into an organisation. Covers a verification standard that is quick for the real user and hard for a stranger, what never counts as proof, and the standard itself.
• The Password Reset Itself, Done Properly Every Time
  A temporary password that forces a change, never over an open channel, never in the ticket. Covers telling the user where else it will break, the follow-up that confirms it, and the reset reply.
• The Layered Plan That Makes Password Tickets Rare
  Expiry policy, single sign-on, self-service reset, lockout tuning, the onboarding briefing and the phone reminder, each removing a slice. Covers what each layer removed at a fictional desk, and the layer plan.
• Measuring the Password Problem Month by Month
  The count, the share, the cut by cause, the Monday peak, the spike after a policy change, the month you can declare victory, and the monthly report line.

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.