Escalation and ambiguity resolution
When a support or developer agent should hand off to a human, offer to resolve, or ask a clarifying question: the three escalation triggers, why sentiment and self-reported confidence fail as signals, explicit criteria with few-shot examples, and AskUserQuestion for ambiguity in Agent SDK apps.
Design effective escalation and ambiguity resolution patterns
~8 min read · 7 practice questions ·
What the exam expects
- Recognize the three escalation triggers: an explicit request for a human, a policy exception or gap, and inability to make meaningful progress.
- Honor an explicit demand for a human immediately, but acknowledge frustration and offer to resolve when the customer has not asked for a person and the fix is within the agent's capability.
- Reject sentiment scores and self-reported confidence as escalation signals and replace them with explicit criteria plus few-shot examples in the system prompt.
- Escalate when policy is silent on the specific request instead of extending or inventing a rule.
- Ask for another identifier when a lookup returns several matches; in Agent SDK apps, let Claude ask clarifying questions with
AskUserQuestionthroughcanUseTool.
Key terms: escalation trigger (a categorical condition that requires handing off to a human); policy gap (a request the written policy neither allows nor forbids); escalation accuracy (share of conversations correctly escalated); disambiguation (asking for an identifier that picks one record); AskUserQuestion (the Agent SDK tool Claude calls to ask the user multiple-choice questions).
Key facts
- Detail
- Human request, policy exception or gap, no meaningful progress
- Detail
- Escalate immediately, no investigation first
- Detail
- Acknowledge, offer to resolve, escalate if the customer reiterates
- Detail
- 95 percent or higher
- Detail
- Typically 70–80 percent handled without a human
- Detail
- At least 4–5 "good" examples, can include guardrails and tool calls
- Detail
- Known misclassification; direct Claude on when sentiment matters
AskUserQuestion trigger- Detail
- Fires
canUseToolwithtoolNameAskUserQuestion
tools array- Detail
- Must include
AskUserQuestionor Claude cannot ask
- Detail
- 2-4 choices, each with
labelanddescription
- Detail
canUseToolnever fires for them (allow rules,bypassPermissions)
- Why is a sentiment classifier a poor escalation trigger?
- When should a frustrated customer be escalated even though the agent can fix the issue?
- When does an agent ask the customer instead of escalating?
- What must an Agent SDK app with a restricted
toolsarray do so Claude can ask clarifying questions?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Claude Certified Architect - Foundations pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 30 lessons of the Claude Certified Architect - Foundations guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams
Practice for the Claude Certified Architect - Foundations exam
Certifyforce is an independent study resource and is not affiliated with, endorsed by or sponsored by Anthropic. Claude is a trademark of Anthropic.