Skip to main content

First Call Resolution

I was recently asked
"Do you have an average for the service desk of first call resolution?  We are trying to set a target for the team and I cannot find any data which gives me any indication what a good target would be." 
First call resolution (sometimes called "first contact resolution" or FCR) is an industry recognized metric for the performance of the Service Desk.   Analysts are measured on their ability to restore service to a user and close an incident during the first call or contact.    

This is a difficult metric to benchmark across all organizations and all incidents.   Factors such as incident complexity, service desk skills and empowerment,  outsourcing and remote control capabilities can influence the ability (or inability) to restore service during the first contact.

While ITIL acknowledges FCR as an important Service Desk metric, it steers clear of offering a target or benchmark.  Industry experts generally accept a FCR range of 65 to 80 %.   Despite this,  I would recommend avoiding a "one size fits all" approach and instead suggest that you map FCR targets to your high level incident models.  Requests and standard changes might be expected to exceed 90% FCR.   Major incidents would likely have a very low FCR target until a trusted workaround is identified and deployed.  In this way, the message behind the metric is situational and clarifies opportunities for specific improvements.

There is a fine line between creating too many or too few FCR goals.  Too few and you may hold the Service Desk up to an impossible, generic goal.  Too many and the metrics may no longer be measurable, meaningful and manageable.   The "right" target will depend on your available resources (technical, financial, and human) as well as what you will do with the data once it is benchmarked.   

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem