{"id":281,"date":"2016-09-02T10:03:03","date_gmt":"2016-09-02T09:03:03","guid":{"rendered":"https:\/\/www.feverbee.com\/roi\/?p=281"},"modified":"2026-03-16T22:17:07","modified_gmt":"2026-03-16T22:17:07","slug":"measuring-first-contact-resolution","status":"publish","type":"post","link":"https:\/\/www.feverbee.com\/roi\/measuring-first-contact-resolution\/","title":{"rendered":"Measuring First Contact Resolution"},"content":{"rendered":"<section class=\"content standard\"><div><\/p>\n<p><aside class=\"\"><\/p>\n<h1>10<\/h1>\n<h2>10.3: Measuring First Contact Resolution<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-7\" src=\"\/wp-content\/uploads\/sites\/2\/2016\/09\/sponsored-by-sap.png\" alt=\"Sponsored by SAP\" width=\"113\" height=\"65\" \/><\/p>\n<p><\/aside><\/p>\n<p><article class=\"\"><\/p>\n<h3>Now you\u2019re on to the final customer service benefit of a community, namely <a href=\"http:\/\/www.oracle.com\/us\/products\/applications\/improving-contact-resolution-1599286.pdf\"><em>first contact resolution<\/em><\/a> (FCR). FCR is so similar to agent productivity that we almost combined the two. However, we opted against it because FCR is such a widely used metric to gage success and is <a href=\"https:\/\/www.talkdesk.com\/blog\/how-to-calculate-first-call-resolution\/\">easy to measure<\/a> for an organization. The FCR rate is the number of customer problems resolved at the first attempt (i.e. the number of calls a customer service takes to resolve the problem of a single customer).<\/h3>\n<p><div class=\"tweet\">\r\n\t<a href=\"https:\/\/twitter.com\/intent\/tweet?text=The+FCR+rate+is+the+number+of+customer+problems+resolved+at+the+first+attempt+by+a+customer+service+rep&amp;url=https:\/\/www.feverbee.com\/roi\/measuring-first-contact-resolution\/\" target=\"_blank\">\r\n\t\t<h3>The FCR rate is the number of customer problems resolved at the first attempt by a customer service rep<\/h3>\r\n\t\t<span class=\"tweetButton\">&nbsp;<\/span><p class=\"tweetLink\">Click to Tweet<\/p>\r\n\t<\/a>\r\n<\/div><\/p>\n<p><div class=\"boxout\"><\/p>\n<p>By exposing customer service representatives to the community, they may be able to identify and resolve a larger number of calls they receive at the first attempt.<\/p>\n<p>This might be through finding a similar discussion topic in the community and seeing how other customers solved the problem. It might be by building a bigger database of customer-supported solutions. It might be by becoming aware of new issues as they are emerging and preemptively developing solutions for them.<\/p>\n<p><\/div><\/p>\n<p>Resolving a problem at the first attempt reduces the overall number of calls the customer service team receives. This is the comparative metric we aim to measure here.<\/p>\n<p>You need six pieces of information to calculate this rate. These are:<\/p>\n<ol>\n<li>Number of calls received by agents \u2018not exposed\u2019 to the community per month.<\/li>\n<li>Number of customers helped by agents \u2018not exposed\u2019 to the community per month.<\/li>\n<li>Number of calls receives by agents \u2018exposed\u2019 to the community per month.<\/li>\n<li>Number of customers helped by agents \u2018not exposed\u2019 to the community per month.<\/li>\n<li>Number of customers who call for support per year.<\/li>\n<li>Cost per call.<\/li>\n<\/ol>\n<p>Notice above the difference between a call and a customer. A customer may make multiple calls during any given month.<\/p>\n<p><div class=\"cta spreadsheet\"><div><h3>Community ROI Template<\/h3><\/p>\n<p>You can enter the information <a href=\"http:\/\/roi.feverbee.com\">into this spreadsheet here<\/a> or follow the method below.<\/p>\n<p><\/div><\/div><\/p>\n<p><\/article><\/p>\n<p><\/div><\/section>\n<section class=\"content flipped\"><div><\/p>\n<p><aside class=\"\"><\/p>\n<p><div class=\"cta questions\"><div><h3>Any Questions?<\/h3><p>Don\u2019t understand? Need some help? Ask a question in FeverBee Experts.<\/p><p><a class=\"button\" href=\"https:\/\/experts.feverbee.com\/t\/roi-testing-title-change\/4041\">Ask a Question<\/a><\/p><\/div><\/div><\/p>\n<p><\/aside><\/p>\n<p><article class=\"\"><\/p>\n<h2>Step One:\u00a0Measure the Impact<\/h2>\n<p>The best method to measure the value of improved FCR rate is to measure the difference in FCR rates between two randomly selected groups of agents who have or haven\u2019t been assigned to a community \u2018<em>condition<\/em>\u2019. This is the same process we used in determining average call handling time. We expose half to the community as a resource, while the other half continues as normal.<\/p>\n<p>If this is not possible, it may instead be possible to measure the FCR rates of agents who visit the community and, for those who do not, to identify possible differing rates. Alternatively, it might be possible to measure the FCR rates before the community was created and after the community was created. As before, the best method is a direct split test comparison.<\/p>\n<p>We can either use database queries to identify what % of calls were repeat calls or use follow-up questions on the call itself to identify first contact resolution rates. If we assume a customer will, on average, only contact the organization once per month about a problem (e.g. they don\u2019t have multiple problems in a month), we can track the number of customers who call twice during that time period.<\/p>\n<p><a href=\"\/wp-content\/uploads\/sites\/2\/Screenshot-2016-08-05-09.54.00.png\"><img loading=\"lazy\" decoding=\"async\" class=\"screenshot alignnone wp-image-457 size-full\" src=\"\/wp-content\/uploads\/sites\/2\/Screenshot-2016-08-05-09.54.00.png\" alt=\"screenshot-2016-08-05-09-54-00\" width=\"721\" height=\"172\" \/><\/a><\/p>\n<p>For example, if an organization receives 16,324 calls per month from 11,405 customers, we know that 4,919 (30.1%) of these calls were repeat calls. This means the FCR rate is 69.9% (11,405\/16,324).<\/p>\n<p>If agents exposed to the community condition improve their FCR to 89.5%, this is a 28% difference (89.5-69.9\/69.9). Note here that we\u2019re measuring % improvement, not overall % difference. This tells us that agents exposed to the community are 28% more likely to resolve a call at the first attempt than agents not exposed to the community.<\/p>\n<p><\/article><\/p>\n<p><\/div><\/section>\n<section class=\"content standard\"><div><\/p>\n<p><aside class=\"\"><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-909\" src=\"\/wp-content\/uploads\/sites\/2\/Measuring.png\" alt=\"Measuring\" width=\"326\" height=\"467\" \/><\/p>\n<p><\/aside><\/p>\n<p><article class=\"\"><\/p>\n<h2>Step Two: Measure Increase in Calls Resolved On First Attempt<\/h2>\n<p>Now we can multiply this % increase by the number of customers who call the support line. We will need to either manually get this data from the database or use a sampling technique of a % of customers to determine how many call customer support.<\/p>\n<p>This will reveal the total number increase in customers whose questions were answered at the first attempt, as shown below.<\/p>\n<p><a href=\"\/wp-content\/uploads\/sites\/2\/Screenshot-2016-09-01-21.59.55.png\"><img loading=\"lazy\" decoding=\"async\" class=\"screenshot alignnone wp-image-456 size-full\" src=\"\/wp-content\/uploads\/sites\/2\/Screenshot-2016-09-01-21.59.55.png\" alt=\"screenshot-2016-09-01-21-59-55\" width=\"991\" height=\"123\" \/><\/a><\/p>\n<p><\/article><\/p>\n<p><\/div><\/section>\n<section class=\"content flipped\"><div><\/p>\n<p><aside class=\"\"><\/p>\n<p><div class=\"cta share\"><div><h3>Share Your Efforts<\/h3><p>Let us know what you measure.<\/p><p><a class=\"button\" href=\"mailto:richard@feverbee.com?subject=Share%20Example\">Share With Us<\/a><\/p><\/div><\/div><\/p>\n<p><\/aside><\/p>\n<p><article class=\"\"><\/p>\n<h2>Step Three: Measure total cost savings of calls resolved at first attempt<\/h2>\n<p>We can now multiply this increase in calls resolved at the first attempt by the cost per call to calculate the total cost savings attributable to the community.<\/p>\n<p><a href=\"\/wp-content\/uploads\/sites\/2\/Screenshot-2016-09-01-22.01.15.png\"><img loading=\"lazy\" decoding=\"async\" class=\"screenshot alignnone wp-image-455 size-full\" src=\"\/wp-content\/uploads\/sites\/2\/Screenshot-2016-09-01-22.01.15.png\" alt=\"screenshot-2016-09-01-22-01-15\" width=\"997\" height=\"147\" \/><\/a><\/p>\n<p>This reveals the total cost savings through improving the FCR rate per year.<\/p>\n<p><\/article><\/p>\n<p><\/div><\/section>\n<section class=\"summary\"><div><article><h2>Summary<\/h2><\/p>\n<ol>\n<li>The First Contact Resolution (FCR) rate is the number of problems resolved at the first attempt. This is a widely used metric in customer service sectors.<\/li>\n<li>Higher FCR rates reduce the number of calls to the customer service center and increase customer satisfaction.<\/li>\n<li>To accurately measure FCR rate, run a controlled trial where half the agents are exposed to the community and half are not. Measure the difference between the two as a percentage.<\/li>\n<li>Now multiply this percentage by the number of customers who call for support per year and then the cost per call to reveal a total cost saving.<\/li>\n<li>This is not a perfect method. It makes assumptions about how many problems a customer is likely to have, which may be false<\/li>\n<\/ol>\n<p><\/article><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-281","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/posts\/281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/comments?post=281"}],"version-history":[{"count":0,"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/posts\/281\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/media?parent=281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/categories?post=281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.feverbee.com\/roi\/wp-json\/wp\/v2\/tags?post=281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}