Release Notes | Language IO Inline for Zendesk
These are the Release Notes for the Language IO Inline for Zendesk.
Please see the installation instructions in Installing Language IO Inline for Zendesk.
June 3, 2026: 1.4.0
New
Support for OAuth 2.0 Authentication
The application now supports OAuth 2.0 authentication. This provides an alternative connection method for organizations that require it for compliance or security policies. Basic Authentication (Auth Token) remains fully functional. You can continue using your existing credentials or migrate to OAuth 2.0 with help from our Support team.
October 16, 2025: 1.3.0
Improved
Improved re-detection process for agents
We made the language re-detection process more intuitive. Now, when the agent clicks the re-detect button and the newly detected language matches the previously detected language, a message appears that asks the agent if the detected language is correct.
If the agent clicks "no", the transcript pop-out window opens, with a prompt for the agent to highlight a section of text. This highlighted section is used to re-detect the language of the end user.
If the agent clicks "yes", the alert is dismissed. No further action is performed.
Refining the re-detection alert
When the message is a number, email address, date, and short words, the re-detection alert does not activate. This is to prevent agents from accidentally re-detecting the wrong language (this is because the sample size would be too small for an accurate detection).
Agent and end user languages specified in transcripts
Transcripts now clearly specify both the agent's language and the end user's language in a pinned section at the top of the Language IO transcript pop-up. This way, agents no longer have to close the window and go back to the application to check the languages.
Translating past messages
Agents can now translate previously untranslated past messages in a transcript, provided that they are tagged as “customer text” and “original”.
November 15, 2025: 1.2.2
Fixed
Linebreaks not maintained when auto-send is disabled
A formatting issue was found in Messaging where, when "Translate and send (outbound)" was disabled, the formatting of a message was not maintained when the agent translated the message.
This is now fixed, and the formatting of a translation should be maintained when "Translate and send (outbound)" is disabled.
May 14, 2025: 1.2.1
Improved
Performance optimization
We made several improvements to optimize the performance of the Inline application to solve random issues such as delays or duplicate messages where both the original and the translation would be sent to a recipient.
November 13, 2024: 1.2
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?
For more information about how to use Translation Optimization, see Using Translation Optimization in Language IO Inline Translation for Chat, Tickets, and Messaging.
Retranslation and Quality Rating Flags
The Language IO Inline Translation for Chat, Tickets, and Messaging application now supports retranslation. This feature allows agents to request a new translation if, for any reason, they are not satisfied with the first translation offered by the app.
The application also supports Quality Flag Rating. When enabled, agents can see a flag icon next to the end user's translated message. If they are not satisfied with the translation, they can click the flag, turning it red. This action is reversible.
July 9, 2024: 1.1.5
Improved
Auto-send disabled when not supported
When translating a messaging session for a channel that does not support translate and auto send, the toggle is automatically disabled and the agent cannot toggle it back on. Hovering over the toggle shows the following help text: “Automatic sending is not currently supported for the active channel. After translating, click the Zendesk Send button”.
Alert when re-detection might be needed
Agents now receive an alert when the source and target text are the same, so that they can re-detect the language of the conversation. Until now, re-detection was automatic but it could cause issues when the message was a number or a short word like “no”. Agent now have the option to accept or reject a re-detection, so that re-detect does not happen when it is not needed
June 11, 2024: 1.1.0
New
Support For Merged Tickets
When a ticket is merged into a secondary ticket and there are untranslated messages on the secondary ticket, we now give you the ability to translate these past messages. In addition, we also translate the message in the secondary ticket that indicates which message is was merged from, so that the agent has all of the necessary context from the previous ticket. Note that once a ticket is closed, it is no longer possible to translate past messages that were left untranslated.
Improved
Language detection set to ticket assignee
Tickets can only be translated to the language of the agent assigned to the ticket. This way, even if multiple agents are actively viewing the same ticket, it does not generate multiple translations for the same source text.
Autolaunch is now a configurable option
Until now, the Language IO Inline application launched automatically with the ticket or session. From this version, auto-launch of the sidebar application is now configurable. This way, the sidebar app can be launched by the agent when needed, instead of automatically for every ticket, messaging session, or chat.
New message when no new translatable content is found
Until now, there was no visual feedback when an agent clicked “Translate Untranslated Messages” but there was nothing to translate. This could lead to some confusion as to why the button was not doing anything. From this version, when an agent clicks on the “Translate Untranslated Messages” button and there is nothing to translate, they are notified with the message “There are no incoming messages left to translate”.
New message when the requested language is not configured
Until now, there was no feedback when the detected language was not a language configured for the Language IO account. From this version, when the detected language is not configured, the following message shows: “Translation is not supported for the language detected."
Fixed
Line breaks in translation results
A bug was reported where extra line breaks were added to the translation results, which caused formatting issues. This is now fixed. There are still scenarios in which this issue might still occur with one translation vendor; we are working alongside this vendor to solve this issue permanently. If you see this issue reoccur, please contact Language IO Support.
March 19, 2024: 1.0.2
Improved
Language Re-detection and automatic retranslation
Agents can now re-detect the language of an end-user with a click on the customer language code:
After the re-detect is complete, the application translates the end user's latest message to the newly detected language automatically if “auto-translate (inbound)” is checked. Otherwise, a click on the Translate previous messages button will translate all of the end-user's previous messages:
Fixed
Application title does not allow special characters
Titles of applications in Zendesk cannot contain special characters such as ?, /, ‘, _, <, or >. The title of the application was updated to reflect this so that the title of the application does not have to be changed during installation.
February, 14, 2024: 1.0
Introducing the Language IO Inline Translation for Chat, Tickets, and Messaging app
Language IO is proud to present the new Language IO Inline Translation for Chat, Tickets, and Messaging app for Zendesk. This new offering is an alternative to our existing app, now called "Language IO Parallel Translation for Chat, Tickets, and Messaging".
The Parallel app exists solely in the side bar next to the conversation space, whereas the new Inline app is more integrated within the native Zendesk conversation space.
Features
When the Inline app is enabled, agents see a Language IO button in the text editor (1), as well as a settings panel in the side bar (2):
When a Chat, Messaging or Ticket session is loaded, the toggle values in the sidebar are determined by the default admin settings for the organization. The customer locale is determined by the first interaction with the customer. For more information, see the User Guide.
Translation
Auto-translate (inbound)
When the "Auto-translate" setting is turned on when the session is loaded, it automatically translates all untranslated customer messages as they are received. Translation are posted as an internal note.
Translate previous messages
If the Auto-translate setting was turned off and some messages are left untranslated, the agent can use the Translate previous messages button. This action translates all untranslated customer messages and posts them as a single internal note.
Translate and send (outbound)
Once the conversation starts and the customer locale is detected, the agent can simply click on the Language IO icon in the message field to translate their message before sending it to the customer:
Depending on the settings of the "Translate and Send" toggle, agents can choose between translating and sending immediately, or simply translating, then manually sending the message.
Install & User Guides
To install the application, see the installation instructions here.
For the full User Guide, see here.