
Quality Times, Vocalabs' Newsletter
Pretty Good Practices
In This Issue
PRETTY GOOD PRACTICES
Agile Customer Feedback is an approach to designing customer feedback processes to make them a dynamic, responsive part of a company's continuous improvement strategy, rather than just a passive measurement tool.
At Vocalabs we've observed a number of common problems with survey processes. For example, feedback that's not timely enough to be useful, data that's not relevant to the organization, and surveys which annoy or confuse customers. We developed Agile Customer Feedback to lay down the principles and practices we use to build an effective and responsive customer feedback process. At its core, Agile Customer Feedback consists of five key principles:
- Respect and listen to customers and they will want to give feedback
- Always be collecting feedback from customers
- Adapt the customer feedback process to evolving business needs
- Disseminate customer feedback in real time throughout the company
- Target surveys to customers who are likely to tell you something you don't know
We've published a new white paper outlining several Pretty Good Practices which can help make a customer feedback program more effective, responsive, and actionable. While not every practice makes sense for every situation, we hope these ideas will help you find some ways to improve your customer feedback. Please download our white paper or contact us for more information.
FOR MORE INFORMATION: You can also download our October 2012 white paper: Agile Customer Feedback: A Dynamic, Responsive Approach to Customer Feedback.
RETHINKING THE CSR
Traditionally, the job of the Customer Service Representative (CSR) was to take requests and orders from customers and generally handle transactions as cost-effectively as possible.
Today, most routine transactions are handled through self-service. Most customers prefer to use a company's website instead of calling on the phone, especially for simple stuff. It is more and more often the case that the CSR is handling complicated transactions, situations where the self-service didn't work, and cases where the customer needs to be doubly certain that his problem will be taken care of.
What will the job of the CSR be like in the future, when nearly all customers take care of their business online? CSRs will be left with nothing but the more complex and high-stakes problems. I think this will lead to the job becoming less the traditional CSR, and more like a Customer Advocate.
The difference is that where the CSR represents the company to the customer, the role of a Customer Advocate is to represent the customer within the company. For example:
Types of Interactions
- Customer Service Representative: Most transactions are routine, and this is the customer's first attempt to solve the problem.
- Customer Advocate: Most transactions are exceptions to the normal process, and the customer has already tried other ways to solve the problem.
When Multiple Calls Are Required
- Customer Service Representative: Different CSRs will handle the customer's multiple calls. Each CSR will have to take time to become familiar with the customer's case.
- Customer Advocate: The same Customer Advocate will keep working with the customer until the problem is solved (or it becomes clear no resolution is possible).
Measuring Performance
- Customer Service Representative: Measured on how efficiently the CSR can handle a large volume of transactions.
- Customer Advocate: Measured on how effectively the Customer Advocate finds solutions which are acceptable to both the customer and the company.
When a Customer Wants Special Treatment
- Customer Service Representative: Will generally enforce company policy, but may be empowered to make limited exceptions.
- Customer Advocate: Will explain the policy to the customer, and help argue the customer's case for an exception. Authority to enforce policy and make exceptions resides elsewhere in the organization.
General Role
- Customer Service Representative: Interfaces between the customer and the company's internal business processes (order entry, billing, etc.).
- Customer Advocate: Interfaces between the customer and the company's internal structure and decision-making processes (management, other organizational silos, etc.).
It's still going to be a long time before the call center's job is primarily handling these more complex interactions, but it is starting to happen today. I'm seeing more companies moving away from efficiency-based metrics (like calls per hour) and towards outcome-based metrics (resolution, satisfaction, and related metrics). I'm also seeing more companies questioning the assumption that most calls are coming from customers who haven't attempted self-service.
So the role of the CSR is clearly shifting, whether the job description is or not.
Closing the Loop in Closed Loop Customer Feedback
In This Issue
Closing the Loop in Closed Loop Customer Feedback
Closed Loop is a popular buzzword for customer feedback programs today. It means implementing a formal process whereby customer feedback is used to drive change in the company in order to improve customer feedback.
This kind of cycle is a powerful tool--in fact, I would argue that it's pretty much the only way to build an effective and useful customer feedback process. After all, if the customer feedback isn't being used to drive change in the company, then what's it good for?
But most advocates of a closed loop process aren't really closing the loop. That's because most supposedly closed loop customer feedback processes don't formally consider the customer survey as part of the "loop" to be "closed." In other words, the company never reconsiders whether the survey is asking the right questions of the right people. It is just assumed that the survey should keep doing the same thing no matter what.
In fact, some of the proponents of closed loop processes actually advocate for very rigid and inflexible customer surveys: specific questions, with very particular sampling methods, applied in exactly the same way for every company.
That kind of rigidity (proponents would call it "consistency") is important for cross-company and cross-industry benchmarking, but it's not very helpful when trying to improve a particular customer experience at a particular company. It even sounds a little crazy to suggest that the customer survey which will yield useful, actionable feedback from a customer logging on to a bank website is the exact same customer survey which gives useful, actionable feedback from a customer buying a used car.
Instead, the customer survey itself needs to be part of the closed loop process. As companies examine their feedback they should constantly be asking questions like:
- Are we asking the right questions?
- Are we targeting the right customers for the survey?
- Is this survey yielding useful data?
- Are there issues we should be exploring in more depth on the survey?
- Are the right people getting the right data from the survey to make the best use of it?
The questions to ask, customers to talk to, and how to use the survey data will all change constantly as the company and its business environment evolves. The survey which works today isn't likely to be optimal a year from now, and five years from now it may seem close to irrelevant.
So when you build your closed loop customer feedback process, remember that the customer feedback also needs to change with the company.
Metrics are Less Important than Process
I see a lot of people spend a lot of time and effort making sure they focus on the "right" metric in their customer feedback program. Net promoter? Customer Satisfaction? Customer Effort? Something else? All of the above?
There's often a lot less thought going into what to do with the survey data: who should get it, how often, how will it be used, how will people be coached and compensated, how will you follow up with customers, and so forth.
This is a big mistake, since most of the value of a successful customer feedback program comes from all the things that happen after the data is collected. In my not-very-scientific estimation, I would say that 75% of the value is in the process, with only 25% from the metrics.
I could be wrong, though: I would believe that as much as 90% of the value is in the process.
Even a mediocre metric is going to allow a lot of improvement in a well-designed closed-loop feedback process. But no metric, no matter how good, is going to drive change if there's no follow-through.
So why so much attention to the metric, and not everything else?
I think it's because deciding what metrics to include on a customer survey feels important but doesn't require much hard work. Everyone can advocate for their favorite survey questions, there can be a lively discussion, and an executive can weigh in to break the tie. You get to feel like you had a productive day.
But getting everything else right takes a lot more time, effort, and attention. A successful customer feedback program needs to be actively managed, it requires ongoing executive attention and support, and it requires constant tweaking to adjust to the changing dynamics of the business. You can't just throw money at it.
Most people think that the scarcest resource at most companies is money. That's often true in small companies, but most large companies have plenty of money to invest in the things they think are most important. In big companies, often the hardest resource to obtain is attention--especially executive attention.
So it's easier to pretend that the customer feedback program doesn't need any ongoing attention, that you can make the big decisions once and be done with them.
But that's not a recipe for success. Success requires focusing on the rest of the customer feedback process, and making it an ongoing priority. That's hard. And that's why people spend so much time worrying about the metric.
Integrating Customer Interviews into Salesforce Workflows
In This Issue
Integrating Customer Interviews into Salesforce Workflows
I'm pleased to announce the availability of Vocalabs' immediate live customer interviews integrated into Salesforce.com workflows.
This means that any event in Salesforce can trigger an immediate call from one of Vocalabs' professional interviewers to get customer feedback. You can trigger a survey when a customer calls for service, when a trouble ticket is closed, after an installation is complete, whatever you want. The survey call can happen in as little as three to five minutes, or at a later time if that's more appropriate. You will get real-time data as interviews are completed, complete with interview recordings, alerts and notifications, and our unique interactive reporting tool.
Because this is Salesforce, setup is simple: just add an outbound notification to the Salesforce workflow. We will design an interview script tailored to your unique needs, and manage the survey process from start to finish.
This gives you the simplicity and immediacy of an e-mail or IVR survey, but with the depth and human touch only a live interview can deliver.
I'm very excited about this new service we're offering. Never before has it been so simple to collect such deep, immediate feedback, and deliver it to the places in your organization where it can have the most impact. I hope you agree. Please contact us at inquiry@vocalabs.com to talk about how we can get you started today. And I really mean today.
Forcing a Response
One of the more-abused practices in survey design is forcing a response to a particular question.
You've probably experienced this: when doing a survey (usually online), you leave a question blank and try to continue. Rather than going to the next question, the survey highlights the blank question and requires you to answer before continuing.
In theory this might be OK if you were highly confident that the list of options you gave covered every possible customer and situation. Even then, I think there are legitimate reasons why someone might decline to answer almost any survey question.
In the real world, of course, this is not what happens. All too often there's something the survey writer didn't think of, and the customer is forced to answer a question she feels she can't. The customer will do one of two things: abandon the survey (which is bad), or make something up (which is worse). Either way, the survey isn't getting the data you wanted.
I've encountered this many times. Recently, I was taking a customer survey for an organization I've done business with in the past few years, and I did have some feedback to offer: specific products I would like to see them offer in the future. About the third question on the survey asked me which products I'd purchased in the past two years, and offered a list of about 20 different products. The stuff I'd actually bought wasn't on the list.
Naturally there was no option for "some other product," and the survey wouldn't let me continue without selecting something.
In this case, I abandoned the survey. In the past I've been known (to my eternal shame) to just make stuff up in order to be given the chance to give the company a piece of my mind.
This is why I think that forcing the customer to respond to a particular survey question is almost always bad practice. You may decide to discard some surveys after the fact because the customer skipped too many questions--but at least give the customer the opportunity to provide the feedback she wants.
2012 NCSS Data Released
In This Issue
NCSS Results for Mobile Phones (2012)
We released the latest results for the National Customer Service Survey (NCSS) on Mobile Phone Customer Service this month. We have been interviewing customers of AT&T, Sprint, T-Mobile, and Verizon immediately after a customer service call since mid-2009. This report is based on 9,195 interviews of customers of the four companies over that period.
The most dramatic change in 2012 from 2011 is the significant improvement in the customer service metrics at Verizon. The company gained ten points in overall call satisfaction over the past year, as well as significant improvements in IVR satisfaction, call resolution, and ease of reaching a person.
Historically in our survey, Verizon has consistently posted the top scores for agent satisfaction, while underperforming on IVR satisfaction and ease of reaching a person. With this position, it makes sense for Verizon to improve its IVR to make it easier for customers to reach an agent when needed. This plays to the company's strength of having the best customer service representatives in the industry.
We also saw a continuation of T-Mobile's gradual drop in customer service-related metrics in 2012, with call satisfaction dropping, and customers in our survey reporting that it was harder to reach a person and they had to jump through more hoops to get what they needed on the call.
Sprint's business metrics have been on a gradual upward trend since 2009, and that continued into 2012; however, the company's customer service related scores have not changed significantly in our survey in 2012 as compared to 2011. In our executive summary we take a closer look at the ups and downs of Sprint's customer service over the past several years.
NCSS Results for Banks (2012)
We also released NCSS results for Banks, covering 2011 to 2012. We began collecting customer interviews about Bank of America, Chase, Citi, and Wells Fargo in April 2011, and this report is based on 2,980 interviews collected during the period from April 2011 through December 2012.
Over the past year we observed a general improvement in our survey scores across the industry. None of our nine key metrics dropped by more than one percentage point at any of the four companies. Chase and Citi posted the largest improvements, while scores at Bank of America and Wells Fargo increased by a more modest amount. Since Bank of America and Wells Fargo were ahead on customer service in 2011, the net effect of this was to tighten the race for best service.
Customer authentication in the automated part of the call is a pain point for many of the customers we interviewed in our survey. At each of the four companies, between 2.1% and 4.3% of all customers reported that they had a problem getting past the point in the call where the IVR asked them for an account number or PIN. This represents a surprisingly large percentage of the overall call volume, and since we don't specifically ask about authentication problems, it's likely a lot of customers are having problems who didn't report them on our survey.
What's more, many of the problems customers reported should have been anticipated. We saw many customers calling to report lost or stolen cards who were asked to enter their account numbers--a situation where it's reasonable to expect that the customer might not have an account number handy. We even had one report of a frustrated customer who was asked to enter an account number just to get the hours of the local bank branch.
I applaud the improvements the banking industry made in 2012, especially given than banks do not, in general, have a reputation for stellar service. There is still a lot more room for improvement, and a lot of it boils down to paying careful attention to what customers want and the best way to serve them.
In This Issue
Net Naughty nice Index (NNNI)
Memo
From: Crinkletoes, Chief Operational Elf (COE)
To: All Elves
Re: Adoption of NNNI across all North Pole operations
As many of you have heard, beginning this Christmas season the North Pole will replace our traditional Naughty or Nice list with the Net Naughty Nice Index (NNNI), a change which will bring us into alignment with the state of the art for a 21st century gift delivery network, and provide us with dramatic improvements in operational efficiency.
This is a big change we've been working on all year in cooperation with the top consultants in the field, and I know you all have a lot of questions. In this memo, I've compiled some of the most frequently asked questions and their answers.
Why the change?
I think many of you will agree that the Naughty or Nice list, while part of our corporate heritage, is an inefficient, outdated business process. By adopting the latest techniques we can achieve the same or better level of gift giving accuracy at considerably less expense. Just the process of checking the Naughty or Nice list twice takes the effort of thousands of elves. NNNI is statistically accurate enough that this costly and redundant step will no longer be necessary. Furthermore, while the Naughty or Nice list was very subjective and required a lot of judgment calls, the NNNI is completely objective, based on mathematical models and statistics.
Who else is using NNNI?
Naturally, we will be the most prominent adoption of NNNI to date. You can't get much bigger than the North Pole, ho ho ho!
Still, it's good to ask whether NNNI has ben adequately tested in the real world. Research published in the Elven Management Journal shows that NNNI is highly correlated with actual naughty or nice behavior; and I expect to see announcements soon that the Easter Bunny and the Tooth Fairy are also switching to NNNI. NNNI is quickly being established as the only metric needed to track the relative niceness of children.
What if we make a mistake?
You may have heard that with NNNI we will end the practice of checking our list twice. This will save considerable elf magic, which we can put to better use elsewhere at the North Pole.
Some of you are rightly concerned that this may lead to more mistakes where children who deserve toy trains or dolls get lumps of coal, and vice versa. Of course, we did occasionally make mistakes on the Naughty or Nice list, which is why it was necessary to check it twice in the first place.
We have given this a lot of consideration, and we hired as consultants the researchers who developed the NNNI. They have shared with us their proprietary research proving that across a large enough statistical sample, NNNI is an almost perfect predictor of actual incidence of naughty and nice behavior among children in our target demographics.
For example, when we compared the average NNNI for all children in New York City, we found that it matched the statistically weighted average position of all New York children on the Naughty or Nice list to a very high degree of accuracy. It was this research which gave us the confidence to eliminate the redundancy in our old process as part of this rollout.
How does NNNI work?
Whereas the old Naughty or Nice list required the work of many elves to examine the behavior of children one-by-one, the NNNI uses a crowdsourced process to leverage the "wisdom of crowds" to achieve the same result with considerably less effort.
The NNNI begins with a large statistical sample of millions of children, and ask each of them one simple question: "On a scale of zero to ten, where zero is very naughty and ten is very nice, how naughty or nice are the other children you generally associate with?"
The data from this question are fed into a mathematical model which uses the social graph of each child to calculate an aggregate NNNI for a large population of children. Then, intersections of the social graph are used to identify "supernodes" of niceness or naughtiness--essentially very nice or very naughty children. The relative distance of each child from the supernodes is then used to calculate each child's NNNI score upon which we base gift-giving decisions.
What other changes are taking place?
With the increased efficiency and accuracy of NNNI, we are also making significant reductions in our complaints and returns departments. We simply will not need as many elves to handle the volume this year.
This has allowed me to exceed my stretch goals for operational efficiency at the North Pole this year, an achievement which I am very proud of.
Thank you to everyone who provided input during this process. You are what makes the North pole great!
In This Issue
Two Stories
Every company makes mistakes, and what often drives a company's reputation for good or bad service is how it handles the mistakes and weird situations. Were employees empowered to fix the problem, maybe even bend the rules a bit? Or did they fall back on process and bureaucracy, frustrating the customer's attempts to find a way to fix the problem?
This month, we're sharing two stories of what happens when customer service processes break down.
Service Recovery Done Wrong
by Peter Leppik, CEO
"Service Recovery" is the fancy term for making things right when they go wrong. It's a powerful tool for improving brand loyalty when done right, but done wrong it can backfire.
I recently traveled to Las Vegas for a conference. I stayed at the conference hotel, the New York New York--not the swankest place in Vegas by any stretch, but certainbly a respectable hotel for a business traveler.
There was only one problem: by the time I arrived at midnight, the hotel was out of nonsmoking rooms in the room type I had reserved. I'm not a very demanding business traveler: I really only insist on two things. Basic cleanliness and a nonsmoking room. In the year 2012 in the United States, these are things every traveler should expect at any hotel.
Normally this is not a problem. I've had this happen to me dozens of times over the years, and the hotel upgrades me to whatever nonsmoking room is still available. But apparently this is not the policy at the New York New York: they made me pay for an upgrade to a fancy suite as the only way to have me and all my belongings not smell like smoke in the morning. The check-in agent offered no other options (or even much sympathy), so I grudgingly paid for the upgrade.
By this point in my customer experience the hotel had earned a black mark in my book. I don't care so much about the dollars, but I do care that they don't consider a nonsmoking room important for guests who want one. Since a nonsmoking room is very important to me, that's reason enough not to go back. But as a customer I'm still recoverable, if the hotel recognizes its mistake and makes amends.
So the next morning I related my story to one of the conference organizers and several other attendees. The conference organizer passed this along to the hotel management, and the next day I got a call from one of the guest relations people.
Now we are in the Service Recovery phase. The hotel knows they have an unhappy customer and they are reaching out to me to try to make it right. Research as shown that taking care of a customer's problem properly will actually make a more loyal customer, but not taking care of a problem will lead to a disloyal customer likely to spread negative word-of-mouth. So it's important to do this right, and convert that upset customer into a brand advocate.
The representative from the hotel was very polite, listened to my problem, agreed that I should not have had to pay extra just to get a nonsmoking room. And then she offered to refund one night of the two-night upgrade fee.
Wait, what?
If she agreed that this should not have happened, then why is the hotel only offering to fix half the mistake?
The issue in my mind was never the money so much as the fact that a nonsmoking room is, for me, a basic amenity like clean sheets. From the hotel's response, I can only conclude that my initial conclusion--that they don't think a nonsmoking room is all that important--was correct.
So rather than convince me to return, the hotel actually reinforced my initial negative impression. And like the good Detractor that I am, I am telling everyone--including you, my reader--the same thing: If you care about getting a nonsmoking room, don't stay at the New York New York. Because they don't care, and their actions speak very loudly.
And that is how you do service recovery the wrong way.
Silos vs. Service
by David Leppik, VP of Software Development
Customer service isn't something you can master and then forget: it takes constant vigilance. In our research, we've found that Sprint went from being the worst cell phone company in customer service to being the best—only to drop back down to the worst position again. And I think my story illustrates what I think is going wrong.
I recently got an iPhone 5, but it took far more effort than it should have. My order was blocked by Sprint right before it was going to ship, I spent an hour and a half on the phone with Apple and Sprint customer service, and nobody knew what had gone wrong.
Here's what I think happened: Apple's computers were doing a final, pre-shipment confirmation of my order with Sprint. Something went wrong. Sprint blocked my order without any indication of why. A person from Apple called me to let me know what had happened (they didn't want me to get the bad news via email) and that I should call Sprint. The Apple rep explained that since the problem might be something like a late payment, Apple wasn't getting involved.
So Sprint made a mistake, and mistakes like this happen. But what really made it bad is how Sprint handled it.
Sprint's front-end customer service staff were friendly and even enthusiastic about helping me. But because I bought my phone through Apple, my support requests are required to go through Sprint's National Sales Support Desk—and only their channel partners are allowed to speak to that Desk. Or as the Desk rep told the Apple rep, "we can only validate through a store."
The problem was eventually solved by an Apple rep calling an Apple Store employee, who called Sprint's Support Desk. The Support Desk verified that there was no reason for my order to be blocked, and assured me (over a muffled, echoey chain of phone lines) that the next order would not be blocked. Apple offered to expedite my next order, but I needed to wait 24 hours for the cancelation to go through, so that Sprint wouldn't block the new order as a duplicate.
What should have happened is this: the first rep I talked to—or her manager—should have been allowed to talk to the National Sales Support Desk. They would have confirmed that my order block was a mistake and then consulted with Apple on how to proceed. This should have taken just a few minutes.
I'm sure there's some good reason why that Desk is kept separate, but there should be some allowance for customer service emergencies. Yet even when everyone involved was able to verify that a loyal customer was being treated wrong, corporate procedure took precedence over doing the right thing.
Every system breaks down from time to time. Courts convict the wrong person. Wars and natural disasters break normal channels of communication. So every bureaucracy tolerates broken rules sometimes. The National Sales Support Desk wouldn't have needed to go through proper channels to respond to their building burning down. And my guess is, when Sprint was at their best at customer service, they would have found a way to do the right thing.
That's what makes great customer service hard. Sometimes you need to bend the rules in the service of the customer. Especially when the rules don't make sense under the circumstances. In the absence of a top-down customer service mandate, bureaucracy takes over. And it can happen incredibly fast.
At Vocalabs, we know from empirical evidence that what matters in customer service is actually serving the customer. Not by being friendly or following etiquette procedures, but by finding a way to help. Apple didn't have a procedure for re-enabling my order, so I had to place a new order. But I didn't mind (much) because they made it clear that they would do whatever it took to fix my problem. Sprint made it equally clear that my problem wasn't their problem.
In This Issue
Customer Service Strengths
This month we published another cross-industry National Customer Service Survey (NCSS) report, this one taking an in-depth look at the relative strengths and weaknesses of the eleven companies in our ongoing survey. We examined over 9,000 completed customer interviews, and for each company looked at the call satisfaction and resolution rates based on the call reason or product the customer was calling about.
We found that no company outperforms or underperforms everywhere: each company had some strengths and some weaknesses and nobody was good or bad across the board. Even Apple, which has a well-deserved reputation for outstanding service and support, had products where our survey responses were no better than its peers. Similarly, T-Mobile had worse survey scores than other wireless carriers for many types of calls, yet still held its own for other call types.
This result is surprising, because we tend to think that a company with good (or bad) customer service is good (or bad) across the board. The reality is more complex, and every company has room to improve somewhere.
For full details, please download our executive summary.
Agile Customer Feedback
I've observed a number of common problems with survey processes. For example, feedback that's not timely enough to be useful, data that's not relevant to the organization, and surveys which annoy or confuse customers. We developed Agile Customer Feedback to lay down the principles and practices we use to build an effective and responsive customer feedback process. At its core, Agile Customer Feedback consists of five key principles:
- Respect and listen to customers and they will want to give feedback
- Always be collecting feedback from customers
- Adapt the customer feedback process to evolving business needs
- Disseminate customer feedback in real time throughout the company
- Target surveys to customers who are likely to tell you something you don't know
Following these principles enables you to build a customer feedback program which is a dynamic and responsive part of the business, as opposed to a passive measurement tool. This addresses many common problems I see with customer feedback processes:
- Inflexibility: The customer feedback process can't adapt to changes in business needs.
- Unfriendliness: The survey doesn't leave a positive impression with the customer.
- Low Response: It's hard to get customers to participate (this may be related to unfriendliness).
- Not Actionable: The feedback doesn't make it clear what specific changes have to take place.
- Not Relevant: The reports don't address the specific needs of the people who need to use it (or they may address certain people's needs but not others).
- Stale: By the time the feedback is delivered, it's too old to be meaningful.
- Poor Metrics: Metrics are too high-level, not high-level enough, not relevant to business needs, create perverse incentives, or are not tailored to the recipient.
- Flood of Verbatims: Too much unstructured, free response feedback which takes too much time and effort to analyze.
- No Credibility: Obvious data quality problems aren't addressed, leaving the whole process open to attack from people who disagree with the data.
- Not Persuasive: Nothing happens because the process doesn't create a sense that something needs to be done.
We just published a white paper going into a lot more detail about Agile Customer Feedback, and you can download it from our website.
In This Issue
Credit Card Complaint Data from the CFPB
Recently the Consumer Financial Protection Bureau (CFPB) started publishing a data set of consumer complaints about credit cards. As this data complements Vocalabs' National Customer Service Survey data on customer service at major banks, we are republishing the CFPB data as a set of dashboards and reports comparing different companies' credit card complaints in several key metrics. These reports and dashboards will be updated as new CFPB data becomes available.
We have created three graphical dashboards comparing companies' performance on key metrics. The dashboards show graphs for the eight companies with the most complaints in the database (as of September 2012), and we also have interactive tables with complete data for all companies.
-
Timely Responses: Shows how often customers received a timely response to their complaints about different companies. View Dashboard | View Table
- Customer Disputed Resolution: Compares the percentage of complaints where customers disputed the resolution offered by their bank. View Dashboard | View Table
- Monetary Resolution: Shows how often customer complaints resulted in the bank paying the customer money in order to resolve the complaint. View Dashboard | View Table
We are also providing other data and metrics in an interactive table format, allowing anyone interested to build their own views of the report and export the data as a spreadsheet. We have pre-built a few tables you can use as starting points:
- Complaint Metrics by Company: All three of the metrics in the dashboards above, included in a single table for convenience.
- Complaint Metrics by Complaint Type: The three metrics in the dashboards, calculated by type of complaint.
- Types of Complaint by Company: The major types of complaints, calculated by company.
We hope you find this a useful tool for better understanding this data set. Please let us know if you have any suggestions for improvements.
ROI of Customer Feedback
The return on investment of a good customer feedback program is more complicated to quantify than, for example, a new speech recognition system or more efficient contact center scheduling.
The ROI comes from a lot of sources. Some of these are hard dollars, and others are squishier:
- The easiest return to quantify comes from finding and fixing broken processes and systems. It's common to find policies which can be streamlined, self-service processes which make no sense to the customer, and even systems which are outright broken. These cost hard dollars, and customers are usually very happy to tell you about them.
- It's also easy to quantify the value of better decision-making. A good customer feedback program will give hard data about the customer impact of spending money on different parts of the service experience. For example, how much will customer satisfaction and loyalty improve by streamlining an IVR, and is it worth the money? Without the data, you have to take the vendor's word.
- Better service leads to a strong improvement in customer loyalty. Our NCSS data consistently shows a 40-45 percentage point gain in customer loyalty among customers who report excellent customer service as compared to those whose service was mediocre or poor. Measuring the quality of the customer service experience is a critical piece in delivering outstanding service.
- A strong customer feedback program is also a powerful training tool. People respond powerfully to hearing immediate feedback from real customers, and that means measurable improvements in service levels and less time spent in coaching or remediation.
- The hardest return to quantify, but perhaps the largest, comes in brand image. Many companies (I won't name any but you can probably think of a few names) have seen hundreds of millions of dollars in marketing and brand equity destroyed when the company gets a bad reputation online because of poor service, missteps, and neglecting the basics of taking care of customers.
In This Issue
Vocalabs Teams with Listening Methods to Measure Self-Service Effectiveness
We've recently teamed with startup Listening Methods to give our clients some unique new tools for measuring and improving the effectiveness of speech and IVR systems.
Listening Methods' technology passively listens to customer calls and automatically tracks what happened during each call. For example: did the customer hit zero at the first prompt; did the customer get caught in a loop; were there multiple recognition errors during the call; or did the customer successfully use self-service.
Using this call-by-call data, we can categorize each customer's experience and target immediate in-depth follow-up interviews within a few minutes of the end of the call. This lets us select just the customers who had particular kinds of service experiences, and measure things like:
- If a customer hangs up before completing a transaction, how often will the customer call a competitor instead and how much lost revenue does this represent?
- What percentage of customers who "zero out" to an agent could be self-served, and why are they unwilling to try?
- How much does a negative IVR experience impact top-level business metrics like customer satisfaction or Net Promoter?
Targeting the interviews means that we can answer these questions more cost-effectively and in more detail than with a broad-based customer survey, and the immediate follow-up lets us ask very specific questions about the customer's particular experience. Because the interviews are tied to specific customer experiences we can use this feedback to discover specific ways for our clients to streamline their processes, improve sales, reduce churn, and save money.
We recently published a joint whitepaper with Listening Methods, available for download on our website. This whitepaper outlines the Voice Self-Service Score, a methodology for using the statistical call-event data combined with targeted customer feedback to generate a numerical score for self-service effectiveness.
We're very excited about this, and please don't hesitate to contact us if you would like more information.
Simple is Hard
If you hang around user interface designers long enough, eventually you will hear the phrase "Simple is hard."
Designing an intuitive, easy to use system is surprisingly difficult. Under the surface, today's technology is overwhelmingly complex. The only reason mere humans can use something like, say, an iPhone, is because almost all the complexity is hidden by the user interface.
To make this appear simple, the user interface designer has to figure out how to communicate all the functions to the user (or at least the important ones) in a way which seems obvious, but without overwhelming the user with all the unimportant stuff. It's a tough challenge, not least because most UI designers (many of whom are programmers) don't think like users.
The same thing is true for customer service. In many ways a company is like a very complicated machine, and customers are like the users. A company's web site and contact centers are the interfaces through which the customer tries to accomplish something, just like the touchscreen is the interface for doing stuff on an iPhone.
We want the customer to feel that the company is easy to do business with. Customers should not need to learn how a company's internal processes work, or spend time coordinating different parts of the organization.
This is hard to accomplish. It means designing customer service processes to hide all the internal complexity of a company, clearly communicate how to do those things customers probably want to do, and making sure that a customer's needs are properly coordinated inside the company.
But it can be done.
In This Issue
- National Customer Service Survey Report: The Customer Frustration Index
- Pushing Customers into Self-Service
National Customer Service Survey Report: The Customer Frustration Index
Our newest National Customer Service Survey report is a close look at three specific ways companies both drive up the cost of their customer service and needlessly frustrate customers in the process. We analyzed over 8,000 customer interviews after customer service calls to eleven different companies over the last 18 months, and discovered some interesting facts:
- Making it harder to reach a person is almost completely ineffective as a strategy for increasing customers' use of self-service.
- Customers who have to call multiple times to get what they need are just as satisfied as first time callers if they can pick up where they left off from the earlier calls. However, repeat callers who have to start over from the beginning are extremely dissatisfied.
- Customers who use self-service by their own choice are more satisfied than callers who spoke to a person. Customers who stay in the IVR despite needing to talk to a person are extremely dissatisfied.
These findings are perhaps not surprising, but very few companies take them into account when designing their speech and IVR systems. We found that between a fifth and a third of callers to the companies in our sample experienced at least one of these problems. That makes these design issues collectively a major driver of customer dissatisfaction and poor resolution of service calls.
More details and complete statistics are in our Executive Summary, available for download on the Vocalabs website.
Pushing Customers into Self-Service
I don't think it's any secret that some companies "hide the ball" in customer service, and made it hard to reach a person in hopes that customers will use self-service instead. Most industry experts agree that this is backwards thinking that went out of style with Duran Duran, but it still happens.
But does it work? How often will a customer successfully use self-service despite being frustrated by an inability to reach an agent?
As part of our new National Customer Service Survey report we took a close look at this question. The answer surprised me, and it might surprise you, too.
The answer is: For all intents and purposes, Never.
Among customers who (a) reported that it was hard to reach an agent AND (b) did not speak to an agent, only 5% reported that they got what they needed on the call.
Companies who intentionally make it hard to reach an agent believe customers will start out trying to reach a person, find it difficult, then successfully use the IVR. This use pattern does not exist to any meaningful extent. Instead, customers start out trying to reach a person, find it difficult, then eventually either reach a person or hang up in frustration (perhaps to call back later).
So why do so many companies keep making it hard to reach a person? Three reasons:
- They think it should work.
- It looks like it works when customers hang up without talking to anyone (in reality, most of them will probably call back later).
- They don't bother to measure customer opinions about self-service.
