Clear Escalation Triggers
Explicit requests, policy gaps, no progress, thresholds.
Why Escalation Triggers Matter
An autonomous Claude agent will eventually hit a wall it cannot or should not cross alone. The question isn't whether to escalate to a human, but when — and that decision must be defined by clear, deterministic triggers, not vibes.
In the Customer Support scenario, a refund agent that escalates too late frustrates users; one that escalates on every hiccup destroys its own value. This lesson nails down the four reliable escalation triggers the exam expects you to recognize:
- An explicit human request
- A policy gap (no rule covers the case)
- No progress after genuine attempts
- A threshold violation
Trigger 1: Explicit Human Request
If a customer asks to speak to a human, that is not a signal to interpret — it is an instruction to obey. Escalate immediately.
Do not try to talk the user out of it, re-route them through more self-service, or run sentiment analysis to decide if they 'really' meant it. A direct request for a person is the single most unambiguous trigger you will ever get. Treat it as a hard, deterministic branch in your control flow.
# Detect an explicit handoff request as a deterministic branch
def should_escalate(user_message: str) -> bool:
handoff_phrases = [
"talk to a human", "speak to an agent",
"real person", "transfer me",
]
text = user_message.lower()
return any(p in text for p in handoff_phrases)
if should_escalate(latest_user_message):
escalate_to_human(reason="explicit_request", transcript=history)All lessons in this course
- Clear Escalation Triggers
- Anti-Pattern: Sentiment & Confidence Scores
- Structured Error Context
- Local Recovery vs Escalation