Password Reset Help Desk Guide: Why Password Resets Fail and How to Fix Them

Password resets are one of the most common help desk requests—and one of the most frustrating to resolve. If you work on a help desk, you’ve probably dealt with a password reset that “should have worked” but didn’t. In this guide, you’ll learn why password resets fail on the help desk, the most common password reset issues, and a repeatable process to fix them without losing control of the call.

Common Password Reset Problems on the Help Desk

Let’s be honest. Password resets shouldn’t be that hard. Somebody calls and says they don’t know their password, you push a couple buttons and tell them to create a new one. Bam. Easy as that, right? Wrong. The process is rarely that simple because you’re not interacting with computers - you’re dealing with people. Most password reset issues fall into a predictable pattern. The problem usually isn’t the reset itself—it’s a misunderstanding about what is being reset, where, or when the change actually takes effect.

• Problem #1: You reset the wrong password. I’ve had it happen where a user calls me and tells me they can’t log in to their computer. I, assuming they meant logging in to their network user account, promptly reset their network password… only to realize they were talking about a specific program.

• Problem #2: They “know” their password. These situations are sometimes the most awkward. The user vehemently claims that they know they’re typing in the correct password. Yet, the computer still says it’s incorrect. They don’t want to reset their password. They want their “correct” password to work. This is the same freeze many techs experience when they don’t know the answer right away. At that point, arguing about who’s right doesn’t move the call forward.

• Problem #3: The new password “doesn’t work.” There are many reasons this may happen. The most common scenario is that the user successfully resets their password, and then types the password incorrectly when logging in. Slightly less common are cached credentials. After the user creates a new password, the old password is still saved in their browser’s password manager. Thus, the program still registers incorrect credentials. Less common is a slow sync between programs causing a delay in the new password taking effect. For example, if you reset a user’s network password, this password might need to be synced to Microsoft for their email. If there’s a delay in the syncing of the network and email password, the latter will still register an incorrect password.

The techs who struggle with password resets aren’t lacking technical knowledge. They’re missing a repeatable process. Once you treat password resets like a structured call instead of a quick task, most of the stress disappears.

How to Handle Difficult Password Reset Calls

We know that dealing with people can make a simple process into a much more complex one. This is one of the reasons the help desk feels harder than it looks from the outside. So how should we deal with these situations? Here are a couple guidelines for you to apply to your password reset calls:

1. Never assume what password they mean. Even for a seemingly simple-forward situation like a password reset, don’t take users at their word. Double-check everything they say with follow-up questions. If they say they can’t get into their computer, ask whether the computer is saying they’re entering incorrect credentials or something else. Ask them whether they’re logged out of the computer as a whole or just a specific program. Remember, it’s common for users to misuse techy terms that mislead you. Always ask confirmation questions.
2. Make the reset the obvious path forward. Learn how to get good at making your solution seem like the best one. Your goal is to make the user see how your solution (resetting the password) is the easiest way forward. Even if they “know” their password, learn how to convince them that getting their current password to work is going to take longer than just creating a new one. Typically, this make people more than happy to go along with your suggestion. This might mean briefly explaining the reset process to make them more comfortable or stating that the process typically only takes a couple minutes. Perhaps this means you need to explain a couple reasons their password might be having issues (expiration, database corruption, etc.) to make them more comfortable with knowing they weren’t the one that caused the problem.
3. Stay calm and procedural. Remember that all the user wants is to get on with their day. Snarky comments aren’t helpful. Be direct if a user is typing their password incorrectly, but then offer advice to fix the problem. “Check your caps lock. Try restarting your computer.” If their password needs to be reset, offer to walk them through the process and remind them of your organization’s password requirements.
4. Don’t hang up early. Hanging up before the user logs in will come back to haunt you. I guarantee it. Stay on the phone with the user until the user is completely logged in to the computer or program they’re struggling with. Moments like this are where many techs start questioning whether the help desk is even worth the effort. There are all sorts of things that might go wrong otherwise. They can’t remember the password requirements. They get it reset and then promptly forget the password they just created. They don’t realize they have to type the same password into the “Confirm password” box. The reasons vary, but it’s always to stay on the line instead of hanging up and getting another phone call a couple minutes later for the same problem.

If password reset calls regularly throw you off, the problem isn’t technical skill—it’s not having a clear call structure. The same call-handling process works whether you’re resetting a password or troubleshooting something you’ve never seen before.

Get the free guide: 5 Steps to Handling Help Desk Calls with Confidence