We know how passionate you are about hyper-personalizing your people’s experiences! 🙌

That's why we're happy to announce Multiple Language Support for your Enboarder Journeys. 🎉

This smart new feature will help you localize your Journeys in your employees’ languages in a super simple and effective way!

Multiple Language Support is your magical automatic translation tool built right into Enboarder. It makes it super simple to roll out localized content to your employees globally with just the click of a button, and the eyes of a fluent speaker!

Multiple Language Support is available to all our customers. If you are interested in using this feature, please speak to our friendly support team about having this enabled.

The system now gives you flexibility! We understand that sometimes you might need to launch a journey even if a few non-critical modules haven't been reviewed yet. You now have the option and control to launch a partially translated language if needed.

So best to start small and build your way up! Once you've performed and reviewed these translations, your employees will be able to choose which language they'd like to engage with the content in. Check it out below:

These languages are currently available:

Afrikaans, Albanian, Amharic, Armenian, Azerbaijani, Bengali, Bosnian, Bulgarian, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English, Estonian, Filipino, Finnish, French, French (Canada), Georgian, German, Greek, Gujarati, Haitian, Creole, Hausa, Hindi, Hungarian, Icelandic, Indonesian, Irish, Italian, Japanese, Kannada, Kazakh, Korean, Latvian, Lithuanian, Macedonian, Malay, Malayalam, Maltese, Marathi, Mongolian, Norwegian, Polish, Portuguese, Portuguese (Brazil), Punjabi, Romanian, Russian, Serbian, Sinhala, Slovak, Somali, Spanish, Spanish (Mexico), Swahili, Swedish, Tamil, Telugu, Thai, Turkish, Ukrainian, Uzbek, Vietnamese and Welsh.

For any existing workflows that you have built prior to this functionality being rolled out, you will need to ensure that these workflows are written in the default language of your account. Please liaise with your account team to discuss how we will be able to help migrate these workflows to be able to use multiple language support.

The first time a stakeholder enters Enboarder, they will be prompted to choose the preferred language out of all languages you have translated that specific workflow into.

If, at any point, a stakeholder wishes to update their preferred language, they can do this through their profile.

If a language is chosen that the workflow has not been translated into, the fixed text in the dashboard and buttons within each module will be translated into that language. The stakeholder will then be given the choice of which language they would like to view the workflow in, from the languages that you have fully translated this into.

There needs to be a default (source) language and a destination language. The default language is the language in which the author writes the content. The destination language(s) are the languages in which the content is translated. Your Enboarder account team will be able to help you select your default language.

Once the language is set at the parent account, this will automatically be reflected in the child's account(s). However, child accounts can have this updated in the event they need to set a different default language.

Super admins will be the only admin type that can select which languages are available, as well as whether auto-translation is or isn't used.

When launched into a workflow, employees or managers will be presented with the available languages. Admins now have the option to make a language available even if it is only partially translated. If a language is enabled but not fully reviewed, the employee will see the best available translation, and any missing content will automatically show in the default language.

Note: When an employee or manager selects their second preferred option, or they are shown only the default language, this will not update the preferred language on their profile. This is because the employee or manager may be part of other workflows which has been translated into their preferred language.

Here's an example:

In this situation, Enboarder will display an alert message that this new language will be added across accounts. If you select to proceed with saving the selection, the newly selected language will be added to your account (parent and child accounts where relevant). However, the content in that language will only be available to the employee to read after each module has been marked as reviewed by you.

In this case, you can update the content in your default language and on saving can choose ‘Don’t translate'. This means that content in all other languages won't display this new update.

The correct process would be to add the content to the default language first so that Enboarder is able to translate the content. Adding content to the other languages first and bypassing the default language will cause issues down the line with your content

We have provided an option to re-translate, which is available in the dropdown list of languages, to translate the content to match your most recent updated content in your default language:

While we recommend reviewing all modules to provide a consistent experience, the new system allows you to make a translation available even if it is partial. If you choose to enable a partially reviewed language, All content will either be presented in the translated language or, if missing, will fall back to your default language.

When in the workflow, clicking the flag icon will display how many modules you have marked as reviewed and how many are remaining to be reviewed in each language:

Note: If you have modules in your workflow that do not require translations (such as webhooks or e-sign modules), these will automatically show as reviewed even though you won't have physically reviewed these. So, as an example, even before reviewing any modules, if you have 2 webhook modules in your workflow, it will show 'Reviewed 2/xxx'.

When you click on a language, it will highlight the modules that have been translated with a tick:

This can happen if you have page-level logic enabled on your account and you are looking at a content module.

To review a content page when page-level logic is enabled, the location of the "Reviewed" checkbox is in a slightly different place.

To access the "Reviewed" checkbox, expand out the page-level logic drawer by clicking on the icon:

You will then see the option to mark the page(s) as reviewed here:

Once you enable this feature, you don't need to migrate the old workflows you are happy with. Both old and new workflows using MLS will work.

Text in images, videos and attachments are not translated. Any data displayed from a dynamic token are also not currently translated.

If there are ever any fixed translations (those translations not in your workflow content) that you see aren't quite right, please let our support team know!