Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →In a review of 412 escalations, service-desk author Serguey Shinder reported that about two-thirds did not need an engineer. In his account, many tickets reached engineering because first-line staff lacked permission to complete routine tasks, known fixes had not been documented, or an outdated category list sent tickets to the wrong queue. The finding describes one team, not a benchmark for service desks generally.
What the 412-ticket review found
Shinder’s September 2026 post describes a review of 412 escalations from one month. He says about two-thirds could have been handled without an engineer, while about 130 genuinely required someone senior. He summarized the avoidable cases this way: “They needed a permission or a paragraph.”
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
The reported categories give a practical picture of what he meant:
- 148 requests involved four tasks first-line staff were not allowed to perform: adding someone to a distribution group, releasing a quarantined message, resetting a second-factor enrollment, or restoring a deleted file.
- 96 cases were known faults with known workarounds, but the relevant knowledge was held by two people rather than documented.
- 40 cases were attributed to an outdated ticket-category list that routed requests to the wrong queue.
These are the counts and rounded proportions Shinder reports; the post does not explain whether categories overlapped or provide the classification rules, case-selection method, or measurement process. They should be read as one author’s account of one team’s tickets, not as independently verified results or an industry-wide rate.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Why routine work reached engineering
Permissions did not match the work
In Shinder’s account, first-line staff lacked narrowly scoped authority for common tasks, so requests they could otherwise complete had to move up the support chain. He says the team’s permissions had been tightened after a 2021 audit recommendation and that it relied on the product’s standard roles rather than roles shaped around the tasks it wanted first-line staff to perform.
This is a governance trade-off, not a reason to grant broad administrator access. A service desk can define specific actions for trained staff, record each action, and make it reviewable. The Microsoft Service Manager documentation, for example, describes role profiles that control knowledge-article actions such as reading, creating, editing, and deleting; that illustrates role-based control in that product, but does not establish which product Shinder’s team used.
Fixes were known but not transferable
When a workaround lives only in the memory of a few experienced people, every similar ticket can become a fresh escalation. Shinder says his team’s knowledge-article effort had ended in 2022 after its writer changed jobs. The result, as he describes it, was not a shortage of fixes but a failure to make them usable by the colleagues receiving the tickets.
Categories sent tickets to the wrong queue
An old category tree can misrepresent the systems a team actually supports. Shinder attributes 40 cases to an outdated list that routed tickets incorrectly. In that situation, escalation may reflect a routing problem as much as technical complexity: the ticket reaches a team that cannot act, or gets passed along before the right support group sees it.
What the team changed
Shinder reports three process changes intended to address those causes:
- Delegate narrow permissions. The team added seven limited permissions, with each action logged and reviewable.
- Turn recurring faults into tested articles. A fault escalated three times must receive an article before the ticket is closed. An engineer writes it, then a first-line colleague follows it without help.
- Replace the category tree. The team changed to a list based on the systems it runs and began reporting first-contact resolution by issue type.
The test by a first-line colleague matters: an article that only its author can follow has not yet made the fix transferable. The reported approach also creates a trigger for documentation instead of relying on someone to remember to write an article after a busy incident.
What improved—and what the figures cannot prove
Shinder says first line now closes around three-fifths of incoming work, and that a second-factor reset takes six minutes rather than forty. He also says first-contact resolution had remained at about one-third for four years before the team began reporting it by issue type.
The post does not describe how those outcomes were measured, whether the time comparison recurs under defined conditions, or how much each change contributed. Treat them as the author’s reported results, not a controlled before-and-after evaluation. Reporting first-contact resolution by issue type can help distinguish a change in performance from a change in the mix of incoming tickets; a single overall percentage may conceal both.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBest Value
- Used Book in Good Condition
How to apply the lesson without weakening controls
The useful question is not whether a service desk should eliminate escalation. It is whether each escalation reflects technical difficulty or a gap in permission, knowledge, or routing. A team can examine its own tickets by asking:
- Which repeated requests need an engineer only because first-line staff cannot perform a specific, low-risk action?
- Which known faults have workarounds that are not documented or are not usable by the people receiving the tickets?
- Which categories still map to systems, queues, and ownership that have changed?
- Can a trained first-line colleague follow the proposed article independently, and can the action taken be audited?
- Are resolution rates reviewed by issue type as well as overall?
Keep escalation for work that genuinely needs senior judgment, elevated expertise, or a higher-risk decision. The purpose of narrowing avoidable handoffs is to route each ticket to the right capability—not to treat a lower escalation count as success by itself.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
