Real-Time Chat: Translate Chat Messages Between Rep and Customer


Real-Time Chat

BeyondTrust’s optional integration with GeoFluent gives your support desk a global advantage by translating chats between reps and customers in real time. Without a language barrier, your support team can reach customers across the globe.

Messages between a customer and a representative can be translated in real time if this feature is enabled. Customers who start sessions using the public portal can select their language from the dropdown menu at the top of the page. Representatives can select their preferred chat language from the Settings > Global Settings page in the representative console.

Obtain GeoFluent API

To setup this integration, you need a Lionbridge GeoFluent account, available at https://www.lionbridge.com/get-in-touch/.

Once your account is created, subscribe to the language pairs desired. Language pairs are directional. For example, an English-to-French language pair translates English words to French, but does not translate French words to English. In this example, a second language pair, French-to-English, is required to support the French-to-English translation.

BeyondTrust's Remote Support real-time translation chat supports German, Spanish (Latin American), Spanish (European), Finnish, French, Italian, Japanese, Dutch, Polish, Portuguese (Brazil), Portuguese (Portugal), Russian, Swedish, Turkish, Chinese, and Simplified Chinese.

From your GeoFluent account, obtain the GeoFluent API key and secret. These are used to configure real-time chat translation in Remote Support.

Configure Real-Time Chat Translations

Follow the steps below to enable real-time chat translations for representatives and offer chat language options on the public portal:

  1. Log in to the administrative interface.
  2. Click Localization in the left menu, and then click the REAL-TIME CHAT tab.
  3. A default GeoFluent API URL displays. The default is suitable for North American users. Other areas may see improved performance using the URL https://api-eu.geofluent.com. Your GeoFluent representative can help you decide if you need to change this value.
  4. Enter your API Key.
  5. Enter your API Secret.
  6. Click Save.
  7. The system tests the connection and displays the status. If the Current Status is not OK, confirm the entered values. If necessary, contact GeoFluent for assistance.
  8. Once the status is OK, the Language Pairs selected in GeoFluent display on the lower part of the screen.
  9. Check Enable Real-Time Chat Translations to make the feature available to representatives.

Enable Real-Time Chat Translations in the Representative Console

Console Global Settings with a dropdown to select a preferred chat language.

Once real-time chat translation is enabled, representatives can select their preferred chat language by following these steps:

  1. Download and install the updated representative console.
  2. Log in and click File > Settings.
  3. Under Global Settings, select the Preferred Chat Language from the dropdown list.


Enable Chat Translation Dropdown Menu on Public Sites

Public Portal with the option to select a session chat language enabled.

Once real-time chat translations is enabled, a session language option can be added to public portals. This is in addition to the portal language selection option.

Under Public Portal on the lower area of the screen, click the Public Site link, or click Public Portals in the left menu. Repeat the steps below for each site where a session language option is desired.

  1. Click the pencil icon to edit the site.
  2. Under Edit Public Site, check Display Session Chat Language Dropdown.

The portal now shows two language dropdowns: one for the portal near the top of the screen, and one for the chat session. The location varies depending on the portal layout and options. The language options for the chat sessions are the language pairs selected in GeoFluent. This means a user's desired language for the portal may not be available for chat sessions, or vice versa.


For more information, please see the following: