State of the Service Desk Part 3: Metrics for Service Desk Management

By Dion Williams
CEO & Founder, Servicely · 30+ years in enterprise ITSM
July 19, 2021

This blog series explores the topics discussed in servicely.ai's State of the Service Desk report. More details at the bottom of this blog article.

The following metrics were most commonly mentioned as important to service desk performance:

Customer

  • Net Promoter Score (NPS) (typically used in customer-facing interactions)
  • Customer Satisfaction Score (CSAT) (typically used in employee-facing interactions)

Call Handling

  • First call resolution (FCR)
  • Call handling time (CHT)
  • Call wait time (CWT)
  • Abandonment
  • Outstanding tickets daily, weekly, monthly

Service Level Agreements (SLAs)

  • Tickets currently in breach of SLAs
  • Daily, Weekly, Monthly SLA violations

Capacity

  • Calls per hour, day, week
  • Employees per support analyst
  • Cost per ticket
  • Hours’ work logged per employee per day
  • Recruitment pipeline

There was a range of maturity levels around metrics and SLAs.

At the lower end, one organization was bringing the service desk in house again and had no service levels in place yet. Another organization had only just brought in SLAs in the last six months as part of a service management professionalization program.

At the other end of the scale was a managed service provider who had more maturity and sophistication and was offering different SLAs for different customers, and even different SLAs for different pieces of equipment.

For those with SLAs, some wanted to improve their service levels while others were happy if they could maintain them while they added new services. Generally speaking, the organizations at the lower end of the maturity spectrum saw the most opportunity for improvement in service levels.

Next - Part 4: Increase in Demand

In late 2020 servicely.ai conducted 23 research interviews with service desk executives, managers and practitioners, to explore the State of the Service Desk in the post-COVID19 world.

The interview results were synthesised into a report that covers the following topics:

  1. Executive Summary
  2. Introduction
  3. Service Desk Metrics
  4. Increase in Demand
  5. Transformation, Consolidation and Integration
  6. Shift Left
  7. Automation and Orchestration
  8. Knowledge Management
  9. People Management
  10. Support Channels
  11. Data Quality
  12. Tools
  13. Conclusion

This blog series will serialise the topics listed above. If you would like to discuss any of these topics please get in touch with us here.

Share this post
Monthly Ticket Volume Annual Tickets Cost at $22/ticket
500 6,000 $132,000
1,000 12,000 $264,000
2,500 30,000 $660,000
5,000 60,000 $1,320,000
Scenario 1,000 tickets/month Annual cost
Before AI (all manual at $22) $22,000/mo $264,000
After AI (60% deflected at $3, 40% assisted at $12) $6,600/mo $79,200
Annual savings on ticket handling alone $184,800

Want to run these numbers against your own service desk?

We'll walk through the ROI calculation with you in a 30-minute session — using your actual ticket volume, team size, and current tool costs. No slides. Just your numbers.

Book a personalised ROI session with Servicely
1Annual ticket handling cost (monthly volume × 12 × $22 per ticket)
2Current platform licensing + implementation overhead
3Analyst capacity lost to low-value work (hours × analyst fully-loaded cost)
4Estimated employee lost productivity from MTTR (avg resolution time × impacted users × avg. hourly cost)
1New platform licensing (compare against current — Servicely typically lands at a fraction of ServiceNow's cost)
2Reduced ticket handling (60% of volume deflected; remainder at reduced cost per ticket)
3Analyst capacity recovered (40% productivity gain applied to current team cost)
4MTTR-related productivity recovery (300% faster resolution applied to your incident frequency)

Stay Updated with Servicely

Sign up for our mailing list to stay in the loop with Servicely.

Sign Up
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.