Translating Your Responses | Rasa Documentation

Build Your First Agent

Once you've configured your assistant to support multiple languages, you can translate its content directly in the Studio CMS. Rasa enables you to have fine-grained control over translations for all user facing content including:

1. Translate Responses

Use the language dropdown in the top-left corner of the CMS to select the target language for translation.

Your default language will appear on the left as a reference. To make changes to it, return to the default view.

Note: Before starting translations, ensure your default language response is complete and includes all necessary messages, variants, buttons, and links. All translations will reference this default content.

Missing Translation Warnings

When opening the translation CMS for the first time, you may notice some translation warning badges in your responses. This means that you are missing pre-translated content for that response in the language you have selected. Once you have provided a translation in that language for the given response, the warning will be resolved. You can still train an assistant without resolving these warnings.

Enter your translations in the corresponding fields for each target language.

2. Translate Buttons and Links

Buttons and links are listed beneath each response in the CMS.

3. Using the Rephraser

If you want to skip writing manual translations, you can enable an LLM to generate translations during the conversation. Learn more about Rephraser here. To get started quickly, you can enable the Rephraser globally in your assistant settings or on a per-message basis.

📌 Tip: Translations are not required to publish your assistant, but missing translations may impact the experience for users in that language. You’ll see a warning if translations are incomplete.