top of page

5 Important IT Service Desk Metrics

1. Volume of new tickets

The number of new tickets that the IT service desk has coming in per day, week, or month is important because it can help you to identify whether you have enough resource to cover demand.

In addition to this, if you see a considerable rise in new tickets – perhaps against a particular IT service – it can highlight that there’s potentially a bigger problem brewing that needs prompt resolution.

2. Volume of resolved tickets

If your IT service desk is understaffed, or has process gaps, then you might find that your resolved tickets fall far short of the number of new tickets coming in. If this is the case, then this needs to be highlighted immediately because these unresolved tickets will create a backlog which means an increased workload for your agents but, more importantly, it will probably be adversely affecting employee or business-level performance (due to the delay in resolutions).

A thriving IT support organization will find that its new and resolved ticket numbers align. However, if this suddenly changes – and resolved ticket volumes drop – then you should investigate whether this is a staffing, training, or broken process issue.

3. The size of the ticket backlog

The fewer tickets you have in your backlog queue the better. All IT service desks might wish that their backlog queue could remain at zero forever but, alas, IT is a complex beast and not all tickets will be closed down neatly within their service level agreement (SLA) targets. It’s vital to report on your backlog queue because it only gets harder to manage when you ignore it.

One common practice for IT service desks is bringing in agents to work overtime to clear a backlog queue. However, this is merely a short-term solution and is not effective; without identifying the cause and fixing the underlying problem that backlog queue is only going to grow again.

Overtime to battle ticket queues is also potentially a quickfire way to demotivate your IT service desk team. Instead report on this and dig deeper if you suspect a problem – training, too many incoming tickets (versus available staff), and process problems can all be culprits of a growing ticket backlog.

4. The first response time

The first response time is the time between the original ticket being created and the first notification to the customer that something is happening with that ticket. If your first-response SLAs are public, then this particular metric is certainly one you need to watch. And if you make your customers wait too long before responding to their ticket, then their satisfaction levels are likely going to drop.

If your organization is struggling with its first response time, consider automation which can be used to pick up and assign tickets to the correct department. At the same time a notification is triggered to the customer to advise them the ticket has been logged and progressed. It might feel like a cheat but it’s also going to show the customer that their ticket is being progressed (plus achieving the overall SLA is still important).

5. The level of customer satisfaction (CSAT)

This is arguably the most important metric for many IT service desks given that they exist to serve their customers. The service desk is also the face of IT and sets standards for the whole IT department; thus, if the IT service desk appears to be failing, the reputation of IT as a whole can be damaged.

Regularly report on your CSAT scores and ensure that you use trending reports to check whether you’re improving over time. Or that CSAT levels are in a downward trend despite targets being met – which will allow corrective action to be taken before CSAT scores reach an unacceptable level.

Automation, self-service portals, knowledge documentation, and regular communication can all help to increase customer satisfaction. And if you’re not sure what your customers like and don’t like about IT support within the organization, ask!

There are many benefits to reporting for IT service desks, but the benefits can only be reaped when you’re clear on why the reports are needed. And although reporting takes a lot of effort, which you may sometimes feel could be better spent dealing with your escalations, it will definitely help to improve your service desk, and IT department, over time. So, define your goals and report on what your stakeholders need to know for an improved reporting experience and a better perception of IT support and its results.

10 views0 comments


bottom of page