# google.com / customer_support.account_recovery

Health: degraded
AES: 76
Confidence: low 0.28
Freshness: 0d

## Recipe

Status: active
URI: recipe://google.com/customer_support.account_recovery/public-preflight-v1

1. Open the documented public path for Google Account: Google Account official public help/contact source -> select account, order, billing, refund, warranty, complaint, or service issue -> collect required identifiers and stop before submitting any support request, chat, claim, appeal, or account-recovery action.
2. Check the listed blockers and policy constraints before entering account, payment, booking, or cancellation state.
3. Stop before any irreversible or user-sensitive action and ask for explicit approval.

## Human Approval

Keep the user present for authentication. Do not request, store, or replay credentials or one-time codes.

## Do Not Cross

- Use public help/contact pages only until the user is present and has authorized account-specific support.
- Do not submit contact forms, support chats, warranty claims, refunds, complaints, chargebacks, or account-recovery requests during corpus collection.
- Capture required information, escalation path, and case-ID/confirmation expectations before any user-approved handoff.

## Success Signals

- Support case number or reference ID
- Confirmation email or transcript
- Visible ticket, refund, warranty, complaint, or account-recovery status

## Blockers

- login_required
- human_handoff_required

## Recommended Actions

- Use public help/contact pages only until the user is present and has authorized account-specific support. Keeps the agent inside documented, reversible, user-approved boundaries.
- Capture handoff evidence and pause before accepting retention offers. Keeps user intent explicit during adversarial cancellation flows.