Release Notes - Language IO for Salesforce Chat
These are the Release Notes for Language IO for Salesforce Chat.
Please see the installation instructions in Installing Language IO Chat for Salesforce for the installation link.
v2.46.3 (2025.07.18)
Improved
Suggested replies from Lio Agent Assist not appearing
A bug was found where, when Lio Agent Assistant was installed but the Language IO app would not show the suggested replies if “Use Auto Responder” was checked in the Language IO Chat Public Settings.
This is now fixed and Suggested replies appear as expected.
v2.46.2 (2025.06.04)
Fixed
Chat transfer causes chat window to become unresponsive
A bug was found in an older version of the application (2.44.3) where, when an agent tried to transfer a chat to another agent, the window would freeze or become unresponsive.
This is now fixed and agent-to-agent transfers work as expected. Language IO recommends to upgrade if you are still using 2.44.3.
Automated greeting not sent
A bug was found where, when an end user would start a chat and an agent accepted it, the automatic greetings (autoresponders) would not be sent to the end user. This happened when Attempt Locale
Detection was enabled in the application.
This is now fixed and autoresponders work as expected when an end user starts a chat.
v2.45 (2024.12.09)
New
Creating Translation Turn-Around Time Reports
You can now report within Salesforce for each translation:
- the time when the source text was sent for translation
- this is the moment when the agent or or the end user sent the message.
- the time when the translation was returned
- this is the moment when the translation response is received in Salesforce.
- the unique identifier for each translation
- this is typically the translation id
How it works:
Language IO uses a custom object (Language IO Chat Message) to store individual incoming and outgoing chat messages and their translation. Until now, Language IO always deleted the records of this object after the chat session was done, and only saved the Chat Transcript. This version introduces a new setting option (Keep LIO Message Records) to keep these records so that you can create the relevant reports. This setting is disabled by default.
If the setting is checked:
-
Language IO does not delete the records of the Language IO Chat Message object.
-
Language IO can provide a query that you can use to delete these records after you create the reports that you need.
You can find more information about how to create this report here.
Fixed
Attachments not showing in Language IO tab
A misconfiguration was identified where, when an agent started a file transfer request from the Language IO tab, and the user attached the file, the file was not available in the Language IO tab and the file transfer request showed as still pending, even though the file was in fact transferred successfully and available in the standard tab.
This was caused by a permission issue. The agents are required to have access to the following objects:
LanguageIOLA__ContentAttached__eLanguageIOLA__RatingChanged__e
We added these permissions to the “Language IO Chat User” permission set that is included as part of the package of this application.
Early Access
Introducing Lio Agent Assistant for Salesforce Chat
This feature is not enabled by default.
Language IO is very excited to introduce the new Lio Agent Assistant for Salesforce Chat. Lio Agent Assistant is an enhanced chat experience that helps agents solve end user issues more quickly and efficiently.
To achieve this, it uses Retrieval-augmented generation (RAG), a technique for enhancing the accuracy and reliability of generative AI models with facts fetched from external sources, in this case, connecting to a Knowledge Base of articles to return relevant information about the topic at hand, in the right language.
For Lio Agent Assistant to match chat messages to articles in the customer’s native language, articles in the customer’s language must exist in your knowledge base. Language IO will work with you to ensure that your knowledge base is set up properly to enable you to use Lio Agent Assistant with articles in any language that you prefer.
For more information about how to use Lio Agent Assistant, see Using Lio Agent Assistant in Salesforce Chat.
v2.44.6 (2024.06.18)
Fixed
Third-party custom component interfering with Language IO Component
A bug was found where, if a specific custom third-party component (that is, not made by Language IO) was loaded in the Chat page layout, agents would sometimes see an error when chat messages were received or when the agent accessed the Language IO component. This did not happen when the third-party component was not loaded. This is now fixed so that other custom components in the Chat page no longer interfere with the Language IO component.
v2.44.3 (2024.03.20)
Upgrade instructions
You can upgrade from 2.43 to 2.44.3 directly.
If you upgrade from version 2.42.2 or older, follow these steps.
- First, you must upgrade to the 2.42.3 patch:
- Once the upgrade is complete, upgrade again to 2.44.3:
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 Chat, see Using Translation Optimization in the Language IO plugin for Salesforce Chat.
Improved
Translation of past messages when transferring chats
When transferring a conversation to an agent from a Chatbot or another agent, the second agent can now translate the previous content to their language so they can understand the context of the conversation. Past messages can be automatically translated by enabling “Translate All Untranslated” in the custom settings. If this setting is disabled, the agent can manually translate each message by clicking on the globe icon underneath each text bubble.
Icons used in the Language IO app UI
Translate automatically switch
When toggled on as shown, agent messages are translated automatically when sent.
Optimization switch
When toggled on as shown, agent messages go through the source optimization process.
Show both original and optimized messages
When clicked, the interface shows both the optimized and original message.
Show translation
When clicked, the interface shows the translated message that the end user received.
Transcripts highlights and readability
We made improvements to the way transcripts show the various elements of a conversation.
Before, the transcript highlighted all the translations, regardless of language, and all highlights were the same color:
The new transcripts now highlight the messages in the agent's language, regardless of whether it is a translation or not (In this example, in English). In addition, the user messages are highlighted in yellow, while the agent's messages are highlighted in blue. When optimization is used, the optimized message (which is the one that is translated and sent to the user) is highlighted rather than the original message.
Fixed
Transcript shows user as "null"
A bug was found where, if the "Append Transcript" setting was enabled, some chat conversation in which the transcript was appended after the end of the conversation showed some user messages as coming from "null". This did not happen when the transcript was appended using the "Translate Transcript" button for the same chat.
This is now fixed so there is always a user defined as the origin of the message, with the default being "Visitor" and "Agent" if no names are found.
Component error on re-detect for unsupported locales
A bug was found where the application would throw a component error if the agent tried to re-detect a message in which the newly detected language was not configured for the account (also known as an "unsupported locale"). This happened specifically when "Use Auto Responder" and "Retrieve Greeting from SF" were enabled in the custom settings.
The component error is now fixed so that it no longer happens and the "unsupported locale" message shows as expected.
Older versions
Please consult your Language IO Customer Success Manager if you need to review older release notes for this application.
Comments
0 comments
Please sign in to leave a comment.