- A service desk is the main point of contact between users and IT: it receives, logs, tracks and communicates incidents and service requests, and routes them to the right team or supplier
- Support tiers describe who has the skills; priority describes impact and urgency. Set response targets by priority, not by tier
- Password resets, account recovery and MFA changes are identity functions that attackers target. Verify, approve and log every one
- SLAs should separate response, restoration, resolution and update targets, and match the capacity you have actually staffed or contracted
- Outsourcing support can work well, but your business keeps accountability for priorities, risk and supplier performance
What an IT service desk actually does
An IT service desk is the main point of contact between the people who use IT and the people who run it. It receives incidents and service requests, logs each one, tracks it through to closure, keeps users informed, and routes the work to the right internal team or external supplier. In ITIL 4, the service desk is one practice among several: incident management, service request management and problem management are separate practices that the service desk works alongside. That distinction helps in a small business too. The desk owns the contact and the communication; it does not have to carry out every fix itself.
Many organisations that say they have a service desk are running something looser: an email address, a group chat, and a few people who respond when they happen to see a message. A real service desk receives requests through a defined channel, logs them as individual items, assigns ownership, tracks progress, and closes them with confirmation that the problem is resolved. No logging means no backlog visibility. Unowned tickets get ignored. Without closure confirmation, your queue fills with issues marked "probably fine now" that nobody has verified.
It also needs to handle two distinct flows: incidents (something is broken and needs fixing now) and service requests (a user needs something set up, changed, or explained). Treating all requests the same way creates priority confusion. A laptop that will not boot is not in the same category as a request to add a new user to a shared drive. Your desk needs to distinguish between the two, even at a basic level.
Generic "minutes lost per incident" figures tell you little about your own business. For each significant incident, record how long the interruption lasted, how many users were affected, and which business processes stopped or slowed (invoicing, customer service, production, payroll). Illustrative scenario, not a benchmark: if email is unavailable for 90 minutes for 30 staff, that is 45 hours of disrupted working time, before counting delayed customer replies.
Service desk, help desk, MSP or IT management?
These terms are often used interchangeably, but they describe different things. Knowing which one you are missing stops you buying a support contract when what you actually need is someone to own IT decisions.
| Term | What it is | What it does not cover |
|---|---|---|
| Service desk | Single point of contact for incidents and service requests, with logging, tracking, routing and user communication | Setting IT strategy, budgets or risk decisions |
| Help desk | A narrower, fix-focused function that answers questions and resolves straightforward faults | Usually not structured service requests, supplier coordination or service reporting |
| Managed service provider (MSP) | An external supplier delivering a defined scope of services under contract, often including the service desk, monitoring and patching | Your business priorities and risk ownership, which stay with you |
| IT management (IT lead or vCIO) | The accountable role that sets IT priorities, approves changes, manages risk and budget, and governs suppliers | Day-to-day ticket handling |
For a deeper look at the sourcing options, read in-house IT vs. managed service provider: how to decide. If you also need to decide where IT is heading, start with an IT roadmap aligned with the business.
Define your support tiers before buying any tools
Before you evaluate any software or service, list the kinds of IT requests your organisation actually raises and decide who should handle each type. This costs nothing and prevents you from over-engineering a support model for problems you do not have.
A three-tier model is common, but it is optional. A small firm can run well with general first-line support, self-service for standard requests (such as installing software from an approved catalogue) and a clear route to external specialists. What matters is that for each request type you know who receives it, who carries out the work, who tracks it and who escalates it when it stalls.
- Tier 1: First-line support. Logging and categorising tickets, printer issues, software installation questions, email configuration, basic hardware troubleshooting, and anything resolvable with a knowledge base article or a short remote session. Password resets and account unlocks often start here too, but only through a verified identity procedure (see the next section). Tier 1 staff need patience, a good knowledge base, remote support tools and clear escalation rules.
- Tier 2: Technical support. Network configuration, application errors that require log analysis, creating or deploying device images, VPN setup, software licensing problems, and anything requiring administrator-level access. Tier 2 engineers need genuine technical skills and the ability to diagnose problems without a script.
- Tier 3: Specialist support. Security incidents, infrastructure architecture, custom integrations, compliance-related system changes, and anything that needs expertise your Tier 2 team does not have. Tier 3 may involve external specialists, a managed security provider, or a vendor's own support team.
How tickets split across tiers varies widely between organisations, so do not plan staffing on rule-of-thumb percentages. Analyse the first 60 to 90 days of ticket data (volumes by category, time to resolve, how often tickets are escalated, and peaks by day and hour) before deciding how much internal or outsourced capacity you need. You may find that many routine requests can move to a self-service portal, or that a handful of complex systems generate most of the effort.
A tier describes who has the skills to handle a ticket. Priority describes business impact and urgency. A critical incident escalated to Tier 3 can need an immediate response, while a low-priority Tier 1 request can safely wait. Do not set response targets by tier alone, and remember that escalating a ticket to a specialist does not change its business priority.
Password resets and MFA changes are high-risk requests
Password resets, account recovery and changes to multi-factor authentication (MFA) methods look like routine Tier 1 work, but they are sensitive identity functions. Attackers know this. Calling the help desk while posing as an employee and asking for a password reset or a new MFA device is a documented route to account takeover: CISA's advisory on the Scattered Spider group describes exactly this technique. Voice cloning and other deepfake tools make impersonation easier still.
- Verify identity securely. Do not rely on details an attacker can find or guess, such as name, job title, manager or employee number. Use a call-back to a number already on record, confirmation from the user's manager through a known channel, an in-person check, or the verification features of your identity platform.
- Require approval and logging. Record who asked for the change, how identity was verified, who approved it and who carried it out. Notify the user through a separate channel after every reset.
- Add controls for privileged and executive accounts. Administrator, finance and executive accounts, and any change to MFA methods, may need a second approver, a specialist queue and a short delay before the change takes effect.
- Keep secrets out of tickets. Never write passwords, recovery codes, MFA secrets or API keys in ticket comments, emails or attachments. Use self-service reset or a secure one-time channel instead.
For more on how attackers get around MFA, read how attackers get around MFA, and see our guide to deepfakes and identity fraud for voice and video impersonation.
Ticketing and tracking: the minimum viable setup
The foundational rule of a service desk is this: if it is not in the system, it does not exist. Every request needs a ticket. Every ticket needs a state (open, in progress, waiting on user, resolved). Every resolved ticket needs a record of what was done. This is not bureaucracy for its own sake. It is the only way to manage a queue that more than one person is working on, and the only way to identify patterns when the same problem keeps coming back.
"A service desk without a ticketing system is a queue that nobody can see."
For small and medium businesses, the tool choice matters less than the discipline of using it. Freshservice, Zoho Desk, Jira Service Management and Help Scout all work at this scale. Freshservice is built for IT service management, with asset tracking, a self-service portal and automation rules. Zoho Desk integrates with other Zoho products if you already use that ecosystem. Jira Service Management suits teams already on Atlassian. A basic configuration of any of them can be running quickly, but an operational rollout takes longer: you need named owners, permissions for support staff, workflows for incidents and requests, SLA rules, reporting and guidance for users. The timeline depends on the complexity of your environment and the integrations you need, such as your identity directory, device management and monitoring alerts.
The minimum setup you need before going live is: one intake channel (a form or email address that creates tickets automatically), ticket categories that map to your request types, an assignment rule so tickets land with the right person, an identity verification step for account and MFA requests, and a simple SLA clock so you can see what is overdue. Everything else (asset management, automation, satisfaction surveys) can be added once the basics are running smoothly. Trying to configure everything at once is how service desk rollouts stall.
SLAs: what to commit to and what to avoid
A service level agreement (SLA) is a commitment about how quickly support will respond to, update on and resolve different types of requests. SLAs are useful because they set expectations, create accountability, and give you a way to measure whether your service desk is performing. They become a problem when they are set unrealistically, because you then spend more energy managing SLA breaches than fixing problems.
The most common mistake growing businesses make is setting the same SLA for everything. A single "respond within one hour" rule sounds professional, but a network routing problem that needs a qualified engineer will not be fixed in an hour, and a request for a new keyboard does not need a one-hour response. Committing to one timeline for everything creates a list of SLA violations that nobody trusts and everyone ignores.
A more durable approach is to set targets by priority. Priority is driven by impact (how many people, services or processes are affected) and urgency (how quickly the impact grows or how close a deadline is). Then separate the clocks that people often lump together:
- Response time: how quickly a person acknowledges the ticket and starts work (an automated email does not count).
- Restoration target: how quickly the service is restored or a workaround is in place, so users can work again.
- Resolution target: how quickly the underlying fault is fixed and the ticket can be closed.
- Update interval: how often the user or business owner hears about progress while the ticket is open.
- Escalation time: how long a ticket can sit at one level before it moves to a specialist or a manager. For example, a critical incident might go to the IT lead immediately, and a high-priority ticket after one hour without progress.
The table below is an illustrative example only, not a recommended baseline for any particular business size. It assumes support during business hours. If you need 24/7 coverage for critical services, that must be contracted and staffed explicitly, and it usually costs considerably more.
| Priority | Example | Response | Restoration | Resolution | Updates |
|---|---|---|---|---|---|
| P1 Critical | Core system down, many users or a key process stopped | 30 minutes | 4 hours | Root cause tracked as a problem | Every 30 to 60 minutes |
| P2 High | A team or key user blocked, no workaround | 1 hour | 8 business hours | 2 business days | Every 2 to 4 hours |
| P3 Medium | Degraded service, workaround available | 4 business hours | 1 business day | 5 business days | Daily |
| P4 Low | Question, minor issue or standard request | 1 business day | Not applicable | 5 to 10 business days | On status change |
Illustrative example, business hours coverage. Replace every figure with targets that match your own capacity and contracts.
Whatever numbers you choose must match the capacity you have actually staffed or contracted, and should be tested against your real ticket history before you publish them. It is better to set conservative targets and meet them consistently than to set aggressive ones and miss them. If you work with a managed provider, the SLAs and coverage hours in your contract should match what you publish internally. Mismatches create gaps that users always notice.
Avoid SLA targets based on what sounds good rather than what your capacity supports. If your Tier 2 engineer is one person covering multiple responsibilities, a 4-hour restoration target on complex issues will breach constantly. Start with what you can reliably deliver and tighten targets as your capacity grows.
When to bring in a managed service provider
A managed IT service provider (MSP) delivers a defined scope of IT services under contract, usually for a monthly fee. That scope often covers the service desk, proactive monitoring, patch management and sometimes security services. The model can work well because the provider spreads specialist staff across many clients, which gives you cover for holidays, illness and staff turnover that a single internal hire cannot provide.
Whether it is cheaper depends on the details. Compare the total cost and the expected quality of three options: internal, outsourced and hybrid. On the provider side, look at the scope and exclusions, the SLAs and coverage hours, how project work and on-site visits are charged, the contract term, exit costs and the time your own staff will spend managing the supplier. On the internal side, use the fully loaded cost of an employee, not just the salary.
| Cost element | Internal employee | Managed provider (defined scope) |
|---|---|---|
| Core cost | Gross salary | Monthly fee per user or device for the agreed scope |
| Employment costs | Employer National Insurance, pension contributions and benefits | Included in the fee |
| Tools and training | Ticketing, remote support and monitoring licences; certifications | Often included; check which licences you still pay for |
| Cover | Holidays, sickness and vacancies need a backup arrangement | Provided by the team, within the contracted hours |
| Extras | Overtime or on-call allowances | Project work, on-site visits and out-of-scope requests, often charged separately |
| Management time | Line management and recruitment | Supplier management, SLA reviews and invoice checks |
| Exit | Notice period, handover and recruiting a replacement | Notice period, handover of data, documentation and access, transition to a new provider |
Illustrative cost model. Fill it in with your own salary data and supplier quotes; figures vary by region, seniority and scope.
A hybrid model is common: a provider handles the day-to-day queue while someone internal owns priorities, procurement and supplier relationships. To see how support costs fit your overall spending, use our IT budget guide.
Even with a full-service provider, your business stays accountable for IT. Someone internal must own priorities, approve significant changes, manage IT and security risk, review KPIs and hold the supplier to its contract. A support provider resolves tickets; an accountable IT lead or virtual CIO (vCIO) decides what IT should achieve and checks whether the supplier is delivering it. Some providers offer both, but they are different roles and should be named separately in the contract.
Before you outsource or launch a ticketing tool
Check these minimum requirements first. Most cost little to set up and are much harder to add once a service is live.
| Area | Minimum requirement |
|---|---|
| Identity verification | Documented procedure for password resets, account recovery and MFA changes, with stronger checks for privileged and executive accounts |
| Access control | Support staff, internal or external, get only the permissions their role needs; admin rights are separate, logged and reviewed |
| Ticket confidentiality | Restricted categories for HR, legal and security tickets; no passwords, recovery codes or secrets in tickets or attachments |
| Supplier governance | Written scope, named escalation owners on both sides, and an exit plan covering data, documentation and access |
| Major incidents | A separate escalation path and communication plan for outages and security incidents, not just a high-priority ticket |
| Knowledge base | A named owner and review cycle for articles, including the procedures a provider follows for your systems |
| Reporting | Monthly figures for response, restoration, backlog and repeat incidents, reviewed by the internal owner |
| Continuity | Cover for the absence of key people, and a fallback if the provider or the ticketing tool is unavailable |
Privacy matters too. A ticketing tool holds personal data about employees and often customers, along with screenshots, attachments and sometimes remote session recordings. Under UK GDPR you need a lawful basis, sensible retention periods and appropriate access controls for that data. When an external provider handles tickets, assess for each activity whether it acts as your processor or as a controller in its own right, and put the right contract terms in place.
Measuring whether your service desk is working
A service desk you cannot measure is a service desk you cannot improve. Most ticketing tools provide basic reporting by default, and you do not need complex analytics to get useful insight. Start with a small set of metrics and review them monthly. Once those are stable and understood, add more depth. Chasing ten metrics from the start usually means none of them get proper attention.
The metrics that matter most in the early stages are: first response time (how long before a person acknowledges the ticket), time to restore (how long until users can work again), resolution time (from ticket creation to confirmed fix), backlog (how many tickets are open and how old they are), SLA compliance rate and repeat incident rate (how many tickets this month concern a problem that appeared before). The last one is particularly valuable. A high repeat rate tells you that your service desk is fixing symptoms, not causes. Recurring printer issues that appear week after week are a hardware procurement problem, not a support problem.
Beyond the numbers, a brief satisfaction survey sent at ticket closure is worth implementing early. A single question ("Was your issue resolved to your satisfaction?") with a yes or no answer and an optional comment field gives you qualitative signal that metrics alone cannot provide. Users who are dissatisfied despite a ticket being marked resolved are often pointing to something important: the fix was temporary, the communication was poor, or the resolution time was technically within SLA but felt unacceptably slow given the impact. That feedback is valuable if you act on it.
The service desk practice is described in ITIL 4, the IT service management framework now owned by PeopleCert. For an overview of the practice, see PeopleCert's ITIL 4 Practitioner: Service Desk page.