King: A Simple Support Escalation Tool With High Leverage

First-line support had to decide whether a customer case should be escalated for fraud review. The logic was not especially glamorous, but it mattered: too many escalations wasted specialist time, and weak decisions increased both handling time and inconsistency.

The team did not need a large platform project. They needed a clearer decision path they could trust in daily work.

I built a simple yes-or-no decision-support flow for support agents, distributed as a clickable PDF.

The intent was straightforward:

• Turn scattered judgement calls into a repeatable sequence
• Reduce reliance on memory or individual interpretation
• Lower avoidable escalations without hiding necessary ones
• Improve speed for a task repeated many times each day

The tool was simple, but its operational effect was strong:

• Handling time dropped
• Error rates went down sharply
• Fewer customers were escalated unnecessarily
• First-line support had more confidence in the decision process

It is one of my favourite examples of high-leverage internal UX. There was no advanced system behind it, just a better structure for repeated judgement in a noisy workflow.