Prompt
How do I implement account recovery if users lose access to email or phone?
Latest observation
Oct 28, 2026
OpenAI APIWeb search: off
Account recovery gets tricky when users lose access to the very things you use to verify them. The safest approach is to support multiple recovery paths and make the strongest path available by default, with escalation only when needed.
Good recovery options
Use more than one of these:
-
Backup codes
- Generate one-time codes when the account is created or after MFA setup.
- Let users download, print, or store them securely.
- Make them single-use and easy to revoke/regenerate.
-
Recovery contact
- Let users add a trusted recovery email/phone/device.
- Require confirmation before enabling it.
-
Authenticator app / passkeys
- Prefer passkeys or TOTP/Authenticator apps over SMS.
- If the primary email/phone is lost, a passkey on another device may still work.
-
Verified device trust
- Remember previously logged-in devices for recovery approval.
- Only after a strong login, and with expiration / revocation.
-
Manual support recovery
- For users who lose everything, provide a support flow with identity verification.
- This should be the last resort.
Recommended recovery model
A practical setup is:
1) During enrollment
Ask users to set up:
- Primary login method
- MFA
- Backup codes
- Optional recovery email or passkey
- Optional trusted devices
Encourage at least:
- One second factor
- One offline recovery method (backup codes)
2) During account recovery
Offer recovery paths in order of strength:
- Passkey / trusted device
- Backup code
- Recovery email/phone
- Manual support verification
3) For manual recovery
Use a step-up verification process, such as:
- Government ID + selfie match
- Recent transaction or billing details
- Previous password plus another factor
- In-app activity history / device fingerprint
- Waiting period before changes take effect
Avoid relying on weak data like:
- Date of birth
- Security questions
- Easily guessed personal info
Security principles
- Don’t allow instant takeover. If recovery changes account email/phone, add a delay and notify all existing contacts/devices.
- Notify all channels when recovery info changes.
- Log and alert suspicious recovery attempts.
- Rate limit recovery attempts.
- Require re-authentication for sensitive changes after recovery.
- Allow users to revoke recovery methods and view active devices.
A good fallback hierarchy
A robust order is:
- Logged-in trusted device
- Passkey / authenticator app
- Backup codes
- Recovery contact
- Support-assisted identity verification
Things to avoid
- SMS-only recovery
- Email-only recovery
- Security questions
- Recovery via knowledge-based personal facts
- Immediate change of primary email/phone without delay or alerts
UX tips
- Make recovery setup part of onboarding, not an afterthought.
- Show users a “Recovery options” page.
- Let them download backup codes once and remind them to store them safely.
- Explain clearly which methods are safest.
- If recovery is impossible, provide a clear “create a new account” path.
If you want a concrete implementation pattern
I can also sketch:
- a recovery flow diagram
- a database schema for recovery methods/tokens
- or an API design for account recovery endpoints.