Release Notes - Language IO for Salesforce Messaging

These are the Release Notes for Language IO for Salesforce Messaging.

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

v1.17.1 (2025.07.18)

Fixed

Sound notifications in the Language IO application

Agents who used the Language IO Messaging component as default received no notification sound when they received a message from the end user, and no notification sound when they sent a message to the end user.

This is now fixed to match the behavior of the standard conversation component, so that notification sounds play when agents receive or send a message from the Language IO Messaging component.

v1.17 (2025.06.03)

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 IO 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. 

v1.16.5 (2025.05.13)

Fixed

Issues between the Language IO Messaging component and certain Lightning Events

A bug was found, where the lightning:conversationChatEnded event would not fire when an end user ended a messaging session. 

This is now fixed to make sure that the lightning:conversationChatEnded event is always recorded when:

• an end user ends a chat,
• when an agent ends a chat from the Language IO Component, and
• when an agent ends a chat from the Conversation Component.

v1.16.4 (2025.05.05)

Fixed

Issues between the Language IO Messaging component and certain Lightning Events

A bug was found, where the Language IO Messaging component did not see or respond to Conversation and Omni events that executed when certain types of events occurred in a console.

These events were used to change the tab color and capture various metrics, based on new message or chat end events.

The events that were fixed were the following:

event name = lightning:conversationAgentSend
event name = lightning:conversationNewMessage
event name = lightning:conversationChatEnded

This is now fixed so that whenever the Language IO code captures a new message event, it logs the information.

v1.16.3 (2025.04.29)

Fixed

Supervisor Name tied to chats instead of Agent Name

In previous versions, when Supervisor monitoring was taking place, the name of the supervisor appeared on the Language IO messaging component instead of the name of the agent who was sending the messages.

In the supervisor's view and the end user's view, it looked like the agent sent the chat, but the Language IO messaging component showed the name of the supervisor instead.

From version 1.16.3 onwards, the name of the agent is now shown in the Language IO messaging component as expected. 

v1.16.2 (2025.04.17)

Improved

Ending a session when using Amazon Connect 

If your organization uses Salesforce Messaging with Amazon Connect, sometimes when an agent clicked "End Chat" from the Language IO component, it would not update the agent's status in Amazon Connect accordingly. Now, clicking "End Chat" changes the agent's status to After Call Work (ACW), followed by "Available", as expected.

v1.16.1 (2025.01.16)

Fixed

Exception Thrown in Enhanced Messaging

A bug was found in Enhanced Messaging where, when agent sent a message, an exception occurred titled "A Component Error has occurred".

This error was caused by not having Lightning Web Security enabled, which is a requirement since Salesforce Messaging version 1.13. This is now fixed.

Limit exception when using language lookup and language field custom settings

A bug was found in Enhanced Messaging where, when the lookup object had many records (that is, more than 50,000), the application threw an uncaught exception when attempting to retrieve the end user's locale.

This is now fixed.

Custom Locale not displaying

A bug was found in Enhanced Messaging where, when language lookup and language field were configured in the custom settings, the end user's locale was not displayed in the User Interface.

This is now fixed and the locale is shown as expected.

Language code reverting to default

A bug was found in Enhanced Messaging where, when the end user's locale was detected but the agent sent a message first, the message would be translated and received in the end user's language as expected, but the end user's locale would then revert back to en_US.

This is now fixed and the detected end user locale does not revert back to default.

v1.16 (2024.09.26)

New

Preferred language for agents now coming to Messaging

As is already available in Chat, agents can now set a preferred language for translation that is separate from their profile language in the Language IO app for Salesforce Messaging. This way, the Salesforce language can remain the same as the rest of the organization, while they conduct conversations in their preferred language.

To enable this for agents, Salesforce administrators must first enable the feature in the settings.

For more information, see:

• Setting up the Agent Preferred Language feature as an Admin
• Setting up the Agent Preferred Language feature as an Agent.

Improved

Optimization Automatically Disabled for Unsupported Languages

Because the Translation Optimization feature is only available in English, the component now automatically disables the toggle when the agent language is set to another language than English. This is expected and normal behaviour. 

v1.15.1 (2024.06.28)

Fixed

Server error visible on the end-user side

A bug was found where, when an organization had Enhanced messaging enabled and when the Language IO application detected a language that was not configured for this organization, the expected 516 error code was visible in the agent portal, as expected, but also on the end user's side. This is now fixed.

v1.15 (2024.05.29)

New

Translation Optimization

Translation optimization is a Language IO feature where an agent's message passes through a Large Language Model routine that lightly alters the source content to increase the likelihood of a high-quality machine translation. This process is designed to preserve the tone and meaning of the agent's original message.

Translation optimization can be useful when you want to ensure the consistency and quality of translations, for example when you have a large pool of agents who may use different styles to address users. Automated optimization can help you use consistent language while saving on training costs.

For more information about Translation Optimization, see What is the Language IO Translation Optimization feature?

To see how you can use Translation Optimization in Salesforce Messaging, see Using Translation Optimization in the Language IO plugin for Salesforce Messaging.

New Channel Proxy

We created a new utility item to handle event notifications for Messaging Sessions. This new feature is not enabled by default. To learn more about this, please submit a support request.

Improved

Differentiating "Customer Inactive" from "End Chat"

The Language IO Messaging component now differentiates between 'Customer Inactive” and “End Chat”, so that the behavior of the component matches that of the native conversation component.

Now, when “Customer Inactive” is clicked, a message shows at the bottom of the conversation to indicate that the agent has left the conversation. When “End Chat” is clicked, a message shows at the bottom of the conversation to indicate that the chat has ended.

Fixed

Messages are displayed out of order

A bug was found where messages in a conversation sometimes would appear out of order in the Language IO component. This is now fixed and messages show in the correct order. 

Messages are not displayed in the translation window after sending

A bug was found where messages sent by an agent sometimes would not show in the translation window. This is now fixed and messages show as expected. 

Auto-responder in the wrong language

A bug was found where, when the agent used the auto-responder and they refreshed the browser, the auto-responder would appear in the customer’s language rather than the agent’s language. This is now fixed.

Translation Toggle Not Turning Off

A bug was found where the translation toggle did not automatically turn off when the app detected that the customer’s locale was the same as the agent’s locale, or when the customer’s locale was an unsupported language. This is now fixed and the translation toggle automatically turns off as expected.

Older versions

Please consult your Language IO Customer Success Manager if you need to review older release notes for this application.