When to use this
- A customer cannot access an account, reset a password, receive a code, or complete MFA.
- An admin, billing contact, agency, former employee, or new owner asks to change account access.
- Your team needs customer-safe wording while identity, ownership, payment, support, or security records are checked.
- AI tools may summarize account status, identity proof, security incident, refund, cancellation, or data-access language without enough approved source material.
Copy/paste account-recovery source card
AI-SEARCH-ACCOUNT-RECOVERY-PASSWORD-RESET-READY
ACCOUNT RECOVERY / PASSWORD RESET SOURCE CARD
Account ID:
Customer / requester name:
Requester role: owner / admin / billing contact / employee / agency / unknown / other
Recovery issue: password reset / MFA / email change / recovery code / locked account / suspected takeover / admin change / other
Identity/authority proof source checked:
Approved public help path:
Official support channel to use:
Account status that can be safely shared: active / locked / under review / disabled / unknown
Security concern present? Y/N/Unknown
Billing/subscription status relevant? Y/N/Unknown
Data-access, deletion, cancellation, refund, or legal/privacy review needed? Y/N/Unknown
What support is allowed to say now:
What support must NOT say now:
Do-not-say list: identity verified / account ownership confirmed / access restored / MFA bypassed / refund approved / breach confirmed / no breach / legal conclusion / private risk signal
CRM/support label: account_recovery / password_reset / mfa_help / admin_change / security_review / owner_review
Next human review step and due time:
STOP PUBLISHING guardrails
- STOP PUBLISHING before AI says identity is verified, account ownership is confirmed, access will be restored, MFA can be bypassed, or a refund/cancellation/security outcome is approved unless the source card proves it.
- STOP PUBLISHING if private security signals, login history, IP/device clues, payment tokens, admin notes, or internal risk scores could be exposed.
- STOP PUBLISHING before changing login email, admin role, billing owner, recovery method, or account status without a named owner and official system source.
- STOP PUBLISHING when support notes, billing records, security alerts, and account profile data disagree.
- STOP PUBLISHING before giving legal, privacy, breach-notification, police-report, chargeback, or compliance-sensitive advice.
Customer-safe snippets
Access-help acknowledgement
“Thanks — we can help with account access, but we need to use the approved recovery path rather than guessing from the message thread.”
Identity or authority check needed
“A person needs to confirm the account record and requester authority before changing login details, MFA, ownership, or billing access.”
Security review in progress
“Because account access can affect private information, we do not want to confirm security details or restore access until the approved review step is complete.”
Unsupported promise prevention
“We cannot promise a refund, cancellation, ownership change, or account restoration from this message alone. The support owner will use the official account source to confirm the next step.”
AI audit prompt
You are reviewing an account-recovery, password-reset, MFA, admin-change, billing-owner, or security-review answer for AI search, a chatbot, a help center, or a support macro. Use only the source card below. Draft a short customer-safe reply that helps the requester use the approved path without inventing identity proof, ownership, access restoration, MFA bypasses, refunds, cancellations, breach status, legal/privacy conclusions, or private security signals. If any STOP PUBLISHING rule is triggered, output: NEEDS OWNER REVIEW and list the missing fields.
Source card:
[PASTE SOURCE CARD]
Why this matters for AI search
Account-access answers are high-risk because AI systems can blend help-center steps, old policy pages, security notes, billing records, support macros, and generic password-reset advice into one confident answer. A source card keeps private security signals private and keeps public answers tied to approved facts.
This free checklist pairs with SEO After AI, which includes practical AI-search visibility and source-control workflows for small businesses that need answer engines to quote accurate, current, human-reviewed information.