A help desk works well when requests arrive in one place, carry enough detail to act on, and get handled in a sensible order. Whether your help desk is an in-house person or an outside provider, some of the most avoidable problems come from how requests are made and tracked, not from a lack of technical skill. These are the mistakes worth fixing first, and what to do about each.
1. Requests that skip the ticket system
A quick text to the IT person, a hallway mention or an email to someone’s personal inbox feels faster. But a request that is not recorded cannot be prioritized, handed to someone else when that person is out, or counted when you look for recurring problems.
The fix: one way in. Pick a phone number, email address or portal for all requests, tell staff it is the only route, and have whoever receives an informal request log it before working on it.
2. Tickets without the detail needed to act
“My computer is broken” starts a round of questions before any work can begin. A useful request answers a few things up front:
- Who is affected, and on which device or account?
- What exactly happens, including any error message or a screenshot?
- When did it start, and did anything change around that time?
- Is anyone else affected, and can the person still work?
The fix: put those questions on the request form or in a short guide for staff.
3. Living with recurring problems
It is easy for staff to put up with a slow laptop or a printer that jams rather than report it again. The workaround becomes routine, and the cause is never found.
The fix: tell staff to report repeat problems every time, and ask your help desk to link repeat tickets so someone looks for the underlying cause instead of resetting the same thing again.
4. No agreed definition of urgent
If every request is marked urgent, none of them is. If nothing is, a server outage can wait behind a request for a new mouse.
The fix: agree on priority levels with your help desk, with plain examples. A typical set: the whole business is down; one person cannot work; something is degraded but usable; a request or question. Write the target response for each level into your agreement.
5. Resetting passwords and MFA without checking who is asking
Attackers call help desks pretending to be employees. CISA’s advisory on the Scattered Spider group describes calls to IT help desks that aim to get passwords reset or MFA moved to a device the attacker controls. A friendly, helpful help desk is exactly what that approach relies on.
The fix: a written identity check for every password reset, MFA change and new-device enrollment. Call the person back on a number already on file, or confirm with their manager, before making the change. Treat pressure and urgency as a reason to slow down. Security awareness training should cover this for staff on both sides of the call.
6. Late notice of new hires and departures
When IT hears about a new hire on their first morning, the account, laptop and licenses are not ready. When IT hears about a departure days later, the person’s access stays open in the meantime.
The fix: a simple form that HR or managers submit as soon as a start or end date is known, covering accounts, devices, licenses, shared mailboxes and building access. For departures, remove access on the last day.
7. Knowledge that lives in one person’s head
If only one person knows the Wi-Fi password, how the backup works or which vendor supports the accounting software, every absence becomes a problem.
The fix: written documentation for each system: what it is, who supports it, how to get help, and where admin credentials are stored in a password manager rather than in a spreadsheet.
8. Never looking at the tickets as a whole
Tickets are a record of where technology gets in your staff’s way. Without a periodic review, the same causes keep coming back.
The fix: review ticket reports with your help desk at a set interval. Look at the most common categories, repeat issues for the same people or devices, and anything that took too long. Pick one or two causes to fix properly before the next review.
What to do next
Start with mistakes 1 and 5: a single route for requests, and an identity check for password and MFA changes. Both cost little and improve service and security at once. If you use an outside provider, our managed IT services page describes how we handle support, and you can request a Blind Spot Scan for a broader view of your setup.