Skip to main content

Should Service Requests be Included in First Call Resolution metrics?

I recently had a question regarding the inclusion of Service Requests into metrics for First Call Resolution. As always, the answer is “it depends”!

ITIL now treats Service Requests and Incidents as two different processes – Service Request Fulfillment and Incident Management. Both are generally logged into the same tool and owned by the Service Desk. They are also measured by their own key performance indicators and metrics. ITIL does not consider first call resolution as a process metric - it is more of a service desk performance measurement.

First call resolution historically helps measure the handling of incidents by the Service Desk. The definition of an incident is usually pretty clear. However, since the definition of a service request can vary greatly from organization to organization, the value of including requests in incident metrics may also vary.

If your definition of a service request includes pre-authorization and funding, then the Service Desk’s ability to fulfill the request during the first call likely falls into the same percentage as incidents. However, if service requests may require an additional layer of management approval or the service desk does not have the skills and authority to fulfill the requests, then it is unfair to hold them to a first call resolution metric that is unachievable. What do you consider to be the “first call”?

I would also consider your assignment of urgency, impact and priority when deciding whether to include service requests in your statistics. Are you using the same standard for determining the priority of service requests and incidents? Should an analyst spend more call time fulfilling a service request in order to meet the target while a user with a potentially higher priority incident is in queue?

HDI’s recently published results of its Support Center Practice survey, including some statistics about first call resolution. While most respondents targeted over 70% first call resolution, only about 40% actually achieved that goal. Given that, I would recommend reviewing all of the criteria used for this important measurement.


mozrat said…
Good post.

I definitely agree that the processes are different, especially when you consider the outcomes

* Incident: Restoration of service
* Service Request: Fulfilment of a request, normally an addition of service.

I think the idea that a Service Request is a fulfilment of a standard change is close enough to be useful too.

I also agree that the same group of people should handle both processes (the Service desk) so it comes down to tooling to make sure that this is easy and intuitive for operators to use.

Another point would be prioritisation and SLAs. I wouldn't normally expect to manually prioritise a Service Request, we've advertised that fulfilling this type of request takes a certain amount of time, so it makes a priority kind of redundant.

Incident Management tends to base SLA on priorities, whereas the Request Fulfilment process is a lot more complicated. Requesting a new user account seems to be quite a quick task, whereas requesting a new laptop would involve hardware delivery times, engineering effort to build and configure etc.

Lastly - you didn't mention automation in your post. Incidents are hard to automate (the resolution). But Request Fulfilment is a great opportunity to break out the workflows and try and make the process repeatable.

Thanks Professor!

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 policies (r…

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 the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…