Why is it importantOur new multilingual-bot-(MLB-)feature enables you to show your bot in different languages instead of needing separate bots for your different customer bases. This reduces the maintenance effort tremendously. However, there are also some use cases where going with MLB might be not sufficient. Here is an overview of pros and cons for both approaches that help you decide for the smartest setup for your specific use case. Best PracticesIn short:Go with MLB whenever possible: If only the wording or the text/images differ per country. If the content, the behavior, and the intended appearance of your bot strongly differs across languages (or country pages), the MLB feature might not work for you. Here is why:In general, we always advice you to go with the MLB-approach whenever possible because: You can handle all changes in one bot, reducing the amount of maintenance tremendously. The bot adapts automatically to your page's language (after inserting one line of code) or uses the browser language of the end user. The end users can switch the bot language by themselves.You see analytics and performance of one bot across all languages.However, based on the limitations of MLB, there are points to consider as listed in this table: Feature/TopicMLBSeparate botsSame content, structure, appearance, and behavior, only different languages. This is what the MLB feature has been built for Not recommended.Different topics/bot structures per language or per country page Small adjustments (e.g. showing one solution only for one language) can be solved with channel variables. If the content differs strongly, this bot will get messy though.Define the complete structure and content per bot. BUT: Several bot set ups and multiplied maintenance.Different brands/behavior/look and feel/tone of voice in different countries/languages The appearance (colors, behavior) cannot be defined per language. However, you can adjust the tone of voice per language in the same botDefine the appearance and behavior per bot. This is recommended especially if you have separate brands within your company.Different handover instances, e.g. different email addresses based on country. Small adjustments (e.g. showing one solution with a specific handover only for one language) can be solved with channel variables. Routing based on languages is possible in most CRMs based on the different subject line. However, thefallback handover will always be the same across the whole bot.  Define separate email addresses, handovers, or modules in every bot. BUT: more maintenance effort.Reporting Currently, we show one Analytics dashboard across the whole bot. This means you'll have a performance overview across all languages, but no separation into different languages. If this is important to you, please reach out to your contact person as we offer some manual workarounds. With one Dashboard per bot, you can see the performance per bot that has a specific language. BUT you'll have to add up the numbers manually across all bots for overall KPIs. Free Text Input (NLP-Feature) Currently only works for the default bot language if this language is one of the supported languages for NLP.Works for the default language of every separate bot, as long as this language is supported for NLP.Additional ResourcesFind more info on the MLB feature in these articles: Translations in the Solvemate WidgetAdding translations in the Web AppTranslations - Requirements & Limitations