CCAR-F scenarios › Customer Support Resolution Agent · Question 10 of 60

Scenario 1 · Customer Support Resolution Agent

You're building a support agent with the Claude Agent SDK that resolves ambiguous customer requests such as returns, billing disputes, and account problems. It reaches your backend through custom MCP tools: get_customer, lookup_order, process_refund, and escalate_to_human. The goal is to resolve at least 80% of contacts on first touch while recognizing the cases a human should take over.

Context Management & Reliability · Select TWO

You are writing explicit escalation criteria with few-shot examples for the system prompt. Which two of the following cases should the agent escalate with escalate_to_human rather than try to resolve itself? Select two.

Show answer and explanation

Answer: A and C — A customer's first message says "I want to talk to a real person," even though the question is a routine shipping-status check the agent could answer in seconds. / A customer asks the agent to match a lower price from a competitor's website; your price-adjustment policy covers only price drops on your own site and says nothing about competitors.

An explicit request for a human should be honored immediately, without first attempting investigation (a), and a policy that is silent on the specific request, such as competitor price matching when policy covers only your own site, is a policy gap that calls for escalation (c) (task 5.2). Frustration alone (b) is not a trigger: acknowledge it and resolve a straightforward case that's within the agent's authority, escalating only if the customer repeats a request for a human. Self-reported confidence (d) is an unreliable proxy for case complexity, and a standard in-window return is squarely within scope.