The quick read
- Transfer the question, relevant history and attempted steps so the customer does not repeat everything.
- Test ordinary cases and policy exceptions.
Choose a useful scope
Define which questions can be answered from approved information. Identify cases requiring context, exceptions or human authority. A narrow reliable service may help more than broad coverage that customers must constantly double-check.
Make escalation useful
Transfer the question, relevant history and attempted steps so the customer does not repeat everything. Distinguish a proposed solution from an action already completed. Give the human reviewer the evidence needed to continue.
Measure resolution
Test ordinary cases and policy exceptions. Track incorrect answers, repeated loops and the quality of human follow-up, not just the proportion of conversations contained by automation. For a returns assistant, an unanswered exception should become a clear handoff rather than an invented rule. Escalation belongs inside the product design. A system can be successful by recognising its limits early and moving the customer toward a dependable resolution, with less repetition and a clear account of what remains to be decided.
Sources & notes
AI-assisted editorial content checked against the linked sources.
anthropic.com — official reference
Sources reviewed for the September 2026 launch edition.