Most mid-sized employers staff their help desk by guesswork. Someone leaves, a posting goes up for a generalist, and the job description lists every tool in the building. Six months later the team is behind, the best technician is doing password resets, and the owner wonders why IT feels expensive.
The fix starts with your own ticket data. Pull 90 days of tickets and sort them. In nearly every office we see, the queue breaks into the same few buckets, and each bucket calls for a different kind of person.
Read the queue before you write the job description
Group tickets into five categories:
- Access: password resets, account lockouts, permissions.
- Devices: printers, laptops, monitors, peripherals.
- Connectivity and email: network drops, mail errors, VPN trouble.
- Software: installs, updates, slow or crashing applications, how-to questions.
- Security: phishing reports, suspected malware, odd login activity.
In most organizations, access and device tickets make up the largest share by count. They are also the quickest to close. That matters, because it tells you where the volume is and where the skill is needed. They are rarely the same place.
Match each bucket to the right level of person
| Ticket type | Who should handle it | What to hire for |
|---|---|---|
| Access and lockouts | Self-service tools, then tier 1 | Patience, identity checks, clear writing |
| Devices and printing | Tier 1, with a deskside option | Hands-on repair, good phone manner |
| Network, email, software | Tier 2 | Real troubleshooting, admin rights experience |
| Security incidents | Tier 2 or a named security lead | Judgment under pressure, containment steps |
The common mistake is hiring tier 2 skill and assigning tier 1 work. You pay for a systems person and get a password desk. They get bored, and good people leave a job like that in under a year.
The reverse mistake is just as costly. A tier 1 hire with no escalation path will sit on a mail server fault or a suspected phishing hit because nobody told them to hand it up.
Automate the repetitive work first
Password resets and lockouts are the obvious candidates for self-service. If your identity system supports a reset portal with multi-factor verification, turn it on before you add headcount. That one change can take a visible slice off the queue.
Be realistic about it, though. Automation removes the simple tickets, so the work left for your people is harder on average. That changes the hire. After you automate, you need fewer pure tier 1 hands and more people who can diagnose. Plan the role for the queue you will have in a year, not the one you have today.
The same goes for AI-assisted ticket triage and chat tools. They can route and draft answers. Someone still has to own the knowledge base, check the answers and spot the pattern when the same fault shows up 30 times in a week. That is a real job, and it suits a sharp tier 2 technician.
Treat security tickets as a separate duty
A phishing report or a malware alert is not a normal ticket. Speed matters, and so does what the technician does first. Isolate the machine, preserve evidence, tell the right person.
If you do not have a security lead, decide who the technician calls. Write it down. Then screen for it when you hire: ask candidates to walk through the first 15 minutes of a suspected compromise. Strong people answer in order. Weak ones start fixing things.
Hiring signals that hold up in an interview
Technical certifications help, but they are not the whole picture. For help desk roles, test these:
- Written updates. Ask for a short note to a non-technical user explaining a network outage. Clarity predicts user satisfaction better than most technical quizzes.
- Diagnostic order. Give a symptom, such as a laptop that connects to Wi-Fi but loads nothing, and listen for how they narrow it down.
- Escalation instinct. Ask when they would stop and hand a ticket up. The right answer is specific.
- Documentation habit. Tickets are a record. People who close them with useful notes make the next fix faster.
When contract coverage makes sense
Help desk demand is uneven. A software rollout, an office move, a Windows migration or a cloud cutover can double the queue for six weeks and then fade. Hiring permanent staff for the peak leaves you overstaffed the rest of the year.
Those are good moments for contract technicians, either to absorb tier 1 volume while your regular team handles the project, or to bring in a tier 2 specialist for the migration itself. Set the end date and the handover notes up front so the knowledge stays when they leave.
A permanent hire is the better call when the same ticket types keep returning, when after-hours coverage is a real need, or when your team is already one resignation away from a gap.
What to do next
Export your last quarter of tickets, sort them into the five buckets and count them. Then compare the result to the people you have. If tier 2 work is landing on tier 1 staff, or the reverse, you have found your hiring need. Fix the self-service gaps first, then write the role for what remains.
If you want a second opinion on how to structure the team, or you need a help desk technician, a tier 2 analyst or short-term contract coverage in Canada or the US, a Traverse recruiter can help with that.