Routed by rule
To the person authorised for this decision at this amount in this entity, not into a shared queue that whoever is least busy drains.
AI capability
Everyone evaluates agents on what they do when they are confident. The property that actually determines whether automation works in a finance function is what happens the rest of the time — because that is the part that lands on a person, and a bad escalation costs more than doing the work.
Act inside rules your controller wrote.6 of 12 actions permitted
What it does
To the person authorised for this decision at this amount in this entity, not into a shared queue that whoever is least busy drains.
The document, the contract, the vendor history, the budget, the candidates considered, and why each was rejected — so the reviewer decides rather than investigates.
Low confidence, a policy boundary, a conflicting signal, or missing information — each is a different problem and stating which changes what the person does.
An escalation nobody actions is a stalled transaction. Time limits, reassignment, and visibility of what is waiting on whom are part of the mechanism rather than a report.
What the person chose, and where they overrode, becomes evaluation data. Escalations that recur identically are a configuration problem rather than a workload.
Escalation rate by workflow, by vendor, by entity, tracked over time. A rising rate is a signal about the data, not about the agent.
Consider a workflow running at eighty-five percent straight-through. The fifteen percent that escalates is now the entire job of whoever receives it, and it is the hard fifteen percent — the ambiguous, the unusual, and the genuinely wrong.
If those arrive as a link to a record and a note saying review required, the person does the investigation from scratch and the automation has saved nothing on the cases that cost the most. Escalation quality, not straight-through rate, is what determines whether the numbers translate into hours.
The four reasons are genuinely different. Low confidence means the agent had the information and could not decide. A policy boundary means it decided and is not permitted to act. A conflicting signal means two reliable inputs disagree. Missing information means the answer is not in the system.
Each implies a different action, and lumping them into one exception queue means the person works out which every time. Stating it is close to free and it is the single change that most reduces handling time.
A shared exception queue routes work to whoever is available, which means decisions are regularly made by people who are not authorised to make them and are then rubber-stamped afterwards.
Routing by the same authority model that governs everything else means the person who receives it can actually decide it. That is faster and it is the difference between a control that operates and one that is documented.
The same escalation appearing weekly is not a workload problem. It is a missing policy, a vendor record needing attention, or a threshold set wrong.
Recurring escalations are grouped and surfaced as configuration suggestions rather than delivered individually forever, which is how the escalation rate falls over time rather than plateauing.
Limits
Every capability page on this site carries one of these, because a feature described without its boundaries is a claim rather than a description.
If nobody is authorised for a decision, escalation has nowhere to go. That gap is an organisational one and configuration surfaces it rather than solving it.
An agent that never escalates unnecessarily is an agent escalating too little. We tune toward over-escalation early and pull it back on evidence.
Where the missing information lives in somebody’s head or in an email thread, no amount of context assembly finds it. The escalation says so rather than guessing.
Questions
Tell us how exceptions are routed today. That is usually where the hours actually are.