Skip to main content

First Call Resolution (FCR) According to ITIL and General Best Practice

A reader recently asked me to comment on what a First Call Resolution (FCR) is according to ITIL and general best practice. When collecting metrics you want to be sure that the reporting brings good business value. From a reporting perspective it might serve well to report incidents and requests separately.    

Each organization will have to have policies for how the metrics are reported based on business value.  One option is to have a policy that will report on “Service Requests” separate from “Incidents”.  If we do not separate the logging and reporting for these very distinct processes the combined metrics and reporting might not be something that is meaningful or that could be acted upon correctly.  You could end up with a very high FCR rate but your Mean Time To Restore Service metric could be breaching the SLA.  Therefore, the question is not whether the call was resolved at first line, but rather was it a FCR for an Incident or Request/Standard Service?  Report upon them separately.

If you do not currently have the option to separate the records and reports for Incidents and Service Requests and you want to capture the FCR for “Incidents ONLY” then you might have a category or classification for incidents and a policy that states FCR reporting includes only those incidents that are IT related, outages, faults, break fix type of situations.
  
A “Service Request” should have a high if not a 100% first call resolution rate because a “Service Request” is a request from an end user for information, for comments or perhaps to fulfill a “Standard Service”.  A Standard Service has a Standard Operating Procedure/model that is followed to fulfill the request. 

Sometimes we also will run “Standard Changes” through the function of the Service Desk as though it were a simple “Service Request”.  A Standard Change is a pre-authorized, pre-approved, low risk and repeatable type of change.  A “Password Reset” would be an example of a very basic “Standard Change”.  It is very helpful to report upon these “Standard Changes” separate from Incidents.

The real key is to record and report upon Incidents and Requests separately to get the type of metrics that are meaningful to your business.

If you are engaged in these activities there is a lot of information and training available.  ITIL Foundation training is a great place to start and if you have that, there is a class that goes into great detail for the clarification and delineation for all of the “Operational” processes.  That course is called “Operational Support and Analysis”.   Take a look at the resources and training provided here and let me know if you have further questions.   http://www.itsmacademy.com

Comments

Popular posts from this blog

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

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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