Escalation done right: what a human should actually see

Good escalation hands a reviewer a decision they can act on immediately: the exception type, the amount, the supplier, what's already been checked, and the two or three options available to close it. Most escalations fall short of that. They forward a raw case number and a one-line reason code, and the person on the receiving end has to reopen the ERP and reconstruct what already happened before they can decide anything.

Most escalations dump a case on the reviewer's desk

A typical escalation email reads "invoice #48291, price variance, please review." The reviewer now has to pull up the invoice, find the PO, locate the contract, check whether receiving confirmed the goods, and figure out who to call if the numbers still don't reconcile. All of that work happened once already, whoever or whatever first identified the exception saw all of it, and none of it survived the handoff.

A useful escalation already answers the easy questions

The invoice amount, the PO number, the supplier's contact, whether receipt was confirmed, what tolerance threshold was breached and by how much, whether this supplier has triggered the same exception before: none of that requires judgment to gather, so none of it should land on the reviewer's desk unanswered. An escalation that arrives with those facts already attached turns a fifteen-minute investigation into a two-minute decision.

Give the reviewer a narrowed choice, ready to act on

Once the facts are attached, the decision usually narrows to a small set of options: approve the variance because it matches a known freight surcharge, reject it and request a corrected invoice, or flag it for the supplier relationship owner because this is the third time this month. Presenting those options directly, instead of a blank case and an ERP login, is what separates an escalation that gets resolved same-day from one that sits for a week.

Escalate what actually needs judgment

Plenty of exceptions look complicated but don't actually need a person: three systems disagree on a receipt date, but the answer is sitting in a shipping confirmation email that nobody checked. That's a fact-finding problem. It never needed a person's judgment, and routing it to a human anyway is how exception queues turn into a headcount plan. Reserve escalation for the cases that genuinely need a person: a disputed charge with no clear answer, a write-off above policy, a supplier relationship decision. Everything else belongs with an agent that can gather the context itself, after routing has already sent the case to whoever, or whatever, can actually close it.

Fragment's agents resolve most exceptions before they ever reach a person, and when a case does need judgment, it arrives with the context already attached. See how it works in Fragment's workflows, or book a demo to see an escalation done right.