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

    1344 Ideas

    Back to top of the list
    dhorvathCommunity Manager

    End-User Tool Approval Preferences2. On Roadmap

    How are we improving the product?Let users choose how long a tool approval lasts (once, for the current session, or always), then manage those choices outside the runtime prompt on the Connectors settings page. Users can review their preferences, reset them to the admin default, and avoid repeated prompts for tools they already trust.

    0
    1 month ago
    dhorvathCommunity Manager

    One-Click MCP Catalog5. Controlled Availability

    Connect popular MCP servers in one click from a growing catalog.

    0
    1 month ago
    dhorvathCommunity Manager

    Admin Controls for MCP Clients4. Future Consideration

    Admin Controls for MCP Clients include:MCP Tool approval policy -> Let admins set an approval policy for an individual tool: follow server guidance, always ask, or never ask. Block Tool Availability -> Let admins block an individual tool so it can never run anywhere in the org, instead of having to disable the whole server.

    0
    1 month ago
    davrey04Participating Frequently

    Add functionality to Knowledge Studio1. New

    Knowledge Studio presents topics where we already have at least one ServiceNow article.Suggestions are:From the main page of KS, be able to mark a topic or item as Already Exists. This prevents it from being presented for 3-6 months. There is no reason to create a second version with the same content.Mark suggestions as Not relevant: The topic is not relevant to our users or our business. There is no reason to write an article that can only be used by 1-2 upper admins while ignoring the needs of the many. Mark Suggestions as complete: KS users can review a suggestion and when relevant articles are written or updated, mark them so they are removed from the list.'What is also helpful is integrating some of the functions from the Employee Experience Insights. Since gaining access to EXI, I’ve found it more useful than KS. Why? Because EXI shows me areas of concern and then lets me drill down into various topics.Ideally, I could find a topic with an insight and have KS suggest an update to an existing article. When no article exists, it could create an outline of a new article then ideally draft the precise steps new users could take to resolve the related issue.Having this integration would let our bot quickly and more accurately relate an article to a user’s comments.

    0
    1 month ago
    amykNew Participant

    Enable dot-walking into custom_attributes in the Data Mapper1. New

    Description: The Data Mapper's "Available data input" picker lets you browse and select standard fields (e.g. department, cost_center_id) by clicking through the list, without needing to know their exact names in advance.custom_attributes (and custom_data), however, show up as a single collapsed entry.To reference a specific one (e.g. user.custom_attributes.office), you have to already know the exact attribute name and type it out manually. There's no way to expand and browse the individual keys the way you can with other nested fields like employment_info.Ask: Allow custom_attributes (and custom_data) to expand in the picker like other structured fields, so devs can see which attributes are actually available to them and select the one they need without already knowing its exact spelling.Why it matters: Custom attributes vary by org and are often configured by someone other than the person building the workflow. Without visibility into what's available, builders have to go dig through documentation or ask around just to get the name right, slowing things down and risking silent mapping errors from typos.

    0
    1 month ago
    JennyPNew Participant

    Use POST binding when granting consent1. New

    We have some Outlook Plugins we implemented and we are noticing that our users were getting a 404 error when they were trying to consent. After some research, it was determined that it was the sign in link that it was too long and exceeding the limit set on our SAUTH realm. We were able to adjust it and increase it and that seemed to resolve the issue, however our SAUTH team asked for the possibility to do a POST binding which will fix it from the get go. Something for consideration

    0
    1 month ago
    dhorvathCommunity Manager

    ServiceNow Flows & Actions in Moveworks5. Controlled Availability

    What is ServiceNow Flows & Actions in Moveworks?ServiceNow customers have built years—often decades—of business logic and automation using Flow Designer, Workflow Studio, actions, and subflows. This capability makes those existing ServiceNow automations available as execution tools for Moveworks agents.Rather than rebuilding the same logic in a separate system, teams can expose selected ServiceNow actions and subflows through a ServiceNow MCP server. The Moveworks Assistant can then invoke those tools as part of a conversational request, while the underlying automation continues to run in ServiceNow.AvailabilityThis capability depends on MCP Workspace, which will provide the Moveworks-side experience for configuring and managing MCP connections and tools.  How it worksAn administrator configures an MCP server in ServiceNow using MCP Platform Manager. The administrator registers the appropriate Flow Designer actions and subflows as MCP tools. Moveworks connects to the ServiceNow MCP server and makes the approved tools available to its agents. When a user's request requires an action, the Moveworks agent invokes the relevant ServiceNow tool and presents the result in the conversation.ServiceNow supports creating MCP tools from both Flow Designer actions and subflows.What can users do?The available experiences depend on the automations each organization chooses to expose. Example requests could include:“Register Tempo Analytics as a new business application.” “Start the employee offboarding workflow for this contractor.” “Request approval to add this application to the software catalog.” “Provision the standard development environment for my new engineer.” “Run the approved remediation flow for this configuration item.” “Create the application record and route it to the correct owner for approval.”For example, an existing ServiceNow flow could check whether an application already exists, create or update the appropriate records, route an approval request, and notify the relevant teams. The employee initiates the request in Moveworks, while ServiceNow remains the system executing the established workflow.Why it mattersReuse existing investments: Extend ServiceNow automations your organization has already designed, governed, and tested. Avoid duplicate development: Make existing actions and subflows available to Moveworks agents instead of recreating their logic elsewhere. Bring execution into conversation: Let employees initiate complex workflows using natural language in the Moveworks Assistant. Keep administration in ServiceNow: ServiceNow administrators choose which automations become MCP tools and how those tools are configured.Configuration and requirementsAdministrators will configure the ServiceNow MCP server and select the actions and subflows that should be exposed as tools. Individual tools must meet ServiceNow's compatibility, input/output, and access-control requirements.This capability uses MCP to connect Moveworks agents to the tools configured in the customer's ServiceNow instance. Additional resourcesServiceNow MCP Platform Manager Create a tool from an Action Create a tool from a Subflow

    0
    1 month ago
    atulchandNew Participant

    Add fields in Analytics1. New

    Enhancement to enable missing API fields (Location, department, country, lanuage) which are available in the OOB Dashboard. 

    1
    1 month ago
    JRO193New Participant

    In Chat Provide Thinking Detail for All Thinking Messages After Prompt1. New

    AdventHealth is writing to suggest that Thinking Detail be added to each separate Thinking message presented after prompt for clarity so that multiple messages do not appear redundant.  In the example below, the first arrow points to Thinking Detail and the second to the spot where we would like the detail for that thinking step to be added: 

    0
    1 month ago
    JRO193New Participant

    Message Indicating Longer Processing Time in Chat1. New

    AdventHealth would like to propose an active indicator to denote that a chat response is forthcoming with a message to indicate that the chat is “still thinking” or “working on it”.Some of our Moveworks Plugins require more processing time than others, yet the system doesn’t actively indicate that the Chat is still “thinking” before providing an answer.  The result is that the user may leave the chat assuming that the chat is either not working or will take too long.  Example: 

    0
    1 month ago
    Penny Zhou
    Penny ZhouCommunity Manager

    Minor ML Update: Reducing Source-System Mentions in Assistant Answers6. Delivered

    How are we improving the Assistant’s behavior?Previously, Enterprise Search answers sometimes named the backend system that stored the content—such as “Google FAQ,” “GSheet,” “ServiceNow,” or “Content Gateway”—instead of focusing on the information itself.With this update, answers describe the content directly, making responses clearer and more natural. For example:Before: “According to the Google FAQ, employees receive 20 days of PTO.”After: “Employees receive 20 days of PTO.”Before: “Based on the information I found in Content Gateway, submit the request by Friday.”After: “Submit the request by Friday.”Citations and source links continue to work as before, so users can still inspect and open the underlying documents.When is the release date?Frontier release: October 6, 2026Standard release: October 8, 2026Basic release: October 13, 2026Technical restrictionsNo configuration is required. This is a prompt-only behavior change; retrieval, ranking, document permissions, and existing customer-specific attribution settings are unchanged.DocumentationNo additional helpsite documentation is required for this behavior change.

    0
    Penny Zhou
    1 month ago
    Aishwarya ParthasarathiNew Participant

    Report an issue - button1. New

    Suggested Enhancement: Consider displaying "Report an Issue" as a button instead of a hyperlink.Buttons are generally more noticeable and intuitive for users than hyperlinks. Colleagues are more likely to engage with a clearly visible button when they need to report an incident. Increasing the visibility of this action could help drive users toward the correct Incident reporting channel. This may improve adherence to the intended reporting process and potentially increase the number of incidents raised through the appropriate workflow.

    0
    1 month ago
    marissa.lacombeParticipating Frequently

    Enhancement to keep formatting when copy/pasting Generated Content4. Future Consideration

    When generating content via Moveworks you cannot copy/paste the content to another platform (email/teams etc) while maintaining the formatting. Once you paste the content, all formatting is lost & has to be redone. I tested in Microsoft Copilot and the formatting is retained.Here are some screenshots showing the user experience and what happens when i copy/paste this generated content  Subject: Features of ArteyBody:Hi [Recipient's Name],I wanted to share some key features of Artey with you:- Automated Approvals: Streamlines the approval process for various requests.- Knowledge Search: Provides quick access to relevant documents and information.- Ticket Management: Helps in tracking and managing IT tickets efficiently.- Email Drafting: Assists in drafting emails for various purposes.- Outage Reporting: Identifies and reports active outages affecting services.Please review and let me know if you need any additional information.Best regards,Marissa Lacombe

    8
    1 month ago
    Indrashis
    IndrashisCommunity Manager

    Data Crawling Updates for Migrated Content Connectors6. Delivered

    What changesMigrated content connectors appear under Content (new architecture) in Moveworks Setup → Data Ingestion → Data Crawling. As these connectors move to the new ingestion architecture, their troubleshooting view changes to failed API request counts and a View Failed Logs action.The updated view helps administrators investigate failed source-system requests. It is an interim monitoring experience and does not provide the previous full-refresh and incremental run history or an overall crawl-health assessment.AvailabilityThe updated view is released. Content (new architecture) appears automatically for connectors after they are migrated to the new ingestion architecture for your organization. The connector migration determines when you see the section; you do not need to enable the view yourself.Your organization may have connectors under both Content and Content (new architecture) while migrations continue. Follow the instructions for the section where your connector appears.How to investigate a failed requestOpen Data Crawling in Moveworks Setup and expand Content (new architecture) using View Crawls.Locate your connector under the relevant resource group and select View Failed Logs.Review the Timestamp, Error Code, Error Message, and API Request. Filter by error code to narrow the results.Use the request details to investigate source-system access or configuration with your administrator. Contact Moveworks Support if the issue remains unexplained.What the view can and cannot tell youCrawl Health displays Not applicable. This means the section does not provide a crawl-health assessment; it is not a Healthy or Unhealthy result. Full-refresh and incremental run charts, individual run details, and per-run record inspection are unavailable in this view.Failure counts represent logged API-request events. Multiple entries can refer to the same endpoint or problem. Counts do not measure missing documents or unique unresolved issues, and historical failures may not describe the connector's current state.An empty failed-request table does not establish complete or current ingestion. Use the existing record-level inspection tools in Control Center to investigate a particular article or file. Contact Moveworks Support for unresolved questions about missing or stale content.Customer actionYou do not need to recreate your connectors or move them between sections. For connectors that appear under Content (new architecture), use the updated failed-request investigation workflow. Connectors under Content continue to use the existing run-based monitoring experience.DocumentationSee the Data Crawling View documentation.

    0
    Indrashis
    1 month ago
    rijesh_rkNew Participant

    Add Mandatory Classification to Thumbs-Down Feedback for Better Issue Diagnosis1. New

    When a user gives a thumbs-down to a response from Una, we currently rely on open-ended comments to understand what went wrong. However, this often leads to vague or inconsistent feedback that’s hard to action.Proposal: Introduce a mandatory follow-up prompt that classifies the issue into one of the following categories: Didn’t understand the request  Gave incorrect info  Took too long  Other: [Open comment box]Why this matters:This simple classification will allow us to precisely tag the root cause of dissatisfaction—whether it's a prompt interpretation issue, a knowledge gap, or a latency concern—without having to manually interpret user narratives. It will significantly improve our ability to:Prioritise fixes based on issue type Track trends over time Route feedback to the right teams (e.g. content, infra, NLU)Example:User asks: “Reset my password.”Una responds.User gives thumbs-down → Prompt appears:“Sorry that didn’t help. What was the issue?”User selects: [ ] Gave incorrect infoThis structured input will help us move from anecdotal to actionable insights.

    1
    1 month ago
    KaviKnown Participant

    Enable Conversation ID Mapping for Agent Studio Use Cases4. Future Consideration

    I propose introducing a mechanism to pass the conversation ID to use cases created via Agent Studio. Since most ticket operations in our organization—such as ticket creation and notifications—are planned to be customized using Agent Studio, having the conversation ID available within these use cases would allow accurate mapping between bot interactions and downstream ticket actions. This would significantly improve tracking, reporting, and deflection analytics.

    6
    Kevin Mok
    1 month ago
    JennyPNew Participant

    Bring Custom Attributes to Raw Interactions table1. New

    I would love to be able to add custom attributes into the Raw Interactions table. There are some custom attributes that will help us address a current reporting limitation we are experiencing. Currently I am manually doing data joins to derive meaningful business reporting that could be easily fixed if I have one custom column added to the raw table. The raw interaction export does not expose all customer-specific metadata directly in the dataset. For example, my reports required mapping interaction data across 11 regions, 83 companies, and 5,269 departments (I know!!!) 

    0
    1 month ago
    Derrick
    DerrickInspiring

    UI-Based On-Prem Agent Service Management1. New

    ProblemToday, configuring a new service for an on-prem Moveworks Agent requires administrators to obtain server access, manually modify the agent configuration file, and restart the Docker container. This creates operational overhead, requires elevated permissions, and increases the risk of configuration errors.Additionally, when an agent is upgraded through the Moveworks UI, the version displayed in the underlying configuration file does not appear to be updated, creating potential confusion when troubleshooting or validating deployed versions.Proposed EnhancementExtend the On-Prem Agent management experience to allow administrators to:Add, edit, and remove service configurations directly through the Moveworks UI. Validate configuration settings before deployment. Apply configuration changes without requiring manual file edits or direct server access. View the effective running configuration and deployed agent version from a single interface.Additional ImprovementEnsure agent upgrades performed through the UI update all version references consistently, including any version information stored within the agent configuration files, so administrators can easily verify the currently deployed version.Business ValueReduces the need for sudo/server access. Eliminates manual configuration file maintenance. Lowers risk of configuration errors and deployment inconsistencies. Improves operational efficiency and supportability. Provides a more complete self-service administration experience for on-prem agent management.

    0
    Derrick
    1 month ago
    James_N111New Participant

    Add a column to Analytics Interactions to identify Event Triggers1. New

    I am having trouble getting an account of what event triggers are used as I can not find that information on the csv export file. Though the interactions can be looked at in detail through Data API, my team is looking for alternatives to Snowflake for sustained reporting. In order to get an account as to how many times a plugin is used as an event trigger and to verify correlation with the Analytics Overview dashboard, I propose adding an Event Trigger Used column to the Interactions report.

    0
    1 month ago
    atulchandNew Participant

    Moveworks: Screenshot/Image reading capabilties1. New

    Moveworks currently does not support reading images/screenshots. Hence colleagues have to describe the issues in words rather than just sharing the screenshot of error received.

    0
    1 month ago
    raelee.busk

    Analytics Overview Confusion1. New

    Since switching to the new AI Assistant version of the bot, we’ve learned a lot about using and interpreting the analytics that come with it, and overall, the improvements over time have been great. That said, there are a few areas where enhancements could make a big difference in usability of the data without adding extra steps or the need to dig in to feel confident with the data.Some details, like formatting and consistency, are minor. The bigger challenge for us is the Overview page in AI Assistant Insights.For example, the report at the bottom of the page shows plugin calls categorized as unsuccessful, served, and used. While this is interesting, it’s hard to apply in a meaningful way. It often requires cross-referencing individual plugin insights pages to track activity and effectiveness, which adds complexity.It would be incredibly helpful to have options to filter this data, like viewing only served and/or used plugin calls and to click on categories to see relevant chat data directly. This would reduce the need to navigate to “View interactions” or dig through raw data with multiple filters just to understand interaction patterns.I’d love to hear how others might be using this data as it is right now, though. If anyone has suggestions, I’d be open to hearing them!

    1
    1 month ago
    willmurphyCommunity Manager

    Minor ML Update: Context-aware toxicity filtering6. Delivered

    Key DatesFrontier: September 2 2026Standard: September 8 2026Basic: September 10 2026Learn more about our model upgrades here.We’re upgrading the AI Assistant’s toxicity filtering to consider the full context of a conversation rather than evaluating content in isolation. This provides a more accurate understanding of user intent and helps identify genuinely harmful content. The upgrade also reduces false positives, allowing safe conversations to continue without unnecessary interruption. Administrators can review the configuration steps for more information: https://help.moveworks.com/agent-studio/agentic-ai/conversational-safeguards-assistant/configure-moveworks-toxcity-filter#configuration-steps

    1
    1 month ago
    SudheerCommunity Manager

    Merge Employee Communications with ServiceNow4. Future Consideration

    How are we improving the product?Teams currently need to configure employee communications separately across EmployeeWorks and Moveworks.A unified API will allow teams to launch a single employee communication across both surfaces together. This reduces duplicate authoring and helps employees receive consistent, timely communications wherever they work.Why is this important?A connected workflow simplifies communication management and helps organizations deliver a consistent employee experience across EmployeeWorks and Moveworks.

    0
    1 month ago
    vpawar
    vpawarCommunity Manager

    Domain Separation2. On Roadmap

    How are we improving the product?Managed service providers (MSPs) often serve multiple customers through a single domain-separated ServiceNow instance, where each customer’s data is partitioned into a separate domain. EmployeeWorks does not support this deployment model today.This initiative will help MSPs extend EmployeeWorks to customers within shared, domain-separated ServiceNow environments.What is included in this milestone?This milestone adds domain-level filtering for the ServiceNow connector within Moveworks. This enables the connector to operate within the intended customer domain when connecting Moveworks to an MSP’s shared ServiceNow instance.Future milestones may expand support for domain-separated deployment models.

    0
    vpawar
    1 month ago
    kyril.remillard
    kyril.remillardCommunity Manager

    Automate EmployeeWorks Onboarding for ServiceNow Customers6. Delivered

    How are we improving the product?ServiceNow customers will have a ready-to-use EmployeeWorks instance available on day one.Automated configuration synchronization from ServiceNow to EmployeeWorks will establish the required baseline configuration, reducing manual onboarding work and helping customers get started faster with a consistent setup.How does it work?Required EmployeeWorks configurations are synchronized from ServiceNow.New customers receive an EmployeeWorks instance with the baseline configuration already available.Existing AI-native customers will be migrated using internal tooling operated by FDEs.Customer impactCustomers will spend less time waiting for manual configuration and can begin onboarding with a prepared EmployeeWorks environment.

    0
    kyril.remillard
    1 month ago
    Show more activity

    Filter by product

    • All products
    • Analytics
    • AI Assistant
    • Tool 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
    • Channels
    • Assistant Platform
    Terms & ConditionsAccessibility statement