Can't log in: SaaS support reply templates
Login problems are urgent for the customer and usually simple to fix: the wrong email address, a reset link in spam, a Google sign-in account versus a password one, or a lost two-factor device. These replies walk through the likely cause without confirming account details to someone you have not verified.
Template
Subject: Getting you back into {workspace}
Subject: Your {workspace} account access
Subject: Password reset sent
- {first_name}
- The customer's first name.
- {login_url}
- Your app’s sign-in page.
- {agent_first_name}
- The first name of the teammate sending the reply.
- {workspace}
- Your company or product name.
When to use it
- A customer says they cannot log in or the password reset email never arrives.
- Someone signed up with Google and is now trying to use a password, or the other way round.
- A customer has lost access to their two-factor authentication device.
How to use it
- 1
Check the account first
Look up which email and sign-in method the account uses before replying, so you send the right fix the first time.
- 2
Verify before changing anything
Only change the email address or remove two-factor after the request comes from the registered address or passes your identity checks.
- 3
Ask what they see
If the first fix fails, ask for the exact error message or a screenshot rather than guessing again.
Common mistakes
- Confirming whether an email address has an account to someone you have not verified.
- Removing two-factor authentication because the request sounds urgent.
- Sending a reset link when the customer signs in with Google or SSO, where a password does not apply.
What they usually ask next
Once they are back in, customers often notice a charge they want explained. Billing question
Related templates
All saas support templates- Billing questionReply templates for SaaS billing questions: unexpected charges, prorated upgrades, invoices and plan changes. Explain the charge and link the invoice.
- Bug report acknowledgementReply templates for acknowledging a SaaS bug report. Confirm the issue, offer a workaround, set expectations and promise to email when it is fixed.
- Feature request replyReply templates for SaaS feature requests. Thank the customer, ask what they are trying to do, log it honestly and never promise a ship date.