Skip to main content
Back to App Settings In the case of multilingual AI Agents, while much of the assistant’s behavior doesn’t change with the language, the semantics does impose some restrictions. This document lists the different behaviors that are language-dependent, so you can cater for such scenarios. This article discusses language-specific components for multilingual AI Agents, as well as feature support and behavior, as compared to single language assistants. This article lists the AI Agent 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 NameTypeDescription
App NameStringName of the assistant
App DescriptionStringDescription of the assistant
AI Agent SynonymsObjectArrays 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 AI Agent synonyms.
App Error CodesObjectArrays 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 AI Agent’s Dialog Tasks.
Field NameTypeDescription
Dialog Task NameStringName of the dialog task
Dialog Task DescStringDescription of the dialog task
Dialog Task Upgrade MessageStringMessage 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 NameTypeDescription
Dialog Component IntentStringName of the User Intent node
Dialog Component DescriptionStringDescription of the User Intent node
Dialog Component SynonymsObjectSynonyms for the words in the entity node names. Refer to Managing Synonyms to learn more.
Dialog Component PatternsObjectPatterns 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 App Prompts and Error Prompts fields in the Entity node of the dialog tasks.
Field NameTypeDescription
Message Template TextStringThe text entered in User Responses, App 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 NameTypeDescription
Alert NameStringName of the alert task
Alert Short DescStringDescription of the alert task
Alert KeywordsArrayThe search keywords entered for the alert task
Alert PatternsArrayArray 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 SynonymsObjectArrays 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 PatternsObjectArrays consisting of patterns for each task field. Replace the pattern text with the translated text. Refer to Managing Patterns to learn more.
Alert Ignore WordsArrayArrays 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 MessageStringUpgrade short message related to the alert task.
Alert Upgrade Long MessageStringUpgrade long message related to the alert task.
Alert Query FieldsObjectArrays consisting of key-value pairs of Alert Field Help and Alert Field Title. Replace the text with the translated text.
Alert Payload FieldsObjectArrays 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 NameTypeDescription
Alert Field TitleStringThe title of the user input field related to the alert task, for example, Choose city
Alert Field HelpStringThe 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 PlaceholderStringThe placeholder text displayed inside the field.

App Filters

JSON object consisting of the following translatable components related to app filters:
Field NameTypeDescription
Filter NameStringName of the task filter

IDP Config Form Fields

JSON object consisting of the following translatable components related to IDP configuration form:
Field NameTypeDescription
IDP Form FieldStringName of the IDP Form Field displayed to the end-user in the authentication dialog

Pattern Support

Patterns can be used for Intent detection and Entity extraction. These rules are for AI Agent 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 SyntaxIntent Detection and Entity Extraction - Supported in LanguagesIntent Detection and Entity Extraction - Not Supported in LanguagesSmall TalkTraitsKnowledge Graph
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-YesYesYes
word1_word2 - Enforce phrase, no additional words allowed in between word1 and word2.All languages-YesYesYes
word1 * word2 - 0 to infinite number of additional words between the specified words/phrasesAll languages-YesYesYes
*word1 n word2 - Exactly n number of additional words between the specified words/phrasesAll languages-YesYesYes
*word1 0 word2 - To disable wildcards between two tokens.All languages-YesYesYes
word1 < word2 - Indicates the match for word2 should start from the beginning of a sentence.All languages-YesYesYes
word1 > word2 - Indicates the end of the sentence and no words are allowed after it.All languages-YesYesYes
!abc - Indicates the word/concept “abc” should not exist anywhere in the user utterance after this tokenAll languages-YesYesYes
!!abc - The very next word/concept should not be “abc”All languages-YesYesYes
[ … ] - Used to define a group of words/concepts and the match should be against exactly one of the group declared in [ ].All languages-YesYesYes
{ … } - 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-YesYesYes
( … ) - 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-YesYesYes
<< … >> - Used to find words in any orderAll languages-YesYesYes
’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 patternAll languages-NoNoNo
System Concepts - Support for built-in conceptsEnglish, German, Spanish, FrenchPortuguese (Brazilian), Portuguese (European), Italian, Chinese simplified, Chinese traditional, Indonesian, Korean, Dutch, Japanese, Arabic, Finnish, Russian, Polish, Ukrainian, Swedish, Kazakh, Norwegian, Hindi, Telugu, Tamil, Marathi, Catalan, TagalogNoNoNo
Developer concepts - Support for developer-defined conceptsEnglish, 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*-YesYesYes*
Two-letter identifiers for Dates - Like Mo for Monday, Tu for Tuesday, etcEnglish, German, Spanish, Portuguese (Brazilian), Portuguese (European), Italian, Chinese simplified, Chinese traditional, Indonesian, Korean, Dutch, Japanese, Arabic, Finnish, Russian, Polish, Ukrainian, Swedish, Kazakh, Norwegian, HindiFrench, 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 AI Agents:
NLP FeatureSupported in LanguagesNot Supported in LanguagesSmall TalkTraitsKnowledge Graph
List of Values
Full MatchAll languages---No
Partial MatchAll languages---No
Exact MatchAll languages---No
Ambiguity behaviorAll languages---No
Ambiguity with multi-item selectionEnglishNot supported in any language except English--No
Spell CorrectionEnglish, German, Spanish, French, Portuguese (Brazilian), Portuguese (European), Italian, Indonesian, Korean (from ver7.3), Dutch, Arabic, Finnish, Russian, Polish, Ukrainian, Swedish, Kazakh, NorwegianChinese simplified, Chinese traditional, Japanese, Hindi, Telugu, Tamil, Marathi--Yes
Amend EntitiesEnglishNot supported in any language except English--Yes
Sentiment AnalysisEnglish, 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
App Synonyms (default)English, German, Spanish, French, TagalogPortuguese (Brazilian), Portuguese (European), Italian, Chinese simplified, Chinese traditional, Indonesian, Korean, Dutch, Japanese, Arabic, Finnish, Russian, Polish, Ukrainian, Swedish, Kazakh--Yes
Knowledge Graph
PatternsAll Languages---Yes
Search in AnswerEnglish, 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 CorrectionEnglish, 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 supportAll languages except EnglishEnglish--Yes
NL Engines
Dependency Parser ModelGerman (from ver7.3), French (from ver7.3), Italian (from ver8.0)English, Spanish, Portuguese (Brazilian), Portuguese (European), Chinese simplified, Chinese traditional, Indonesian, Korean, Dutch, Japanese, Arabic, Finnish, Russian, Polish, Ukrainian, Swedish, Kazakh, Norwegian, Hindi---