Contact Centre Monitoring Matters

Because what you don’t record can hurt you

Making sure your call centre monitoring solution is working properly is an ongoing challenge. Whether it’s legal, healthcare, or financial services, large organizations need recordings to satisfy compliance requirements and to resolve legal disputes with customers.

Financial institutions, which I’ll focus on for the sake of this blog post, greatly depend on having all interactions recorded accurately and stored in an easily accessible manner. Contracts could be established through verbal communication or other forms of media like email or instant message. Buy or sell orders could be entered during voice or video calls. It’s crucial these interactions are documented for later reference.

If a regulator comes to your organization and requests a sample of specific recordings on file, you need to be ready to present them. Otherwise, fines start at $25,000 to $50,000 and quickly escalate all the way into the millions. In some jurisdictions, you’re required to pay a percentage of your daily turnover for the period you’ve been out of compliance. That means tens of millions of dollars for some larger global financial institutions. Noncompliance could ultimately result in the suspension of your trading license.

Common Stumbling Blocks

Since making sure all interactions are recorded is so important, what are some common problems that you’ll want to avoid? Recording systems are built on solid, reliable technology. It’s rare for issues to originate in the recording system itself. Instead, the problems usually arise because the recording system lives in an ecosystem. The system must interoperate with a whole range of other solutions, technologies, and hardware. A single problem in any of these other systems can trigger intermittent failure to capture recordings properly.

The most common stumbling block is when a company just assumes the recording system is working properly within its environment. It’ll install the system, get it up and working, and maybe even run a few tests to verify it is capturing recordings. Unfortunately, the system may not be properly integrated with other components of the ecosystem. Configuration glitches, environment issues, or user behavior may result in intermittent failure to record. If that happens, you’ll end up with the false belief that you have all recordings on file.

Once a regulator makes a visit or a company receives a recording-retrieval request for other purposes, it will end up finding out it has absolutely no record of certain calls. It’s simply too late at that point, and the organization will enter into a reactive mode to see where any problems lie. It may then decide to perform testing in the early morning before business opens, and place synthetic calls or human calls to make sure the system is functioning properly.

Unfortunately, these types of tests only give a small sample size, which wouldn’t cover all the potentially different use cases that come into play during regular business hours. Systems operate at variable loads and with differing pathways. Synthetic calls before the start of business are helpful, but real-time monitoring during the course of business can flag the real issues as they happen. Without real-time monitoring the organization might be missing hours of calls before it even realizes a problem has occurred.

Avoid Issues by Staying Proactive

How can you avoid these problems? Doubling up isn’t just expensive, it wouldn’t actually fix the underlying cause. Instead, a good practice is to conduct tests in many different use case scenarios. During the course of the day, a system needs to monitor every step of the ecosystem to ensure the recording system is properly connecting with every individual call. All different forms of media (such as mobile devices, financial system turrets, or traditional call centre systems) need to be taken into account.

Here’s a simplified set of proactive questions you should be asking yourself:

  • Was the call connected to conference in and record the interaction?
  • Was the duration of the call consistent with the file size, indicating that the recording was captured?
  • Was the recording properly transported to the storage system?
  • Can the file be retrieved from storage?

If any of those steps were to fail, or if any other alerts were to come up during a cross-system check, you’d be able to take action in real time before it impacts other users and other interactions.

At the end of the day, reliable call recording is essential. You don’t want to risk rapidly escalating fines, the loss of reputation with customers, or even the risk of losing your trading license. All it takes is some proactive steps on your part to ensure that layers of interoperable technology are working together as they should.

Thank you to no jitter and Integrated Research (IR) for this article

Elevating IVR: Stop the Hatred for Automation

IVR.

In many customers’ minds, this three-letter acronym is a four-letter word. It’s not uncommon for callers to mutter a diverse range of other forbidden words whenever interacting – or trying to interact – with a contact center’s IVR system.

But IVR is not deserving of such hatred. IVR systems are not inherently flawed or evil, nor are the companies that use an IVR to front-end their contact centers. The reason why the general public’s perception of IVR is so negative is that so few of the systems that the public has encountered have been designed properly by the humans behind the scene. The technology itself has tons of potential; it’s what’s dumped into it by organizations overly eager to enjoy the cost-saving benefits of phone-based self-service that makes the machines such monsters.

Not all IVR systems in existence today are so beastly. Some, in fact, not only play nice with customers, they delight them and keep them coming back for more. So how have the owners of these much-maligned systems succeeded in getting callers to drop their pitchforks and torches and embrace IVR?

By adopting the following key practices, all of which I stole from a host of IVR experts and now pass off as my own:

Adhere to the fundamentals of IVR menu design. Most of what irritates and confounds customers with regard to IVR can be easily avoided. Callers often opt out of the system or hang up due to too many menu choices, confusing phrasing/commands, and fear of dying alone in IVR hell.

Here are a handful of essential menu features and functions common to the best-designed IVR applications:

  • No more than four or five menu options
  • The ability to easily skip ahead to desired menu choices (e.g., having the system recognize that the customer pressed “3” or said what they wanted before the system presented such options)
  • Use of the same clear, professional recorded voice throughout the IVR
  • (For touchtone systems specifically) Giving a description of an action/option prior to telling the caller what key to press for that action/option (e.g., “To check your balance without bothering one of our expensive agents, press ‘1’”; NOT “Press ‘1’ to check your balance without bothering one of our expensive agents.”)
  • The ability to opt out to and curse directly at a live agent at any time

Invest in advanced speech recognition. In leading contact centers, traditional touchtone IVR systems are being replaced by sleeker and sexier speech-enabled solutions. While you may not want to listen to a writer who thinks that IVR can be sleek or sexy, you should, as today’s advanced speech recognition (ASR) solutions have helped many customer care organizations vastly improve self-service, and, consequently, reduce the number of death threats their IVR system receives each day.

Powered by natural language processing, ASR systems provide a much more personalized and human experience than traditional touchtone ever could. Traditional touchtone is like interacting with Dan Rathers, while ASR is like talking to Oprah.

Even more importantly, ASR-driven IVR systems enable contact centers to vastly reduce the number of steps callers must take to get what they need. Customers can cut through unnecessary menu options by saying exactly what they want (e.g., “I would like the address of your call center so that I can punch the last agent I spoke to in the face”).

Use CTI to ensure smooth, smart transfers. Even if your IVR system is perfectly designed and features the universally appealing voice of James Earl Jones, many callers will still want to – or need to – speak to a live agent featuring the universally less-appealing voice of a live agent. And when this happens, what’s universally aggravating to callers is – after providing the IVR with their name, account number, social security number, height, weight and blood type – having to repeat the very same information to the agent to whom their call is transferred.

To avoid such enraging redundancy – and to shorten call lengths/reduce costs – leading contact centers incorporate CTI (computer telephony integration) technology into their IVR system. These applications integrate the voice and data portions of the call, then, with the help of magic fairies, deliver that information directly to the desktop of the agent handling the call. With today’s technologies, it’s really quite simple (though, granted, not always cheap), and the impact on the customer experience is immense. Rather than the caller starting off their live-agent interaction with a loud sigh or groan, they start off with the feeling that the company might actually have a soul.

Regularly test and monitor the system. Top contact centers keep a close eye on IVR function and callers’ interactions with the system to ensure optimum functionality and customer experiences.
One essential practice is load-testing any new IVR system prior to making it “open for business”. This involves duplicating actual call volumes and pinpointing any system snags, glitches or outright errors that could jam up the system and drive callers nuts.

Once the IVR system is up and running, leading contact centers frequently test it by “playing customer” – calling the center just as a customer would, then evaluating things like menu logic and speech recognition performance, as well as hold times and call-routing precision after opting out of the IVR.

Some contact centers have invested in solutions that automate the IVR-testing process. These potent diagnostic tools are able to dial in and navigate through an interactive voice transaction just as a real caller would – except with far less swearing – and can track and report on key quality and efficiency issues. Many other centers gain the same IVR-testing power by contracting with a third-party vendor that specializes in testing self-service systems.

Internal IVR testing alone is insufficient to ensure optimal customer experiences with the IVR. The best contact centers extend their call monitoring process to the self-service side. Quality specialists listen to live or recorded customer-IVR interactions and evaluate how easy it is for customers to navigate the system and complete transactions without agent assistance, as well as how effectively the IVR routes each call when a live agent is requested or required.

Today’s advanced quality monitoring systems can be programmed to alert QA staff whenever a caller gets entangled in the IVR or seems to get confused during the transaction. Such alerts enable the specialist – after having a laugh with his peers over the customer’s audible expletives – to fix any system glitches and perhaps contact the customer directly to repair the damaged relationship.

Thanks to Call Center IQ for the article. 

Multichannel and Multimodal Contact Centres: How Do You Know It All works Together?

IQ Services- Contact Centre Testing & Monitoring

The convergence of voice, web, social media and video means that solution providers are coming up with exciting and sophisticated ways to allow users to take more control of their customer service experience. Customers want to decide how they communicate with your company, and how your company communicates with them.

Two of the challenges facing contact centres today are “multichannel” and “multimodal” technologies. This article will explore these terms and introduce some ways to ensure that the performance of these capabilities can be maintained and optimized.

In addition to speaking with an agent, today’s customers have access to a variety of self-service options; they can schedule a service call via the Web or an IVR by logging in with an account number, or they can send an email or chat with an online representative. The availability of multiple touch-points by which a customer can access your company is a multi-channel contact centre solution, with each transaction utilizing just a single channel at a time.

Even a chat session that results in a callback or click-to-call event uses only one channel at a time, even though the contact centre offers up multiple channels.

Enter Multimodal.

Now with SmartPhones and WebRTC, consumers have access to a much richer and potentially more powerful user interface. Add a Bluetooth headset to the SmartPhone and now the user can access the rest of the phone’s features while carrying on a conversation. Consumers are already tapping multimodal capabilities through features like Amazon’s Kindle Fire “Mayday” button and click-to-call interactions with insurance agents that allow the policy holder to take a video of damage to their car and submit it to the agent for an estimate – all while still talking to the agent.

But what about the contact centre side of that multimodal experience?

With SIP pipes into the centre and WebRTC extended to the agents wherever they may be, this multimodal scenario is possible today. But now, in addition to the communications pipes being converged, the content (previously segregated and siloed), must be integrated as well. These are new frontiers for contact centre architectures and just like the technologies that emerged previously (IVR and web self-service, speech reco, CTI, IPT), they will run into some bumps in the road.

And that’s where IQ Services comes in.

IQ Services offers testing and monitoring services that determine whether all your customer facing solutions work as desired under load and continue to be available 24/7 in production.

  • Do you know if an increase in voice traffic adversely affects response time of your web self-service solution?
  • Can your SIP pipes handle the same sudden increase in incoming traffic your old-fashioned TDM boxes handled sitting down?
  • Are you concerned about your process for logging-in remote agents via the web and delivering calls to them?
  • How about proving that your converged queuing process properly elevates high-profile chat customers over lower priority voice customers?

Our systems can easily be configured to interact with your multichannel or multimodal contact centre solutions to ensure it all works together, whether it’s one channel at a time or across multiple channels. The insight we provide will give you confidence that the experience your customers have is the one you intend – one that delivers on your company’s brand promise. Contact us to learn more.

Thanks to IQ Services for the article.

Using Virtual Customers® to Optimize Customer Service Experience

IQ Services VC 101

Providing Contact Centres with Reliable, End-to-End Performance Metrics

Many people believe they are best served by real people, not by voice robots. That’s the rationale behind GetHuman.com. But the economics and utility of self-service as an alternative to live agent interactions are so compelling that self-service solutions are here to stay.

Providing multiple touch-points is a huge technology investment. Technology is great, but you can’t just diligently manage the implementation process and then assume all is well with the customer service experience. Because nothing is static in this world, it is extremely important to confirm from the customer perspective that your contact centre technology really is capable of delivering the experience you intend, one that defends your brand promise and delivers on it every day in production.

In 18 years of supporting clients through the installation phase and into the production phase of the contact centre lifecycle, we’ve learned many lessons about how to best evaluate and optimize the Customer Service Experience (CSE) that is the foundation of delivering your brand promise. This article introduces the process we’ve built based on our experience. It’s a process that ensures the contact centre technologies for which you’ve spent hundreds of thousands of dollars and count on to take care of your customers the way they want to be taken care of is, in fact, offering up the customer service experience you intend, an experience that delivers on your brand promise and doesn’t push customers away.

How?

IQ Services VC 101Introducing the Virtual Customer® Process

The Virtual Customer Process positions the customer service perspective as a key element of your technology management toolkit. It’s a proven process that ensures the customer service experience delivered is aligned with the intentions of the Customer Experience & Brand Management teams, because its first step is identifying key customer types and defining how they will interact with the contact centre technology you put in place. By doing so, the Virtual Customer Process goes beyond using only internal metrics that confirm everything is Working As Designed (WAD), it monitors and measures actual customer service experience as it’s delivered.

Once you have actual Customer Service Experience data, you can create a feedback loop by tweaking your systems and observing the impact on the actual CSE delivered, not just on internal metrics such as CPU time or QoS.

When you know the service experience delivered by your contact centre technologies defends your brand standards, you can also be confident the experience delivered increases satisfaction, builds loyalty and creates advocates.

What is the Virtual Customer Process?

The Virtual Customer Process is a multistep approach that first defines and then deploys Virtual Customers (VCs) to perform real, end-to-end transactions for the purpose of evaluating application and technology performance variables that impact Customer Service Experience.

What are “Virtual Customers?”

Virtual Customers are automated processes that follow test case scripts to interact with the Contact Centre just like real customers, performing real transactions.

How Does the Virtual Customer Process Work?

The first step in the Virtual Customer process is a communications assessment. During this step, key customer activities are identified, the associated Virtual Customer interactions are defined and scripted, and the plan for deploying the VCs so they can collect actionable data is mapped out. The challenge is selecting the best type(s) of VCs to perform the activity required to evaluate contact centre performance. Actionable data is CSE information that can be used to evaluate business solution performance relative to defined CSE objectives and metrics.

Deploying Virtual Customers

Once the VCs are defined and the ramp-up and rollout plans are established, the VCs are deployed as test traffic to access contact centre technololgy from the outside-in, providing your company with reliable, end-to-end performance metrics from the customer perspective.

Key considerations in deploying VCs include:

  • Risk analysis and consequences
  • Section of the right VC interactions
  • Clearly defined availability and performance objectives and metrics
  • Benchmark assessment
  • Reporting and notification criteria

What is CSE Optimization?

  • A process for deploying VCs to collect data that can be used to evaluate and improve business solution performance, relative to defined objectives and metrics
  • An iterative process that tunes CSE delivered

Conclusion

Properly implemented, the Virtual Customer Process® is a critical element of an integrated continuous improvement process. It hones and perfects a customer service experience that defends your brand promise, thereby positively impacting key metrics such as customer effort, customer loyalty, and net promoter score. Experiences that mirror your brand promise ultimately have bottom line impact. Optimizing customer service experience is a direct path to enhancing ROI.

Thanks to IQ Services for the article. 

Testing IVR at the Top of the Stack: How and When to Stay on Top of the Caller Perspective

The IQ Services Difference

In the world of computing technology and communications solutions, the last twenty years have been one revolution after another. Faster processes, niftier appliances, smarter phones, and virtualized services are everywhere. Contact centers have grown from hunt groups and operator consoles to full-blown CRM solutions riding on top of evolving, complex technologies.

Many of us are excited to use the new technologies because of three potentially significant benefits:

  • generate cost savings
  • facilitate increase revenues
  • provide better customer service

Many businesses are really good at tracking the cost savings and revenue generation benefits associated with technology deployment and upgrades. But a recent IQ Services poll revealed that 68 percent of respondents did not have a proactive way to track the customer service quality offered by their IVR and other customer-facing technologies. Some of these businesses use internal monitoring to see if all the individual technologies are working. But they do not have an effective way to test or monitor from the top of the stack or the critical end-to-end caller perspective.

How to Get the Caller Perspective

So how do you get to the “top of the stack” of caller perspective of IVR and end-to-end contact center solution performance and service quality?

Although the answer to this question is “it depends on your business requirements, practices and objectives,” there are four general best practices almost any business can quickly use to get and maintain a holistic view of service quality delivered by customer-facing technologies:

  • secret shoppers
  • customer satisfaction interviews/surveys
  • social media monitoring
  • IVR application testing and monitoring

The first three best practices – secret shoppers, surveys and social media – tend to receive a lot of buzz in CRM and technology circles. There is no lack of information about these critical outside-in techniques for assessing a business’ customer-facing technologies and customer service practices.

IVR Application Testing and Monitoring

Let’s briefly explore the fourth, less explored bullet – IVR testing and monitoring. To ensure IVR and customer-facing technologies perform and deliver the expected service quality, testing and monitoring techniques must be used before and after deployment. Before initial deployment or before any significant change in capacity, infrastructure, or application functionality is finalized, the following testing must be completed to ensure optimal service quality:

Application feature testing: helps ensure the whole application – every logical twist and turn – works as specified

Application load testing: confirms the integrated customer-facing technologies perform as specified under full load

Application usability testing: delivers crucial insight as to whether prospective users/customers are befuddled by the application or they can quickly and efficiently navigate the menu options.

When? Before Deployment

Rigorous application feature testing, load testing and usability testing are required to ensure IVR applications are easy to use and implemented according to business rules. There are so many things to be learned from these techniques:

  • Does the application respond as expected?
  • Are your premium customers treated in the manner you expected?
  • Are unexpected results associated with a particular dialog state or call flow?
  • Does the application “sound” right?
  • Do early smoke test results conducted throughout development indicate discrepancies between the development effort and the design?
  • Do critical flows through the application work as designed?
  • Do global commands work at every state?
  • How does the solution respond to an out-of-grammar or invalid input?
  • What happens after consecutive invalid inputs?
  • How does the system respond to a valid input after invalid input?
  • What happens when an input barges into a playing prompt?
  • What happens if no inputs are made?
  • Does the application perform under expected load? Under peak conditions?
  • Can callers complete the self-service transactions you’d most like to keep in the IVR?

For each best practice and service quality technique, there are a range of approaches that vary in terms of cost, resource commitment, value of insight delivered and more. Each business must evaluate the insight and value against the cost and risks of each approach to determine the right combination.

There’s the manual approach. Since you already have a captive staff to carry it off, you ask your coworkers and employees to use the IVR. They let you know whether or not they think the application flows as the documentation you sent them said it should. You assign each person to a handful of paths selected from hundreds of possibilities and ask them to email the results.

This approach can help minimize front-end costs. But it is not always efficient or effective since your co-workers may be busy and many of the things you need to learn from application testing are hard to uncover without a more structured and automated approach to testing. In the end, you can incur costs you did not plan for with this approach.

You can hire an army of testers – people who are trained to make test calls. With this approach, you can avoid over-burdening your existing staff. However, you may be dealing with the imprecision of people making phone calls, interpreting responses and taking notes. It may also mean you can only test a subset of the application’s functionality.

You might consider buying test equipment.

Automation adds precision. Someone must be trained or hired who knows how to program the test cases, connect the device to the network and run it. The results must still be evaluated and reported.

You could outsource the project. By using a company with facilities and expertise to comprehensively exercise all features of an IVR application, you avoid burdening your overworked team. You also know the most updated techniques and tools are leveraged to test report results.

Whatever option you choose, application testing MUST take place. There is too much at risk to put a system into production without having validated its functionality, usability and robustness.

When? After Deployment

Once an IVR or customer-facing solution is in production, a business must know it keeps working around the clock to take care of your customers.

There is no need to run through all the test cases every hour just to be sure. You need a quick snapshot of how the solution is performing from the caller perspective. Most likely there are a handful of paths through the IVR application that will signal a problem. By running through these paths in the application every few minutes – or even once an hour – you can be confident the overall system is delivery quality service from the caller perspective. As with pre-deployment testing, there are a variety of approaches to monitoring service quality of production technologies, manual calls, purchased equipment or outsourced services.

Whatever approach is right for your business, it is critical that you not simply trust all is well. Immediate warning about issues, daily metrics and other monitoring reports give you the oversight you need to deliver top notch customer service through IVR and self-service solutions.

Stay on top of your IVR and customer-facing technology performance by testing at the top of the stack. You owe it to your customers and to the business stakeholders who expect as much value from the technology as possible.

Thanks to IQ Services for the article.