For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
My organisation considers that an incident is resolved
as soon as the fix is delivered?
12%
[ 1 ]
only once the fix is confirmed as successful?
87%
[ 7 ]
other?
0%
[ 0 ]
Total Votes : 8
Author
Message
Peana Newbie
Joined: Aug 12, 2009 Posts: 3
Posted: Thu Aug 27, 2009 7:45 pm Post subject: Incident resolution question
Hi,
In my organisation we try to generally follow the principle of not resolving an incident until resolution has been confirmed e.g. it remains open until the user confirms that the fix applied was successful. However, most of the third parties we deal with will resolve an incident as soon as they have delivered a fix - if necessary the call will be reopened. I therefore wondered how most other organisations operate?
The business like our current approach, but I feel we may not be doing ourselves any favours.
I've tried to add a poll - not done this before, so apologies if it is wrong! I'd be interested to find out how other companies deal with this.
In my opinion It's better to confirm with the customer before closing the ticket. As the solution you may provide might not fix the issue and that can cause the user to call over and over again. For example a customer calls in several times for the same issue. Where every time one of the staff members provides a different solution assuming that it will fix the issue but it doesnt. Put your self in that user shoes, you wouldnt be happy about the service.
Why let the user call in many times while you can prevent this, by asking a small question that well deliver end user satisfaction.
Regards,
A
Last edited by thechosenone69 on Thu Aug 27, 2009 11:44 pm; edited 2 times in total
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Thu Aug 27, 2009 11:21 pm Post subject:
Peana,
thechosenone69 is perfectly correct. Pay attention to the distinction between the term "resolved" and the term "closed"
You should never close an incident until resolution has been confirmed and this will often, but possibly not always, require direct consultation with the user(s) involved. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
I agree that it is much better for customer satisfaction to confirm resolution. I think we might need to persuade our third parties to see things in the same way!
Good point about resolved and closed - I've tried to explain to colleagues that there is a difference on many occassions, but it is still a cause of confusion for some. Although, I must admit that I find myself saying closed sometimes when I mean resolved.
No Problem, I would also like to suggest suggest that when dealing with 3rd party suppliers, let them adhere to your own company policies not necessarly to just resolving incidents. It can be for Changes, releases, adding new assets etc.. this will make your life easier
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum