Build better products with our product team.
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.
This is the AI Assistant as an agent within the Microsoft Copilot experience. Right now, this is a Closed Controlled Availability and not accepting new customers at this time.Read more - https://www.moveworks.com/us/en/company/news/press-releases/moveworks-third-party-agent-for-microsoft-365-copilot
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.
Can we have interactive buttons available again for Agent Studio?Previously, this feature was only supported in Classic Studio, which is being phased out soon. We’ve been developing several use cases that rely on active user input, and the lack of buttons is creating friction in the experience.More teams are requesting approval workflows through our chatbot. While the interactive button options can be done natively with ServiceNow, it won’t be possible for other API-based use cases, which could make the experience inconsistent and confusing for end users.Additionally, many of the plugins showcased in the AI Agent Marketplace display buttons as part of their interface. Does this indicate there’s already a roadmap for bringing this functionality back to Agent Studio?
Enable admins to programmatically access and configure Moveworks
Key DatesFrontier: May 11 2026Standard: May 14 2026Basic: May 18 2026Learn more about our model upgrades here.Improvements to how the AI assistant identifies and selects the right applications and resources when processing user requests. This update ensures that customer-configured catalog items are prioritized over generic defaults, leading to more accurate plugin responses — particularly for software access workflows.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.