Skip to main content

Help desk support services: a buyer’s decision guide

A practical guide to support intake, ticket ownership, escalation, reporting, onboarding and access controls.

Abstract 3D render of three clear glass steps rising to a tall cobalt blue glass block

A practical guide to support intake, ticket ownership, escalation, reporting, onboarding and access controls.


A help desk is the first point of contact for the people who use your technology. It takes requests and incidents, sorts them, solves what it can and passes on the rest. Choosing one well means deciding what it covers, how work is prioritised and escalated, what you will see in reports and how the service starts. This guide sets those decisions out in the order you will meet them, so that you can compare providers on the same terms. It is written for the person who will brief the provider and later judge the result.


Related: managed IT services and outsourced help desk.

What a help desk covers, and where managed IT begins

A help desk deals with the day-to-day questions and faults of the people who use your technology: a password reset, access to shared files, a laptop that will not connect, a request for new software, an email that behaves oddly. Its job is to receive, route and resolve those requests, and to keep the requester informed.


Managed IT is wider. It also covers the work behind the scenes, such as patching, monitoring, backups, the lifecycle of users and devices, and planning, often with the help desk as its front door. A help desk on its own can therefore be a sensible purchase when other people already look after the environment, and a poor one when nobody does. If you want to share the work with your own team, our guide to co-managed, managed and break-fix IT sets out how the models differ.

Design the request journey

Choose clear channels for incidents and service requests, then define the information needed to route them: affected user, system, business impact, urgency and safe contact details. Confirm that users receive a reference and know how to add context. Avoid asking people to send passwords or sensitive data in ordinary tickets.


Decide at the same time which requests the help desk may complete itself and which need your approval. A password reset can usually be done on the spot once the person’s identity is checked; access to finance records, or removing a leaver’s accounts, normally needs a named approver on your side. Write the approvers down, with a deputy for each, so that a request does not wait because one person is away.


Finally, agree how people will reach the desk. One form or mailbox is easier to manage than several informal routes, and an urgent route for outages is worth defining separately, so that nobody uses the ordinary queue for a problem that stops the office.

Ticket categories and priorities

Categories say what a ticket is about; priorities say how soon it matters. Keep both lists short, because long lists tend to be applied inconsistently. A workable set of categories separates incidents (something that worked has stopped), service requests (something new or a routine change), access and account changes, and questions that need advice rather than a fix.


Priority usually combines impact and urgency:


  • Critical: many people cannot work, or a security incident is suspected;
  • High: one person or team is blocked and has no workaround;
  • Normal: work continues with a workaround, or the request is routine;
  • Low: a convenience, a cosmetic fault or a question with no deadline.

Ask the provider who sets the priority, whether the requester can challenge it, and how a ticket is re-rated when new facts appear. Priority should describe business impact, not how loudly the request was made. After a few months, compare the categories with real tickets; that can show which ones to merge.

Clarify ownership and escalation

Document who owns a ticket at each stage, when it moves to a specialist, and who updates the requester. Distinguish acknowledgement, first response and resolution; they measure different events. Set escalation triggers around business impact, security concerns, blocked work and elapsed time, with an accountable receiving team.


Help desks commonly work in levels, and it helps to know what each is for:


  • Level 0, self-service: guides and simple forms the user can follow alone;
  • Level 1, first line: logs, classifies and resolves common requests from documented steps;
  • Level 2, specialist: deeper diagnosis of accounts, devices, software and networks;
  • Level 3, engineering or supplier: changes to the environment and faults that need the software maker.

Ask for the hand-off rules: what the first line must try before escalating, what travels with the ticket, and who tells the requester that ownership has changed. Nobody should have to explain the problem twice.

Office desk with a monitor, a plant and a notepad, and a headset resting on an empty chair
A help desk works best with one queue and clear tiers

Self-service and a knowledge base

Self-service removes the simplest tickets from the queue, but only when the material is accurate and easy to find. A knowledge base earns its place when it holds short articles for the questions people ask repeatedly: connecting to Wi-Fi, setting up multi-factor sign-in, requesting access, using a shared mailbox, what to do after losing a device.


Ask who writes and maintains those articles. A sensible pattern is that the help desk drafts one whenever the same question returns several times, a named owner reviews it, and out-of-date articles are retired. Check that people can reach the knowledge base from a phone when their computer is the problem, and that sensitive internal instructions sit behind sign-in.


A knowledge base also protects you when people change. Procedures held in one technician’s memory leave with them; procedures in a shared library stay.

Tools a help desk needs

Tools matter less than how they are used, but a few capabilities are worth checking. Ask about them as capabilities, not as product names:


  • a ticketing system that records every request with its owner, status and time stamps, and that you can export;
  • a portal, mailbox or chat route that people will actually use;
  • remote support that asks the user’s permission and leaves a record of the session;
  • an inventory of devices, accounts and software that the desk can search while it works on a ticket;
  • a knowledge base linked to tickets;
  • reports you can read without help.

Ask who owns the data held in the ticketing system, whether you can take your history with you if you change provider, and how access for the provider’s staff is approved, logged and removed. Those answers matter more than any feature list, and a short test with your own sample tickets shows more than a brochure. If you move provider, see what to collect if you change provider.

Make reporting comparable

Define each metric before reviewing a dashboard. A ticket count, backlog age, reopen rate and time to resolution answer different questions. Segment by priority and request type, and read the figures with service hours and ticket scope in view. Use trends to find recurring causes rather than treating one number as a complete measure of quality.


Agree a regular review, monthly is common for small organisations, and quarterly can suit once things are stable. A useful agenda is short: ticket volume and mix, the oldest open items, repeat issues and their causes, changes of scope, and actions from last time with owners and dates. Ask for the underlying ticket list on request so that you can sample it yourself.


Treat reviews as a place to remove causes, not to defend numbers. If the same printer, permission or application appears every month, the fix may belong in a small project rather than in the queue.

Help desk support lifecycle
Support lifecycle overview
Read the steps as text

Intake and triage, resolve at tier, escalate if needed, verify and close, report and improve

Prepare onboarding and controls

Inventory supported users and systems, document known issues, agree access approval and removal, and test the routing path before transition. Establish a review cadence for unresolved tickets, knowledge articles and scope changes. Agree early how the service is charged; our guide to managed IT pricing models explains the common structures. Keep administrative credentials out of shared notes and use controlled access procedures. For joiner and leaver steps, see our IT onboarding and offboarding checklist.


Before the switch, run a short pilot with a small group, so that routing and hand-offs are tested on real tickets, and tell people where to ask for help and what to include. After the transition, keep a short stabilisation period in which you read every escalation and every complaint. Early gaps are often missing documentation or unclear approvers, and both are quick to fix when someone is looking for them.

Who answers your users: comparing support models

The right model depends on who already looks after your environment. The table compares four common arrangements; our guide to outsourcing versus in-house IT goes deeper into that decision.


ModelWho answers usersFits whenWatch for
In-house teamYour own staffYou have enough people to cover absences and specialist skillsSingle points of failure when someone is away or leaves
Outsourced help deskA provider’s first line, escalating to your teamYour team can fix problems but should not take every requestClear hand-offs and who approves access
Co-managed ITShared between provider and your team by agreed rulesYou have some IT staff and want extra capacity or skillsA written split of responsibilities, so nothing falls between the two
Managed ITThe provider, with the help desk as the front doorYou have no in-house IT, or it is stretchedScope, escalation to your management and how changes are approved

Abstract 3D render of a stack of clear glass cards with one cobalt card lifted from the pile
Triage picks the next request by impact and urgency

Questions to ask a provider

Put the same questions to every provider so that the answers can be compared:


  • Which requests does the first line resolve, and which does it pass on?
  • Who sets priority, and how is it changed?
  • What counts as first response, and what counts as resolution?
  • Which languages and hours does support cover, and what happens outside them?
  • Who writes the knowledge base, and who owns it?
  • What will the monthly report show, and who attends the review?
  • How is access granted, recorded and removed?
  • Can you export your ticket history if you leave?
  • What lies outside the agreed scope, and how are extra requests handled?

BlueNova IT supports English and Spanish. If your people work in other languages, our guide to multilingual IT support covers what to check.

A decision checklist

Before you choose, check that you can answer yes to each of these:


  • You know which systems, sites and groups of users the help desk must support.
  • You have named approvers, with deputies, for access and purchases.
  • You have agreed the priority levels and what each one means for your organisation.
  • Escalation routes are written down, including who receives them on your side.
  • First response and resolution are defined separately.
  • Support languages and hours match when your people actually work.
  • You know what the monthly report contains and who reads it.
  • You have a plan for the first weeks, including a pilot and a review.
  • Your ticket history and knowledge base can leave with you.

If several answers are no, settle those first. They are easier to agree before a transition than during one, and a provider who asks about them is showing the right instincts.

Frequently asked questions

What should a support request include?
A concise description, affected service, impact, urgency, useful error details and a safe way to follow up. Do not include passwords or unnecessary personal data.
What is the difference between first response and resolution?
First response records an initial acknowledgement or action. Resolution records when the issue is considered addressed under the agreed process. Define both consistently.
When should a ticket be escalated?
Escalate when impact, security risk, specialist access or elapsed time crosses an agreed trigger, and transfer ownership with the evidence already collected.
Which help desk metrics are useful?
Backlog age, ticket volume by type, reopen rate and response or resolution times can help when definitions and scope are consistent.
How can onboarding reduce disruption?
Use an agreed inventory, knowledge transfer, access approvals, routing rehearsal, named owners and a process for open issues.
What is the difference between a help desk and managed IT services?
A help desk is the front door for requests and incidents: it receives, sorts, resolves or escalates them. Managed IT also covers the ongoing work behind the scenes, such as patching, monitoring, backups and planning. Many managed IT arrangements include a help desk, but a help desk on its own does not look after the environment itself, so check who does.
What priority levels should a help desk use?
Four levels are a common choice: critical, high, normal and low, defined by business impact and by whether a workaround exists. Write down what each level means for your organisation, who can change it and what is expected at each one. Longer lists are harder to apply consistently.
Does a small business need a knowledge base?
It is not essential on day one, but it becomes useful once the same questions keep returning. Start with a handful of short articles for the most common requests, give each an owner and a review date, and let the help desk add new ones as patterns appear.
Which languages and hours does BlueNova IT support cover?
Support is available in English and Spanish, Monday to Friday, 09:00–⁠18:00 CET/CEST. BlueNova IT works mainly with small and midsize companies in Europe, often with distributed or multi-site teams; on-site work is confirmed per project.

Let’s talk about your IT.

Tell us what your team needs today and what you would like to improve.