Summary
You can translate email channel phishing scenarios into every language your company uses. This includes scenarios you created from scratch and library scenarios you duplicated. Adaptive translates scenario content with AI. You can then edit any translation by hand.
Employees get the scenario in their preferred language when your campaign is set to Localize scenarios to match employee's language. To learn more about your localization options for phishing campaigns, see Localizing phishing campaigns.
Before you start
Set your company languages first. When you translate custom content, we’ll use this list to determine which languages that content should be translated into. Open the scenario's Languages card and click Update languages, or go to your company language settings. To learn more, see Company Languages.
Note that English is the source language for all translations. This means it’s the source of truth for all other languages you support: edits made to the English source variant can be translated into all other languages via one click.
Only scenarios that start via the email channel can be translated. Scenarios that start with a text message or a phone call do not currently support translations.
Spoof pages and fail pages for email channel scenarios are translated.
Translate a scenario built from scratch
Open the scenario and click Edit on the phishing email.
In the Languages card, click Generate translations.
When the translations are done, open the language menu in the Languages card to view each language.
To translate one language again, open the language menu, click the ⋮ next to the language, and select Retranslate.
Edit a translation
In the Languages card, select the language.
Edit the subject, sender name, or email body.
Click Save Message.
A translation you edit by hand shows Modified. When you update translations later, Adaptive does not overwrite your edits unless you choose to.
Sender details across languages
When you change the sender name, subdomain, or domain on the English source email, the change applies to every language automatically.
You can set a different sender name or subdomain for one language. After you do, later changes to the English sender name or subdomain won’t overwrite that language’s value.
The domain is the same for all languages. This is true whether or not your company uses SMTP or domain-managed email. To change it, edit the source email.
Retranslating after you change the English source email
When you change the text or formatting of the English source email and save, translations for this email show as Out of date. This includes changes to the subject, the body, and rich text formatting such as bold or links. Changes to the sender name, subdomain, or domain don’t make translations outdated. See Edit a translation for how sender details work across languages.
In the Languages card, choose one of the following to bring translated variants back up to date:
Update Translations: Adaptive translates the changes you made to your scenario. You choose which languages to update, and whether to overwrite translations you edited by hand.
Keep current translations: the current translations stay as they are and show as up to date.
Outdated translations keep sending until you update them.
If you leave the editor with unsaved changes, Adaptive asks if you want to save, discard, or keep editing. It also tells you how many translations will become outdated if you save.
Delete a translation
You can delete a language's translation when a scenario should only go out in some languages.
In the Languages card, open the language menu.
Click the ⋮ next to the language and select Delete translation and confirm.
Employees who have that language preference will receive the email in the original source language in new campaigns. The language shows No translation. To translate it again, select Translate for that language.
Note: Update Translations also translates languages you deleted. To keep a language deleted, update languages one at a time.
Translation statuses
In the Languages card of the scenario details page, you'll find five different statuses representing the state of its translations:
No Translations
This scenario has no translations. All employees will receive it in the source language.
Updating
Adaptive AI is currently translating your scenario.
Up-to-Date
All translations are up to date. The count includes the source language.
Outdated
The source email changed after these languages were translated.
Error
These translations failed. Update them to try again.
In the scenario library, each card shows how many languages the scenario sends in. The count is orange when some translations are outdated.
Adding scenarios to a campaign
When you add a scenario to a new campaign, Adaptive warns you if the scenario is missing translations or has outdated translations. This applies to company scenarios and library scenarios.
If a scenario is missing or has outdated translations, you can proceed with creating a campaign. Languages with no translation send the source language email, and outdated translations still send.
Good to know
Translation changes apply to new campaigns. A campaign that’s already running keeps the versions that existed when you created it. This is true when you edit a language, edit the English source, or generate a translation for a language that didn’t have one.
When you duplicate a library scenario, its existing translations are copied too.
Upload HTML saves the email right away, because Adaptive checks the file first. Translations become outdated when the uploaded email changes the body.