
Service Operations · Module 3 of 4
The Triage Line: Why "First Come, First Served" Is the Expensive Default
Cedarline's hardest tickets escalate to one senior specialist, and she is a bottleneck of exactly one. Two kinds of work sit in her queue: urgent escalations (a failed bulk order, a wholesale account an hour from leaving) where a minute of delay costs about $120, and routine ones where it costs $20. Right now whoever escalated first is served first, which is what a ticketing tool does when nobody has an opinion. It draws no complaints, and it makes everyone wait the same 30 minutes: the churn-risk ticket sits behind the address change, and the desk carries $120 an hour of waiting cost. Reorder to serve urgent first and the bill falls to $70, but not because anything got faster. Watch the third gauge: the load-weighted total waiting is 0.375 under every order you can build, identically, because of Kleinrock's conservation law. You cannot reorder your way to less waiting; you can only decide who does it. So decide by cost: serve the highest c·μ first, urgent's index is 720 against routine's 120, and the fixed pool of waiting lands on the customers who mind least. Get that index wrong and it bites: routine-first costs $195 an hour and breaches the urgent promise outright, which is exactly where 'close the most tickets' and 'answer the loudest' quietly lead. And the rule is bounded twice, on purpose. Strict priority has no floor (push urgent load up and the class served second goes from 40 minutes to 75 to 188, while its own volume never changes) so real desks run priority with a promotion clock. Then an outage doubles urgent work and no ordering meets both targets at all; the lever stops being order and becomes load. Stack the cards by hand, run the hour, and watch one needle refuse to move. How many is svc-01's question. How arranged is svc-02's. In what order is this one.
0 of 22 items completed0%~97 min remaining
Material · 22 items