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.   


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 the

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th