Contact Center Email Interface with Tracking Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Contact centers face inefficiencies in handling emails, including lack of redundancy, ineffective email management, and limited flexibility in using disparate email systems and clients, which can lead to lost emails and poor customer service.

Innovation Solution

A contact center system with an email interface that integrates with an enterprise email system, allowing for email tracking, prioritization, and routing, while preventing duplicate replies and enabling multiple contact center systems to synchronize and operate redundantly, ensuring email handling across various clients and systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If contact centers use traditional email handling methods, then email storage and basic sending are possible, but email management efficiency is poor and duplicate replies occur

Engineering Contradiction:
Improveemail handling efficiencyVSAvoidemail tracking accuracy
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring email interactions and updating the tracking data structure in real-time. When an email is received, sent, or replied to, the system records these events and uses this feedback to prevent duplicate replies and maintain accurate interaction history, thereby improving email handling efficiency while preventing information loss

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary email tracking data structure that sits between the email interface and the contact center operations. This intermediary layer captures, stores, and manages email interaction data, serving as a mediator that prevents direct duplicate responses while maintaining comprehensive tracking of all email communications

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If contact centers integrate with enterprise email systems, then email access and storage are improved, but system complexity increases

Engineering Contradiction:
Improveemail storage reliabilityVSAvoidsystem integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system achieves universality by designing the email interface to work with multiple email systems and protocols simultaneously. The email tracking data structure and control mechanisms are protocol-agnostic, allowing the system to integrate with various enterprise email systems without requiring separate implementations for each, thus improving reliability while managing complexity through a unified approach

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The email interface acts as an intermediary layer between the contact center system and enterprise email systems. This intermediary abstracts the complexity of different email protocols and storage mechanisms, providing a standardized interface that improves reliability of email storage while hiding the underlying system complexity from the rest of the contact center operations

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If contact centers allow multiple email clients, then agent flexibility is improved, but email management consistency deteriorates

Engineering Contradiction:
Improveemail client flexibilityVSAvoidemail management consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system maintains consistency across multiple email clients by implementing feedback loops that continuously synchronize email interaction data with the central tracking data structure. Each email client receives feedback about the current state of email interactions, ensuring that agents using different clients see consistent information and that duplicate replies are prevented regardless of which client is used

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The email tracking data structure serves as an intermediary that mediates between multiple email clients and the email interface. It maintains a single source of truth for email interaction data, ensuring consistency across all clients by coordinating access and updates, thereby allowing agent flexibility while preserving email management consistency

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of information

If contact centers implement email tracking, then email interaction monitoring is improved, but data management complexity increases

Engineering Contradiction:
Improveemail interaction trackingVSAvoiddata structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the email tracking data structure into distinct, organized components that store different aspects of email interactions separately. This segmentation makes the data more manageable and easier to query, improving tracking capability while reducing the perceived complexity through structured organization of tracking information

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10158600B1Email handling for a contact center
Publication Date: 2018.12.18 SHORETEL INC
  • US10158600B1 patent drawing
  • US10158600B1 patent drawing
  • US10158600B1 patent drawing

AI summary

This disclosure relates to handling email for a contact center. In one example, a contact center system can include an email interface to access an enterprise email system, inbound emails to and from each inbound mailbox in the contact center system being stored and maintained in the enterprise email system. An email tracking data structure can be stored in memory, the email tracking data structure programmed to store interaction data corresponding to each email interaction being processed by the contact center system. An email handling control can be programmed to control sending a reply email to a given incoming contact email from a contact based on the interaction data associated with the given incoming contact email, the reply email being sent to the contact through the enterprise email system via the email interface.