Call Center Context Recovery via State Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Call center systems often experience premature disconnections due to network or device failures, forcing callers to reexplain their issues to different agents upon reconnection, leading to inefficiencies and frustration.

Innovation Solution

Implementing a system that stores run-time state information for caller-agent connections, allowing for priority reconnection to the same agent upon reestablishing contact, thereby preserving context and reducing the need for repeated information exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system reconnects callers to available agents after disconnection, then service continuity is improved, but callers may lose context and need to reexplain their issues

Engineering Contradiction:
Improveservice continuityVSAvoidcall context
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by storing call context information in a database before disconnection occurs. When a caller is reconnected, the system retrieves the stored context information beforehand, ensuring that both the caller and agent have the necessary context ready before the conversation resumes, thus preventing information loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary mechanism - a database - that stores and manages call context information. This intermediary preserves the call context between disconnection and reconnection events, allowing the information to be retrieved and presented to the appropriate agent without requiring the caller to reexplain their issue.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the system stores run-time state information for all caller-agent connections, then reconnection efficiency is improved, but system complexity and resource usage increase

Engineering Contradiction:
Improvereconnection efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system applies local quality by storing detailed run-time state information only for specific calls that experience disconnections, rather than uniformly storing information for all caller-agent connections. This selective approach focuses resources on cases where context preservation is most needed, reducing overall system complexity while maintaining reconnection efficiency for affected calls.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes parameters by storing only essential run-time state information (such as call duration, issue type, and partial dialogue) rather than complete call recordings. This parameter optimization reduces the volume of stored data and associated system complexity while still providing sufficient context for effective reconnection.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If the system implements priority reconnection to the same agent, then customer satisfaction is improved, but agent availability and workload distribution may be affected

Engineering Contradiction:
Improvecustomer satisfactionVSAvoidworkload distribution
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic agent assignment by initially attempting to reconnect callers to their original agents, but automatically adapting to assign callers to alternative available agents if the original agent is unavailable. This dynamic approach prioritizes customer satisfaction through familiar agent reconnection while maintaining flexibility to ensure efficient workload distribution across the agent team.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback mechanisms to monitor agent availability and reconnection outcomes. When priority reconnection to the same agent is attempted, the system receives feedback on agent availability and adjusts its behavior accordingly - maintaining the priority reconnection strategy when agents are available while seamlessly transitioning to alternative agents when needed, thus balancing customer satisfaction with workload distribution.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8582750B2Connection recovery in a call center
Publication Date: 2013.11.12 CISCO TECHNOLOGY INC
  • US8582750B2 patent drawing
  • US8582750B2 patent drawing
  • US8582750B2 patent drawing

AI summary

In one embodiment, a method includes detecting termination of a first connection between a first caller and a first agent during a communication session between the first caller and the first agent. The method also includes storing information indicating a state of the communication session at the termination of the first connection, and communicating the information to the first agent or to a second agent in response to establishment of a second connection between the first caller and the first agent or the second agent to facilitate a continuation of the communication session.