The emails that go out after a session can be translated along with the rest of the experience. Setting up the sequence itself is covered in Post-experience email sequence.
Which language a participant gets
Emails go out in the language the session ran in. A host running a French session sends French emails to everyone in it. Anything not translated falls back to English, field by field — so an untranslated subject line arrives in English even if the body is in French.
Translating subject lines
Open the experience and go to Translation.
Scroll to the Emails section below the content rows.
Click into the Subject line cell for the language you want and type.
Subject lines behave like any other translation cell: the same badges, the same custom marking when you edit by hand, and the same per-field translate button if your organisation has auto-translate.
If your subject line contains a variable such as the experience title, it's preserved when you translate. Type around it rather than trying to retype it.
Translating email bodies
Bodies are shown in the Translation tab as a read-only preview, because they can contain blocks that pull in session data and don't survive being edited as plain text. To write a body in another language:
Use the globe in the toolbar at the top of the experience to switch your editing language.
Go to the Email tab.
Edit the email as normal — you're now editing that language's version.
You can still trigger auto-translate for a body from its cell in the Translation tab; it's only hand-editing that has to happen in the Email tab.
Sending emails to a translator
Email subjects and bodies are included in the XLIFF export and import, so they travel with the rest of the experience's text. See Working in the Translation tab.