We are often asked to conduct small workshops for IT organizations to help Service Desk agents to better understand the differences between Incidents and Service Requests. In most cases, once the differences are explained and a few example are provided, people start to get it.
However, there are some instances when simply looking at a list of examples is not an effective approach to the correct classification of Incidents. This is primarily due to the fact that no list can predict every possible user call to the service desk.
While it may be possible to capture, record and classify the most frequent system breakdowns and user requests, the possiblities are infinite. If there were such a rule, we could simply program a computer to do the work and save a lot of money.
Until then, Service Desk agents will have to use their knowledge of IT and ITIL to make the determination.
For example, sometimes the difference between an Incident and a Service Request is determined by the details. An error downloading software to a user workstation can be attributed to several different causes.
The user could lack the appropriate knowledge or skills (Service Request)or, the error could be related to a fault in the infrastructure (Incident). By asking follow-up questions, the Service Desk agent, should be able to determine to most appropriate classification and course of action.
The point, is that in many situations, it is "why" rather than "what" the user is unable to do that determines whether the ticket should be classified as an Incident or as a Service Request.
Understanding this helps the IT organization to produce more accurate reports about the health of the inftastructure. These reports are also useful in identifying areas for targeted improvement and user training opportunities.
This post was contributed by Danielle Baker, Managing Director of Red Engine Consulting. Danielle is a certified V3 Expert and has extensive experience in ITSM, Organizational Change and Project Management.