By ITIL® from Experience©
A lot of IT professionals at one point or another experienced the situation when a user needed something immediately only to discover that the user was nowhere to be found when additional information was required or to confirm that the issue was resolved.
One method to help users remember that they have outstanding business with IT is to send them an email notification when the Incident or Service Request is opened with the Service Desk. Many users keep this email in their inbox as a reminder until the issue or request is closed.
To avoid breaching, implement in the ITSM Tool an action/status to indicate that the next step is with the user, which also stops the SLA clock. For examples this action could be called: Info Requested, User Validation Required, Waiting User Response. This enables IT to focus on other requests and avoid breaching the SLA.
An effective method to re-establish communication with the use is for the Service Desk Manager to contact the user’s manager when the issue prevents the user from working. Although this method usually works well, many users will not appreciate having their managers contacted. Therefore this method should be reserved for cases when the individual is frequently unresponsive or is a difficult user.
Also, don't forget to communicate this policy1 to customers and users. One of the first steps should be a discussion with the Customer during an SLA review meeting. Then the policy can be added to the SLA.
Stopping the SLA clock is not bad customer service, it is efficient service delivery as it enables IT to focus its effort on helping users instead of chasing them.
- How to automate the chasing of users to confirm that their incident or service request can be closed
- Should we stop the clock to avoid breaching the SLA
- How to close incidents and request for service when users are not getting back to us
- Do we need an SLA for VIPs
From Around the Web:
Copyright 2012, 2013 - ITIL® from Experience - D.Matte