Traditional contact center business intelligence (BI) has been very useful for understanding overall metrics and workforce management. But a large – and critical – gap exists at the agent level. Data collection typically can’t see into an agent’s entire suite of applications. If it could, it would offer very fast insights on some of the seemingly unintelligible aspects of agent behavior.

This shortfall can be seen in some of these areas:

• Lack of insight into agent activity. Tracking average handle time (AHT) is relatively simple, from tracking call beginning and end times from the switch. But contact centers have very little visibility into specific agent activities during the course of a call. Some things to consider: Why do certain call types take three minutes? What happens during those three minutes?
  
  
• What applications or pages are navigated? What information is being copy-and-pasted? What application or page is in focus for the largest percentage of time? And calls and workflows might span as many as eight to 10 applications, so capturing user metrics across these applications is important for identifying process bottlenecks.
  
  
• Lack of real-time visibility into compliance violations. This includes multiple types of compliance violations: government regulations, do-not-call lists, client or partner restrictions or lack of adherence to desired business process flows.
  
  
• Lack of timely identification of undesired customer activity or positive opportunity. Real-time data on agent/application interactions can provide tip-offs that a liability such as an account cancellation is in progress, or an opportunity, like an up-sell, is possible, and quickly trigger responses.
  

There are probably other gaps that you can recall from your own experience. The next section discusses current solutions.

Solution: Agent Operations and Execution

Contact center analysts hunting for better performance often see several main data strategies for analysis and improvement. One, call management and analytics, is a mature field that uses tools to judge and improve call processing by analyzing the structure of the call itself. A common goal is improving First Call Resolution (FCR). Another, described as “augmenting or alternate technologies,” can include self-service channel alternatives to direct agent interaction. These channels include Voice Response Units (VRU) and Web-based applications such as account access and Frequently Asked Questions.

However, consider an alternative: real-time data support to agent operations and execution. This approach is based on how the agent uses and interacts with the assigned suite of desktop and other enterprise applications to handle calls and resolve problems. Data-wise, it’s possible to collect each mouse movement or click of any application running on the desktop, including Web-based and streaming, such as Citrix. This data is much more granular, and can be applied in a number of solution areas, such as:

Identifying business process bottlenecks. Newer data collection technologies have made this significantly faster and much more precise than, for example, Six Sigma analysts standing behind agents with stopwatches or regularly reviewing calls and screening recordings.

And once bottlenecks and pain points are identified, it is possible, using the same technology platform used to capture the events, to quickly construct automations to remove human interaction from the process. Examples include eliminating the cutting-and-pasting of large amounts of data, concurrently eliminating data errors, by automatically synchronizing customer data between the CRM application and any others on the desktop, and, taking it a step further, by allowing data entered in one application to be pushed to, and update, all other applications automatically.

Identifying compliance violations in real time, and alerting appropriate staff. The monitor-and-automate ability of the technology platform described can extend any application or groups of applications to easily generate alerts, flexibly, based on virtually any user action or specific workflow sequence. For example, if an agent issues a credit above a pre-defined limit, a manager is automatically alerted.

Identifying critical actions and triggering responses, such as workflows, based on real-time events. For example:

• Compliance adherence. Real-time agent data can trigger automations to restrict and report. An above-the-limit funds transfer can trigger an immediate freeze or cancellation of the action as soon as it is detected and before it can be executed. The event is detected, and complex automations stop the transaction, report the attempt to management, and immediately restrict access. Or, in a common scenario, routine but required Federal, State, or local regulatory statements, prompts, and disclosures can automatically display at any step during a call, and assurance logic can be added to confirm that the agent has communicated (orally, by fax, by email, etc.) the information to the customer.
  
  
• Call escalation. Customers are routinely identified by category and value when calling, and certain transactions can alert specialists elsewhere in an enterprise who can assist or intervene. Account cancellation is one example. If an agent is servicing a high-value client though a CRM system and starts an account cancellation process, an alert automatically starts a call or screen recording and sends an SMS alert to a call center manager.
  
  
• Up-sell offers. Database matching logic can quickly associate customer data with sales offers on the back end, and an automation can then trigger the offer to the agent’s desktop in a timely fashion for a rapid close.
  

Extend the process to virtual agents. Turning real-time data into action is not restricted to human agents. Self-service operations and applications can be extended in the same fashion, opening opportunities for sales, enhanced service and compliance, and even intervention by a human agent at any point in a customer contact.

Accessing Real-Time User Data

As stated earlier, much of a contact center’s data is limited to what is provided by the switch or IVR. Most contact centers can tell you what their average call times are but have little or no hard data to document the business process workflows that occur during the call. There is a general lack of data about the interaction between agents and the (often) many applications used by an agent to handle a call.

The good news is that such data does readily exist. Every application accessed by an agent requires some form of user interface (including a browser for cloud/SaaS applications), which in turn relies upon the underlying Windows operating system as a central connection point for the user. Every mouse click, every character entered into a data field, every check box, every interaction that an agent has with an application creates an event that is communicated between operating system and application. By accessing this flow of communication between the operating system and applications, you gain tremendous insight into the real activities of agents.

There are technologies on the market today that enable you to readily access this information and put the events in the proper context. This gives you insight into what is occurring within the applications themselves or in workflows that span multiple applications.

The events that you monitor and act on are under your total control. For example, you might want to track every agent event and pass that information into a business intelligence system for identifying process bottlenecks. You might discover, for example, that 40 percent of your average call is spent navigating multiple applications to find the same set of customer information. In this scenario, you could then employ an automation solution that pre-navigates applications to the proper customer records in order to shorten call times.

You might decide that you want to only capture real-time events when an agent is committing a compliance violation. For example, you might set up an alert anytime an agent changes a customer credit limit beyond a pre-defined ceiling. Or, you might set up an alert when an agent closes out a call without confirmation that a government-mandated disclosure statement has been read, or even if the agent fails to add call wrap-up notes to a CRM application.

As it relates to quality management, you might leverage real-time agent activity to trigger a call recording system. In this scenario, you might trigger and tag a call recording anytime an agent opens an account cancellation screen or accesses a high-value client in a CRM system.

The possibilities are endless once you are able to tap into the rich world of agent activity occurring at the desktop level.