Cognigy.AI features a powerful Localization concept, that allows for customizability combined with content re-use.
The Localization view allows for the configuration of any number of localizations. The system works with fallback layers, meaning that a Locale that has not any content configured, will fallback to another Locale that has.
With Cognigy.AI 4.10.0 automatic translation of content such as Nodes / Intents has been added to the Cognigy.AI platform. Cognigy's solution is a native integration of leading machine translation providers into the Conversational AI platform.
More details about automatic localization you will find here: Automatc Localization.
Using localization in Flows¶
Localizations act as groupings of specific content and can be applied in Flows by using the Localization drop-down functionality.
When switching Localization, the Flow will change its appearance. "Greyed out" Nodes indicate that they have not been localized yet.
Switch Locale during a conversation
It is possible to change the locale of a flow during a conversation by using the Switch Locale node.
Adding a Locale to a Node¶
When a different Locale is activated in the Flow (by using the drop-down at the top), individual Flow Nodes can be be overwritten with a specific Locale.
This can be done by click on a specific Node and then selecting Add Localization at the top of a Node. As soon as a localization has been added, the Node will be colored again in the Flow Chat, indicating that a localization has taken place.
With Cognigy.AI 4.10.0 the Agent configuration has been extended with a section "Translation Settings".
The configuration options and their functions are listed below:
|Translation Provider||currently available provider with Cognigy.AI 4.10.0:
- Microsoft Translator
- Google Cloud Translation
- DeepL Translate Pro
|Translation Provider API Key||The API Key to use for the Translation Provider.|
|Request Retries||How often to retry calling the translation provider if an error occurs.|
|Request Timeout||How long to wait for the provider to answer a request (in milliseconds).|
|Sentence Cache Expiry Timeout||How long to keep translated sentences in the cache (in seconds).|