Release Notes - Language I/O for Salesforce Messaging version 1.17

These are the Release Notes for version 1.17 released June 3rd, 2025.

If you are installing the application for the first time, see the installation instructions in Installing Language I/O Messaging for Salesforce for the installation link.

New

Raising a flag and sending a whisper to an Omni Supervisor

Agents can now raise a flag to alert a supervisor that they need assistance, and send a whisper (an agent to supervisor chat message) to this supervisor. Supervisors can also raise or lower a flag, and agents are notified of this action. This way, the Language I/O Messaging component behaves like the native Salesforce interface. 

This is configurable in the Lightning Record Page builder.

Improved

Tracking translation turn around time and word counts in Enhanced Messaging

Customers can now create reports within Salesforce for each translation for the following criteria:

• a unique identifier for each translation request for easier tracking
• time when the source text was sent for translation
• time when the translation was returned
• total time difference between the sending and receiving
• word count per translated message

Alerting agents when the language of the end user might have changed

Agents now receive an alert when the language of the end user may have changed. When the "same language" alert icon appears in an end user message, agents can click on this icon to see both the original message and the translation: this way, they can compare the two and see if any action is needed. This allows them to know when they might need to re-detect the language, so that they can continue responding in the end user's preferred language.

Note that this warning works by comparing the source and the target text of the translation. However, requests that have an incorrect language defined sometimes result in a failed or inaccurate translations, causing no warning to appear.

Fixed

Storing the end user language in a related field in Enhanced Messaging

A bug was found, where even when the "Language Lookup” and “Language Field" were properly configured, the “Language Field" value with the customer language would not be referenced or updated. This is now fixed and the “Language Field" value is updated as expected.

Auto response disappearing in Standard Messaging

A bug was found in conversations with Standard Messaging, where if an auto response only had text for the agent language, but not also for the visitor language, the auto response would disappear on the agent side if they refreshed the browser. This is now fixed.