Update (June 2026): The MLS UI improvements originally planned for end of June have a new rollout date of August 2026 due to changes in our roadmap. We're still excited to bring you these enhancements: 1) a new UI language setting that controls the interface (navigation, controls, labels) independent of what language users type in, available on our Web product; and 2) display of citations in the original content language with an option to translate to the query language across AI Assistant and Enterprise Search App.
🎉 Update (May 2026): MLS for Files is live as of May 18, MLS for all customers in all regions! You can now ingest non-English files such as PDFs, MS Word and MS PowerPoint and search will work the same way it does for KBs. See post below for full details.
We're excited to announce more powerful, upgraded Multilingual Support (MLS) capabilities coming to Assistant and Enterprise Search!
Today, via the Knowledge Search (KS) plugin, Moveworks supports non-English search for Knowledge Base Articles (KBAs) by converting both non-English queries and non-English KBAs to English in order to process them. While this approach provided multi-language support, it introduced risk of accuracy loss along the way. Additionally, non-English search is currently not supported for files.
With our upgraded, native MLS capabilities, we will support non-English search for files along with KBAs. We’ll eliminate the "double translation" approach entirely, leading to improved accuracy and reliability. Our new upgraded search capabilities, powered by next-generation retrieval and ranking models, work directly over content in its original language across 30+ languages, delivering better relevance quality and more reliable results.
We'll also simplify language and geo controls with this upgrade. Today, admins must manually configure language and geo boost settings, and users must explicitly set a preferred language for it to influence results. With enhanced MLS and the new Enterprise Search (ES) plugin (more details here), both become native ranking signals in the core stack, which means employees will automatically see results best matched to their locale and query language without requiring manual configurations. You will still be able to interact with Assistant in 100+ languages as you do today.
In Q3, we'll further enhance user control by replacing today's "preferred bot response language" with two settings that apply across Assistant and Search:
- App Interface Language: Sets the language of the UI (navigation, controls, labels), independent of what language a user types.
- Response Language: Sets the default language for responses, employee communications and notifications. Regardless of this setting, users can interact in any language and the experience will respond in the language used for that interaction.
Also in Q3, we’ll display citations in the source’s original language, with the option for users to translate them into their query language when needed.
Refer to the table below for a comparison of current and future state.
When will this MLS upgrade be available?
Early access to new MLS capabilities will be available starting early Q2 onward, with general availability starting mid-late Q2.
Get early access
If you'd like to try upgraded MLS capabilities ahead of the general rollout, please fill out this form to register your interest for early access. Reach out to your account team with any questions.
| Functionality | Current State: KS plugin | Future State: ES plugin + MLS |
|---|---|---|
| Non-English content search | KBAs: supported ✅ Files: not supported ❌ | KBAs: supported ✅ Files: supported ✅ |
| Admin controls on geo/language relevance | Three admin-configured controls for geo + language | Admin boost controls removed; geo/language handled natively via ranking signals |
| Geo handling | Two admin controls: Geocode Boost (KBAs) + File Search Geocode Boost (Files) with Disabled/Soft/Hard | Geo becomes a ranking signal (no hard/soft settings) |
| Language handling | One admin control: Language Boost with Disabled/Soft/Hard | Language becomes a ranking signal (no hard/soft settings) |
| Retrieval and ranking language handling | Double translation of non-English queries and non-English documents | Retrieval and ranking done natively in original languages |
| Query/response language handling | Assistant understands all languages, but will respond in the bot preferred response language if it’s set Scenarios: • English users can only see English sources in the response, no matter what settings • Spanish users may see English and/or Spanish sources in the response, depending on the setting | Assistant understands all languages, and is designed to respond in the language the user types in. It will do so the vast majority of the time. In some cases, Assistant may use the broader context of the conversation, such as a user's preferred language setting or frequent language switches, to determine how to respond, which can occasionally affect consistency.
|
| User preferred language (coming in late Q3) | Users can set their own bot preferred language through Assistant; admin-default used if not set | User can set two language settings: UI and preferred response; admin-default used if not set |
| Citations display language (coming in late Q3) | Citations are shown in the bot preferred language, either natively or translated on-the-fly | Citations are shown in the original content language, with an option for the user to translate to the query language |
