An AI assistant that can update records or initiate transactions needs more than a generic confirmation dialog. Tiered approval matches the review required before an action to its impact, so consequential actions receive stronger scrutiny than routine ones. section 4.7.1
A tiered workflow can distinguish three levels of impact:
- Low impact: For viewing data or minor updates, display the interpreted action and proceed after a brief timeout, allowing the user to intervene. section 4.7.1
- Medium impact: For scheduling or standard updates, display key parameters and require a single confirmation. section 4.7.1
- High impact: For financial transactions, bulk operations, or irreversible changes, require individual verification of each critical parameter. section 4.7.1
Confirmation is not a substitute for execution checks. Before approving a status change, verify required documentation and automated approval thresholds. Before issuing a refund, check that the original transaction exists and has not already been refunded. section 4.7.1
Claim updates with approval thresholds
ClaimAssist binds write actions to the authenticated user: customers can affect their own claims, while adjusters can affect assigned cases. For routine updates, it displays the intended action and waits for confirmation. Actions above automated approval thresholds require a human reviewer, regardless of the conversation. section 4.9
Some operations should be excluded entirely, such as changing contract terms or deleting records without recovery options. Where exclusion is impractical, a human can approve before execution or monitor the system in real time and intervene. Explicit boundaries and narrowly scoped credentials help limit what a manipulated assistant can do. section 4.7.1 section 4.9
