0Pricing
Claude Architect · Lesson

Anti-Pattern: Sentiment & Confidence Scores

Never escalate on mood or a self-rated 1-10 score.

The Tempting Shortcut

When you build a Claude agent that handles real users, one question dominates: when do we hand off to a human?

A seductive idea appears early: "Let the model tell us how it feels." Ask Claude to rate its own confidence 1-10, or run a sentiment classifier on the customer's tone, and escalate when the number crosses a line.

It feels data-driven. It is actually one of the most common anti-patterns on the certification exam. This lesson shows you why, and what to do instead.

What a Good Escalation Trigger Looks Like

Escalation should fire on observable, verifiable facts about the conversation, not on a vibe.

The exam recognizes exactly four good escalation triggers:

  • Explicit human request — the user asks for a person. Escalate immediately.
  • Policy gaps — the situation falls outside what the agent is allowed to resolve.
  • No progress after attempts — repeated tool calls or turns yield nothing.
  • Threshold violations — a concrete, defined limit is crossed (e.g. refund amount).

Each of these is grounded in something you can point to in the transcript or the data.

All lessons in this course

  1. Clear Escalation Triggers
  2. Anti-Pattern: Sentiment & Confidence Scores
  3. Structured Error Context
  4. Local Recovery vs Escalation
← Back to Claude Architect