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. Integrations
  2. External NLU Adapters

External NLU Adapters

Kore.ai has one of the best NLP engines in the market including the unique Multiengine NLP capability. However, to provide integration flexibility and let the customers use the NLU engine of their preference with other features of the platform, Kore.ai provides an ability to make an external NLU engine co-exist with our built-in NLP engines.

Overview

The Kore.ai XO Platform provides an option to configure and enable an external NLU adapter for your Virtual Assistant so that you can easily use the NLU models built and trained on the other engine. Integration with external NLU engines is provided on the platform as an additional helpful feature for Intent and Entity detection. All other functionalities are managed on the Kore.ai XO Platform. When the adapter is enabled, the external engine’s intent or entity detection takes precedence. However, Kore.ai proprietary NLU acts as a fallback, in case the external engine fails to detect an intent or entity. Additionally, you have the option to continue training intents on the XO Platform while also utilizing previously trained intents from the external engine.

The Build → Integration → External NLU page has the list of available adapters

Note: This is a VA specific configuration. Different VAs in a workspace can use different external NLU engines. In the 10.0 release only the Dialogflow ES adapter is supported. Kore.ai Platform would extend support for other adapters soon.

Adapter Configuration

Steps to configure an external NLU adapter:

  1. Click on the External NLU adapter corresponding to the engine you want to use for intent and entity detection, to configure the settings.
  2. Provide the configuration details required for establishing authorized connection between the Kore.ai and the external engine.
    Note: Authorization keys and other parameters configured here are required by the external engine to allow APIs access.
  3. In the platform specific settings, by default De-identification of PII data is selected as No as shown in the preceding screenshot.
    Note: De Identification of PII data means removing or masking PII data in order to reduce the risk of disclosure of user’s sensitive information that is connected with the data. If the de-identification of PII is disabled for the External NLU Adapter, any API call being made to the external NLU will send the masked PII data in the payload. If you select the option – do not de-identify PII data from the user input, intent or entity detection may not work properly. To know more about PII data, see Redacting Personally Identifiable Information.
  4. Click Save, to save the configurations.
  5. You can check the External NLU connectivity by clicking TEST. On successful completion of the test, the following message is displayed.

    Note: You can configure multiple external adapters but you can enable only one external NLU adapter at a time. You can test the connection for an adapter that has all the mandatory fields configured. The test can be executed even if the adapter is not enabled.
  6. External NLU can be enabled either by updating the configuration setting to Yes under the Enable External NLU Adapter option in the configuration panel, or by using the Enable/Disable option that is displayed on clicking the ellipsis icon.
    Note: Starting from 10.1 released on 16-April-2023, the Universal Bots (UB) allows you to link bots that are using external NLU alongside other bots using built-in NLP. However, the UB dialog tasks and linked bot qualification always use Platform’s built-in NLP.

Note: External NLU is supported only for intent, Entity nodes and FAQs.

See Dialogflow Engine to understand the Dialogflow usage. See Test and Debug to know how to test your virtual assistant to validate the external NLU and to understand the conversation behavior.

External NLU Adapters

Kore.ai has one of the best NLP engines in the market including the unique Multiengine NLP capability. However, to provide integration flexibility and let the customers use the NLU engine of their preference with other features of the platform, Kore.ai provides an ability to make an external NLU engine co-exist with our built-in NLP engines.

Overview

The Kore.ai XO Platform provides an option to configure and enable an external NLU adapter for your Virtual Assistant so that you can easily use the NLU models built and trained on the other engine. Integration with external NLU engines is provided on the platform as an additional helpful feature for Intent and Entity detection. All other functionalities are managed on the Kore.ai XO Platform. When the adapter is enabled, the external engine’s intent or entity detection takes precedence. However, Kore.ai proprietary NLU acts as a fallback, in case the external engine fails to detect an intent or entity. Additionally, you have the option to continue training intents on the XO Platform while also utilizing previously trained intents from the external engine.

The Build → Integration → External NLU page has the list of available adapters

Note: This is a VA specific configuration. Different VAs in a workspace can use different external NLU engines. In the 10.0 release only the Dialogflow ES adapter is supported. Kore.ai Platform would extend support for other adapters soon.

Adapter Configuration

Steps to configure an external NLU adapter:

  1. Click on the External NLU adapter corresponding to the engine you want to use for intent and entity detection, to configure the settings.
  2. Provide the configuration details required for establishing authorized connection between the Kore.ai and the external engine.
    Note: Authorization keys and other parameters configured here are required by the external engine to allow APIs access.
  3. In the platform specific settings, by default De-identification of PII data is selected as No as shown in the preceding screenshot.
    Note: De Identification of PII data means removing or masking PII data in order to reduce the risk of disclosure of user’s sensitive information that is connected with the data. If the de-identification of PII is disabled for the External NLU Adapter, any API call being made to the external NLU will send the masked PII data in the payload. If you select the option – do not de-identify PII data from the user input, intent or entity detection may not work properly. To know more about PII data, see Redacting Personally Identifiable Information.
  4. Click Save, to save the configurations.
  5. You can check the External NLU connectivity by clicking TEST. On successful completion of the test, the following message is displayed.

    Note: You can configure multiple external adapters but you can enable only one external NLU adapter at a time. You can test the connection for an adapter that has all the mandatory fields configured. The test can be executed even if the adapter is not enabled.
  6. External NLU can be enabled either by updating the configuration setting to Yes under the Enable External NLU Adapter option in the configuration panel, or by using the Enable/Disable option that is displayed on clicking the ellipsis icon.
    Note: Starting from 10.1 released on 16-April-2023, the Universal Bots (UB) allows you to link bots that are using external NLU alongside other bots using built-in NLP. However, the UB dialog tasks and linked bot qualification always use Platform’s built-in NLP.

Note: External NLU is supported only for intent, Entity nodes and FAQs.

See Dialogflow Engine to understand the Dialogflow usage. See Test and Debug to know how to test your virtual assistant to validate the external NLU and to understand the conversation behavior.

메뉴