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

    chaney.zimmerman
    chaney.zimmermanEmployee

    Create Support Ticket from Log Entry4. Future Consideration

    Occasionally, some unexpected behavior will arise from an Agent Studio plugin, built in functionality, etc. Today I was picking through the logs for a plugin that ran earlier this week and found which log identified the break, but it’s not expected to me based on previous testing. I prepared to open a support ticket and thought: It would be nice to have a quick/deep link of some sort to open a ticket directly from this log entry I’m viewing, with the log automatically attached to the support ticket.The same functionality could be useful on the Raw Interactions table in the Analytics module as well. 

    2
    Ajay Merchia
    Forum|Forum|4 months ago
    gsachdevNew Participant

    Ingest ServiceNow Content Management news articles as a native knowledge source in Moveworks1. New

     OverviewMoveworks currently supports ServiceNow Knowledge Bases as a native data source for AI-powered responses. We'd like to propose extending this native ingestion capability to also include pages and news articles published through the ServiceNow Content Management System (CMS).Problem Statement Organizations frequently use ServiceNow CMS to publish important internal news, announcements, etc that are separate from structured Knowledge Base articles. Today, this content is not surfaced by the Moveworks bot, meaning employees receive incomplete or outdated answers — especially during organizational changes, system outages, or rolling news updates where CMS articles are the authoritative source. We'd like Moveworks to natively ingest ServiceNow CMS content (news articles, landing pages, topic pages) in addition to existing Knowledge Base ingestion — with the following capabilities:Native connector: Treat CMS pages/articles as a first-class source alongside Knowledge Base articles in the Moveworks data ingestion pipeline. Configurable scope: Allow admins to select which CMS categories, topics, or content types to include/exclude. Freshness sync: Respect publish/unpublish dates so the bot only surfaces active, non-expired articles. Attribution: Surface the article title and CMS URL in bot responses, consistent with how KB articles are cited today.Expected OutcomeBot AI responses become more accurate and timely by incorporating the full breadth of published internal content from ServiceNow — not just structured KB articles. Employees get one consistent answer source rather than being told to "check the intranet separately."IT, HR, and Communications teams who publish CMS-first content and want that content reflected in Moveworks AI responses without manual duplication.

    0
    Forum|Forum|4 months ago
    Indrashis
    IndrashisCommunity Manager

    Max Capacity Connector - MS Teams (Live Search)2. On Roadmap

    New Max Capacity connector for MS Teams - this will enable searching over all of you conversations from within MS Teams. This will be a live search connector.

    0
    Indrashis
    Forum|Forum|4 months ago
    2613196
    2613196

    Friendly Naming and Notes Support in Moveworks Studio4. Future Consideration

     To improve clarity and maintainability of complex workflows in Moveworks Studio, I’d like to request the ability to assign friendly names and contextual notes to various elements such as actions, activities, and scripts—especially within compound actions and the visual editor. This enhancement would significantly improve collaboration, debugging, and onboarding for new team members.Key aspects of the request:Allow users to assign custom, human-readable names to: Actions Activities Scripts Compound actions (especially in Moveworks Studio) etc Enable inline notes or annotations that: Appear as comments in code view Display as visual notes or tooltips in the visual editor Ensure that switching between code and visual modes preserves these friendly names and notes Optional: Provide a toggle or UI element to show/hide notes for a cleaner workspaceThis feature would enhance usability and make complex workflows more intuitive and maintainable.Example of a layout. 

    3
    2613196
    Forum|Forum|4 months ago
    2613196
    2613196

    Add Support for Cited Sources in Moveworks Conversation Flows3. Existing Functionality/Native Skill

    Plugin responses often pull data from multiple systems, users must see source details to trust the answer.  We have some cases where they are required to validate the queries etc before using them. such as our case in using Databricks AI/BI Genie, where we have to show the query, and raw data so the user can validate the response and query. Current cited‑source links are only an option for Compound Actions. Showing citations lets us include IDs, URLs, and troubleshooting metadata that reduce escalations. Improves accuracy, transparency, and aligns with Moveworks’ own rationale for verifiable, grounded answers. Critical for both user clarity, data use requirements and developer debugging.  This is also extremely important, to provide a way for the users to verify the real source of the provided answer, as knowledge or other sources might get called in place of the expected plugin.

    2
    2613196
    Forum|Forum|4 months ago
    Indrashis
    IndrashisCommunity Manager

    Troubleshooting Hub: Content2. On Roadmap

    What’s changing?Moveworks is introducing a dedicated Content experience in the Troubleshooting Hub within Moveworks Setup. It will bring content health, record-level troubleshooting, and access investigation into one customer-facing experience.The Troubleshooting Hub will help admins and implementation partners understand whether content and permissions are syncing correctly, identify customer impact, and resolve issues without navigating multiple tools or interpreting internal ingestion processes.The experience will include:Content health at a glance: Review synced and failed record counts across the organization and individual content sources.Source-level monitoring: Understand whether a newly configured source is scheduled, progressing normally, active, or affected by an issue.Impact-based issues: See clear explanations of problems such as blocked first syncs, stopped updates, stale permissions, or unavailable content.Record-level troubleshooting: Search content and understand whether each record is synced, stale, or failed, including the relevant reason and freshness information.Check Access: Test whether a specific employee can access a specific record and understand the identity, group, permission, audience, and access-rule decisions behind the result.Guided resolution: Review the affected scope, likely cause, recommended actions, ownership, and the checks needed to confirm recovery.These changes are designed to help admins and partners detect content and access issues earlier, understand their impact, and resolve common problems with less reliance on Moveworks Support.

    0
    Indrashis
    Forum|Forum|4 months ago
    sidvermaCommunity Manager

    Agent Studio Redesign6. Delivered

    Redesign Agent Studio's visual design to reduce cognitive load

    0
    Forum|Forum|4 months ago
    dhorvathCommunity Manager

    Agent Alerting: Log Export4. Future Consideration

    Detect failures and route alerts to the right owners (and/or into third party tools) so teams can fix issues quickly. Pipe Agent Studio's run-time logs directly into your existing tools, so you can build the dashboards and incident response workflows you already have.  

    2
    Forum|Forum|4 months ago
    wyuEmployee

    Hyperlink Preservation6. Delivered

    Ensures hyperlinks are consistently preserved and retrievable within citation summaries provided by the AI assistant.

    0
    Forum|Forum|4 months ago
    jgilmourNew Participant

    Analytics allowing for filterable custom attributes1. New

    Currently within Analytics, we can only use ‘department’ however we have other custom attributes that are ingested such as subFunction and Function. Having the ability to filter in analytics across these custom attributes would be extremely beneficial as right now we can’t drill down into how certain functions within a department are utilizing moveworks. I understand we can re-map department as a 1<>1 with another custom attribute, but I would like to be able to easily ingest others into analytics and filter on those. 

    0
    Forum|Forum|4 months ago
    jgilmourNew Participant

    Google Shared Drive Integration Leveraging Google Tags1. New

    I could see ingesting google drive content and having attribute filtering based on tag for ingesting/not ingesting content as a great improvement from whats available today.For example: An HR team may not want any sensitive information ingested into moveworks, but not want to restructure their google shared drive. Applying an ‘moveworks-ignore’ tag to not include this would be great as it allows for keeping the file hierarchy the same. 

    0
    Forum|Forum|4 months ago
    JLucasNew Participant

    Test Button(S) to validate URLs1. New

    Would be very helpful to have ability to test/validate at a per line level external references to ensure access/response is there.Example: under Import Settings → Form URL template (& Order guide URL template) a “test button” next to the text field where the URL is entered that a user can click for moveworks to make a call to the URL and provide a pop up with a positive or negative response of what the URL returned (ie something like a short ack handshake string or something) This would help in setup/troubleshooting 

    0
    Forum|Forum|4 months ago
    JLucasNew Participant

    ServiceNow Order Guide Interoperability1. New

    Would love to see Moveworks be able to work within an Order Guide to allow users to fill out multiple forms contained with an Order Guide vs the way it works today where it creates a link and directs the user out of Moveworks to the form

    0
    Forum|Forum|4 months ago
    andrew.mairena
    andrew.mairenaCommunity Manager

    Slack Marketplace App4. Future Consideration

    Making the Slack app available via the Slack Marketplace Store, for customers on the US Data Center 

    0
    andrew.mairena
    Forum|Forum|4 months ago
    andrew.mairena
    andrew.mairenaCommunity Manager

    Slack Native Reference Popup + Global Actions Revamp5. Controlled Availability

    Use the Slack pop-up to manage the MW Reference modal and Global Actions 

    0
    andrew.mairena
    Forum|Forum|4 months ago
    harman_devNew Participant

    Preserve User Identity & Interaction History Across Email (Join-Key) Changes1. New

    Today, any change to a user’s email address—the universal join key in our instance—causes Moveworks to create a new user record and deactivate the previous one. This breaks analytics continuity, as historical interactions remain tied to the old user ID and metrics such as first_interaction_time and latest_interaction_time reset under the new record. This behavior can also be triggered when a user updates their first or last name in Entra, since those updates often result in an email address change.Proposed solution: Introduce a stable, canonical user identity that is independent of mutable attributes like email address and use that identity to preserve analytics continuity across profile changes.

    0
    Forum|Forum|4 months ago
    ivovybiralNew Participant

    Unily Connector — Page Type Ingestion Filter1. New

    We'd like the ability to filter Unily content ingestion by page/content type.Currently, all content types are ingested without the option to exclude specific categories. This creates a practical problem: content types like news articles have a short shelf life and, once stale, can cause the assistant to return inaccurate or outdated responses. The only current option is to exclude entire site sections, which is too blunt when the issue is type-specific.A page type filter — ideally configurable per connector instance in the admin UI — would allow teams to include only the content types that are appropriate for AI assistant retrieval (e.g. policies, how-to guides, FAQs) and exclude those that aren't (e.g. news, announcements, event pages).This would improve response accuracy and give admins more precise control over what the assistant surfaces to users.

    0
    Forum|Forum|4 months ago
    rahulthakur
    rahulthakurCommunity Manager

    Content Troubleshooting Enhancements in Moveworks Setup6. Delivered

    Major upgrades to Data Crawling Viewer and Control Center with crawled records view, failed API call insights, record activity logs, improved indexing terminology and Redesigned UI/UX.

    0
    rahulthakur
    Forum|Forum|5 months ago
    ctallmanNew Participant

    Moveworks API for Moveworks3. Existing Functionality/Native Skill

    Is there a plugin available that allows Moveworks to pull data out of itself? We have a great idea by one of our analysts. Every day they manually go into Analytics and download the csv of customer feedback. Then they manually sort through the responses to find the details they need so they can reach out to the negatives (thumbs down) and find out more detail. Their idea is to have Dot (our Bot) automatically send a message to him every day containing all the prior days negative interactions.

    3
    Ajay Merchia
    Forum|Forum|5 months ago
    stackdaveNew Participant

    Stack Overflow: updates to the connector listing6. Delivered

    https://marketplace.moveworks.com/connectors/stackoverflowStack Overflow has recently rebranded, there are a few changes to make:Update the logo (asset here) Connector “How to implement” page Under “Prerequisites” Stack Overflow Enterprise Plan → Stack Internal (Enterprise) plan. Plugin “Search for a question” On Overview: Stack overflow → Stack Overflow On the “How to implement” page Under “Introduction”: Search a Question on StackOverflow for Teams → Search a Question on Stack Overflow Internal ...their organization’s private Stack Overflow for Teams knowledge base directly… → their Stack Internal directly Under “Prerequisites”: Stackoverflow Connector → Stack Overflow Connector Under “Installation Steps”: Stackoverflow Connector Guide → Stack Overflow Connector Guide  Under “Appendix  - URL and Query parameters”: Stack Overflow for Teams subdomain → Stack Internal subdomain Thank you for your help!

    2
    Ajay Merchia
    Forum|Forum|5 months ago
    Ajay Merchia
    Ajay MerchiaCommunity Manager

    Minor ML Update: Tool Response Rendering Improvements6. Delivered

    Key DatesFrontier: May 18 2026Standard: May 20 2026Basic: May 26 2026Learn more about our model upgrades here.</ul><p><strong>Tool Response Rendering Improvements</strong><br />We've made some updates to how the Moveworks AI Assistant presents tool responses!<br />The Assistant now presents clean and concise results. Previously, some responses were excessively verbose or surfaced extra, unnecessary information, rather than synthesizing it into a helpful answer. Improvements include four changes that will make responses clearer:</p><ul><li><strong>Relevance by default:</strong> When sharing information from a tool response, the Assistant surfaces only details relevant to your request. Raw data fields, internal identifiers, and technical values you can't act on are omitted.</li> <li><strong>Synthesized answers:</strong> When multiple tools contribute to a response, results are combined into a single coherent answer.</li> <li><strong>Plain-language errors:</strong> When a tool encounters an error, the Assistant describes the outcome in plain language.</li> <li><strong>Clean output by default:</strong> The Assistant won't include verbose technical data in responses unless it's directly useful to you.</li></ul><p><strong>To verify the improvements</strong><br />After the update is live in your environment: Ask a question that normally triggers a verbose tool response. The Assistant should return a concise, relevant answer.

    0
    Ajay Merchia
    Forum|Forum|5 months ago
    srankichCommunity Manager

    Image Input for LLM Actions4. Future Consideration

    Process images alongside text in your LLM actions using the new `image` parameter on `generate_text_action` and `generate_structured_value_action`. Accepts a File object from a File Slot, enabling OCR, receipt parsing, and visual analysis. Available for OpenAI Direct connections.

    1
    Forum|Forum|5 months ago
    yashCommunity Manager

    Insights for custom Agents2. On Roadmap

    A suite of dashboards highlighting insights for performance and adoption of your custom agents

    0
    Forum|Forum|5 months ago
    yashCommunity Manager

    Insights for Specialized Assistants2. On Roadmap

    You go-to dashboard for assessing performance and adoption for specialized and scoped agents

    0
    Forum|Forum|5 months ago
    yashCommunity Manager

    Moveworks Insights6. Delivered

    You go-to dashboard for getting usage and adoption insights for overall Moveworks platform.

    0
    Forum|Forum|5 months 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