Desk Guide v1
Desk Guide
Desk Guide
Version 1

Translation

Copy link

Sendbird Desk supports translation for messages in tickets. This feature allows agents to translate messages into different languages, making it easier to communicate with customers who speak different languages than their own.

Once enabled, agents can translate the following messages:

  • Customer messages into the agent's language
  • Agent messages into the customer's language

You can turn this feature on and off under Settings > Desk > AI features > Translation in Sendbird Dashboard.

Note: This feature is powered by Sendbird AI agent. To learn more, contact us.


How to enable

Copy link
  1. Go to Settings > Desk > AI features > Translation in Sendbird Dashboard.

  2. Toggle on the Translation switch.

  3. Configure the following settings:

  • Enable translation preview: When enabled, agents can see both the original and translated messages in the ticket view. If disabled, only the translated message is shown.
  • Update customer language and country: Choose who can update the language preference for customers. You can select either All agents and admins, Admins only, or No one.
  • Agent access: Choose who can use the translation feature among agents. You can select either All agents or Selected agents.

  1. Once enabled, agents can start translating messages in tickets. Using the translation option in the message input area, agents can choose a language to translate their messages into and even preview the translation before sending it.

Language and country preference

Copy link

To use the translation feature effectively, both agents and customers need to have their language and country preferences set. The AI translation engine uses these preferences to determine the target language for translations and localization.

Language

Copy link
  • Agents

When the Translation feature is enabled and agents have the proper access, each agent can select up to five preferred languages in their profile.

  • Customers

Agent messages will be translated into the customer’s preferred language. A customer’s preferred language can be set through:

Note: Updating a customer’s language in Sendbird Dashboard is permitted only for agents with the required permissions as defined in the feature settings. See the How to enable section above.

Country

Copy link

Take the AI-powered translation one step further with glossary-based localization. To support glossary-based localization, a Country field is added to customer fields and works together with Language. This combination enables localized glossary terms during translation. First, set a country preference for customers through:

Once the locale information is set for a customer, create a glossary with localized terms for specific language–country pairs. During translation, the AI engine references the glossary to apply localization based on the customer's language and country preferences.

How language and country preferences work in a ticket

Copy link
  • Language:

  • If the agent and customer have different language preferences, AI translation is applied.

  • If the customer's language preference matches one of the agent's, no translation is applied.

  • Country

If both the language and country preferences are set for a customer and glossary is provided, localization can be applied during translation based on the terms defined for that specific language–country pair.

Country valueLanguage valueLocalization by countryAI translation

Yes

Yes

No

No

No

Yes

No

No

Permission control

Copy link

You can also set who can update these settings under Settings > Desk > AI features > Translation in Sendbird Dashboard. Depending on this configuration, only the agents with the appropriate permissions can update the Language and Country preference for customers.


Localization with glossary

Copy link

Each business has its own set of terms and phrases that are unique to its industry or operations. To ensure accurate translations, you can create a glossary of these terms and their corresponding localizations. This helps maintain consistency and clarity in communication with customers.

How it works

Copy link

AI translation and localization work based on two inputs: your glossary and your customer’s language and country preferences.

First, create a CSV glossary that defines terms and their localized values. Each localization column should be labeled with a language–country code pair (for example, en_US, fr_FR). You can also specify whether each term should be localized or remain unchanged.

After your glossary is shared with us, the AI translation engine applies the glossary alongside the customer’s language and country settings. Localization behavior follows the values defined in the DNT(Do Not Translate) and target_language_code columns:

DNTtarget_language_codeResult

true

Localization provided

Term remains unchanged and not translated.

true

N/A

Term remains unchanged and not translated.

false or N/A

Localization provided

Translated using glossary values.

false or N/A

N/A

Translated by AI based on context.

How to create a glossary

Copy link
  1. Create a glossary file in CSV format. Each row should contain a term and its corresponding localizations. Refer to the sample format below for column order and content:

RequiredColumnDescription

term

The term or phrase to localize. A glossary can include up to 1,000 terms, with each term limited to 1,024 bytes.

source_language

The language code of the original term, following ISO 639 (for example, "en"). To specify a regional variant, combine the language and country codes using the ISO-3166-1 format (for example, en_US, en_UK).

description

A short description that provides context to improve translation accuracy.

target_language_code_1, target_language_code_2, ...

The target language code of each localized term. Use ISO-639 for the language code and ISO-3166-1 for the regional suffix (for example, en_US, fr_FR). Each column contains the localized version of the term in a different target language. Up to 50 target language columns are supported.

non-translatable

Indicates whether the term should remain unchanged during translation. Set to true to prevent translation. (Default: false)


  1. Send the file to your Sendbird support contact to upload the glossary to your Sendbird Desk application.

  2. Once uploaded, the AI translation engine will reference the glossary when translating messages, ensuring that the specified terms are translated according to your preferences.

Supported languages and countries

Copy link

The following list shows the language codes supported by Sendbird Desk at this moment.

LanguageCountry
AVAILABLE_TRANSLATION_LANGUAGE_SET = (
    "ar",     # Arabic
    "az",     # Azerbaijani
    "cs",     # Czech
    "da",     # Danish
    "de",     # German
    "el",     # Greek
    "en",     # English
    "es",     # Spanish
    "fi",     # Finnish
    "fil",    # Filipino
    "fr",     # French
    "he",     # Hebrew
    "hi",     # Hindi
    "hr",     # Croatian
    "hu",     # Hungarian
    "id",     # Indonesian
    "it",     # Italian
    "ja",     # Japanese
    "ko",     # Korean
    "ms",     # Malay
    "nb",     # Norwegian Bokmål
    "nl",     # Dutch
    "pl",     # Polish
    "pt",     # Portuguese
    "ro",     # Romanian
    "ru",     # Russian
    "sv",     # Swedish
    "th",     # Thai
    "tr",     # Turkish
    "uk",     # Ukrainian
    "vi",     # Vietnamese
    "zh-cn",  # Chinese (Simplified)
    "zh-tw",  # Chinese (Traditional)
)

Translation preview

Copy link

When the Enable translation preview setting is turned on, agents can see both the original and translated messages in the message input area. This allows agents to verify the accuracy of translations before responding to customers.

Note: Agents can't directly edit the translated message in the preview. To modify the message, agents need to edit the original message and then generate a new translation.


Visibility of original and translated messages

Copy link

For readability and clarity, the visibility of original and translated messages differs between agents and customers:

  • Agents: can see both original and translated messages for customer messages, as well as their own messages.
  • Customers: can only see the translated messages sent by agents.