Semantic Routing for Customer Service Agent Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional customer service systems are inadequate in determining customer needs and selecting the most qualified agents to address specific customer requirements, leading to inefficient handling of customer contacts and inadequate support for service agents due to their minimal proficiency in handling diverse customer needs across multiple channels.

Innovation Solution

A customer service system that employs intelligent and continuous semantic analysis, combining semantic engines, automatic speech recognition, and adaptive app engines to analyze customer interactions, enrich data, and route contact events to the most suitable service agents based on their skills and attributes, thereby enhancing guidance and resource allocation for both customers and service agents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service agents are tasked with handling a wide variety of customer needs across multiple channels, then the system can handle diverse customer interactions, but service agents receive minimal training and have only minimal proficiency in servicing any given customer need

Engineering Contradiction:
Improveability to handle diverse customer needsVSAvoidservice quality
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments customer needs into specific categories and routes contacts to agents specialized in those categories. Instead of requiring agents to handle all customer needs, the system divides the workload based on agent expertise and customer need classification, improving both specialization and overall service quality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer (semantic analysis engine, contact enrichment module, routing system) between customer contacts and service agents. This intermediary automatically classifies, enriches, and routes contacts to the most suitable agents, eliminating the need for agents to directly interpret diverse customer needs without support.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If conventional CRM systems are used to handle customer contacts, then customer relationships can be managed, but the systems cannot handle the increased complexity created by multi-channel contacts and outdated legacy systems

Engineering Contradiction:
Improveability to handle multi-channel contactsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system creates a universal contact enrichment module that can interface with multiple communication channels (voice, email, social media, text) and legacy systems through standardized semantic analysis. This single module handles diverse contact types and system interfaces, reducing overall system complexity while maintaining high adaptability.

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

Solution Approach 2:

The semantic analysis engine acts as an intermediary layer that translates diverse multi-channel contact formats and legacy system data into a unified semantic representation. This enables conventional CRM systems to handle complex multi-channel contacts without requiring fundamental system redesign.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If conventional CRM systems are used, then customer contacts can be tracked, but the systems cannot understand the meaning of customer requests and cannot automatically improve the process without operator intervention

Engineering Contradiction:
Improveunderstanding of customer request meaningVSAvoidautomatic process improvement
Core Design Contradiction:
Loss of informationVSExtent of automation

Solution Approach 1:

The system enables self-service automation where the semantic analysis engine automatically interprets customer request meaning, enriches contact data, determines appropriate actions, and routes to suitable agents without operator intervention. The system serves itself by automatically improving the contact handling process based on semantic understanding.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual operator interpretation and classification of customer requests with automated semantic analysis technology. Instead of relying on operators to understand customer meaning, the system uses computational semantic processing to automatically extract meaning, classify needs, and initiate appropriate workflows.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Extent of automation

If IVR systems are used to allow users to indicate needs via menu items, then some automation is achieved, but many users incorrectly indicate needs or override the menu to request immediate connection, leaving user needs largely unknown when agents receive contacts

Engineering Contradiction:
Improveautomation of need indicationVSAvoidaccuracy of user need identification
Core Design Contradiction:
Extent of automationVSLoss of information

Solution Approach 1:

The system performs preliminary semantic analysis of customer communications before they reach the agent. By continuously monitoring and analyzing customer interactions across channels, the system builds an enriched understanding of customer needs in advance, ensuring accurate need identification even when customers bypass IVR menus or provide incorrect selections.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10453075B2System and method for meaning driven process and information management to improve efficiency, quality of work, and overall customer satisfaction
Publication Date: 2019.10.22 ALMAWAVE LABS SRL
  • US10453075B2 patent drawing
  • US10453075B2 patent drawing
  • US10453075B2 patent drawing

AI summary

A contact need classification is determined based at least in part on semantic characteristics of contact text or contact audio data from a communication device. A service agent profile is selected from a plurality of service agent profiles based at least in part on the contact need classification. A contact event is initiated with an agent communication device associated with the selected service agent profile.