> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Real-time translation for sessions

> Translate customer messages into your agents’ language and agent replies into the customer’s, with a glossary for terms that must stay as written.

Real-time translation lets customers and agents each write in their own language. Customer messages are translated into your agents' language, and agent replies are translated into the customer's language before they are sent. Turn it on when your team supports customers in languages your agents don't speak.

> [!NOTE]
>
> **Settings → Translations** in your [OpenCX dashboard](https://platform.open.cx/settings/translations). Requires the **Translations** permission in [Roles](https://docs.open.cx/security/roles.md): **Read** to view, **Write** to change the switches or the glossary.

## Settings

![Turning on Translate customer messages in Settings, Translations, and choosing Polish as the target language for agents](https://mintcdn.com/openchat/hiyaCL2S28Hya6Q7/images/settings/translation-on.gif?s=b945ce00f0a39f14a07841489e6055f9)

Turn on Translate customer messages, then pick the language agents read. Each change saves on its own.

| Setting | What it does | Default |
| - | - | - |
| **Translate customer messages** | Translates incoming customer messages into the target language below | Off |
| **Target language for agents** | The language agents read customer messages in. Shown while **Translate customer messages** is on. | English |
| **Translate agent responses** | Translates agent and workflow replies into the session's language before they are sent | Off |
| **Translation glossary** | Terms kept exactly as written in every translation | Empty |

The two switches are independent: you can translate only one direction. Translation is off for the workspace while both are off.

If your workspace uses a connected helpdesk such as Zendesk or Salesforce, turning on the first switch shows a **Compatibility with** notice: translation works in the OpenCX chat widget, and not for email or forms handled in that helpdesk. Select **Continue** to turn it on anyway.

## What agents see for customer messages

Customer messages are translated as they arrive once a person is handling the session: after the AI agent hands off, when a teammate is assigned or takes over, or when the AI only drafts replies for agents. Messages that arrive while the AI agent handles the session on its own are kept as written. A message already in the target language is not translated.

In the [inbox](https://platform.open.cx/inbox), a translated customer message shows the translation. To compare, open the message's menu and select **Show original message**: the **Original Message** dialog shows what the customer wrote next to what the agent sees. AI suggestions are shown in the agent's language too; see [AI suggestions when customer messages are translated](https://docs.open.cx/inbox/intro.md#ai-suggestions-when-customer-messages-are-translated).

## What happens to agent replies

When **Translate agent responses** is on, the composer shows **Reply will be translated to** and the customer's language while an agent writes a reply in a session whose language is known. Internal comments are never translated.

* The reply is sent in the session's language. The agent keeps seeing what they wrote; **Show original message** shows the version the customer received.
* A reply already in the customer's language, such as a [translated macro](https://docs.open.cx/ticketing/macros.md#translate-macros-automatically) or an unedited AI suggestion, is sent as written.
* A session needs a known language. If it has none yet, OpenCX detects it from the customer's recent messages when an agent opens the session; if it can't tell with confidence, replies in that session are sent as written. Phone sessions are not detected.
* Messages sent by workflows are translated the same way.

### Channels

| Where the reply goes | Sent translated |
| - | - |
| Web chat widget, email sent from OpenCX, SMS, WhatsApp, Instagram, Messenger, X, app store reviews, Slack | Yes |
| Sessions linked to a HubSpot or Intercom conversation | No: the agent's original text is posted there |
| Email that a connected helpdesk sends for you, such as a Zendesk ticket | No: the agent's original text is posted there |

## Keep terms consistent with the glossary

Add product names, plan names and other terms that must never be translated. In **Translation glossary**, select **Add term**, enter the **Term** and a **Translation note**, such as "Keep as Dashboard in all languages", then select **Add term** in the dialog. Both fields are required.

* Every translation keeps the term exactly as written; the note gives context for the rest of the sentence.
* For session messages, the glossary applies only while one of the switches is on. The page says so while translation is off.
* [Automatic macro translations](https://docs.open.cx/ticketing/macros.md#translate-macros-automatically) also keep your glossary terms as written, whether or not real-time translation is on. They use the term only, not the note.

## Other ways OpenCX translates

| Feature | What it translates | Where to set it |
| - | - | - |
| Real-time translation (this page) | Session messages, for every agent and the customer | **Settings → Translations** |
| [Translate messages in your view](https://docs.open.cx/inbox/intro.md#translate-messages-in-your-view) | Only what you read, in your browser. Needs Google Chrome. | A session's **More options → Translation** |
| [Macro translations](https://docs.open.cx/ticketing/macros.md#translate-macros-automatically) | Your macros, translated once ahead of time | **Settings → Macros** |
| [Help Center translations](https://docs.open.cx/help-center/translations.md) | Help Center articles and categories, with their own glossary | Your Help Center's language settings |

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| Customer messages are not translated | The AI agent is still handling the session on its own | They are translated once a person handles the session. Use [Translate messages in your view](https://docs.open.cx/inbox/intro.md#translate-messages-in-your-view) to read earlier ones. |
| The composer never says the reply will be translated | **Translate agent responses** is off, the session has no known language, or you are writing a comment | Turn the switch on, or check the language flag in the session header |
| The customer received the agent's original text | The session's replies go through HubSpot, Intercom or a connected helpdesk | Expected. Those systems receive the original text. |
| **Translate customer messages** turned on by itself | In a workspace that never used translation, turning on **Translate agent responses** first also turns on customer messages | Turn **Translate customer messages** off again |

***

## Related Documentation

> [card] [Macros](https://docs.open.cx/ticketing/macros.md)
>
> Translate macros ahead of time

> [card] [Inbox](https://docs.open.cx/inbox/intro.md#translate-messages-in-your-view)
>
> Translate only your own view

> [card] [Help Center translations](https://docs.open.cx/help-center/translations.md)
>
> Translate articles

> [card] [Roles](https://docs.open.cx/security/roles.md)
>
> Grant the Translations permission


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.