Virtual Agent Registry Engine for Request Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face challenges when submitting requests to virtual agents, as they may not be aware if the selected virtual agent can fulfill the request, leading to time-consuming searches or unfulfilled requests.

Innovation Solution

A registry of virtual agents is implemented to direct user requests to a capable virtual agent, even if the initially selected agent is unable to fulfill the request. This involves a registry engine that identifies suitable virtual agents based on supported intents and confidence scores.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a user selects a virtual agent to submit a request, then the user can interact with the virtual agent, but the user may be unaware whether the virtual agent can fulfill the request, leading to unfulfilled requests or time-consuming searches

Engineering Contradiction:
Improverequest fulfillment reliabilityVSAvoidtime to find capable virtual agent
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis by the registry engine to identify which virtual agents are capable of fulfilling a request before the user needs to know. The registry engine evaluates virtual agents' skills, knowledge bases, and capabilities in advance, so when a user submits a request, the system can quickly redirect to an appropriate agent without requiring the user to search or wait for failure messages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The registry engine acts as an intermediary between the user and virtual agents. Instead of the user directly interacting with a potentially incapable virtual agent, the registry engine receives the request, analyzes it, and redirects to a suitable virtual agent. This intermediary layer ensures reliable request fulfillment while minimizing user effort and time loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system implements a registry of virtual agents to redirect requests, then request fulfillment reliability improves, but the device complexity increases

Engineering Contradiction:
Improverequest fulfillment reliabilityVSAvoidregistry system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The registry engine performs multiple functions within a single component: it maintains the registry of virtual agents, analyzes incoming requests to determine capability matching, identifies suitable virtual agents, and manages redirection. This multi-functionality reduces the need for separate complex systems for each task, thereby limiting the increase in overall device complexity while maintaining high request fulfillment reliability.

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

3Loss of information

If a virtual agent provides an error message when incapable of fulfilling a request, then the user is notified of the failure, but the user is left unsure of what further steps to take

Engineering Contradiction:
Improveinformation about next stepsVSAvoiduser guidance ease
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

Instead of providing a dead-end error message, the system implements feedback by automatically redirecting the user's request to a capable virtual agent. The registry engine monitors which agents can fulfill requests and ensures the user receives constructive feedback in the form of successful request routing, eliminating uncertainty about next steps and maintaining ease of operation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12321868B1Fulfilling requests through a registry of virtual agents
Publication Date: 2025.06.03 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC
  • US12321868B1 patent drawing
  • US12321868B1 patent drawing
  • US12321868B1 patent drawing

AI summary

Disclosed are various embodiments for fulfilling requests through a registry of virtual agents. A request can be received from a first virtual agent. An intent corresponding to the request can be identified, and a second virtual agent associated with the intent can be identified. An identifier for of the second virtual agent can be provided to the first virtual agent.