Build better products with our product team.
UCA -Preflight Checks ensures uninterrupted, successful UCA plugin runs.We do this in 2 ways:We ask for all of the UCA connectors required from the user before the plugin runs - no surprises. We continue the plugin execution with all of the prior context in tact so that users don’t have to manually “retry” - it just works.
Hello,In Plugin Insights, the section “What content items are being cited by the AI Assistant?” provides a very valuable overview of top-cited content, including counts of helpful and unhelpful feedback as well as related tickets. However, the current experience makes it difficult to take the next analytical step directly.Current LimitationAt present, clicking on the unhelpful/helpful feedback count does not provide access to the underlying conversations. To investigate these cases, users must:Access a different module (Moveworks Setup), which requires additional permissions not available in Analytics Manually search for KB article ID Navigate to the feedback table and filter out relevant feedback based on KB article IDThe same goes for tickets data – you can’t access underlying conversations leading to ticket creation from hereThe only thing you can drill down from this view is total interactions table which does not contain any feedback related data in the table/raw dataCurrent set up limits the ability to quickly derive insights.Proposed ImprovementEnable direct drill-down functionality from Plugin Insights Allow users to click on the helpful or unhelpful feedback count for a given content item Display a filtered list of all content-related conversations with users’ feedback entries
As per: https://help.moveworks.com/docs/multilingual-support-assistant and https://help.moveworks.com/docs/multilingual-support-copilot multilingual support is capable of translating everything EXCEPT an Agent’s comments back to a user’s preferred language on a ticket. A one-way translator is not sufficient to maintain a conversation. This is not a fully completed product as is and should not be advertised as such.PLEASE enable two-way translation for ticket comments.
I have created a couple of highly customized connectors in Moveworks and would like to put them for sell. Is there a Marketplace where I can share it for users. Something equivalent to ServiceNow Marketplace where I have my customized scoped hosted and make revenue in application keys in accordance to its usage.
TL;DRAdd connector visibility in UI → eliminate guesswork across environments.ProblemMultiple ServiceNow environments (DEV → UAT) connected in Moveworks. Forms with the same name appear multiple times with no indication of source environment. When a form fails to fill, it’s unclear which environment it belongs to. Current workaround requires checking ingestion timestamps/logs → inefficient.RequestSurface Connector / Environment on: Imported Forms table (new column) Form detail page (Overview section) Expected OutcomeQuickly identify whether a form is DEV or UAT. Remove need to cross-check ingestion logs. Faster troubleshooting and safer configuration.
Enable employees to create task-specific Assistants with enterprise governance and analytics.
Key DatesFrontier: April 20 2026Standard: April 22 2026Basic: April 24 2026Learn more about our model upgrades here.We've made improvements to our toxicity filter, resulting in more reliable and consistent moderation within the assistant.
Problem: The Moveworks Employee Slate notifications panel currently requires colleagues to individually click each notification to mark it as read, with no option to mark all as read or bulk select via checkboxes. This makes the panel unusable at scale, since a colleague with 40 notifications must perform 40 separate clicks to clear their unread count to zero.Feature Request: Add bulk action controls to the Employee Slate notifications panel, including a "Mark all as read" button that clears every unread notification in a single click, and individual checkboxes on each notification with a "Mark selected as read" action for users who want to clear notifications in batches. These controls should be persistently visible at the top of the panel so colleagues can manage high notification volumes efficiently without repetitive clicking.
MoveWorks should support handling Purview Sensitivity Labels in SharePoint documents; at a minimum, provide ways to filter out documents with certain labels in knowledge ingestion and possibly provide other features (like label recommendation when drafting emails/documents and applying labels to documents).
Enable admins to configure custom domains in Ticket routing and workflows DSL so custom domain ticketing can be supported.
Despite clear user utterances (e.g. payslip, salary, tax form, leave balance), the Moveworks AI often fails to classify topics correctly, pushing high‑volume demand into “uncategorized” buckets. Improving intent‑to‑topic mapping here would increase accuracy and insights quality. We also noticed that Moveworks Analytics struggles to categorize a Domain when citing mainly (only?) pdf files when generating response and it states Domain as “N/A”.
Enable multi-brand customers to apply different branding for different populations of users.
Contrary to earlier assurance, during tests we have identified that Moveworks is not able to follow/read Salesforce permissions when ingesting content from Salesforce Knowledge. It creates a situation for us that end-users can get access to content through Moveworks that normally they wouldn’t see as their access is restricted in Salesforce. It would be great if Moveworks could read Salesforce permissions in this respect same way as it does it for Sharepoint.
We would like to request that Data API supports user additional information stored on user roster (e.g. user location, country etc.). We are building dashboards in other platforms like PowerBI bringing data sources from various systems including Moveworks. This limitation blocks us to do that fully automatic.
I would propose to consider removing “preferred language” setting in AI Assistant. We see challenges, when end-user sets keeps preferred language as “English” for example (which is a default one) and starts talking to AI Assistant in other language. There are scenarios that at times Moveworks AI determines that the user wants to change preferred language and offers that, but sometimes it doesn’t recongize such intend and just responds. It leads to situations when parts of the answer sometimes are written in English and parts in other language and we have been told this could be underlaying reason for this behavior (i.e. that “preferred language” setting is different to the language user actually speaks to AI Assistant). Instead, it would be great if Moveworks AI just continue recognizing the language in which user speaks to it and then provide the answer in it without a need to even think/consider the preferred language setting.
It would be great if conversation context could be kept/”remembered” by Moveworks regardless if same user talks to AI Assistant on MS Teams or Slack or “on Web” version. We have business requirement to surface AI Assistant also on our intranet main page, but because MS Teams remains our main experience layer for Moveworks AI, the fact that context is not kept between various forms of displaying AI Assistant made us resigning from doing so.
It should be configurable whether end-user for the given deployment of Moveworks sees details of how many systems & articles AI reasons through before answer is provided. In our case, end-user do not see value in seeing all those details that AI is going to let’s 45 Sharepoint articles and 15 ServiceNow knowledge materials. We would like to have an option to turn it off.
Real-time text streaming from the Assistant within Slack. Users see response tokens appearing progressively, like a live typing effect.
The Assistant responds to every channel message - including responses from web search and Agent Studio plugins - with polished feedback and live agent hand-off flows in DM.
Support Vetted Content in Assistant experience
Being able to easily see the title of a SharePoint site that a file or internal knowledge article comes from would be an awesome quality of life feature for knowledge ingestion!
Hi ,As we have multiple Moveworks instances within our organization, I would like to explore the possibility of configuring distinct color schemes for each instance. This would enable quick visual identification at a glance. Regards,Rajeev
SummaryMoveworks ticket and approval notifications do not display Multi‑Row Variable Set (MRVS) data from ServiceNow catalogue items. This leaves approvers without key context.ImpactLimited visibility for access requests using MRVS Extra friction opening ServiceNow to review details Slower approvals and reduced confidence in notificationsRequestAdd support to parse and render MRVS rows inline in Moveworks notifications so approvers can make informed decisions without leaving Moveworks.If MRVS is used in your ServiceNow environment, please upvote.I’ve already been down the support route and they encouraged me to raise a product idea.
Improving reliability and clarity of file upload prompts in plugin workflows — ensuring users get timely upload buttons and clean completion states across multi-step interactions.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.