Designing Support Tiers
It is 09:04 and the senior engineer is resetting a password. Somewhere behind her a volume is quietly filling, and a patch window is slipping to next month. The one project with a deadline has not moved since Tuesday. All of that is because every ticket on this desk reaches everyone, and she was free. Nobody designed that. A desk with one queue and no lanes routes its most routine work to its most expensive hour, and does it again at 09:40. The opposite failure is just as common: the desk with four tiers on a three-person team. A ticket visits every queue before anyone works it, and "kick it upstairs" has become a sport with no winner.
This series is about getting the lanes right, which is a routing problem rather than a status ladder. It covers what support tiers are for, and the four parts every real tier is made of. It covers what L1, L2 and L3 each take, resolve and never touch, with one ticket's path through all three and the clock running. It covers when tierless swarming beats tiers and the two rules that keep it from eating the senior engineer's week. Then come escalation boundaries that hold because they are written down, with a four-line handoff. It covers what tiers look like when there are three of you and everyone is also everything else. And it covers the four numbers that say whether your tiers are working or only drawn. Each article has a template to copy and a story from a desk that found out the hard way.
Articles in This Series
- What Support Tiers Are Actually For
The three jobs tiers do and the four costs they bring; a tier as a routing decision, not a rank. Covers the queue, skill list, access list and time box every tier needs. Also covers the signs you need tiers, the signs you have too many, and a scored worksheet. - L1, L2, L3 in Practice
What each lane takes, resolves, never touches and needs in skills and access. Covers a table of who owns the common ticket types, and one VPN ticket's path through all three with timestamps. Also covers the bounce-back, and a one-page tier charter template. - When Tierless Swarming Beats Tiers
Pull, not push; help in the open; one owner per ticket. Covers where swarming wins, where it fails, the chat-channel version for a small desk, and swarming hours. Also covers a side-by-side comparison with tiers, the hybrid most teams settle on, and a rules card. - Escalation Boundaries That Hold
Why boundaries leak; the three boundary rules of what, when and how; and the four-line handoff note. Also covers the time box done honestly, the bounce-back rule, the "kick it upstairs" culture and its cure, and a boundary card to copy. - Tiers for a Three-Person Team
One and a half tiers: a rotating L1 lane, everyone else as L2, vendors as L3. The rotation, what the lane resolves, who covers what when someone is out, protecting project time, and a three-person operating sheet. - Measuring Whether Your Tiers Work
Resolution by tier, escalation rate, bounce-back rate and time at each tier; healthy ranges with hedges. Covers the signals a boundary is misplaced, and getting the numbers from any tool without gaming them. Also includes a fifteen-minute quarterly tier review sheet.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.