GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
LLM and Generative AI Logs
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Composite Entities
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. Docs
  2. Process Apps
  3. How To Articles
  4. How to Pass Meta-information During Agent Transfer

How to Pass Meta-information During Agent Transfer

As part of your Virtual Assistant design, you can choose the scenarios where you want to hand off the conversation to human agents. As part of this hand-off, it is important to pass the current conversation context to the Agent Hand-off / CCaaS system. This information can be used in the CCaaS system to set the requisite skills, routing rules, and so on.

The XO Platform offers an extensible framework for handling agent transfer conversations. Within this framework, you can pass any additional metadata you want to share with the agent. This capability allows agents to access supplementary information about the user’s details or queries in advance, enabling them to handle the conversation more efficiently.

How this works

  • The XO platform has introduced a new agent metadata object. This metadata object is currently supported for ServiceNow and Genesys agent integrations, with each integration having its own dedicated metadata object. The naming conventions for these metadata objects are as follows:
    • ServiceNow Agent: “ServiceNowMetaData”
    • Genesys Agent: “GenesysMetaData”
  • The XO platform offers a built-in utility function called “agentUtils.setMetaInfo” to facilitate the exchange of additional information with the agent metadata context object. Developers are expected to leverage this function to set any supplementary data they wish to share with the agent.
  • This function can be utilized anywhere the platform allows the definition of JavaScript code, providing developers with flexibility in integrating custom metadata at various points within the conversational flow.

Set the additional information in the metadata object

  • Before the agent transfer node gets executed in the platform, you need to set the additional information in the metadata object.
  • For example, if you want to set the employee’s “Employee ID” and “Department” in the metadata, a script can be used to set the information in the context, as shown in the screenshot below.

  • The values from the context can be used to set the metadata.
    • For example, if you have collected employee data using entities and wish to pass the gathered entity values to the agent system, you can dynamically define the values by leveraging the entity information available within the context object.
let metaData = {
“EmployeeID”: context.entities.EmployeeID
“Department”: context.entities.Department
}
agentUtils.setMetaInfo("GenesysMetaData", JSON.stringify(memberInfo))

How to access the Metadata in the Genesys agent

As part of the Genesys Bot connector setup, you need to make Get and Set the participant data that needs to be transferred to the agent. The metadata shared by you will be available in the form of attributes in the Genesys agent system. Then you need to set the attributes that need to be shared with the agent using the “SetParticipantData” action in the Genesys bot connector before transitioning to the “ Transfer to ACD” action.

Follow these steps:

  1. In the Genesys agent, click Add attribute in the “SetParticipantData” settings and provide the Key-value pairs that are passed as part of the metadata.
  2. Click Save and then click Publish.

  3. Once the agent transfer call is initiated, the additional metadata is available to the agent at Performance > Workspace > Interactions > Interaction Selected > Participant Data.

How to Pass Meta-information During Agent Transfer

As part of your Virtual Assistant design, you can choose the scenarios where you want to hand off the conversation to human agents. As part of this hand-off, it is important to pass the current conversation context to the Agent Hand-off / CCaaS system. This information can be used in the CCaaS system to set the requisite skills, routing rules, and so on.

The XO Platform offers an extensible framework for handling agent transfer conversations. Within this framework, you can pass any additional metadata you want to share with the agent. This capability allows agents to access supplementary information about the user’s details or queries in advance, enabling them to handle the conversation more efficiently.

How this works

  • The XO platform has introduced a new agent metadata object. This metadata object is currently supported for ServiceNow and Genesys agent integrations, with each integration having its own dedicated metadata object. The naming conventions for these metadata objects are as follows:
    • ServiceNow Agent: “ServiceNowMetaData”
    • Genesys Agent: “GenesysMetaData”
  • The XO platform offers a built-in utility function called “agentUtils.setMetaInfo” to facilitate the exchange of additional information with the agent metadata context object. Developers are expected to leverage this function to set any supplementary data they wish to share with the agent.
  • This function can be utilized anywhere the platform allows the definition of JavaScript code, providing developers with flexibility in integrating custom metadata at various points within the conversational flow.

Set the additional information in the metadata object

  • Before the agent transfer node gets executed in the platform, you need to set the additional information in the metadata object.
  • For example, if you want to set the employee’s “Employee ID” and “Department” in the metadata, a script can be used to set the information in the context, as shown in the screenshot below.

  • The values from the context can be used to set the metadata.
    • For example, if you have collected employee data using entities and wish to pass the gathered entity values to the agent system, you can dynamically define the values by leveraging the entity information available within the context object.
let metaData = {
“EmployeeID”: context.entities.EmployeeID
“Department”: context.entities.Department
}
agentUtils.setMetaInfo("GenesysMetaData", JSON.stringify(memberInfo))

How to access the Metadata in the Genesys agent

As part of the Genesys Bot connector setup, you need to make Get and Set the participant data that needs to be transferred to the agent. The metadata shared by you will be available in the form of attributes in the Genesys agent system. Then you need to set the attributes that need to be shared with the agent using the “SetParticipantData” action in the Genesys bot connector before transitioning to the “ Transfer to ACD” action.

Follow these steps:

  1. In the Genesys agent, click Add attribute in the “SetParticipantData” settings and provide the Key-value pairs that are passed as part of the metadata.
  2. Click Save and then click Publish.

  3. Once the agent transfer call is initiated, the additional metadata is available to the agent at Performance > Workspace > Interactions > Interaction Selected > Participant Data.
메뉴