AI Workflow Policy Generation for Customer Support Ticket Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional customer support systems face inefficiencies due to the reliance on human agents for ticket labeling, routing, and response generation, leading to delays, high labor costs, and frustration for customers, especially when dealing with complex or non-routine questions.

Innovation Solution

The implementation of an AI-augmented customer support system that utilizes machine learning models to automatically generate responses, route tickets, and assist human agents by providing suggested answers and knowledge articles, leveraging historical data and natural language processing to improve response accuracy and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If human agents manually search and label customer support tickets, then accurate categorization can be achieved, but response time increases and labor costs rise

Engineering Contradiction:
Improveticket categorization accuracyVSAvoidticket response time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary automated labeling and routing of tickets before human agents review them. Machine learning models pre-categorize tickets and suggest appropriate agents, so that when human agents do review tickets, the heavy lifting of initial classification is already done, reducing their search time while maintaining accuracy through human-in-the-loop verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An AI assistant acts as an intermediary between incoming tickets and human agents. The system automatically generates suggested labels, routes tickets to appropriate queues, and provides context summaries to agents, serving as a mediator that prepares work before human intervention and reduces the cognitive load on agents.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If human experts manually label and route tickets, then accurate routing decisions can be made, but labor costs and operational delays increase

Engineering Contradiction:
Improverouting decision accuracyVSAvoidticket processing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service routing where tickets automatically route themselves based on ML-predicted categories and agent availability. The AI assistant autonomously assigns tickets to appropriate agents or queues without requiring manual expert intervention for routine cases, while still allowing human experts to override decisions when needed, thus maintaining reliability while scaling throughput.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically adjusts routing parameters based on real-time conditions such as agent workload, skill levels, and historical performance. Machine learning models continuously learn from routing outcomes and adjust routing strategies, changing the parameters of the routing decision process adaptively to maintain high accuracy while optimizing for speed and resource utilization.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If a small number of ticket categories are used, then easier management and agent training is achieved, but adaptability to handle diverse customer issues is reduced

Engineering Contradiction:
Improveagent training easeVSAvoidticket category coverage
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system segments the ticket classification task into multiple hierarchical levels. Instead of forcing agents to master a single flat taxonomy, the ML model automatically creates multi-level categorizations (broad categories → subcategories → specific issue types) based on the actual content of tickets. Agents work with simplified high-level categories while the system handles the complexity of fine-grained classification, maintaining ease of operation while achieving high adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The category structure is made dynamic rather than static. The ML model automatically discovers and creates new categories as emerging ticket patterns are detected, and the taxonomy evolves over time based on actual customer issues. This allows the system to adapt to diverse issues without requiring manual restructuring of the entire category hierarchy, maintaining ease of use while increasing versatility.

Inventive Principle:
Principle #15Dynamics

4Reliability

If extensive institutional knowledge is made available to agents, then better support quality can be provided, but agents face practical difficulties in accessing and using all available knowledge

Engineering Contradiction:
Improvesupport qualityVSAvoidknowledge access complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the most relevant institutional knowledge for each specific ticket and presents it to the agent, rather than displaying all available knowledge articles. The ML model analyzes the ticket content and selectively retrieves pertinent documentation, case studies, and solutions, filtering out irrelevant information. This maintains support quality by providing targeted knowledge while reducing complexity by eliminating information overload.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The manual process of agents searching through extensive knowledge bases is replaced with an automated AI assistant that performs semantic search and knowledge retrieval. The system uses natural language processing to understand ticket context and automatically fetch relevant institutional knowledge, replacing the mechanical searching process with intelligent automation. This maintains comprehensive knowledge access while simplifying the agent's interaction to simple queries and suggestions.

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

Data Source

PatentUS20240386214A1System and method of automatically generating a natural language workflow policy for a workfow for customer support of emails
Publication Date: 2024.11.21 FORETHOUGHT TECH INC
  • US20240386214A1 patent drawing
  • US20240386214A1 patent drawing
  • US20240386214A1 patent drawing

AI summary

A natural language workflow policy is generated for a workflow to solve customer support tickets is automatically generated from representative tickets. Tools, such as API calls, may also be automatically generated from representative tickets. In one implementation, a clustering technique may be used to identify representative answers for particular customer support topics. The generated workflows may be used by a large language model to generate answers for customer questions for an autonomous AI chatbot agent.