Request a quote
Emergency SectorsCareers About us Blog Get in touch
Headset on a desk in front of a monitor showing chat windows

An IT helpdesk ticketing system: buy your own or use your provider’s

Choosing an IT helpdesk ticketing system usually starts with comparing brands, and that is rarely where the difference lies. What decides whether tickets are resolved on time is how the system is configured: which categories, which priorities, when the clock runs. And once you outsource the service desk, a question appears that nobody asks up front: whose system is it, and whose data is in it?

7 min read Written by the ITproposal team
Short answer

Almost every ticketing tool can do what an IT service desk needs. The difference is configuration: a short list of categories, priority derived from impact and urgency, and an SLA clock that pauses while you wait for the user.

If you outsource the service desk, using the provider’s system is often quickest. Then agree in writing that the tickets, the knowledge base and the link to your assets belong to you.

Agree the exit export on the day you start: which fields, in what format, with attachments and history, and within what period.

What an IT helpdesk ticketing system must do

A ticketing system for IT is not the same as a customer service tool, even though they look alike and some vendors sell both. The requester is a colleague, the ticket concerns a device or an account, and the agreement on how fast it is picked up sits in an SLA. That gives you a checklist for any product:

  • Channels. Email, a portal, phone and often Teams or chat, all landing as tickets in one place. A request that only lives in someone’s inbox does not exist for reporting.
  • Categories and routing. A ticket reaches the right team automatically, based on what the user picks or what the email says.
  • Priority and an SLA clock. The system works out the priority, sets response and resolution targets, and pauses the clock when the requester needs to reply. Without the pause you measure your own waiting time.
  • A knowledge base. Fixes your colleagues can use themselves, and that the team finds again next time.
  • Asset links. The ticket is attached to the laptop, printer or licence it concerns. Only then do you see the same device coming back every month.
  • Reporting. Volumes per category, resolution times, SLA performance and recurring issues, without anyone maintaining a spreadsheet.
  • Permissions and an audit trail. Who may see which ticket and who changed what. Tickets hold personal data, and sometimes passwords that should never be there.

You will see the term ITSM, IT service management. Products that use it usually add change management, problem management and a configuration database. For a small organisation that is more than needed; for a mid-sized one with its own IT team it is often exactly what is missing.

Why configuration matters more than the brand

The well-known products, from ServiceNow and Jira Service Management to Freshservice, Zendesk and TOPdesk, can all do the list above, in different ways and at different scales. We do not rank them. What we do see in practice is two organisations on the same system with completely different results.

One has forty categories of which five are used, a priority the requester chooses (so it is always “high”), and an SLA clock that keeps running while someone is on holiday. The other has eight categories, a priority that follows from two questions, and a monthly report somebody actually reads. The second one works, and the brand has nothing to do with it.

So the question is not “which ticketing software is best” but “who configures it and keeps it tidy”. A system without an owner fills up within a year with categories nobody understands any more.

Categories: few, and from the requester’s point of view

Categories have two jobs: getting the ticket to the right person, and showing afterwards where the work comes from. You need fewer of them than you think.

  • Start with six to ten top-level categories in the user’s language: devices, accounts and access, email and Microsoft 365, printing, network and wi-fi, phones, business applications, requests.
  • One level below at most. Nobody picks correctly three levels deep, and then your reporting stops being right.
  • Separate incidents from requests. “My laptop won’t start” and “I need a laptop for a new starter” call for different handling and a different clock.
  • Watch “other”. If more than a small share ends up there, a category is missing or one is too vague.

After three months, check which categories stay empty and which are too big. A category list is only good after its first review.

Setting up priority and the SLA clock

Do not let the requester choose the priority. Derive it from two questions the system asks or the service desk fills in:

  • Impact: does it affect one person, a department or the whole organisation?
  • Urgency: can work continue, continue with difficulty, or has it stopped?

The combination gives a priority from one to four, and each priority carries a response and resolution target from your SLA. How to pick targets you can actually hit is covered in our article on SLAs you can actually meet.

Three settings decide whether the clock measures or misleads:

  • Calendar. Does the clock run in office hours only, or evenings and weekends too? It must match the contract.
  • Pause. On “awaiting user” or “awaiting supplier” the clock stops, and the system records for how long.
  • Escalation. A ticket nearing its target goes to a second person automatically. Not as a penalty, but so it does not sit there.

Buy your own ticketing system or use your provider’s

There are two routes. You take your own ticketing system, in your name, used by your own IT staff and perhaps an outside party. Or you outsource the service desk and work in the provider’s system, with a portal and reporting for your organisation.

Using the provider’s system fits when you have no IT department of your own, or when the service desk handles almost every ticket. There is nothing to configure, license or maintain, and the provider has already tuned it to the way it works.

Your own system fits when several parties handle tickets (an in-house administrator, an external service desk, an application supplier), when other departments such as facilities or HR work in it too, or when you want the data entirely in your own hands for another reason. The provider then works in your system, and it must be able and willing to do so.

One question often settles it: who still needs access in three years if the current provider has gone? If the answer is “only the successor”, using the provider’s tool with a solid export clause is enough. If the answer is “we do”, the system belongs with you.

What changes when you outsource the service desk

After a few years, a provider’s system holds a lot of your knowledge: which devices keep coming back, which fix worked, which user was given which rights and why. That is valuable, and it sits somewhere that is not yours. So agree up front:

  • Data ownership. Tickets, attachments, knowledge articles and asset links belong to your organisation, even when they live in the provider’s system.
  • Visibility during the contract. A portal showing every ticket, not just a monthly report with totals.
  • The exit export. Which fields, in what format (a file another system can import, or via an API), with full history and attachments, and within what period after notice.
  • The assets. If tickets hang off devices, make sure the asset register itself comes with you. A ticket history without the devices it refers to is a list of loose sentences.
  • Personal data. Tickets contain names, email addresses and sometimes more. The provider is then a processor under UK GDPR or the GDPR, which calls for a data processing agreement covering retention and deletion.

If the provider works in your own system, it is the other way round: make sure its accounts are named, that you can disable them yourself when it leaves, and that its staff see no more than they need.

How to choose an IT helpdesk ticketing system

If you are choosing your own, skip the vendor’s demo data and run a trial with twenty real tickets from last month. You see straight away how many clicks an ordinary ticket takes and whether your categories fit.

Then ask about what the demo leaves out:

  • How do you export every ticket with history and attachments, and how much work is that?
  • Is there an API to connect your asset management, identity management and Microsoft 365?
  • Can users sign in with their existing account (single sign-on)?
  • Where is the data held, and who at the vendor can access it?
  • What happens to the data when you cancel, and how soon is it deleted?

The system also measures how many tickets staff handle and how fast. If you intend to use that to assess people, tell them and set the rules before you start, not afterwards.

Where our work stops

What we do. We provide the service desk, and that includes a ticketing system set up along the lines above: short categories, priority from impact and urgency, an SLA clock that pauses, a knowledge base and links to assets. Whether that happens in our system or yours is agreed before we start, including the exit export.

What we do not do. We do not make ticketing software and we are not an independent adviser comparing products: as a service desk provider we have an interest, and you are right to weigh that. Nor do we give a legal opinion on the data processing agreement or the exit clause; have those checked by a lawyer or your data protection officer.

Frequently asked

Questions we get about this

The five that come up most.

What is an IT helpdesk ticketing system?

It records every incident or request as a ticket, with a requester, a category, a priority and an owner. Nothing gets lost in an inbox, a clock runs against the agreed response and resolution targets, and afterwards you can see where the work comes from.

What features does IT ticketing software need?

Intake by email, portal, phone and chat, automatic categorisation and routing, priority and an SLA clock that pauses while you wait for the user, a knowledge base, links between tickets and devices or licences, and reporting without spreadsheets. Permissions and an audit trail belong on the list too.

Do we need our own ticketing system if we outsource the service desk?

Not necessarily. Using the provider’s system is often quickest, as long as you agree that the data is yours, that you can see every ticket and that there is an export at exit. Your own system fits better when several parties or departments work in it.

How many categories should a helpdesk ticketing system have?

Start with six to ten top-level categories in the user’s language, with one level below at most, and keep incidents separate from requests. After three months, check which stay empty and how much lands in “other”; that tells you what to merge or add.

Which ticketing system do you recommend?

We do not rank products, and as a service desk provider we are not an independent party either. Nearly every well-known product can do what an IT service desk needs. What makes the difference is the configuration and who maintains it, so test a product with twenty real tickets rather than a demo.

Related services

Further reading

What the ticketing system connects to.

Brands

The brands above, one page each

What the brand makes, which lines we supply and what we do around it.

Shall we hold your ticketing setup up against your tickets?

Send us your current categories and a month of tickets. We will tell you what we would change in the configuration, and what the agreement on data and export should look like if you outsource the service desk.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call