What are the dos and don'ts for building a multilingual bot on Haptik?
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
- Getting Started
- Bot Building
- Conversation Design
Code Step Integration Static Step Integration Shopify Integration SETU Integration Exotel Integration CIBIL integration Freshdesk KMS Integration PayU Integration Zendesk Guide Integration Twilio Integration Razorpay Integration LeadSquared Integration USU(Unymira) Integration Helo(VivaConnect) Integration Salesforce KMS Integration Stripe Integration PayPal Integration CleverTap Integration Fynd Integration HubSpot Integration Magento Integration WooCommerce Integration Microsoft Dynamics 365 Integration
- Agent Setup
- Analytics & Reporting
- Commerce Plus
- Troubleshooting Guides
- Release Notes
Dos for multilingual bots
- Once the bot is ready in English, then you can add languages from the Edit bot option.
Don'ts for multilingual bots
- Do not add User Messagesin languages other than English.
- In the case of Words and Phrases entity, do not add dictionary in languages other than English.
There is a Limitation to Multilingual bots.
When the user initiates the chat with the bot with just one Non-English word, the bot won't be able to detect what the user intends, and it would lead to a Bot Break, or the Bot might respond with a Smart Assist, depending on how it is configured.
On the other hand, the bot would comprehend a Non-English sentence very well at the initiation of the chat, since the bot would have enough information to understand what that sentence is, and what the user is requesting.
- If the user initiates the chat with Oi, which means Hi in Portuguese, the bot won't be able to understand what the user intends to say, as Oi might have many meanings and it is not clear as to what meaning implies here.
- But on the contrary, if the user initiates the chat with Oi preciso de ajuda, which means Hi I need help. In this case, the bot has enough information to understand what the user intends to say.
- The bot would respond accordingly and would give a befitting response in the chat.
There is a solution for this limitation.
- Here, you would have to add a Smart Skill "Language Switcher" in the bot and link it with all the languages your bot supports.
- Open the static step "language change detect" and open the bot responses.
- Open the entity "language_switch_detection", and take the backup of the dictionary.
- Create a new "Words and Phrases" type of entity, and upload this backup in its dictionary.
- Configure your response, and you are done.
So every time the user would initiate the chat with Non-English words, this Language Detection step would get triggered, and it would identify the language.
Once, the language has been identified, the bot would understand the meaning as well as the intent of the message, and accordingly, the bot would give the response to the user.
- In the image shown below, you can see the user has typed Hola, which means Hi in Spanish, after which the bot asked the user which language the user wants to switch to?
- In the Message Log, you can see that the user message Spanish triggered the language change detect step, which later triggered the lang code step, and it detected the language to be Spanish.
- Once the bot has detected the language, it gave a response as Tu idioma ha sido cambiado a español, which means Your language has been changed to Spanish.
- So you see, this saved the chat, and the language detection step avoided the Bot break situation.