Skip to main content
Use Translate to translate the text currently in the Zendesk composer. Translate is available in both Email Mode and Chat Mode.

​
Translate a draft

1

Write or generate the reply

Translate requires text in the composer. Type a draft or use Generate / Chat Reply first.
2

Open Translate

Click Translate in the RAUM editor.
3

Choose the target

Select a target language from the searchable language picker, or enable Auto-detect when you want RAUM to choose the target from the ticket context.
4

Run the translation

RAUM reads the live composer text and applies applicable Translate-specific AI Guidelines for the ticket and target language.
5

Review before sending

Check names, product terminology, numbers, legal wording, URLs, and anything your locale-specific support policy treats specially.

​
What happens to the original text?

Translate preserves the existing composer text and appends the translation after a separator. In rich-text composers the separator is rendered as a horizontal rule. In plain-text mode it is represented by a text separator. This makes it easy for an agent to compare the original and translation before deciding what to keep.

​
Searchable language picker

The current app offers 20+ common target languages. The picker includes languages such as:
  • English, Spanish, French, German, Italian and Portuguese;
  • Japanese, Korean and Chinese;
  • Russian, Arabic and Hindi;
  • Dutch, Polish and Turkish; and
  • several Nordic and Southeast Asian languages.
Use the current app selector as the authoritative list because supported language options can expand over time.

​
Translate-specific AI Guidelines

Administrators can mark an AI Guideline for Translate instead of normal Response generation. Translate guidance can be targeted by the same supported Zendesk context and, importantly, by the target language. Use this for rules such as:
  • preferred terminology in one locale;
  • words or product names that must remain untranslated;
  • formal versus informal address;
  • required legal phrasing; or
  • preserving SKUs, order IDs, URLs and codes exactly.
A Translate-only guideline does not shape ordinary Generate replies. Configure AI Guidelines →

​
Auto-detect

When Auto-detect is enabled, the language selector is disabled and RAUM infers the appropriate target from the ticket context instead. Use an explicit target language when the customer’s desired language is known and you do not want the system to infer it.

​
Cached translations

Translate can participate in response caching. If a valid cached result requires an agent freshness decision, the app can offer Use cached or Regenerate before applying it.

​
Email versus Chat Mode

The same Translate panel is used by both modes, but the surrounding workflow differs:
  • Email Mode is intended for longer Zendesk replies.
  • Chat Mode is intended for realtime conversation drafts.
The transformation still starts from the text currently in the composer.

AI Guidelines

Create Response and Translate-specific communication rules.

Chat Mode

Use Translate alongside the other realtime controls.