Technology

Agent empathy, how on Earth can you measure that?

Contact centers, despite the technology, are very people oriented organizations. Their purpose is to service, acquire or retain customers for the organization through personal contacts with the agents. One of the major challenges contact center agents have is sounding genuinely interested in their customers’ problems even when they have already handled dozens of calls about the same subject on the same day. This is the holy grail that is known as “empathy”. Customers buy on emotion. Emotion frequently plays a role even in business to business situations, which is why promotional gifts and corporate hospitality are big business.

 

Not a good approach to customer relations

The Cambridge English Dictionary defines empathy as “the ability to share another person’s feelings or experiences by imagining what it would be like to be in their situation”. I would suggest that agents are not required to feel empathy for the customer, but they have to be able to demonstrate empathy.

First of all, this means recognizing how the customer feels. This is sometimes easier to understand when the customer is on the phone than when the customer is communicating through e-mail or chat. The agents then have to respond appropriately to the customer’s needs and the feelings they have expressed.

To measure how empathetic an agent is, the first question on an evaluation form would be to ask how upset the customer appeared to be. The evaluator will consider the customer’s language including the tone that the customer adopts. In written communications, this can be understood by obvious signs, such as the use of capitals and explanation marks (“!”) or strong language. There are also less obvious signs that might be lost on agents who are not native speakers of the customer’s language. These include the use of adverbs or sarcasm. (“I am just asking you to fix my product” – in this example, the word “just” speaks volumes about how the customer feels.)

The second question is whether the agent’s response was appropriate to the customer’s feelings. For example, if a customer is angry about his product not working, the agent might firstly respond that he sees why the customer is angry and then reassure the customer that he is working on his problem. Many times, when a person shows that he recognizes why the customer is angry, this will reduce the customer’s level of aggression. The customer feels his grievance has been recognized, even if the agent does not necessarily admit responsibility on the company’s behalf. On the other hand, telling a customer to “calm down” will rarely if ever solve anything. The agent who says this is showing that he does not understand why the customer is upset and is, in effect, dismissing his feelings as irrational behavior.

To drive the desired agent behavior, you will need to give agents high scores for correctly identifying when a customer is angry and further high scores for giving responses that show an understanding of how the customer feels. Low scores on these questions will lead to conversations about how to recognize customers’ feelings or how to respond correctly to specific situations where a customer is angry or upset. These conversations will focus agents on how they can handle customers’ feelings as skillfully as they handle the customer’s issue with the product.

 

 

 

Bookmark and Share

Quality management. It’s not just about saving money!

Technology vendors in the contact center market frequently sell their technology by presenting their clients with a Return On Investment (ROI) calculation. This is usually along the lines of how much money an organization can save by reducing Average Handling Time or increasing First Call Resolution.

Contact centers are service delivery organizations, so are airlines and hotels. Airlines usually buy their aircraft from the same manufacturers. They all fly similar routes and at the same speed. Most hotel rooms contain an en suite bathroom, TV and double bed. Breakfast is usually served as a buffet. The differentiation is in the service. It’s the service and positive customer experience that keeps customers loyal to brands when there are cheaper alternatives.  It’s the service and positive customer experience that turns customers into fans.

Great service that sets an organization apart from the rest is not achieved by good luck, nor is it achieved by magic. Good service is achieved by developing a robust and rigorous set of standards,  making sure that staff are trained to handle all eventualities in accordance with these standards and running frequent checks and feedback sessions to ensure that standards are properly adhered to.

Excellent service: technology, passion and hard work combined

To achieve this in the contact center environment, the contact center needs the right technology to enable them to monitor interactions, evaluate them quickly, impartially and accurately and deliver the feedback to agents.

What the contact center also needs is hard work from the management team itself. Success in contact centers comes from what people do. Someone has to listen to and evaluate the calls, and then give agents the appropriate feedback and follow up. Missing evaluations is like taking your eye off the ball when playing competitive tennis. It will result in failure.

Petra Kvitova, Wimbledon women's champion 2011, keeping her eye on the ball.

Like most matches, the battle to achieve great service is won by a little bit of technology and know how and a lot of determination and persistence.

Bookmark and Share

ZOOM CallREC release 4.4.1 – What's new there

It has been a few days since we released the next version of our flagship product – ZOOM CallREC, version 4.4.1.paper plane
It’s a minor release; however there are some important new features and improvements.

Let me briefly describe what has been achieved and how it helps to improve usability, and make CallREC a more robust product.

Multi-Server Setup
Multi-Server deployment was already supported by CallREC; however we have improved the setup process itself. Version 4.4.0 already introduced a new installer, but it didn’t specifically support multi-server deployments and you had to do a lot of changes manually. Now during installation you can easily choose what the server role will be, where the other servers are and prepare almost all the required configuration steps. The only step missing now is NFS file sharing; this must still be done manually.

Full Implementation of IPP Libraries
This one is really technical, so what does it mean for “ordinary people”? IPP stands for “Integrated Performance Primitives” and is an Intel software product. Intel defines it as “an extensive library of multicore-ready, highly optimized software functions for digital media and data-processing applications”. Wow!
Basically, Intel provides optimized software libraries for media processing, which we’ve decided to use instead of our existing media processing tools (these libraries were already present in the recently released 4.3 version).
We have replaced the decoding libraries that handle all the G.whatever codecs (G.711, G.722 and G.729). This first step brought us a significant performance boost and  now we have made another step—we have replaced the encoding part (the libraries that are responsible for mp3 encoding). We were previously using open source libraries that had occasional issues, which had already caused us long-term pain. Now with IPP we have a much more stable and reliable media encoding part.
The side effect is that we can no longer support the Speex codec for recorded calls. Speex was officially discontinued in version 4.3 (although it was still available) and has now finally been removed. We believe this will not be an issue, since only a few CallREC users ever tried to use it and no one has been using Speex in a production environment.

Genesys Integration Module Improvements
The Genesys Integration Module went through a substantial redesign last year. The vast majority of changes were implemented in the latest 4.3.2 release. Now all of them (and a couple of new ones) have been ported to the 4.4.1 release as well.
Among the changes, such as improved reliability and efficiency in attaching the related call data, there is a really interesting feature—you can choose what external data will be attached and saved in the database (regardless of T-Server properties, attached data or configuration information). Some customers use tens of different attached data, so in some cases we were saving 70-80 different key-value pairs for every call, even if they used just a few.
The database performance impact is obvious. Now we can precisely set up what information will be stored and what will not.

Improved GUI Search Performance for Large Databases
The database and its associated parts are now one of the most closely monitored components and is the focus of a lot of development work. Changes in database structure and related components are planned for the next major releases, but we wanted to improve performance sooner—and on top of the current structure.
Fortunately we were able to implement some tweaks that have a big impact, boosting the database and GUI search performance significantly for external data. The tradeoff is that you need to stick to the recommendations and there are a few small limitations, but it flies!

Bug Fixes
No software is perfect and CallREC is no exception. There are several bug fixes in the Multimedia Management Tools (MLM), the Migration Tool (a Swiss army knife for upgrading data from one version to another) and in the setup scripts.
Last (but not least), CallREC version 4.4.1 includes Apache Tomcat application server version 6, which itself solves some issues encountered when running GWT based applications—such as ZOOM ScoreCARD.
There’s still a lot of work to do to make CallREC the “best solution in the world”. It’s a challenge for us and we’re working hard to deliver the best we can. Stay tuned—there are loads of exciting new features to come. And of course, we’ll be only too happy to share them with you…

Bookmark and Share