The Most Automatable Support Task

Password resets are boring, repetitive, and identical every single time. The customer says "I forgot my password" in one of 50 different ways, and the answer is always the same: "Go to [link] and click 'Reset Password'."

If you are still handling these manually, you are spending real human time on a task that requires zero human judgment. Let's fix that.

The 5-Minute Setup

Minute 1: Make sure you have a self-service password reset page. If you are using any modern auth provider (Auth0, Supabase, Firebase, Clerk), you already have one. Copy the URL.

Minute 2: Create a routing rule for the password_reset intent.

Minute 3: Write the auto-reply:

"You can reset your password here: [your-reset-link]. If you are still having trouble after resetting, reply to this message and we will help you directly."

That is it. Three key elements: the link, clear instructions, and a fallback for when it does not work.

Minute 4: Set the confidence threshold to 80%. The classifier is very good at identifying password reset requests because they follow consistent patterns.

Minute 5: Test it. Send a test message like "I can't log in, forgot my password" and verify the auto-reply fires correctly.

What the Classifier Catches

The password_reset intent covers more than just "I forgot my password." It also catches:

• "I can't log in"
• "My password isn't working"
• "How do I change my password?"
• "I need to update my login credentials"
• "I've been locked out of my account"
• "Forgot password"
• "Reset my password please"
• "I don't remember my password"
• "Can't sign in"

All of these get the same response: the reset link.

Handling Edge Cases

"I reset my password but it's still not working." This is no longer a simple password reset. The classifier will typically assign a different intent (login_issue or technical_support) or the confidence score will be lower, routing it to a human.

"My password was changed and I didn't do it." This is a potential security issue, not a password reset. The classifier should pick up on the security concern and route it differently, likely as account_security with higher priority.

"I need to reset the password for my team member." This is an admin action, not a self-service reset. The classifier will usually flag the difference, but set your confidence threshold to catch these edge cases.

The Numbers

For a typical SaaS product:

• Password reset requests make up 8 to 15% of all support volume
• Average time to manually handle one: 2 minutes (read, find link, compose reply, send)
• With automation: 0 minutes and 3 seconds per message
• Monthly time savings for a product with 300 support messages: 3 to 6 hours

It is not the biggest time saver in absolute terms, but it is the easiest win. Five minutes of setup time buys you months of hands-free password reset handling.