> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/channels-integrations/text-channels/webchat/configure-ucc-translation.md).
# Configure UCC translation providers
Configure UCC translation providers for the documented WebChat and Dialogue Studio integrations, subject to deployment applicability.
{% hint style="warning" %}
This guide covers UCC provider configuration for the documented WebChat and Dialogue Studio translation integrations. Confirm the prerequisites, runtime settings, and plugin registration for your deployment. Keep provider subscriptions, logging, and recording decisions separate from enabling translation.
{% endhint %}
{% hint style="info" %}
Feature availability
This feature requires Dialogue Studio. Dialogue Studio is available with Enterprise when purchased separately, or through Enterprise Plus, which includes Dialogue Studio.
{% endhint %}
This article shows you how to translate spoken or written customer dialogues in real time. You can enable translation in WebChat (See: [WebChat Live Translation](https://atlas.anywhere.now/channels-integrations/text-channels/webchat))or in Dialogue Studio (See: [Configure a Live Translation in Dialogue Studio](https://atlas.anywhere.now/channels-integrations/text-channels/webchat/configure-ucc-translation#dialogue-studio-live-translation-example)).
## Prerequisites
* Dialogue Studio enabled for the UCC.
* Google Cloud Translation API key (required when **TextTranslationService** is set to **Google**). See [Set up Cloud Translation](https://cloud.google.com/translate/docs/setup).
* Azure AI Translator resource key (required when **TextTranslationService** is set to **Microsoft**). See [Create a Translator resource](https://learn.microsoft.com/azure/ai-services/translator/create-translator-resource).
Important
When you create the Azure Translator resource, set the Region to Global. Other regions are not supported.
true or false
Default: false
| Logs all translated text to the UCC log. |
### Record translations
Store translations in a text file alongside audio recordings.
| Setting | Value | Description |
| ----------------------- | ----------------------------------------------- | -------------------------------------------------- |
| UseTranslationRecording | true or false
Default: false
| If `true`, writes all translations to a JSON file. |
#### Recording location
Translation files are saved in the same folder as audio recordings. For path details, see [Managing Recordings](https://atlas.anywhere.now/operate/recording-and-interaction-data/manage-call-recordings).
## Dialogue Studio Live Translation Example
{% hint style="warning" %}
This example is not a production-ready flow. Its introduction and language-configuration sections reverse the described default customer and agent languages. Inspect the actual Transcribe, Translate, and Say nodes and their culture settings before testing; do not rely on the inconsistent default-language prose.
{% endhint %}
This flow will create live audio translations for a conversation. Anything a customer says will be translated and the translation is spoken to the agent and vice versa.
The default configuration after import is that a customer speaks Dutch and the agent speaks English. Change the transcription and translation nodes if you like to changes this. Make sure you create custom voices in the say nodes.
There are some says to guide a customer and agent because the transcriptor needs to be started before the conversation will be translated. Everything can be changed to your desires.
Follow the comments in the flow for information about getting started and how to change the configuration.
After you get it working you can add or change anything you like. For example it is possible to save all texts and translated texts to a database or send chats to an agent with both transcripted texts also. This is just a sample to get you started.
### Preview
[](https://github.com/AnywhereNow/atlas-docs/tree/main/channels-integrations/.gitbook/assets/2488733b8d707469.png)
### Import Flow
This flow can be imported directly into your Dialogue Studio:
1. Open the menu in the top right
2. Select "**Import**"
3. Select "**Examples**"
4. Select "**\[Audio] Live Translation**"
5. Change Import to "**New flow**"
6. Select "**Import**"
### Preparations
Before the InDialogue Started node will be triggered you need to configure agents and skills in your UCC. Use Dialogue Studio or the default IVR options to choose the desired skill, when an agent accepts this flow will be triggered.
Follow the rest of the comment to check the configuration.
There is some simple javascript in this flow to save the data about the customer and the agent, it is also used to transfer the translated text to the other participant. Notice that editing this can break the scenario.
#### Configure Translation
For this flow you need translation configured on your UCC, see: [Configure UCC translation](https://atlas.anywhere.now/channels-integrations/text-channels/webchat/configure-ucc-translation)
#### Configure Transcribing
For this flow you need transcribing configured on your UCC, see: [How to configure UCC speech to text transcription](https://atlas.anywhere.now/operate/recording-and-interaction-data/configure-ucc-transcription)
### Configuration
#### Configure UCC
The first step is to connect the flow to the UCC. This needs to be done for the following nodes:
* InDialogue started
This can be done by double clicking on the node and selecting your UCC. If you haven't created a flow before, see: [Create your first flow](https://atlas.anywhere.now/contact-center-configuration/building-your-callflow/via-dialogue-studio)
#### Configure Customer Language
By default the customer is configured as English . If you want to change this, you need to alter the following nodes:
* Transcribe to EN
* TranslateENToNL
* PlayEnglish
This can be done by double clicking on the node and changing the culture info.
#### Configure Agent Language
By default the agent is configured as Dutch. If you want to change this, you need to alter the following nodes:
* Transcribe to NL
* TranslateNLToEN
* PlayDutch
This can be done by double clicking on the node and changing the culture info.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://atlas.anywhere.now/channels-integrations/text-channels/webchat/configure-ucc-translation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.