{"id":5763,"date":"2016-03-22T21:42:39","date_gmt":"2016-03-22T21:42:39","guid":{"rendered":"https:\/\/multiacademstg.wpengine.com\/20000academy\/?p=5763"},"modified":"2025-07-07T09:38:14","modified_gmt":"2025-07-07T09:38:14","slug":"itil-incident-management-how-does-it-influence-customer-satisfaction","status":"publish","type":"post","link":"https:\/\/advisera.com\/20000academy\/blog\/2016\/03\/22\/itil-incident-management-how-does-it-influence-customer-satisfaction\/","title":{"rendered":"ITIL Incident Management \u2013 How does it influence customer satisfaction?"},"content":{"rendered":"<p>Satisfied customer will pay your bills. Unsatisfied customers \u2013 well, maybe they pay the next one, but certainly not for the long term. With that act (not paying the bill, i.e., not using your services anymore), the customer wants to say something \u2013 he is not satisfied either with your service or the way you support it; i.e., there is a lack of customer satisfaction. And that\u2019s something that should bother every organization.<\/p>\n<p>There are many points where low quality can be \u201cbuilt\u201d into the service, e.g., low quality during design of the service or while building a service. But, low quality will be highly visible once the service enters the live environment. It\u2019s hard (and expensive) to influence customers\u2019 dissatisfaction with a low-quality service. But, there is one more source of customers\u2019 dissatisfaction with operational services \u2013 the organization\u2019s performance during <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=resolution-and-fulfillment-processes&amp;doc=incident-record\" target=\"_blank\" rel=\"noopener noreferrer\">incidents<\/a>.<\/p>\n<h2>What\u2019s the importance?<\/h2>\n<p>Maybe your organization has the best IT service strategist, or system admin, or developer\u2026 That\u2019s good for the organization, but customers will not see that. What do they see? They see your Service Desk and how well you solve incidents that happen on the services they use. And that\u2019s exactly how they will judge you.<\/p>\n<p>I have witnessed a situation where one of my colleagues explained why she avoids opening incident tickets \u2013 there were a few older tickets that were never resolved. The consequence is \u2013 distrust. So, efficiency in incident resolution directly influences customer satisfaction (or dissatisfaction).<\/p>\n<p>Except that they get a direct look-and-feel at how efficient you are while solving their incidents. The Service Level Agreement (<a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=service-level-agreement-sla-\" target=\"_blank\" rel=\"noopener noreferrer\">SLA<\/a>, official contract between you and your customer) contains obligations that you have to fulfill. Resolving incidents and respective target resolution time is just one of them. That\u2019s the point when Incident Management efficiency is being measured.<\/p>\n<p>And, there is one more thing that you have to be aware of. When an incident happens and a service is interrupted, it not only means that you have to invest your time and effort \u2013 your customer\u2019s productivity decreases as well.<br \/>\n<div id=\"middle-banner\" class=\"banner-shortcode\"><\/div><script>loadMiddleBanner();<\/script><br \/>\n<div id=\"side-banner-trigger\" class=\"banner-shortcode\"><\/div><\/p>\n<h2>How to measure customer satisfaction?<\/h2>\n<p>Let\u2019s recall how <a href=\"https:\/\/advisera.com\/20000academy\/what-is-itil\/\" target=\"_blank\" rel=\"noopener noreferrer\">ITIL<\/a>\u00a0presents value. There are three parameters that describe the value that an IT service achieves (from a user\u2019s point of view):<\/p>\n<ul>\n<li>preference \u2013 what did the user want to get?<\/li>\n<li>business outcome \u2013 what did he get?<\/li>\n<li>perception \u2013 how does he feel about the service? This is the most complex one, but it may be the most important one when we talk about customer satisfaction. And, since that customer is a user of your services, incidents influence the customer\u2019s perception directly.<\/li>\n<\/ul>\n<p>First of all \u2013 you need to know how well or badly you are doing. That means that you will be interested to know how efficient your Incident Management process is. Efficient means, in this case, how satisfied your customers are and how good your performance is regarding <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=service-level-agreement-sla-\" target=\"_blank\" rel=\"noopener\">SLA<\/a> parameters. It\u2019s easier with finding out whether the SLA parameters are fulfilled \u2013 tools are an excellent help in this case. Fulfilling SLA requirements will make your customer satisfied, at least from a contractual point of view (they are paying for performance that they should get).<\/p>\n<p>Regarding customer satisfaction \u2013 well, there are several ways to find out the level of customer satisfaction:<\/p>\n<p><strong>Customer Satisfaction Survey<\/strong> \u2013 as with any other <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=customer-satisfaction-survey\" target=\"_blank\" rel=\"noopener noreferrer\">survey<\/a>, that\u2019s always a good idea. Send them a questionnaire and ask them direct questions.<\/p>\n<p><strong>Feedback on resolved incidents<\/strong> \u2013 this is the functionality of an IT Service Management (ITSM) tool. The point is that when the technician finds and implements a resolution for the incident \u2013 the incident\u2019s status changes to \u201cResolved.\u201d The user receives (usually) an email with a notification that the incident is resolved (and some other information), and that he should confirm that. When he confirms \u2013 that\u2019s an excellent opportunity to get feedback from him, usually regarding his satisfaction during incident resolution. In practice, the tool will guide the user to a short survey and ask him a few (don\u2019t overdo it \u2013 if you ask too many question \u2013 no one will give you feedback), e.g., one or two, questions regarding resolving that particular incident. Usually, it\u2019s about quality or speed of the proposed resolution.<\/p>\n<p><strong>Direct call after incident resolution<\/strong> \u2013 once, when we implemented an ITSM tool and a few processes, we decided that after the incident was resolved, a Service Desk\u00a0person would call that user and ask him a few (quality-related) questions. In such way we received direct feedback from the customer about his satisfaction with the Incident Management process.<\/p>\n<p><strong>Meetings<\/strong> \u2013 The Service Level Manager (SLM) is in direct contact with customers and holds regular meetings, usually once a month. And that\u2019s the perfect opportunity to get feedback about customers\u2019 satisfaction with the services and efficiency of the Incident Management process. The <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=business-relationship-management-process\" target=\"_blank\" rel=\"noopener noreferrer\">Business Relationship Manager<\/a>\u00a0(BRM, responsible for business relations with the customer \u2013 read the article <a href=\"https:\/\/advisera.com\/20000academy\/blog\/2013\/07\/15\/business-relationship-management-service-level-management-much-management\/\" target=\"_blank\" rel=\"noopener\">Business Relationship Management, Service Level Management\u2026 Too much management?<\/a>) is in regular contact with the customer and receives direct feedback about his satisfaction.<\/p>\n<h2>What to do afterwards?<\/h2>\n<p>Incident Management is a highly visible process (from both your customers\u2019 as well your own perspective), and that means it\u2019s even more important that it be a well-set and managed process. As you can see, setting up the process is a solid foundation once the service is operational, but that\u2019s not the end of the story. The point is to have your eyes wide open and react to any inconsistency that occurs. That could be the result of a measured incident resolution time (and compared to what is agreed in the <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&amp;doc=service-level-agreement-sla-\" target=\"_blank\" rel=\"noopener\">SLA<\/a>), but it could also be (sometimes even more important) feedback from your customer and his satisfaction with the results of your <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=resolution-and-fulfillment-processes&amp;doc=incident-management-process\" target=\"_blank\" rel=\"noopener\">Incident Management process<\/a>.<\/p>\n<p>Whatever the methodology (measurement or customer feedback), the target is the same \u2013 a satisfied customer. Since they also have their eyes wide open, customer satisfaction is certainly something that shouldn\u2019t be taken for granted. In the end, the customer will know how to reward that.<\/p>\n<p><em>To implement ISO 20000 easily and efficiently, use our<\/em> <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/\" target=\"_blank\" rel=\"noopener\">ISO 20000 Documentation Toolkit<\/a> <em>that provides step-by-step guidance for full ISO 20000 compliance.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Satisfied customer will pay your bills. Unsatisfied customers \u2013 well, maybe they pay the next one, but certainly not for the long term. With that act (not paying the bill, i.e., not using your services anymore), the customer wants to say something \u2013 he is not satisfied either with your service or the way you &#8230;<\/p>\n","protected":false},"author":32,"featured_media":17431,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[528,404,193,357,344,204,378],"class_list":["post-5763","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-business-relationship-management","tag-customer","tag-customer-satisfaction","tag-incident-management","tag-itil","tag-service","tag-service-level-management"],"acf":[],"_links":{"self":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/5763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/comments?post=5763"}],"version-history":[{"count":3,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/5763\/revisions"}],"predecessor-version":[{"id":18560,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/5763\/revisions\/18560"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/media\/17431"}],"wp:attachment":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/media?parent=5763"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/categories?post=5763"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/tags?post=5763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}