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
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Kore.ai XO GPT Model
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
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
SDK Security
SDK Registration
Web Socket Connect and RTM
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
SDK Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Data Tables and Views
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On (SSO)
Two-Factor Authentication (2FA)
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Advanced Topics
  5. Language Management
  6. Multilingual VAs: Components & Feature Support

Multilingual VAs: Components & Feature Support

In the case of multilingual VAs, while much of the assistant’s behavior does not change with the language, the semantics does impose some restrictions. In this document we will list out the different behaviors that would be language-dependent, so you can cater for such scenarios.

This article discusses language-specific components for multilingual VAs, as well as feature support and behavior, as compared to single language assistants. 

This article lists the VA elements for which you can provide language-specific values. You need not translate Standard Responses as the Platform automatically translates them when you enable a language.

Metadata

JSON object consisting of the following translatable elements

FIELD NAME TYPE DESCRIPTION
Bot Name String Name of the assistant
Bot Description String Description of the assistant
Bot Synonyms Object Arrays of important words in the task names and their corresponding synonyms. Enter translation of the words as well as their synonyms. Refer to Managing Synonyms to learn more about bot synonyms.
Bot Error Codes Object Arrays of error codes and their corresponding messages. Enter translations of the error message. Refer to Customizing Error Messages to learn more about error messages.

Dialog Tasks

JSON object consisting of the following translatable components of your VA’s Dialog Tasks.

FIELD NAME TYPE DESCRIPTION
Dialog Task Name String Name of the dialog task
Dialog Task Desc String Description of the dialog task
Dialog Task Upgrade Message String Message displayed to the developer on the History page for the upgraded task

Dialog Components

JSON object consisting of the following translatable components related to the NLP settings of a dialog task.

FIELD NAME TYPE DESCRIPTION
Dialog Component Intent String Name of the User Intent node
Dialog Component Description String Description of the User Intent node
Dialog Component Synonyms Object Synonyms for the words in the entity node names. Refer to Managing Synonyms to learn more.
Dialog Component Patterns Object Patterns for the User Intent and Entity nodes in the dialog task. Refer to Managing Patterns to learn more.

Message Templates

JSON object with arrays of Message Template IDs and Message Template Text values. They correspond to the User Responses field in the Message node and the Bot Prompts and Error Prompts fields in the Entity node of the dialog tasks.

FIELD NAME TYPE DESCRIPTION
Message Template Text String The text entered in User Responses, Bot Prompts, or Error Prompts fields in any Message or Entity node of a dialog task.

Alert Task

JSON object consisting of the following translatable components of your assistant’s Alert Tasks.

FIELD NAME TYPE DESCRIPTION
Alert Name String Name of the alert task
Alert Short Desc String Description of the alert task
Alert Keywords Array The search keywords entered for the alert task
Alert Patterns Array Array of patterns related to the alert task’s name. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Field Synonyms Object Arrays consisting of synonyms for each task field. Replace the field name and the synonyms with the translated text. Refer to Managing Synonyms to learn more.
Alert Field Patterns Object Arrays consisting of patterns for each task field. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Ignore Words Array Arrays of ignore words related to the alert task. Replace the words with the translated text. Refer to Managing Ignore Words and Field Memory to learn more.
Alert Upgrade Short Message String Upgrade short message related to the alert task.
Alert Upgrade Long Message String Upgrade long message related to the alert task.
Alert Query Fields Object Arrays consisting of key-value pairs of Alert Field Help and Alert Field Title. Replace the text with the translated text.
Alert Payload Fields Object Arrays consisting of key-value pairs of Alert Payload fields. Replace the text with the translated text.

Alert Fields

JSON object consisting of the following translatable components in the API Request tab of the Alert task.

FIELD NAME TYPE DESCRIPTION
Alert Field Title String The title of the user input field related to the alert task, for example, Choose city
Alert Field Help String The help text displayed below the field title to describe the task, for example, Which city would you like to get weather alerts for?
Alert Field Placeholder String The placeholder text displayed inside the field.

Bot Filters

JSON object consisting of the following translatable components related to Bot filters

FIELD NAME TYPE DESCRIPTION
Filter Name String Name of the task filter

IDP Config Form Fields

JSON object consisting of the following translatable components related to IDP configuration form

Field Name Type Description
IDP Form Field String Name of the IDP Form Field displayed to the end-user in the authentication dialog

Pattern Support

We have seen in this document, how Patterns can be used for Intent detection and Entity extraction. These rules are for VAs in the English language. In other languages, there may be differences. 

Patterns can be used in Small Talk (while defining queries), Knowledge Graph (using alternate question fields), and Trait identification but their behavior might differ slightly. The table below provides an overview of how this may occur.

PATTERN SYNTAX INTENT DETECTION AND ENTITY EXTRACTION SMALL

TALK

TRAITS KNOWLEDGE

GRAPH

SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES
word1 word2 … wordn

This mandates all the words defined to be available in the user utterance in the same consecutive order with additional words allowed in between, before and after

All languages Yes Yes Yes
word1_word2

Enforce phrase, no additional words allowed in between word1 and word2.

All languages Yes Yes Yes
word1 * word2

0 to infinite number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *n word2

Exactly n number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *0 word2

To disable wildcards between two tokens.

All languages Yes Yes Yes
word1 < word2

Indicates the match for word2 should start from the beginning of a sentence.

All languages Yes Yes Yes
word1 > word2

Indicates the end of the sentence and no words are allowed after it.

All languages Yes Yes Yes
!abc

Indicates the word/concept “abc” should not exist anywhere in the user utterance after this token

All languages Yes Yes Yes
!!abc

The very next word/concept should not be “abc”

All languages Yes Yes Yes
[ … ]

Used to define a group of words/concepts and the match should be against exactly one of the group declared in [ ].

All languages Yes Yes Yes
{ … }

Used to define an optional group or words/concepts and the match would be against zero or one of the words/patterns declared in { }.

All languages Yes Yes Yes
( … )

contain a pattern i.e when a pattern or part of a pattern is enclosed in these parentheses, we treat it as a pattern unlike [ ] and { }.

All languages Yes Yes Yes
<< … >>

Used to find words in any order

All languages Yes Yes Yes
‘word1

If you quote words or use words that are not in canonical form, the system will restrict itself to what you used in the pattern

All languages No No No
System Concepts

Support for built-in concepts

English,

German,

Spanish,

French

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog,

Portuguese (European)

No No No
Developer concepts

Support for developer-defined concepts

English,

German,

Spanish,

French,

Portuguese (Brazilian)*,

Italian*,

Chinese simplified*,

Chinese traditional*,

Indonesian*,

Korean*,

Dutch*,

Japanese*,

Arabic*,

Finnish*,

Russian*,

Polish*,

Ukrainian*,

Swedish*,

Kazakh*,

Norwegian*,

Hindi*,

Telugu*,

Tamil*,

Marathi*,

Catalan*

Yes Yes Yes*
Two-letter identifiers for Dates

Like Mo for Monday, Tu for Tuesday, etc

English,

German,

Spanish,

Portuguese (Brazilian),

Portuguese (European),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

French,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog

No

* in these cases, developer concepts are not supported in entity extraction

NLP Support

Here are the NLP features supported by Multilingual VAs:

NLP FEATURE SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES SMALL TALK TRAITS KNOWLEDGE GRAPH
List of Values
Full Match All languages No
Partial Match All languages No
Exact Match All languages No
Ambiguity behavior All languages No
Ambiguity with multi-item selection English Not supported in any language except English No
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean (from ver7.3),

Dutch,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Japanese,

Hindi,

Telugu,

Tamil,

Marathi

Yes
Amend Entities English Not supported in any language except English Yes
Sentiment Analysis English,

German,

Spanish,

French,

Dutch,

Korean (from ver7.3),

Japanese (from ver8.0),

Russian (from ver8.0),

Kazakh (from ver8.0),

Norwegian,

Tagalog,

Portuguese (European)

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Arabic,

Finnish,

Polish,

Ukrainian,

Swedish,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

Yes
Bot Synonyms (default) English,

German,

Spanish,

French,

Tagalog

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh

Yes
Knowledge Graph
Patterns All Languages Yes
Search in Answer English,

German (from ver7.3),

Spanish (from ver7.3),

French (from ver7.3),

Portuguese (Brazilian) (from ver7.3),

Italian (from ver7.3),

Indonesian (from ver7.3),

Dutch (from ver7.3),

Finnish (from ver7.3),

Polish (from ver7.3),

Swedish (from ver7.3),

Tagalog,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Korean,

Japanese,

Arabic,

Russian,

Ukrainian,

Kazakh

Yes
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean,

Dutch,

Arabic,

Finnish,

Polish,

Swedish,

Ukrainian

Russian (from ver8.0),

Kazakh (from ver8.0),

Japanese (from ver8.0),

Portuguese (European)

Chinese simplified,

Chinese traditional,

Catalan,

Tagalog

Yes
Special Character support All languages except English English Yes
NL Engines
Dependency Parser Model German (from ver7.3),

French (from ver7.3),

Italian (from ver8.0)

English,

Spanish,

Portuguese (Brazilian),

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

Multilingual VAs: Components & Feature Support

In the case of multilingual VAs, while much of the assistant’s behavior does not change with the language, the semantics does impose some restrictions. In this document we will list out the different behaviors that would be language-dependent, so you can cater for such scenarios.

This article discusses language-specific components for multilingual VAs, as well as feature support and behavior, as compared to single language assistants. 

This article lists the VA elements for which you can provide language-specific values. You need not translate Standard Responses as the Platform automatically translates them when you enable a language.

Metadata

JSON object consisting of the following translatable elements

FIELD NAME TYPE DESCRIPTION
Bot Name String Name of the assistant
Bot Description String Description of the assistant
Bot Synonyms Object Arrays of important words in the task names and their corresponding synonyms. Enter translation of the words as well as their synonyms. Refer to Managing Synonyms to learn more about bot synonyms.
Bot Error Codes Object Arrays of error codes and their corresponding messages. Enter translations of the error message. Refer to Customizing Error Messages to learn more about error messages.

Dialog Tasks

JSON object consisting of the following translatable components of your VA’s Dialog Tasks.

FIELD NAME TYPE DESCRIPTION
Dialog Task Name String Name of the dialog task
Dialog Task Desc String Description of the dialog task
Dialog Task Upgrade Message String Message displayed to the developer on the History page for the upgraded task

Dialog Components

JSON object consisting of the following translatable components related to the NLP settings of a dialog task.

FIELD NAME TYPE DESCRIPTION
Dialog Component Intent String Name of the User Intent node
Dialog Component Description String Description of the User Intent node
Dialog Component Synonyms Object Synonyms for the words in the entity node names. Refer to Managing Synonyms to learn more.
Dialog Component Patterns Object Patterns for the User Intent and Entity nodes in the dialog task. Refer to Managing Patterns to learn more.

Message Templates

JSON object with arrays of Message Template IDs and Message Template Text values. They correspond to the User Responses field in the Message node and the Bot Prompts and Error Prompts fields in the Entity node of the dialog tasks.

FIELD NAME TYPE DESCRIPTION
Message Template Text String The text entered in User Responses, Bot Prompts, or Error Prompts fields in any Message or Entity node of a dialog task.

Alert Task

JSON object consisting of the following translatable components of your assistant’s Alert Tasks.

FIELD NAME TYPE DESCRIPTION
Alert Name String Name of the alert task
Alert Short Desc String Description of the alert task
Alert Keywords Array The search keywords entered for the alert task
Alert Patterns Array Array of patterns related to the alert task’s name. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Field Synonyms Object Arrays consisting of synonyms for each task field. Replace the field name and the synonyms with the translated text. Refer to Managing Synonyms to learn more.
Alert Field Patterns Object Arrays consisting of patterns for each task field. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Ignore Words Array Arrays of ignore words related to the alert task. Replace the words with the translated text. Refer to Managing Ignore Words and Field Memory to learn more.
Alert Upgrade Short Message String Upgrade short message related to the alert task.
Alert Upgrade Long Message String Upgrade long message related to the alert task.
Alert Query Fields Object Arrays consisting of key-value pairs of Alert Field Help and Alert Field Title. Replace the text with the translated text.
Alert Payload Fields Object Arrays consisting of key-value pairs of Alert Payload fields. Replace the text with the translated text.

Alert Fields

JSON object consisting of the following translatable components in the API Request tab of the Alert task.

FIELD NAME TYPE DESCRIPTION
Alert Field Title String The title of the user input field related to the alert task, for example, Choose city
Alert Field Help String The help text displayed below the field title to describe the task, for example, Which city would you like to get weather alerts for?
Alert Field Placeholder String The placeholder text displayed inside the field.

Bot Filters

JSON object consisting of the following translatable components related to Bot filters

FIELD NAME TYPE DESCRIPTION
Filter Name String Name of the task filter

IDP Config Form Fields

JSON object consisting of the following translatable components related to IDP configuration form

Field Name Type Description
IDP Form Field String Name of the IDP Form Field displayed to the end-user in the authentication dialog

Pattern Support

We have seen in this document, how Patterns can be used for Intent detection and Entity extraction. These rules are for VAs in the English language. In other languages, there may be differences. 

Patterns can be used in Small Talk (while defining queries), Knowledge Graph (using alternate question fields), and Trait identification but their behavior might differ slightly. The table below provides an overview of how this may occur.

PATTERN SYNTAX INTENT DETECTION AND ENTITY EXTRACTION SMALL

TALK

TRAITS KNOWLEDGE

GRAPH

SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES
word1 word2 … wordn

This mandates all the words defined to be available in the user utterance in the same consecutive order with additional words allowed in between, before and after

All languages Yes Yes Yes
word1_word2

Enforce phrase, no additional words allowed in between word1 and word2.

All languages Yes Yes Yes
word1 * word2

0 to infinite number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *n word2

Exactly n number of additional words between the specified words/phrases

All languages Yes Yes Yes
word1 *0 word2

To disable wildcards between two tokens.

All languages Yes Yes Yes
word1 < word2

Indicates the match for word2 should start from the beginning of a sentence.

All languages Yes Yes Yes
word1 > word2

Indicates the end of the sentence and no words are allowed after it.

All languages Yes Yes Yes
!abc

Indicates the word/concept “abc” should not exist anywhere in the user utterance after this token

All languages Yes Yes Yes
!!abc

The very next word/concept should not be “abc”

All languages Yes Yes Yes
[ … ]

Used to define a group of words/concepts and the match should be against exactly one of the group declared in [ ].

All languages Yes Yes Yes
{ … }

Used to define an optional group or words/concepts and the match would be against zero or one of the words/patterns declared in { }.

All languages Yes Yes Yes
( … )

contain a pattern i.e when a pattern or part of a pattern is enclosed in these parentheses, we treat it as a pattern unlike [ ] and { }.

All languages Yes Yes Yes
<< … >>

Used to find words in any order

All languages Yes Yes Yes
‘word1

If you quote words or use words that are not in canonical form, the system will restrict itself to what you used in the pattern

All languages No No No
System Concepts

Support for built-in concepts

English,

German,

Spanish,

French

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog,

Portuguese (European)

No No No
Developer concepts

Support for developer-defined concepts

English,

German,

Spanish,

French,

Portuguese (Brazilian)*,

Italian*,

Chinese simplified*,

Chinese traditional*,

Indonesian*,

Korean*,

Dutch*,

Japanese*,

Arabic*,

Finnish*,

Russian*,

Polish*,

Ukrainian*,

Swedish*,

Kazakh*,

Norwegian*,

Hindi*,

Telugu*,

Tamil*,

Marathi*,

Catalan*

Yes Yes Yes*
Two-letter identifiers for Dates

Like Mo for Monday, Tu for Tuesday, etc

English,

German,

Spanish,

Portuguese (Brazilian),

Portuguese (European),

Italian,

Chinese simplified,

Chinese traditional,

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian,

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

French,

Telugu,

Tamil,

Marathi,

Catalan,

Tagalog

No

* in these cases, developer concepts are not supported in entity extraction

NLP Support

Here are the NLP features supported by Multilingual VAs:

NLP FEATURE SUPPORTED IN LANGUAGES NOT SUPPORTED IN LANGUAGES SMALL TALK TRAITS KNOWLEDGE GRAPH
List of Values
Full Match All languages No
Partial Match All languages No
Exact Match All languages No
Ambiguity behavior All languages No
Ambiguity with multi-item selection English Not supported in any language except English No
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean (from ver7.3),

Dutch,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Japanese,

Hindi,

Telugu,

Tamil,

Marathi

Yes
Amend Entities English Not supported in any language except English Yes
Sentiment Analysis English,

German,

Spanish,

French,

Dutch,

Korean (from ver7.3),

Japanese (from ver8.0),

Russian (from ver8.0),

Kazakh (from ver8.0),

Norwegian,

Tagalog,

Portuguese (European)

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Arabic,

Finnish,

Polish,

Ukrainian,

Swedish,

Hindi,

Telugu,

Tamil,

Marathi,

Catalan

Yes
Bot Synonyms (default) English,

German,

Spanish,

French,

Tagalog

Portuguese (Brazilian),

Italian,

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh

Yes
Knowledge Graph
Patterns All Languages Yes
Search in Answer English,

German (from ver7.3),

Spanish (from ver7.3),

French (from ver7.3),

Portuguese (Brazilian) (from ver7.3),

Italian (from ver7.3),

Indonesian (from ver7.3),

Dutch (from ver7.3),

Finnish (from ver7.3),

Polish (from ver7.3),

Swedish (from ver7.3),

Tagalog,

Portuguese (European)

Chinese simplified,

Chinese traditional,

Korean,

Japanese,

Arabic,

Russian,

Ukrainian,

Kazakh

Yes
Spell Correction English,

German,

Spanish,

French,

Portuguese (Brazilian),

Italian,

Indonesian,

Korean,

Dutch,

Arabic,

Finnish,

Polish,

Swedish,

Ukrainian

Russian (from ver8.0),

Kazakh (from ver8.0),

Japanese (from ver8.0),

Portuguese (European)

Chinese simplified,

Chinese traditional,

Catalan,

Tagalog

Yes
Special Character support All languages except English English Yes
NL Engines
Dependency Parser Model German (from ver7.3),

French (from ver7.3),

Italian (from ver8.0)

English,

Spanish,

Portuguese (Brazilian),

Chinese simplified,

Chinese traditional

Indonesian,

Korean,

Dutch,

Japanese,

Arabic,

Finnish,

Russian

Polish,

Ukrainian,

Swedish,

Kazakh,

Norwegian,

Hindi

Menu