This one is far more difficult than it seems. But before we look at the "how", I want you to imagine something. If you are calling up a company and all you want is an address to send something to - or an RMA number - do you:
Keeping the ordinary, ordinary means being able to answer simple queries with the right answer quickly. It's a measure of effectiveness and efficiency, not delight. But what it needs to do it is substantial. First, the technology involved means an extensive knowledgebase that houses the answers to many of the questions that you're being asked. It means access to that knowledgebase in multiple ways - via the contact center in a structured database, with a good search engine to get the answer, and perhaps, with a way for the customer to access the database to get their answer without a CSR in the middle a.k.a. web self service. But how you accumulate the knowledge matters too. One new option is the ability to capture the answers from the web which are being answered outside your firewall and then incorporating them into the knowledgebase AFTER you've been able to validate them.
The second facet of keeping the ordinary, ordinary is having a strong set of processes in place to handle escalation and to head off issues that may come into play during the hunt for the ordinary answer. That means a set of embedded best practices that can be utilized in the moments needed and the triggers and alerts that can automatically escalate something to the right person with the right answers. We've seen that manually when we deal with technical support on a problem and the level l CSR can't solve it so they send it to level 2. But in this case the processes are designed to prevent the ordinary from getting extraordinarily bad.
If you don't think this is important, take heed of a study done by Forrester in 2008 which found that the biggest reason that customers didn't like talking to customer service at companies was poor knowledge management (62%)
Customers are complaining about your brand - or issues they are having with it - and they are doing it well beyond any channels that you provide for them. They don't like dealing with CSRs due to a myriad of reasons ranging from poor training to poor knowledge management (see above) to bad data on them - the customers. So they go to their comfort zone - their peers to complain. For the younger of them in particular but to all of the customers in general, the channels that they would complain on are typically social networks like Twitter, Facebook or other external user community or threaded forum. Keep in mind 74% of all folks who are internet users are on a social networks, and, according to the Nielsen Research "Global Flaces on Networked Places" study of 2009, for the first time, more people communicate via those social networks than email.
How do you find out what the customers are saying? The tools are easily available. For example, Radian6, Attensity, the newly renamed Lithium Social Media Monitoring (formerly known as ScoutLabs) and dozens of others are out there to scour the social web and pull down information on what customers are talking about. Depending on which platform you choose, these are organized into reports that are either time agnostic or immediate. How you choose to respond to the information in the reports e.g a service problem is up to how you've decided to handle these kinds of problems - meaning a protocol in place.
I can't tell you enough about the importance of having an approach with specific details such as:
How you deal with things varies from channel to channel. So how you would respond to a bad blog post would vary from how you respond to an issue found on Twitter. But having a methodology and set of guidelines in place for each channel and the level of problem encountered including who responds is not just important but invaluable.
There is one other bit of outreach to consider. As you probably have noticed, a lot of problems and their solutions are actually being proposed by your customers (if your company rolls that way) on user forums that are out there. There's a big upside to that with a little work and a huge downside to it without that work.
Kind of fun actually.
But there is a problem inherent in that. What if I had something told to me wrongly. There was no one to validate the correctness of the procedure so the only way I could validate it was by assuming that if three videos showed me approximately the same thing they were probably right.
Well, Microsoft sort of gets how to deal with this and they have what, if they are conscious of it, is a model deployment. Their MVPs - their top certified technology guys from outside the company - are active on the user forums - validating the approaches, suggesting others in lieu of incorrect processes. In other words, they are engaged with their customers at the places their customers are interacting providing them with service information that is valuable and valid. A win-win-win for Microsoft, the MVPs and the social customers.
Okay, we've seen what you can do with outreach. Now its time for behind the firewall.
What you might be thinking is "well that means customer service communities" and if that's what you're thinking, you'd be right. If you take a look at some of the best, for example, ACT! or Best Buy or even some B2B communities, what you find is a common thread. Customers are rewarded for their participation in the community. Not for their purchase of goods and services, but instead for their help in solving customer service problems and their addition of knowledge to the knowledgebase of the company. This are the primary reasons for the success of customer service communities that are supported by the company and get the customers involved. There are rewards for doing so. Customers are happy to present their problems there before they get to an angry phone call. It's why first contact resolution becomes a more important metric than first call resolution. With the customer service communities, controlled by the company, behind their firewall, the problem often doesn't get to a call (emphasis mine).
What does this mean for customer service representatives? Possibly a lot. Possibly not much at all. It pretty much depends on how much you want to invest in these new approaches and how much you are willing to change your culture to accommodate them.
Just to level set about the CSRs. We're talking about CSRs who are presumably adequately trained in handling service queries, good, bad or neutral for you already. To give you an idea of how to do this, let me tell you a story - in the form of a short, sweet case study.
This is kind of a segue case study because it actually encompasses not only the changing role of the CSR, should you accept this mission, but supports much of what was said in the prior paragraphs. The segue is to the conclusion. So look back to the prior sections in addition to the current one to get a feel for how Intuit does it, because they do it right - with a clear understanding of how the customer has changed.
I want to start the short study with a quote from an Intuit guy who brought what they were doing to the attention of those on the Social CRM Pioneers site - a site that you would be wise to join on Google Groups.
Scott Wilder of Intuit: "It is easier to teach a call center person how to moderate versus teaching a moderator how to learn about a certain product."
Mr. Wilder is a very wise person.
What Intuit does with that in mind is the following:
Note something here about the CSR. They have in some cases very different responsibilities than they traditionally had, but most of them still carry on with their traditional functions. These new roles are at this time for a select group. But there are new roles, and that's something you wouldn't have said 5 years ago.
The average turnover rate for contact centers is two times greater than it is across all industries. This leads many to consider high agent attrition normal, but the truth is that you can save a lot of money by working to reduce it. more
Owning and operating a business comes with its fair share of ups and downs. That said, the more disheartening moments almost always seem to negatively influence your company’s bottom line. Though by no means an all-inclusive culprit, much of the time, a downtrending bottom line can be accurately chalked up to poor customer service—the numbers back us up on this one. more
We’ve put together a comparison guide that covers over 40 of the top call center software options, providing details on pricing, features, support, and integrations. If you want to save time and still make a great investment, this guide is a must read. more