Enabling Multiple Languages

engati provides a number of capabilities to assist you in building and managing your bots in multiple languages as well as just for non english languages these capabilities span across the various key components of the platform, namely faqs and intents which drive the nlp behaviour as well as the paths or the conversational flows some of the key aspects of these capabilities are – tagging faqs for nlp you can tag and associate faqs and intents to a particular language to better manage them as well as use the nlp models specific to the language the user’s queries are also resolved to keep the language factor in mind localize messages in conversation flows (paths) building different paths for different languages is not needed at all since now you can just build a single path/flow and add the strings for the different languages you are supporting localize settings messages similar to the user facing messages for the respective languages, even the settings, and configurations would be managed by the language properties files this includes, among others, the bot’s name itself, various messages for configurations like user feedback, other fixed messages like writing a message, etc this will allow the user the option to customize these as well as have different messages in different languages synonyms & stopwords for languages you can also have separate sets of synonyms and stopwords based on language which are picked up appropriately by the system using localization in engati using localization in engati availability multilingual capability is present in our professional and above plans enabling localization for your chatbot step 1 navigate to configure > languages and click on "enable" step 2 click on "+add new language" and from the dropdown menu select the language step 3 once you are done selecting the language, click on "add language" after the setup is completed, you can see the screen where the languages are available also, the strings for the various paths and settings of the bots are managed in this section the bot has a default language that it uses to fall back for missing strings for other languages as well as for the faqs/intent lookups the default language initially would be set as english which can be changed we will understand the significance of the default language in more detail in a later section add the other languages which you want to support in the bot using the add new button uploading keys managing localized messages all messages from the conversation flow modeler or various bot configurations, are identified & referred to as keys to make your bot communicate in different languages on engati step 1 in configure > language , download the key files for each language you want to translate to start with the english key as your reference step 2 open the english key file and manually translate all of the text values into the desired language make sure to translate all of the bot's responses and phrases step 3 save your translated file separately as this contains the translated key content step 4 back in the engati platform, upload each translated key file in the configuration area for its language step 5 with the translated keys uploaded, your bot can now understand and converse in multiple languages based on the user's selected preferences step 6 repeat this process to add additional languages as needed to make your bot multilingual note characters \\\ and \\\” are not supported in the uploaded properties file customers are requested not to use these characters and ensure the above characters are not present in the properties file upload history will show an error in case these characters are present in the uploaded file emojis and unicode characters aren’t supported as part of localisation, we would suggest not using them in the path names, flow names or node names as it might have certain inconsistencies faqs & intent in the earlier section, we saw how to set up the language feature as well as manage the messages for the paths and settings by using the keys in the properties file now we will focus on the faqs and intents as highlighted earlier, faqs can be associated with a language hence, you can have multiple sets of faqs, each corresponding to the languages you are supporting in the following steps, we are going to learn how to add faqs for the bot which supports two languages go to the faq workflow from the build section click on add faq for adding the queries and their variations select the language you want to associate the particular faq set with enter the query including the variations and their response and click on add the faq will be added and tagged to the language bot behaviour for resolving queries when a user asks a query, it will look up the faqs stored in the user’s selected language (which is set via the ‘select language node’, explained later) it will also additionally look up the faqs that are associated with the bot’s default locale (if they are different) note in case the bot supports only 2 languages, the nlp engine would look through both the languages irrespective of the user’s selected language or the bot’s default language control the user flow after the translated files are set up for the paths and the faqs are added in the respective languages, we will now learn how the user can change the language or how to determine and set the user’s language the select language node is provided to facilitate the setting of a language in the path define a flow and use the node that allows the user to switch to their desired language once this node is encountered, all the nodes/paths after this node would be displayed in a particular language which is selected here also, the nlp engine would consider it as the set language for the user which it would use to determine the response default language the default language is the language which your bot initially displays by default, it is set to english the bot at any time would have one language which is selected as the default this is used as a fallback language as well in case the user’s language is not set or defined changing the default language this default language can be changed by toggling the radio button for a particular language there are two modes that are supported for changing the default language with different behaviours for each the first option is where you can associate the existing faqs of your bot to the new default language and copy over the missing strings of the original default language to the new one the other mode doesn’t do any additional processing of the faqs or strings and keeps them as is notes this essentially becomes migrating from the old to the new default language and is recommended to be used especially for cases where the localization is set up for the first time and the language needs to be updated to the new one you should make sure that all the necessary strings of your bot are added/updated for the default language as it may result in users seeing the keys in place of missing values additional things to know regarding localization business plan users who are using the stopwords and synonyms feature can segregate these into the supported languages and they will be picked up appropriately based on the user and bot settings there would be no changes in language for the entities, they will continue to be language agnostic and can be managed by having multiple values in the same entity or creating multiple entities for each language and associating them with the relevant language faqs the faq upload via csv would also support a new column that would specify the language association of the faqs the values of the language fields should be the iso639 1 code for the language the train workflow would also support specifying the language the only exception would be when selecting from close matches or via search, the language of the original faq trained would continue to be applicable also, interaction history would show the language from which the query was matched as well via tags best practices for building multi lingual bots best practices for building multi lingual bots 1\ easily change the language make it super easy for the bot user to get to the options for changing languages if you are very sure of their configurations, you can use the select language node for doing it as well as control it via the attributes if you are not sure of their preferences, present the options for selecting language upfront you should also have faqs set up to enable changing/switching languages in all the languages you are supporting, especially the default language since that would be looked up to always 2\ multi language instructions make sure to add the messages for changing the language in all the languages you are supporting this fact goes for any greeting or introductory messages as well which are meant to be generic/language agnostic also, at least the most common keywords/actions, faqs should be ideally supported for all the languages for a seamless experience for everyone 3\ no missing values make sure to review all the strings/messages for all the language you have added to check if anything is missing and if everything is correct, including the settings and default values the user experience would be severely affected if the end user sees keys instead of messages from the bot 4\ avoid using special characters special characters like , “”,^ $,# throw an error for some languages adding them to the key will lead to an error while localizing a bot also while creating attributes n needs to add ‘{{‘ in the key, again it will give erroneous output 5\ language not supported if the language you are supporting isn’t on the list of supported languages, you can select the closest one similar to the language and add your faqs and path messages you can choose to leave it as english as well and the default matching rules engine would be applicable in that case 6\ languages supported the following is the list of 52 languages we support at present arabic bengali bulgarian burmese chinese catalan croatian czech danish dutch english estonian filipino finnish french german greek gujarati hebrew hindi hungarian indonesian italian javanese japanese kazakh 27 kannada 28\ korean 29\ malay 30\ malayalam 31\ marathi 32\ mongolian 33\ nepali 34\ norwegian 35\ persian 36\ polish 37\ portuguese 38\ punjabi 39\ pushto 40\ romanian 41\ russian 42\ slovak 43\ somali 44\ spanish 45\ swedish 46\ tamil 47\ telugu 48\ thai 49\ turkish 50\ ukrainian 51\ urdu 52\ vietnamese references references https //help engati com/nlp nlu capabilities learn more about how to train your bot using engati’s proprietary nlp engine https //docs engati com/documentation/build/conversation flow paths/ learn more about how to build conversation flows https //docs engati com/documentation/tutorial on how to add synonyms and stopwords/ learn more about how engati handles synonyms and stopwords as well as options for you to update these for your bot if you face any issues or queries please reach out to us at mailto\ support\@engati com