Documentation Index

Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt

Use this file to discover all available pages before exploring further.

Configure Chat Translation with Language I/O - Live

  • Published on Aug 10, 2026
  • 3 minute(s) read
Prev Next

Configure Chat Translation with Language I/O

Overview

This article explains how to enable real-time chat translation for ScreenMeet sessions using Language I/O as the translation provider. Chat Translation translates in-session chat messages between the agent and the end user so each side reads the conversation in their own language.

The audience for this article is ScreenMeet administrators who manage organization-level settings in the ScreenMeet Admin Console. Configuration on the ScreenMeet side is limited to two fields: the translation provider and the provider API key.

About Language I/O

Language I/O is an enterprise translation platform that provides real-time machine translation for customer support channels including live chat, email, tickets, and knowledge base content. It supports more than 150 languages and is used widely alongside Salesforce, ServiceNow, Zendesk, and Oracle Service Cloud.

ScreenMeet does not resell Language I/O. Your organization contracts with Language I/O directly, and translation usage is billed by Language I/O under that agreement. ScreenMeet calls the Language I/O API using the key you supply.

Language I/O Account Required

If your organization does not already have a Language I/O subscription, request one through the Language I/O demo request page before starting this configuration.

Prerequisites

  • An active Language I/O subscription for your organization.

  • Access to the Language I/O Customer Self-Service Portal at golinguist.com with permission to view the API Key page.

  • ScreenMeet administrator access to the Admin Console for the organization you are configuring.

  • Chat enabled for the ScreenMeet products your agents use, since Chat Translation applies to in-session chat messages.

Step 1: Retrieve your Language I/O API key

The Language I/O API authenticates every request with an API key. Retrieve the key from the Language I/O Customer Self-Service Portal.

  1. Log in to the Language I/O Customer Self-Service Portal.

  2. Open the API menu and select API Key.

  3. Locate the Authentication Key section. If the API Key field is empty, click Generate new API key.

  4. Click the eye icon to unmask the key, then click the copy icon to copy it to your clipboard.

Key Rotation Expires the Previous Key

Generating a new key in Language I/O schedules your existing key to expire in 14 days. If you rotate the key, update the Provider API Key field in ScreenMeet before the old key expires or chat translation will stop working. Full details are in the Language I/O article on Managing your API Key.

Step 2: Enable Chat Translation in ScreenMeet

Chat Translation is configured per organization in the ScreenMeet Admin Console.

  1. Log in to the ScreenMeet Admin Console and open Translation Settings for your organization.

  2. Turn on the Chat Translation toggle.

  3. Set Translation Provider to Language I/O.

  4. Paste your Language I/O key into the Provider API Key field.

  5. Click Save.

Provider API Key Is a Secure Field

The Provider API Key field is write-only and displays the placeholder text Secure field - enter value to override once a key is stored. The saved value is never displayed back. To change the key, type the new value and save again. Leaving the field blank keeps the existing key in place.

Settings reference

Setting

Description

Default

Chat Translation

Enables real-time translation of in-session chat messages.

Off

Translation Provider

The third-party translation service ScreenMeet calls. Select Language I/O.

None selected

Provider API Key

The authentication key issued by your translation provider. Stored as a secure, write-only value.

Empty

Verification

Confirm the configuration with a test session before rolling it out to agents.

  1. Start a ScreenMeet session and open the chat panel on the agent side.

  2. Join the session as an end user in a second browser or on a second device.

  3. Send a chat message in a language other than the agent's language.

  4. Confirm the message is delivered in the reading language of the recipient.

  5. Reply from the agent side and confirm the translation works in the reverse direction.

Test After Every Key Rotation

Run the same verification steps whenever you rotate the Language I/O key. A rejected key produces untranslated chat rather than an obvious error, so a quick test session is the fastest confirmation.

Troubleshooting

  • Messages arrive untranslated: Confirm the Chat Translation toggle is on and that the settings were saved. Re-enter the API key to rule out a truncated paste.

  • Translation stopped working after 14 days: A key rotation in Language I/O expired the previous key. Retrieve the current key and re-enter it in Provider API Key.

  • Translation stopped working immediately: A deleted key is revoked instantly and cannot be recovered. Generate a new key in the Language I/O portal and save it in ScreenMeet.

  • A specific language is not translating: Confirm the language is supported in your Language I/O plan. Review the Language I/O API locales and locale codes reference.

  • Settings look wrong after edits: Click Reset to Defaults to clear the panel, then repeat Step 2. This clears the stored provider and key.

Related articles