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

    1171 Ideas

    Ajay Merchia
    Ajay MerchiaCommunity Manager

    Minor ML Update: File Upload Experience Improvements2. On Roadmap

    Key DatesFrontier: July 2026Standard: July 2026Basic: July 2026Learn more about our model upgrades here.We're improving file upload reliability in plugins. When a plugin needs a file, users will consistently get an upload prompt — even when running multiple file-based workflows back-to-back. We're also fixing cases where stale upload buttons appear after a workflow has already finished.

    0
    Ajay Merchia
    Forum|Forum|1 month ago
    J
    JonathanKnown Participant

    Titles with Literary References - Allowing user friendly labels for Agent STudio1. New

    Because I’m thinking of the user experience I was wondering if we could get user facing labels on Agent Studio Plug-ins.The reason is that right now if someone writes a prompt and it calls in an agent studio plugin they’ll get something like this.GET_TICKET_INFO_CALL_NOW… or something similar.Now this is being done for the deverlopers because it helps them to name things in such a way that they know what they’re using if they’re doing complex actions that reuse some plug-ins. However for users it’s a terrible experience if you’re watching the thinking part during processingInstead if there was a public facing label that said “Running ticket analyzer” or something like that then it would be more informative for the user and a nicer experience overall.

    0
    J
    Forum|Forum|1 month ago
    Simon Vassallo
    Simon Vassallo

    Moveworks Campaign Analytics1. New

    Hi Moveworks,As discussed by another Moveworks customer 9 months ago, we would also like a better experience accessing the campaign data.Is it something that can be exposed via the Moveworks DATA API at some point in the future?Or have the ability to download all the campiagn data at once instead of having to download 1 page at a time.Thanks.

    0
    Simon Vassallo
    Forum|Forum|1 month ago
    DIANA.TWC
    DIANA.TWCInspiring

    Bring back ‘buttons’ for Agent Studio4. Future Consideration

    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? 

    5
    J
    Forum|Forum|1 month ago
    R
    ramapr1New Participant

    Visibility control for last-activity agent name on ServiceNow HR tickets1. New

    Moveworks AI agent currently displays the name of the employee who performed the last activity on a ServiceNow HR ticket. This encourages employees to reach out directly to the assigned agent, rather than keeping all back and forth correspondence within the HR case, which harms traceability and case history.The proposal with this idea submission is to introduce a visibility control setting within moveworks platform to manage whether the last-activity agent name is shown or completely hide the agent name from being displayed when the case notification is sent to the Moveworks agent. This improves privacy and reduces direct, unofficial contact with the assigned agent. Also maintains a complete, auditable log of activity behind the scenes while preserving a clean, traceable ticket conversation for the employee. It helps ensure HR case communications stay within the ticket thread.

    1
    shashrk
    Forum|Forum|1 month ago
    vpawar
    vpawarCommunity Manager

    Moveworks Tools & Platform APIs2. On Roadmap

    Enable admins to programmatically access and configure Moveworks

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

    Minor ML Update: Improve User Message Context during Entity Selection6. Delivered

    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.

    0
    kyril.remillard
    Forum|Forum|1 month ago
    C
    chaney.zimmermanInspiring

    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|1 month ago
    G
    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
    G
    Forum|Forum|1 month ago
    Indrashis
    IndrashisEmployee

    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|1 month 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|1 month 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|1 month ago
    Indrashis
    IndrashisEmployee

    Revamped Content Observability and Troubleshooting Tool in MW Setup4. Future Consideration

    A new and revamped tool within Moveworks Setup for end-to-end observability and troubleshooting for Enterprise Search and Content Ingestion.

    0
    Indrashis
    Forum|Forum|1 month ago
    S
    sidvermaCommunity Manager

    Agent Studio Redesign6. Delivered

    Redesign Agent Studio's visual design to reduce cognitive load

    0
    S
    Forum|Forum|1 month ago
    D
    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
    P
    Forum|Forum|1 month ago
    W
    wyuEmployee

    Hyperlink Preservation2. On Roadmap

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

    0
    W
    Forum|Forum|1 month ago
    J
    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
    J
    Forum|Forum|1 month ago
    J
    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
    J
    Forum|Forum|1 month ago
    afleury
    afleuryInspiring

    Dedicated Notifications Tab for Moveworks in Microsoft Teams (and Slack)1. New

    The ProblemToday, the Moveworks bot in Microsoft Teams (and Slack) only has a Chat and Shared tab. All notifications — ticket updates, approval requests, pending actions, comms — land directly in the Chat conversation alongside regular bot interactions.This creates a real problem:Notifications get buried. As soon as a user sends a new message to the bot, older notifications scroll out of view. There's no way to see a consolidated list of pending items without scrolling back through the chat history. Busy managers lose track of approvals. Managers with high approval volumes can't efficiently triage what needs attention. They're not going to have a back-and-forth conversation with a chatbot to filter down pending requests — they'll just open ServiceNow directly, which defeats the purpose of the bot. The problem gets worse at scale. The more notification types you enable (ticket concierge, approval reminders, comms, visitor alerts), the noisier the chat becomes, and the more likely critical notifications are missed.As one of our store managers put it when testing Bolt visitor notifications:" it kind of got lost between two others, so not necessarily obvious." What We WantWe'd love Moveworks to adopt the same tab structure that other Teams apps (like Workday) already use:Tab Purpose App Dedicated notification feed — ticket updates, approval requests, pending actions, comms. Structured, scannable, persistent. Chat Conversational interaction with the bot — questions, lookups, form submissions. Shared Shared files and links (already exists). The Workday Teams app is a great reference. Its "App" tab shows Quick Actions, tasks, and calendar events — completely separate from the "Chat" tab where users interact with the Workday bot. Notifications like time-off approvals appear in Chat, but the persistent task list lives in App. This separation keeps things clean and actionable.Why This MattersYou've already solved this on the web. The Moveworks Web Assistant (/assistant) has a dedicated Notifications panel — separate from the chat. It works well. But it pulls users away from their primary collaboration platform (Teams/Slack) and requires additional SSO app assignment (e.g. Okta), which is more admin overhead.  Microsoft Teams supports this pattern natively. The Teams platform provides Activity Feed Notification APIs and supports custom tabs within bot apps. The technical capability exists.  Meet users where they are. Moveworks' own mission is to "meet employees where they are." For most enterprises, that's Teams or Slack — not a separate web portal. The notification experience should live there too.  Approval velocity. Managers need a glanceable, structured view of what's pending — not a chat transcript to scroll through. A dedicated tab would significantly reduce approval turnaround time and friction.What This Could Look LikeNotification feed in the "App" tab — filterable by type (approvals, ticket updates, comms, reminders). Badge count on the App tab showing unread/pending notifications. Actionable cards — approve/reject, acknowledge, or deep-link to ServiceNow directly from the notification. Persistent state — notifications remain visible and accessible until actioned, not buried by new chat messages.Who This ImpactsThis isn't a niche request. Every Moveworks customer on Teams or Slack that uses ticket notifications, approval workflows, or employee comms is affected. The challenge scales with org size — the more users and notification types you enable, the worse the chat-noise problem becomes.TL;DRCurrent State Desired State All notifications land in the Chat tab Notifications in a dedicated App tab Notifications scroll away with new messages Persistent, scannable notification feed Managers must scroll or ask the bot to filter Structured view with filters and badge counts Web Assistant has this — Teams/Slack doesn't Parity across all surfaces Web Assistant requires separate SSO/Okta app Keep the experience in Teams/Slack If you're dealing with this same challenge — please upvote and comment. The more visibility this gets, the more likely it makes it onto the roadmap. 🙏Here’s what it could look like 

    0
    afleury
    Forum|Forum|1 month ago
    J
    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
    J
    Forum|Forum|1 month ago
    J
    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
    J
    Forum|Forum|1 month ago
    B
    BHernandezNew Participant

    Enhancement Request: Exclude Hidden Unily Content from Moveworks Ingestion1. New

    Please enhance the Unily connector so that content marked as Hidden in Unily is not ingested or used by Moveworks, even if it is published.Current BehaviorContent with isHidden: true is still ingested because the connector filters on isPublished and isTrashed, but does not currently account for the Hidden flag.Why This MattersWe use the Hidden status in Unily to:Temporarily disable content Prepare content for future release Quickly turn features/widgets on or offIngesting Hidden content causes unintended exposure of content that is intentionally suppressed.Expected BehaviorContent marked as Hidden in Unily should be excluded from Moveworks ingestion and usage.

    0
    B
    Forum|Forum|1 month ago
    andrew.mairena
    andrew.mairenaCommunity Manager

    Slack Marketplace App2. On Roadmap

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

    0
    andrew.mairena
    Forum|Forum|1 month 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|1 month ago
    H
    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
    H
    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