---
schema_version: "1"
id: 972000a56d101deb3bd5a924c6cae87680f2fca3ed5b15069521f122746a6bd5
title: Considerations and Limitations for Real-Time Translations for Enhanced Chat and Enhanced Messaging
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/real_time_translations_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.real_time_translations_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5d84c25aa9ba8a76e879a704547a8f4974a980c244c7322d38316b1d8dd9eb89
description: Before starting your setup process, review the considerations and limitations for Real-Time Translations for Enhanced Chat and Enhanced Messaging.
products:
  - Service Cloud
  - Digital Engagement
release: "264"
---
# Considerations and Limitations for Real-Time Translations for Enhanced Chat and Enhanced Messaging

Before starting your setup process, review the considerations and limitations for Real-Time Translations for Enhanced Chat and Enhanced Messaging.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" colspan="2" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.messaging_editions.htm&amp;type=5&amp;language=en_US" target="_blank">View supported editions.</a></td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <a name="real_time_translations_considerations__d666e2469"><!-- --></a><span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" id="real_time_translations_considerations__d666e2469" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/resources-global/_corporate/images/checkmark.png" alt="Checkmark"></span>
            <strong>This article applies to:</strong>
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Enhanced In-App Chat, Enhanced Web Chat v1, Enhanced Web Chat v2, Enhanced
            WhatsApp, Enhanced Facebook Messenger, Enhanced SMS, Enhanced Apple Messages for
            Business, and Enhanced LINE channels</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/resources-global/_corporate/images/crossmark.png" alt="X icon"></span>
            <strong>This article doesn’t apply to:</strong>
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Standard SMS, and Bring Your Own Channel</td>

        </tr>
      </tbody>
    </table>

## General Considerations

- The [Agentforce for Service](https://help.salesforce.com/s/articleView?language=en_US&id=service.einstein_service_intro.htm) add-on is required to enable and use Real-Time Translations.
- Salesforce uses up to 10 of the customer's most recent messages to detect their preferred language. Language detection works with as few as one message. Service reps’ language preferences are set in their user profile.
- If the customer and the service rep use the same language, no translation option is displayed to the rep.
- If language detection is incorrect, wait a couple of messages and refresh to try language detection again.

## Supported Languages

Supported languages include: Afrikaans, Albanian, Amharic, Arabic, Armenian, Azerbaijani, Bengali, Bosnian, Bulgarian, Catalan, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dari, Dutch, English, Estonian, Farsi (Persian), Filipino (Tagalog), Finnish, French, French (Canada), Georgian, German, Greek, Gujarati, Haitian Creole, Hausa, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Irish, Italian, Japanese, Kannada, Kazakh, Korean, Latvian, Lithuanian, Macedonian, Malay, Malayalam, Maltese, Marathi, Mongolian, Norwegian (Bokmål), Pashto, Polish, Portuguese (Brazil), Portuguese (Portugal), Punjabi, Romanian, Russian, Serbian, Sinhala, Slovak, Slovenian, Somali, Spanish, Spanish (Mexico), Swahili, Swedish, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Uzbek, Vietnamese, and Welsh.

## Usage Types for Real-Time Translations

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col>
          <col>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d123971e136">Digital Wallet Card</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d123971e139">usage type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d123971e142">Description</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d123971e145">notes</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Digital Wallet Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d123971e136 ">Flex Credits</td>

            <td data-label="usage type" class="slds-cell-wrap" style="vertical-align:top;" headers="d123971e139 ">Translation</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d123971e142 ">
              <p>Translation converts text from one human language into
                text of another, a process executed by machine translation models. Translation usage is
                metered by the number of characters processed for the translation. </p>
              <p style="margin-bottom:0;">To understand how your
                consumption appears in the Digital Wallet, consider a scenario where you process 9,000
                characters for translation. Because this usage is in units of one million characters, your
                actual consumption is 0.009 units (9,000 divided by 1,000,000). In the Digital wallet, this
                usage is rounded to two decimal places and the value is displayed as 0.01 units.
              </p>
            </td>

            <td data-label="notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d123971e145 ">
              <p>Translation usage includes a monthly allocation of 250,000 characters per user for every
                Agentforce add-on license.</p>
              <p>This limit refreshes monthly, and any unused characters do not roll over to the next
                month.</p>
              <p style="margin-bottom:0;">When the 250,000 character limit is exceeded within a month, any further usage will
                automatically draw down Flex Credits.</p>
            </td>

          </tr>
        </tbody>
      </table>

## Custom Terminology File Limits and Considerations

Follow these best practices when formatting your custom terminology doc.

- Your file should be UTF-8 encoded.
- When you format your file, keep it uncluttered. Only include terms that you want translated or preserved in a particular way.
- The terminology file is case-sensitive. If you want both the capitalized and non-capitalized versions of a word translated, include an entry for each version.
- Special characters and formatting don’t always translate into another language. Avoid these if possible.

We also recommend reviewing limitations before preparing your custom terminology file.

- Your custom terminology file is considered at translation, but it’s not guaranteed that the translation service will implement it accurately.
- You can upload one custom terminology file at a time. A new upload replaces the former upload.
- The maximum custom terminology file size is 10 MB.
- The maximum number of target languages per custom terminology file is 10.
- The maximum source and target text length per custom terminology term is 200 bytes.

We also offer examples of formatting .csv file type.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <thead class="slds-text-title_caps ">
        <tr><th class="slds-cell-wrap" scope="col" id="d123971e235">File TYpe</th>
        <th class="slds-cell-wrap" scope="col" id="d123971e238">Example</th>
      </tr></thead>
      <tbody><tr class="">
        <td class="slds-cell-wrap" data-label="File TYpe" headers="d123971e235">
          <p>CSV (comma separated values)</p>
        </td>
        <td class="slds-cell-wrap" data-label="Example" headers="d123971e238">
          <pre class="line-numbers slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium slds-scrollable_x"><code>en,es,fr,it
Ursa Major Solar,Ursa Major Solar,Ursa Major Solar,Ursa Major Solar</code></pre>
        </td>
      </tr>
    </tbody></table>