Pretty Good Practices
In This Issue
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.
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).
- 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.
- 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.