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!
What is it?
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!
Is it available globally?
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.
How does it work?
Once you have activated the Multiple Language Auto-Translate from Settings > General Setup > Languages, you can then pick which languages you'd be interested in using - keep in mind that whatever languages you select, you'd need to review each one before your employees will be able to see it reflected on their end. 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:
The below languages will be available in our first release. Please note, if you do not wish to make use of the auto-translate functionality, we've got you! Simply untick the 'Enable Auto-translate' button. You'll then be able to manually enter content for each of the languages you wish to create.
Don't see your language listed? This is our launch list of languages so head on over to our Community Poll to let us know which languages we could do next!
Translations for existing workflows
This new functionality will work straight away for any new workflows that you create. For any existing workflows that you have built, multi language support will not work by default. Please liaise with your account team to discuss how we will be able to help migrate these workflows across to the new format.
Please see below some important FAQs
What is the importance of having a 'default language'?
There needs to be a default (source) language and a destination language. The default language is 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.
How will default languages work if I have multiple Enboarder accounts?
Once the language is set at the parent account, this will automatically be reflected in the child account(s). However, child accounts can have this updated in the event they need to set a different default language.
Who can choose which languages are supported?
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.
If I have a workflow in 3 languages and now I update the language settings to add one more language, what will happen in that case?
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 this has been marked as reviewed by you.
What if I want to update the content in my default language, but don't want to update the content in other languages?
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.
I updated the content in my default language, chose not to update other translations and now I have changed my mind. What should I do?
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:
I have translated a content module into a language and marked it as reviewed however the employee cannot see the content in that language. Why?
You'll want to make sure all the content modules in a given sequence are translated and marked as reviewed. This is done to provide a consistent experience to the employees. All content will either be presented in the translated language or all content will be displayed in your default language. If any modules are still in the default language or are not marked as reviewed, the employee will view all sequence content in your default language.
How, as an admin will I know how many modules are translated in a given 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:
I'm seeing a "Reviewed 0/1" on a content page, but there is no "Reviewed" check box. How do I mark my page as reviewed?
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:
I have workflows/journeys I do not want to migrate to this new functionality, what can I do?
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.