Using Effective Customer Service to Improve Business Results
Challenges with Customer Support
How does your organization view customer complaints? It is unlikely that many organizations welcome customer complaints, but, if handled well, customer complaints can be a significant source of information to control costs and actually enhance customer satisfaction. Yet many organizations seem to have the perspective that addressing customers’ concerns is inherently an impediment to maintaining efficient operations. Much of the management effort directed toward customer service reflects this tension. Often, the emphasis is on taking action—any action—to reduce attention from customers and the press. Too much management time and attention spent on this approach to customer service is expensive and wasteful.
Resource-efficiency and customer service are not opposing forces. In fact, using systematic techniques to escalate and investigate customer complaints, take appropriate containment actions, and then choose and implement corrective and preventive action can help most organizations improve customer satisfaction, cut costs, and achieve superior business results.
Systematic Data Collection
What value does your customer support function provide to your organization and your customers? One measure of their value is the number (or percentage) of customer issues they are able to handle directly and close out during the initial call. Another measure of their value could be the confidence they provide customers that the issues not resolved during the initial call will be handled promptly and effectively. A third measure of their value could be the quantity of information they collect during the initial call that contributes to final resolution of the issue and minimizes the effort required by second and third level support staff to resolve the issue.
Ask yourself these questions:
- What percentage of customer issues are not resolved during the initial call?
- What is the resource cost to your organization of resolving these issues?
- What is the customer satisfaction cost to your organization, based on the amount of time (or number of iterations) required to resolve these issues?
KT has designed a proactive model for maximizing the value that the customer support function can provide to both your organization and your customers. At its core is a systematic approach for managing the information that customers provide to ensure that issues are properly escalated and problems are properly identified and promptly resolved so that customer expectations are, at minimum, met (or preferably, exceeded).
The Logic of the Model
Most problem resolution systems include the following steps:
- Problem Identification — Customer service documents the reported complaint
- Issue Escalation — Management prioritizes the problem and determines if containment is required
- Issue Containment — The organization responds to limit the extent and effects of the issue, as required
- Issue Investigation — A team then investigates the issue and documents their findings
- Fix Selected — The team chooses corrective and preventive actions
- Case Closed — Management then approves the thoroughness of the investigation
- Fix Implemented — A team then implements the Fix
- Fix Approved — Management then approves the efficacy of the Fix
A systematic process for gathering the information required to complete each of these steps effectively is at the core of our model for maximizing customer satisfaction and efficiency. Using “process” thinking helps organizations link customer complaint systems to operations and make the leap from customer service to business results.
In working with one of our clients, we established a systematic approach to documenting complaints, the average time to process a ticket dropped to below 5 minutes from almost 10. More importantly the variation in the time required to process a ticket also decreased dramatically, giving management much better predictability and control of their process. Anecdotally, the second line support staff also saw an improvement in the quality of information they were receiving and needed in order to do their work.
In this paper we will discuss how customer service representatives using a structured approach to gather information can enhance an organization’s Issue Escalation, Issue Containment, and Issue Investigation processes.
Issue Identification begins with the first phone call, e-mail, or fax received regarding a complaint. Customers may initially provide information that is biased by assumptions or premature and inaccurate conclusions about potential causes. The person handling the initial call needs to gather data that provides a robust understanding of the presenting event and how it relates to the product or service in question. It is probably premature to begin exploring the Why, so the initial questions should focus on the What, Where, When, and Extent of the issue. These questions will help us establish what we know to be true about the presenting issue and how it is an issue, rather than what we think might be the issue. If the answers to these are sufficient, they can guide escalation of the issue, decisions on containment, and provide the starting point for determining the cause of the concern. Accurately describing the issue is crucial to the process. “Device is dead” or “Device doesn’t work” does not add much to our
state of knowledge.
When Customer Service representatives collect information about complaints:
- How useful is the information they provide for understanding the scope and impact of the incident?
- How useful is the data for tracking and trending incidents over time?
- How useful is the data for prioritizing incidents and determining appropriate next steps?
Problem Analysis: Finding the Root Cause of Deviations. “A problem well defined is a problem halfsolved.” – John Dewey. To facilitate tracking and trending, customer support personnel should use a consistent framework to document information about customer complaints. Kepner-Tregoe’s Problem Analysis provides such framework for clarifying and documenting non-conformances accurately and concisely.
Case Study Example
This case study provides an example of how an organization with an effective Customer Service data collection protocol was able to promptly recognize a significant issue.
At 9:05 AM this morning, Customer Support received the first call regarding the failure of one of our blood pressure monitors, the BP200 Digital Blood Pressure Monitor. The complaints center on the Liquid Crystal Display which shows the results of the blood pressure reading. Customers are reporting that, at first use, the LCD never comes on, no matter what they do. We have not gotten any calls about our BP300 Digital Blood Pressure Monitor or the BP1000 Wrist Blood Pressure Monitor.
We began to get a few other calls with the same symptoms through the morning. We alerted the regional Help Desks in Seattle, Sacramento, Des Moines, and Montgomery, but none of them had
seen anything like this yet.
By gathering information about where the problem was seen “geographically,” we were able see the pattern that most lived in New England. Three did not, but when asked where purchased, we learned the three “outsiders” had bought their BP200s in New England while on vacation.
By the end of the morning we had received 47 calls. We used this information to create what we thought was a good initial description of the event. Because people used a common convention to document these calls, we were able to determine that there was a pattern and that these were probably not isolated events. Using the problem analysis framework, the team summarized the data as shown in Figure 1.
Issue Escalation and Prioritization
In any business, there are low-level complaints: problems for which you already know the cause; problems for which a fix has already been decided; and problems that are one-time random occurrences of little seriousness. Then there are the high-level complaints, where a key product is experiencing a damaging failure in increasing numbers. It is crucial that the customer service function gather relevant information and communicate it clearly so that management can appropriately escalate the problem and identify the most qualified experts to address the issue. Perhaps just as importantly, we need to determine who we do not need to involve so that they can allocate their time and effort to other important issues.
When people in your organization gather to determine how to address a customer complaint:
- How often are there differences of opinion about the appropriate next steps?
- How long does it take to determine the appropriate next steps?
- How frequently are the wrong people engaged, distracting them from other important activities?
Situation Appraisal: A logical framework for identifying and prioritizing issues. This is especially important when addressing customer complaints where the presenting short-term issue may overshadow more serious long-term concerns. Effectively prioritizing issues and carefully allocating scarce resources is one of the most important elements in a well functioning customer service organization. Kepner-Tregoe’s Situation Appraisal provides a logical framework for prioritizing issues and planning involvement to resolve those issues effectively and efficiently.
Case Study Example
Quality reviewed the information provided by customer service and recognized that they needed to initiate an investigation to determine the cause of BP200 LCD’s not displaying. They had received 47 calls in one day about this one model. The success of this model is critical to our strategic plan to expand in the home health care market.
In addition to minimizing the impact of the issue on customers and the organization, they decided to ask for recommendations on how to contain its effects. The investigation team would be given 24 hours. If we could gather enough data in that time we would focus on solving the problem. If not, we would have to consider recalls, swap-outs, coupons, and the like.
Using the situation appraisal framework, Quality summarized the information and documented their thinking, as shown in Figure 2.
Effective containment requires interim actions and contingent actions to limit the spread of any potential problems associated with the issue. Typically, containment actions are taken before you fully understand the cause. It is important to have accurate documentation of the issue so you can recognize what you don’t know, and consider if what you do know is enough to take action. The data gathered by the customer service function should drive your consideration of possible containment solutions.
Also, when responding to a major customer, you are not selecting a single action but a “course of actions.” Your first response, second response, and third response should fit together into a strategy, and should be triggered by specific trends or thresholds in the data. Consider whether each containment action is reversible, whether it can be over-ridden, and how. Do they build seamlessly, or do they make you appear as if you are thrashing around, trying things out?
When people in your organization initially react to a customer complaint:
- How timely are their responses?
- How appropriate are their responses?
- How well do their responses limit the spread of the non-conformance and its effects on your organization and your customers?
Potential Problem Analysis: Avoiding Risks Inherent in Actions. Potential Problem Analysis helps people efficiently identify measured responses to a customer complaint, and any potential problems or effects that might result. Preventive and contingent actions are established to minimize risks, while promoting and capitalizing actions are established to extend benefits.
Case Study Example
The team decided that, since there were no reports or evidence of injury and the number of cases was still small, there was no immediate need for a re-call or other drastic actions. They did consider how to best manage product already in the field that might begin to display symptoms and how to manage the concerns of customers already experiencing difficulties.
So the team used the logic of potential problem analysis to implement preventive actions to minimize the probability of customers receiving defective units and planned contingent actions to minimize the seriousness if it did happen, as shown in Figure 3.
Finding true cause usually consumes the time and effort of Technical Support Engineers and other Subject Matter Experts. Ideally, when they begin working on the issue, there is a solid baseline of data that can direct them as they switch from passive data collecting to active information seeking. This can include calling key customers and having them test or examine products, having the factory check their production records or QA logs, or having distributors dig through their records. Make sure you have a plan for gathering whatever data is missing, and a way of keeping the data you are working on up-to-date.
When people in your organization investigate issues:
- How much time is spent reworking information that the customer support function could have provided?
- How much time is spent gathering relevant data versus documenting speculations?
- How often do they get to true cause?
Problem Analysis: Finding the Root Cause of Deviations. When something goes wrong, the question is, why? Problem Analysis provides a powerful logic for understanding the root cause of performance deviations. Corrective action that drives business value rests upon a foundation comprised of an effective, systematic logic for finding root cause.
Case Study Example
A number of hypotheses had been generated about the cause of this problem, some based on fact, others on rumor. Certain managers were particularly interested in looking into the new supplier of the LCDs.
The team used the information gathered during the issue identification step to focus their search for additional information and identify relevant changes. Rather than looking for global changes, the team recognized that whatever caused the BP200 LCD not displaying is only affecting BP200s and only began affecting machines on 21 March.
Using this approach they identified 1) the new battery compartment design, and 2) new cellular assembly process as relevant changes, as shown in Figure 4.
The team used this information to develop the hypothesis that employees in the Northborough Plant, now using a cellular manufacturing process where each cell shares all products, are mixing up the battery orientation and battery type between the BP200 with the BP1000. When they use 3 AAA batteries in the lengthwise orientation, the unit will not make contact with the battery compartment and the LCDs will not light.
The team then tested the original hypothesis and the one they developed against the facts they had gathered to assess how well the hypothesis explained all those facts. The original hypothesis about the new vendor could not explain all the facts and was eliminated from consideration.
Employees installing the battery compartment with three AAA batteries lengthwise best explained the facts. They also identified assumptions required to explain the cause and additional information needed to confirm true cause, as shown in Figure 5.
To test this conclusion, the team created a plan to check the returns, and also do some sampling at the stores, to look at the battery orientation and battery type. If the defective units have AAA batteries instead of AA batteries, the cause is confirmed.
These simple checks enabled the manufacturer to find true cause of the customer complaint. The rigorous and timely application of Problem Analysis to the existing data prevented challenging the new vendor, unnecessarily, or the adopting of other expensive alternative courses of action. Redesigning the layout of component parts in the new cellular production area and changing testing protocols prevented recurrence of the problem, improving both productivity and customer satisfaction.
‘When the going gets tough, the tough take really good notes.’ Every time your customers contact you, there is an opportunity to both satisfy their needs and collect valuable information. The initial contact presents an opportunity that may not be available in subsequent communications if customers are not able to remember important details.
How well is your organization using the initial interaction the customer support function has with the consumer to collect information to:
- Track and trend issues in a meaningful way?
- Appropriately escalate issues?
- Choose appropriate containment actions?
- Maximize the effort of specialized resources?
- Find true cause of escalated issues?
The Kepner-Tregoe processes provide a simple framework for integrating the efforts and information gathered by the customer support function into operations, making customer support compliance part of operations, the basis for continuous improvement, and a catalyst for operations excellence.
Founded in 1958, and based on ground-breaking research regarding how people think, solve problems, and make decisions, Kepner-Tregoe provides a unique combination of training and consulting services to improve quality and effectiveness while reducing overall costs. The KT methodology is used at every level of client organizations: to implement strategy, achieve continuous improvement, increase customer satisfaction, and drive effective issue resolution throughout the organization.