Skip to main content

Get Started

The roadmap, product ideas, and product plans are subject to change without notice. These plans may be refined, updated, or revised from time to time, based on customer input and market conditions. The plan described herein is provided solely for information purposes, and is not a commitment, promise, or legal obligation to deliver any material, code, or functionality.

Share your feedback in our Product Ideas Portal

Welcome to the Moveworks Product Ideas Portal!We are committed to listening to and incorporating your feedback to our Moveworks Product Roadmap. What...

    Filter by idea status

    Filter by product

    1293 Ideas

    davrey04Participating Frequently

    Resolving blank feedback1. New

    Currently most knowledge article feedback is a simple thumbs up or thumbs down, with no comments indicating what that user found helpful or unhelpful. What would help is, since Moveworks can access ServiceNow’s tables, having the bot check a feedback item.If the item has a comment, it sends it directly to the ServiceNow Feedback table.If the item does Not have a comment, the bot emails the user and asks them to comment on what they liked or disliked about the article. After sending that note, the bot forwards the feedback to ServiceNow, adding a “Comment requested” like to it.This would help companies that get a lot of feedback improve their knowledge articles. Thank-you.

    0
    Forum|Forum|27 days ago
    Arnaud CLAVEAUNew Participant

    Teams bot with the same look and functionalities as Webchat assistant1. New

    Hello,Currently the Teams bot, does not have the same look and functionalities as the chatbot assistant.Should be good to have the same look / behavior between all Moveworks chats bots (notification tab, chat tab...) and especially in Teams to have confusion between notification and chats / exchange with the bot.Or just propose the chatbot assistant page to be compatible to be embedded in TeamsRegards,Arnaud 

    0
    Forum|Forum|27 days ago
    Arnaud CLAVEAUNew Participant

    SharePoint integration in a site instead of in a page1. New

    Hello currently the Moveworks for Web web part needs to be manually added to each individual SharePoint page. We'd like the assistant to appear automatically on every page across our site(s), without having to add the web part page by page. In SharePoint, the standard way to achieve this is via an SPFx Application Customizer (deployed tenant-wide through the Tenant Wide Extensions list), rather than a page-level Web Part - it injects into a page placeholder (e.g. Bottom) automatically on every modern page, with no per-page setup needed.It is should be good to have Moveworks offering an Application Customizer variant of the SharePoint integration, instead of or in addition to the current Web Part.Regards,Arnaud

    0
    Forum|Forum|27 days ago
    mandarmarkandeyaNew Participant

    Feature Request: Manage Moveworks Support Tickets Directly in the Bot1. New

    Hi everyone,We currently use the Moveworks bot to manage our organization's internal ServiceNow tickets, and it's been a great experience for our team to view statuses and update tickets directly in chat.Since Moveworks recently migrated its customer support ticketing to ServiceNow, I wanted to see if there are any plans to allow us to manage our Moveworks Support Tickets directly from our own bot?Ideally, we would love the ability to:Check the status of our open Moveworks support tickets. Add comments or updates to the tickets directly in the chat interface. Receive proactive notifications when a Moveworks support agent updates our ticket.Having a single pane of glass for both our internal IT tickets and our Moveworks support tickets would streamline our workflow tremendously. Has anyone else built a custom Agent Studio plugin for this, or is this something on the product roadmap?Thanks!

    1
    hundleymf
    Forum|Forum|28 days ago
    afleury
    afleuryInspiring

    Saved prompts and prompt gallery for Moveworks AI Assistant4. Future Consideration

    One of the challenges as a Moveworks Admin and Dev is sharing with the users what prompts they have access to. There is no easy way to export all of them (even via the Support route) and keeping prompts up to date in a document or KB article requires manual effort.Microsoft has taken steps to resolve this issue for users with their Prompt Gallery. As of July, Microsoft will be building the Prompt gallery into the Copilot chat for even easier access.Changes to the Copilot Prompt Gallery app - Microsoft SupportFor best user experience, I would love to see Moveworks implement a solution like this in the AI Assistant as well. https://copilot.cloud.microsoft/en-US/prompts/all?ocid=CopilotLab_M365Chatofficeweb

    6
    afleury
    Forum|Forum|28 days ago
    nicholas.marr
    nicholas.marrNew Participant

    Chatbot iFrame Open Functionality from Hosting Website1. New

    Allow the hosting website presenting the chatbot i-frame to dynamically open the i-frame chat window. In our ServiceNow instance, we have our ColleagueZone page that presents outage information to the user. There are buttons on each individual outage that trigger a Moveworks plugin to provide A.I. insights about the outage to the user’s chat window in Teams. We’d also like it to pop open the i-frame chat window on the ColleagueZone page. We see in the Network console the following event that might drive this behavior, we just want to be able to trigger it from the hosting webpage if possible: {events: [{url: "https://webchat-kprod.moveworks.io/chat", startTime: "2026-08-14T15:37:40.208Z",…}]} events: [{url: "https://webchat-kprod.moveworks.io/chat", startTime: "2026-08-14T15:37:40.208Z",…}] 0: {url: "https://webchat-kprod.moveworks.io/chat", startTime: "2026-08-14T15:37:40.208Z",…} action: {actionType: "OPEN", name: "host_page"} actionType: "OPEN" name: "host_page" namespace: "movewebchat" source: "USER" startTime: "2026-08-14T15:37:40.208Z" url: "https://webchat-kprod.moveworks.io/chat" webMetaInfo: {,…} webappNamespaces: "MOVEWEBCHAT"

    0
    nicholas.marr
    Forum|Forum|1 month ago
    MikeINew Participant

    Include option to remove "thinking" process4. Future Consideration

    The visual created by the “thinking” process occurring and then being replaced by the answer/response can be jarring or distracting. I’d like to have the option to chose a single line of text such as “Working on your request. You’ll see your response here soon...” or simply responding with an emoji to show that the bot has your request. 

    17
    DIANA.TWC
    Forum|Forum|1 month ago
    JacekU
    JacekUNew Participant

    Ability to create NPS and multi question Surveys within Moveworks1. New

    It would be great to improve the Employee Comms Survey functionality to be more NPS inclusive.Currently within Employee communications a survey campaign could be created. However the response is limited to 5 buttons mirroring the CSAT methodology, however many organizations utilize the NPS methodology during surveys. It would be good if there would be the option to have more buttons. It would also be good to have the option of adding multiple questions to a campaign rather than just one. Finally it would be great if after a ticket is resolved, an NPS survey could be sent from Moveworks directly to the user utilizng the above mentioned functionalities.

    3
    Forum|Forum|1 month ago
    afleury
    afleuryInspiring

    Allow Policy Enforcement and Validation for Distribution List Provisioning1. New

    SummaryMany organisations use self-service provisioning to create distribution lists, groups, and collaboration resources. While access controls determine who can request these resources, there is often no way to enforce organisational standards during the provisioning process itself.ProblemToday, administrators can control who is allowed to create resources, but they cannot define and enforce policies that govern what is created.Common requirements include:Naming convention enforcement Approved domain validation Pattern or format validation Resource classification requirements Automatic standardisation of user input Custom business rules based on organisational needsWithout policy enforcement, organisations must rely on user training, manual reviews, or post-creation remediation to maintain standards.Proposed EnhancementIntroduce a policy validation framework that is evaluated as part of the provisioning workflow.Administrators should be able to:Validate user input before resource creation Define required naming standards Restrict values to approved formats or domains Apply automatic transformations where appropriate Display clear validation messages when requirements are not met Configure different policies for different resource typesExample Use CasesEnforcing naming standards for distribution lists Restricting email domains to approved corporate domains Requiring specific prefixes or suffixes Enforcing department or region identifiers Standardising display names and aliases Validating group ownership requirements before creationBenefitsImproved governance Consistent resource naming and structure Reduced administrative overhead Better compliance with organisational standards Fewer provisioning errors Better end-user experience through immediate feedbackWhy This MattersSelf-service provisioning is most effective when organisations can trust that resources created through automation comply with their internal standards. Access control answers who can create a resource, while policy validation answers whether the resource itself meets organisational requirements. Both capabilities are needed for scalable governance.Voting ask: If your organisation uses self-service provisioning and has naming, compliance, governance, or standardisation requirements, please upvote this idea to help prioritise policy enforcement capabilities within provisioning workflows. PS: I’ve already tried Moveworks/ServiceNow Support and Engineering teams advised to raise a Product idea.

    0
    afleury
    Forum|Forum|1 month ago
    ramapr1New Participant

    Improve translation and label clarity for request submission and help options1. New

    There are two areas causing confusion for employees interacting with Moveworks bot in Japanese language.First, the button label currently used across forms - “Complete this request”, is being interpreted too literally. In Japanese, the wording gives the impression that the action will finalize or close a process, rather than simply submit information for a question or request. Users feel this creates the wrong expectation and may discourage users from submitting their HR case request. A more neutral term, such as “Make” or another phrase that clearly indicates submission or creation, would better reflect the intended action.Second, the Get Help link is causing confusion because the Japanese translation appears as Support Request. Users see Get Help referenced in Moveworks bot, but they cannot find that exact option because the translated label is different. This becomes even more confusing when Moveworks bot explains that support request is not the same as Get Help. As a result, users are left unsure which option they should choose.We understand that Get Help is part of Moveworks out of box functionality. We would like to ask if there is any appetite to review or update this terminology for better clarity.In addition, request to make the wording "Complete this request" customizable.Requested outcome: We would appreciate Moveworks reviewing these terms from a localization and usability perspective so the labels are easier to understand for Japanese users and reduce confusion during request submission and help navigation.

    0
    Forum|Forum|1 month ago
    priya.kornalius
    priya.kornaliusKnown Participant

    Proactive Monitoring and Health Dashboard for MW Chatbot Skills4. Future Consideration

    We recently encountered an issue where MW chatbot failed to return relevant articles for a specific query. After reaching out to the support team, I learned that the bot didn’t trigger the knowledge skill plugin, which is responsible for searching related articles. Support team made the necessary adjustments, and the fix worked.However, this raised a concern: how can we proactively track and measure the health of the knowledge skill? We can’t always wait for users to report issues, as this impacts engagement and overall user experience.Wouldn’t it be beneficial if MW offered a health dashboard for all configured skills, allowing admins to monitor performance and make informed decisions? Additionally, having the option to subscribe to status notifications for specific skills would help us catch and address issues in real-time, ensuring smoother operations and exception handling.

    3
    Forum|Forum|1 month ago
    Penny Zhou
    Penny ZhouCommunity Manager

    Minor ML Update: Button-Click Response Language Fix6. Delivered

    Key DatesFrontier: August 17 2026Standard: August 19 2026Basic: August 24 2026Learn more about our model upgrades here.Previously, if you had your assistant set to a language other than English, clicking a button — like responding to a notification, approving a request, confirming an action, or following up on a ticket — could cause the assistant's next reply to unexpectedly switch to English, even mid-conversation. We've fixed this so the assistant now stays in your preferred language throughout these interactions. This applies across all button-based actions, for anyone using a non-English language, whether it was explicitly chosen or set as their default. Typed messages are unaffected — the assistant continues to respond in whatever language you're actively typing in.

    0
    Penny Zhou
    Forum|Forum|1 month ago
    cfinelliParticipating Frequently

    Add Support For Multiple Files In Agent Studio File Slots3. Existing Functionality/Native Skill

    This blog post https://www.moveworks.com/us/en/resources/blog/file-slots-file-uploads#one-file-per-slot-no-overwriting states: “Right now, you can only upload one file per File Slot. And once it’s uploaded, the user can’t replace it — they’d have to start over.This is a limitation we built in, not something forced on us. We could support multiple files, we just haven’t yet.”I’m currently building out employee submitted expense reports in agent studio and would love if they could just bulk upload all their receipts at once rather than 1 at a time. Multiple file support in a single slot would also significantly simplify my conversational workflow design since I wouldn’t need to create a slot for receipt 2, receipt 3, receipt 4, etc.In fact, in the same blog post, expense reports are mentioned: “Think about what you can build: expense reports with receipts attached”This capability would be great. Thanks!

    15
    Forum|Forum|1 month ago
    AMXNew Participant

    Custom Views from View Feedback1. New

    We can currently create and share custom views from the Interactions table for specific domain owners. It would be valuable to offer the same capability in the View Feedback report, allowing helpful/unhelpful feedback to be tailored by domain.Additionally, adding direct links to the content served during each interaction would enable domain owners to quickly review and validate content quality.

    0
    Forum|Forum|1 month ago
    nicole.hulst
    nicole.hulstKnown Participant

    Multiple Triage Models and integration of Triage with Agents from Agent Studio1. New

    We were having high hopes and expectations for Triage 2.0 to help us in reducing manual routing efforts to an absolute minimum. What we have found that Triage works exceptionally well in highly specialized cases where we have a high ticket volume. But this is not scalable. We can either have really good Triage for one Service or really crappy Triage for all our Services. What we obviously want is good to really good Triage for all Services to actually reduce our workload instead of just shifting it to second or third level support. The good results of the specialized models need to be scalable for enterprise wide useTo solve this issue what we require is the possibility to define multiple Models or Indices that run for different groups of Tickets. Ideally we could even have multiple Triage Runs on the same tickets. I envision something like: General Triage runs through all incoming tickets and identifies based on the description the right Service and routes to the respective Service Offering Depending on the Service Offering selected a new model is triggered for Triage for that specific Service and potentially take into consideration more fields than just description to route to the accurate second level group. Meaning we would have multiple models for the different services all specialized in the specifics of each service On a second Triage run also outside information should be taken into consideration such as work instructions for SD Agents that already contain explanations on routing accurately etc. Lastly if Triage cannot identify any further routing but the Ticket still needs automated actions we want to be able to trigger AI Agents to work on the ticket, but that trigger should come from Triage so there is no interference.  

    0
    nicole.hulst
    Forum|Forum|1 month ago
    nicole.hulst
    nicole.hulstKnown Participant

    Multiple Triage Models and integration of Triage with Agents from Agent Studio1. New

    We were having high hopes and expectations for Triage 2.0 to help us in reducing manual routing efforts to an absolute minimum. What we have found that Triage works exceptionally well in highly specialized cases where we have a high ticket volume. But this is not scalable. We can either have really good Triage for one Service or really crappy Triage for all our Services. What we obviously want is good to really good Triage for all Services to actually reduce our workload instead of just shifting it to second or third level support. The good results of the specialized models need to be scalable for enterprise wide useTo solve this issue what we require is the possibility to define multiple Models or Indices that run for different groups of Tickets. Ideally we could even have multiple Triage Runs on the same tickets. I envision something like: General Triage runs through all incoming tickets and identifies based on the description the right Service and routes to the respective Service Offering Depending on the Service Offering selected a new model is triggered for Triage for that specific Service and potentially take into consideration more fields than just description to route to the accurate second level group. Meaning we would have multiple models for the different services all specialized in the specifics of each service On a second Triage run also outside information should be taken into consideration such as work instructions for SD Agents that already contain explanations on routing accurately etc. Lastly if Triage cannot identify any further routing but the Ticket still needs automated actions we want to be able to trigger AI Agents to work on the ticket, but that trigger should come from Triage so there is no interference.  

    0
    nicole.hulst
    Forum|Forum|1 month ago
    rraj
    rrajCommunity Manager

    Deep Research Assistant2. On Roadmap

    Assistant that can deep research on internal knowledge, search the web, and analyze uploaded files

    0
    rraj
    Forum|Forum|1 month ago
    kyril.remillard
    kyril.remillardCommunity Manager

    HRSD Talent Intelligence Assistant2. On Roadmap

    Conversational workforce intelligence spanning instant data-backed answers, interactive deep research, and validated agent workflows like Succession Planning and Talent Risk

    0
    kyril.remillard
    Forum|Forum|1 month ago
    rkolady
    rkoladyCommunity Manager

    Voice Assistant4. Future Consideration

    Access to Moveworks Reasoning Engine via Call Center Integrations  

    0
    rkolady
    Forum|Forum|1 month ago
    anaTylerCommunity Manager

    Source Selection (Web Assistant Only)4. Future Consideration

    Enable users to filter down data sources to specific connectors.

    1
    andrew.mairena
    Forum|Forum|1 month ago
    andrewwhitleyInspiring

    HTTP Action support for multipart/form-data3. Existing Functionality/Native Skill

    As of now, multipart/form-data is not supported in http actions in agent studio. Therefore most of my requests have to be made using the application/x-www-form-urlencoded content type. This results in numerous encoding issues as Moveworks is not natively handling encoding like postman does. Can we get datamapper to support multipart/form-data alongside application/json?

    2
    Kevin Mok
    Forum|Forum|1 month ago
    JonathanKnown Participant

    Agent Studio - Assist Estimate1. New

    With EmployeeWorks coming down the pipe I think it would be a great idea that when you’re testing a new agent studio use case that Agent Studio provides you an estimate on the number of assist that using this module will take.I think that’ll help people try to make things more efficient on their end, but may also help them tailor their launch for people who will use it properly if it’s a high assist use product.

    1
    Forum|Forum|1 month ago
    JRO193New Participant

    Update Analytics Data SLA to 8am Daily1. New

    While we recognize that the current SLA provides for Analytics data availability by 4:00 PM on the following day, we respectfully request that the standard be updated to ensure data is available by 8:00 AM.This data serves as a critical input for daily operational reporting and performance analysis, including First Contact Resolution (FCR), a key metric used to evaluate service effectiveness. Access to prior-day data at the start of the business day is essential for timely reporting, trend analysis, and informed decision-making. Adjusting the SLA to an 8:00 AM availability would significantly enhance our ability to monitor performance and respond proactively to operational needs.

    0
    Forum|Forum|1 month ago
    vpawar
    vpawarCommunity Manager

    Add chatbot name to Data API6. Delivered

    Expose the chatbot / bot friendly name in the Data API so customers can attribute analytics by assistant.

    0
    vpawar
    Forum|Forum|1 month ago
    nicholas.marr
    nicholas.marrNew Participant

    Ambient Agent Plugin Analytics1. New

    It would be nice to be able to gather Analytics on Ambient Agent use cases we deploy such as link or button clicks. As an example, we currently have several plugins related to Clarity timesheets that are both conversationally triggered and scheduled triggered. The conversationaly triggered versions show up in analytics and we can see link and button clicks fine. The scheduled ones however don’t give us any analytics so we can’t update our stake holders to see if users are interacting with these notifications. 

    0
    nicholas.marr
    Forum|Forum|1 month ago

    Filter by product

    • All products
    • Analytics
    • AI Assistant
    • Agent Studio
    • Employee Experience Insights
    • Knowledge Studio
    • Moveworks Setup
    • Enterprise Search
    • Content Integrations
    • Content Gateway
    • Other Integrations
    • Next Gen Triage (2.0)
    • MW4Web
    • Service Management
    • AI Agent Marketplace
    • Agentic Reasoning Engine
    • EmployeeWorks
    • General
    Terms & ConditionsAccessibility statement