What you need to know
The three triggers
| Trigger | Example | Action |
|---|---|---|
| The customer asks for a human | "I want to speak to a person, now." | Escalate immediately, without first trying to solve it |
| Policy is silent or ambiguous | "Do you match a competitor's price?" when policy covers only your own site | Escalate; do not invent a policy |
| No meaningful progress | Tools keep failing; the problem is outside what the agent can do | Escalate with a handoff summary |
Complexity alone is not a trigger. A long, multi-part case the agent can resolve should be resolved.
Explicit demand versus frustration
- A customer who explicitly asks for a person gets one, even when the fix looks easy.
- A customer who is frustrated but has not asked: acknowledge the frustration, offer the resolution if it is within the agent's ability, and escalate if they reiterate that they want a person.
Unreliable proxies
- Sentiment. Annoyed customers often have simple problems; calm customers may need a policy exception. Escalating on negative sentiment sends the wrong cases to humans and keeps the right ones away.
- Self-reported confidence. A model's statement of its own confidence is a poor measure of case complexity, so a confidence threshold makes a weak escalation rule.
Ambiguity: ask, do not guess
When get_customer returns three matches for "Sarah Johnson", choosing the one in the same city as the phone's area code is a heuristic guess, and a wrong guess means acting on someone else's account. Ask for an additional identifier (email, account number, an order number) and confirm before acting.
The same applies to vague instructions in other scenarios: "clean up this module" with no scope deserves a clarifying question or a proposed scope before broad changes.
Put the criteria in the prompt, with examples
Escalation rules work best as explicit criteria plus a few examples in the system prompt, showing cases to escalate and similar cases to resolve.
In the exam
Scenario 1 is the home of these: explicit requests for humans, sentiment-based escalation proposals, competitor price matching, multiple customer matches, and how to write the escalation rules.
Check your understanding
A customer's first message is "Let me talk to a human. Don't try to help me yourself." The issue looks like a simple replacement. What should the agent do?
Show answer
Answer: D. An explicit request for a person is honoured at once, whatever the agent could do itself.
The team proposes escalating whenever sentiment analysis detects strong frustration. What is the main problem?
Show answer
Answer: B. Frustrated customers often have simple problems and calm ones may need exceptions. Sentiment is a poor proxy for case complexity.
get_customer returns three customers named Sarah Johnson. What should the agent do?
Show answer
Answer: C. Asking for an email, account number or order number resolves the ambiguity without guessing. It is within the agent's ability, so escalation is not needed.
Apply it: Cedar Ridge's escalation policy
Write the escalation section of Cedar Ridge's system prompt.
- State the triggers as explicit criteria.
- Write four short examples: two to escalate and two to resolve, each with a reason.
Why: examples teach the boundary better than rules alone. - Write the rule for a frustrated customer who has not asked for a person.
- Write the rule for multiple matches.
Show model answer
1. Triggers. Escalate when (a) the customer asks for a person, (b) policy does not cover the request or is ambiguous, (c) you cannot make progress after two attempts, or (d) a hook blocks the action and says to escalate. Do not escalate because the customer is upset or the case has several parts.
2. Examples
| Situation | Decision | Reason |
|---|---|---|
| "Do you match Rival Outdoors' price?" | Escalate | Policy covers only Cedar Ridge's own prices |
| "Get me a human." | Escalate now | Explicit request |
| Angry customer, damaged item, within 45 days | Resolve | Policy covers it; offer the fix |
| Three issues in one message, all covered by policy | Resolve | Several parts is not complexity |
3. Frustration. Acknowledge it in one sentence, state what you can do now, and offer to do it. If the customer repeats that they want a person, escalate.
4. Multiple matches. Never choose between matching records. Ask for an email, account number or order number, and act only when one verified match remains.