Integrating contact centers with Interaction Controls Component (ICC) for callbacks
Summarize
Summary of Integrating contact centers with Interaction Controls Component (ICC) for callbacks
The Interaction Controls Component (ICC) in ServiceNow allows contact centers to implement callback features, enhancing customer experience by enabling callers to receive a callback when agents are available, rather than waiting on hold. This integration improves agent productivity and customer satisfaction by allowing asynchronous communication.
Show less
Key Features
- Callback Modes: There are two operational modes for callbacks: Customer-first and Agent-first.
- Customer-first Mode: Calls the customer first and only connects to an agent once the customer answers, reducing agent idle time.
- Agent-first Mode: Routes the call to an available agent first, who then dials the customer, allowing agents to preview callback context before connecting.
- Unified Workspace: Agents manage callback interactions directly from the ServiceNow configurable workspace, streamlining the process.
Key Outcomes
By utilizing ICC for callbacks, contact centers can:
- Reduce hold times and improve overall customer experience.
- Enhance agent efficiency by minimizing unnecessary calls.
- Provide flexible scheduling options for customers seeking callbacks.
For implementation and management of ICC integration for callbacks, refer to the respective guidelines provided in ServiceNow documentation.
The callback interaction feature built on the Interaction Controls Component (ICC) supports callback voice interactions directly within the ServiceNow configurable workspace. The workspace provides agents with callback voice interaction and callback control features in a unified view, resulting in improved productivity and enhanced customer experience.
Callback feature overview
Contact Center platforms provide a callback feature that lets callers keep their place in line and receive a callback when an agent is available. The callback requests are assigned to agents based on the order they are received. Alternatively, callers may select a specific date and time for a scheduled callback. The Callback functionality enables contact centers to reduce hold times and enhance customer experience by enabling customers to request a return call instead of waiting in the queue. This asynchronous communication model helps balance contact center load and improves both customer satisfaction and agent efficiency. The callback routing can be implemented in two different modes, depending on operational goals and infrastructure: Customer-first and Agent-first. These modes dictate how and when a call is established between the customer and the agent during a callback request.
- Customer-first mode
- In this mode, CCaaS first dials the customer and connects them to an available agent after the customer answers the call.
Callback flow: The callback request is queued. When the callback request reaches the top of the queue and an agent becomes available, the CCaaS dials the customer first. If the customer answers, the CCaaS dials and connects to an agent by routing the call to the agent's inbox in the configurable workspace. If the agent accepts, the call is bridged. This mode reduces unnecessary agent idle time and ensures that an agent is only engaged when a customer answers.
The following image shows the customer-first mode with an immediate (ASAP) callback request on IVR where a customer is dialed before agent is connected. Agent views the callback interaction as any other normal voice interaction in the CSM Configurable Workspace.
Figure 1. Customer-first mode - Immediate callback request - Agent-first mode
- In this mode, CCaaS routes the interaction first to an available agent. The Agent previews the callback context and dials the customer.
Callback flow: The callback request is queued. When the callback request reaches the top of the queue and an agent becomes available, CCaaS routes the interaction to an available agent. The agent accepts the interaction and opens it in ServiceNow configurable workspace. The agent previews the callback context card and then dial the customer. Dialing the customer can be manual or automatic based on a configuration in CCaaS. If the customer doesn’t answer, the agent can redial or close the callback interaction.
The following image shows the agent-first mode with immediate (ASAP) callback request on IVR where an agent is dialed before the customer is connected.
Figure 2. Agent-first mode - Immediate callback request
To manage and activate the ICC integration for callbacks, see Implement the Interaction Controls Component (ICC) for contact center voice call and callback integrations and Plugin requirements for voice and callback integrations with contact centers.