Escalation
Passing a case from an automated system to a person (or a higher level) because it cannot be resolved safely or well. Handled early, it is protection, not failure.
Escalation is the handoff of a case from automation to a human, or from one level of expertise to another. Typical triggers are low confidence, high consequence, an unusual input, a customer request or a failed attempt.
It is one of the places where human work hides after automation. Teams that count only the removed visible work ignore the human work that moves somewhere else: review, exception handling, context provision, escalation, recovery and accountability. Every escalation costs attention, and a poorly designed one costs more because the person receives it without context.
Designing it well
- Make it a real, staffed path, not a dead-end queue (abstention).
- Hand over the context so nobody starts from zero.
- Escalate early when automation is unlikely to succeed: in customer service this is channel preservation.
- Count escalation volume in supervision load.
An escalation is not a failure of the system; a missing or slow one is.
Read more in The hidden metric in AI automation is supervision.
Related terms
Exception handling
The human and system work needed for cases an automated process cannot complete normally. It is a major place where AI savings quietly reappear as cost.
Channel preservation
Escalating or declining an automated interaction early, on purpose, to protect the customer's willingness to use the automated channel again — treating escalation as protection, not failure.
Abstention
A deliberate option for an AI decision system to decline to decide and return uncertain or high-consequence cases to a person, rather than forcing every input into yes or no.
Supervision load
The human attention an AI system still consumes — context supply, review, approval, correction and exception handling — measured per dependable, completed unit of work.
Used in these essays
AI is removing the coordination tax — the next bottleneck is authority
As AI reduces the cost of moving work between teams and systems, many organizations will discover that the remaining delay is not coordination. It is permission to decide.
An AI agent should get authority per task, not permissions per role
A person's role describes standing access across many situations. An AI agent should receive a narrower authority envelope for the task it is executing now.
Design systems need an interaction policy layer for AI
Components can keep an AI experience visually on-system while the agent is behaviorally off-policy. Design systems now need reusable rules for what AI may present, decide, execute, defer, expose as uncertain, confirm, reverse and escalate.
Your AI agent can follow the objective and still break the company
AI agents can satisfy a local objective while violating the organization’s broader constraints. The control problem is not only model alignment; it is management design.
Stop adopting AI
AI adoption is rising faster than enterprise value because companies keep installing new intelligence inside old operating models.
OpenAI Decisions API turns probability into policy
The provocative part of OpenAI's Decisions API is not that AI can make choices. It is that a model score can quietly become an action — and an action can quietly become policy.
OpenAI Dots is a test of whether AI can carry a goal, not just complete a task
Dots matters less as another capable assistant than as a test of persistent delegation: can AI keep carrying a goal without giving the user a new system to manage?
The wrong questions about AI right now
Many of the questions that helped us orient ourselves around generative AI are now too blunt to be useful. The harder work is no longer asking what AI is in the abstract, but specifying where it works, where it fails, what authority it should have, and what the whole system costs.
A cheaper AI model can move the cost instead of removing it
A lower model bill can hide a higher workflow bill. The useful AI TCO question is not only what got cheaper, but where the cost moved.
The second team is the real innovation test
A successful pilot proves that one team could make something work. Organizational capability begins when a different team can reproduce the useful result without inheriting the original team's exceptional conditions.
Make the AI vendor demo fail
A polished AI demo proves that a system can succeed under prepared conditions. A buying decision needs different evidence: what happens when the system is wrong, blocked, uncertain or halfway through an action.
The hidden metric in AI automation is supervision
As AI moves from assisting work to leading it, hours saved stop telling the whole story. The scarce resource shifts to human supervision: approvals, exceptions, context and judgment.
The agent is not the operating model
Giving AI more autonomy does not remove organizational complexity. It gives that complexity permission to act.
Your AI data agent is creating a second dataset
AI data agents do more than answer business questions. At scale, the pattern of questions, corrections and dead ends becomes a new signal: a map of what the organization is trying to understand, where its definitions are weak, and which decisions deserve better infrastructure.
Your chatbot is borrowing from the next interaction
AI customer service is usually measured one interaction at a time. But a failed automated interaction can change which channel a customer chooses next time. That makes future adoption part of the economics, not a separate trust metric.