Account Changes

Use case

Account changes

Account changes range from harmless preference updates to sensitive changes involving identity, billing, access, ownership, or security.

Actions the agent might take

  • Explain how to update account information.
  • Change low-risk preferences after basic verification.
  • Draft a requested billing or ownership change for review.
  • Route sensitive changes to a secure approval path.
Example boundaryApproval triggerEvidence to retain
Agent may update communication preferences after the customer is signed in.Customer asks to change account owner, billing identity, payout details, or access rights.Authenticated session, requested field, previous value category, approval result.
Agent may draft a change request for a billing contact.Request comes from an unverified channel or conflicts with existing account ownership.Requester identity evidence, account role, change summary, reviewer decision.

Use How to Decide What Your AI Agent Can Do on Its Own to separate low-risk preference updates from account changes that need confirmation or employee approval.

When account ownership is uncertain or verification conflicts with the request, Designing the Handoff When an AI Agent Reaches Its Limits can help define the handoff record and approval path.

Scenarios to test

  • A signed-in customer updates notification preferences.
  • A customer asks to change the email used for account recovery.
  • A user requests transfer of account ownership.
  • A billing contact asks to change payment details.
  • An unauthenticated requester asks for a sensitive change.

For sensitive account changes, also consider recovery before granting authority. When an AI Agent Makes a Mistake: Design for Correction and Recovery explains why some account actions should pause before they create a hard-to-reverse commitment.