Skip to main content

Get Started

The roadmap, product ideas, and product plans are subject to change without notice. This roadmap plan is the current plan for new capabilities in the company’s product lines. However, 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

    1068 Ideas

    vpawar
    vpawarCommunity Manager

    New ticketing setup experience6. Delivered

    Reimagined setup experience for partners to configure ticketing with no friction.

    3
    M
    Forum|Forum|21 days ago
    J
    João Durand

    Option to Duplicate - Plug ins, compound actions, http actions, conversational processes...4. Future Consideration

    Hi community,I don’t know if it is just me but I often have many similar use cases where just one or two variables change... because we need a static process flow on our conversational process.would be nice to have the option to duplicate a Plug in, compound action, http action, conversational process.  I would go to more options button and click duplicate.This would save a lot of time in the development of the use cases.I know its possible to export and import full plug ins - but this create many duplicated actions and its a bundle - you import all of the items.I think this would be a quick win for you guys to implement and a must have! :)thank you

    5
    Derrick
    Forum|Forum|23 days ago
    priya.kornalius
    priya.kornaliusKnown Participant

    Interception is not passing the recommended KB links in ticket comment1. New

    We're experiencing several interception issues with the Copilot version of the bot, which has made the experience increasingly frustrating for the team. I’m documenting one such issue below for the product team to evaluate as a potential improvement opportunity.In the classic version, when the bot intercepted a ticket, it posted its full response along with the referenced KB article links directly in the ticket comments. This was extremely helpful, as it allowed us to:See which KBs were recommended to the user Track the bot’s response accuracy Take corrective actions by updating or improving the KBs based on user feedbackHowever, in the Copilot version, the bot only adds the answer summary in the ticket comment without any reference to the underlying KB sources. Since the bot is summarizing content from the top-ranked results, we have no visibility into which KBs were used to generate the response. This lack of transparency makes it difficult to validate or improve content quality.Moreover, we can’t depend on end users to manually share this information from their chat platforms each time—it’s neither scalable nor reliable.We’ve lost many of the valuable capabilities that the classic bot used to support, and this is affecting our ability to govern and improve content effectively.SuggestionInclude the source KB links or identifiers along with the bot’s response in the ticket comments, just as it worked in the classic version. This will improve traceability, content governance, and user trust in the system. 

    2
    A
    Forum|Forum|26 days ago
    D
    dhorvathCommunity Manager

    Images in Plugin Responses6. Delivered

    Ability to display images from URLs in plugin responses.

    1
    L
    Forum|Forum|26 days ago
    L
    logm001New Member

    Help tab for shortcuts4. Future Consideration

    It could be useful to have a help tab on Teams that describes the commands and add other things useful to the users. 

    3
    afleury
    Forum|Forum|27 days ago
    J
    João Durand

    Expanding Moveworks with Additional LLM Providers1. New

    Hello Community,Nowadays we’re seeing significant innovation from multiple LLM providers.Would it be possible to expand access beyond Azure OpenAI models to include additional providers such as Anthropic (Claude), Google (Gemini), and others?I believe expanding model options would significantly enhance the platform specially in agent studio use cases - using LLM actions.Would this be something worth considering?

    0
    J
    Forum|Forum|27 days ago
    vpawar
    vpawarCommunity Manager

    Ticket Gateway & Identity Gateway5. Limited Preview

    Build your own ticketing integration using Agent Studio Actions. The resulting integration can take advantage of all Service Management SKU capabilities (Interception, EXI, Triage 2.0, etc)

    3
    DIANA.TWC
    Forum|Forum|28 days ago
    rraj
    rrajCommunity Manager

    ServiceNow Enterprise Search Content connector6. Delivered

    Permissioned HTML content (Articles & catalog items) and Permissioned File Attachments (DOC, PPT, & PDF)

    0
    rraj
    Forum|Forum|29 days ago
    rraj
    rrajCommunity Manager

    Slack Enterprise Search connector6. Delivered

    Enables users to search for data from Slack in Enterprise Search

    0
    rraj
    Forum|Forum|29 days ago
    L
    lana.parmit

    Audit logs for logging in with elevated access1. New

    Expand audit/logging for elevated-access areas (Agent Studio, Knowledge, etc.) to capture last-login timestamps and activity.This will let us identify inactive privileged accounts and safely remove or reassign them, improving security and reducing license/support overhead.

    0
    L
    Forum|Forum|29 days ago
    2613196
    2613196

    Add Support for Cited Sources in Moveworks Conversation Flows1. New

    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.

    0
    2613196
    Forum|Forum|30 days ago
    Ajay Merchia
    Ajay MerchiaCommunity Manager

    LDAP Actions6. Delivered

    Ability to execute LDAP commands from Agent Studio plugins.

    1
    D
    Forum|Forum|30 days ago
    J
    João Durand

    Pictures or image files summarization by the assistant1. New

    Hi Community,We had a request where for example a person is locked out of their computer - the assistant takes an image and based on the image extract the key of the machine to unblock the computer.The idea would be to be able to include image files, screenshots and pictures taken from Microsoft Teams and moveworks would be able to act - summarize - extract relevant information for the user.Furthermore this would also assist if a user is having a big error message  and he could take a print screen and the assistant would convert this to text  and query the knowledge base.thank you

    0
    J
    Forum|Forum|1 month ago
    rraj
    rrajCommunity Manager

    Zendesk Enterprise Search connector6. Delivered

    Enables users to search for millions of documents from Zendesk in Enterprise Search

    0
    rraj
    Forum|Forum|1 month ago
    R
    RidgeNew Participant

    Expand EXI to All ServiceNow Data1. New

    We are recently deployed MW into our envirorment, connecting into ServiceNow. We are a full Snow shop with IT, HR, Procurement and other shared service teams enabled on the platform.We see value in EXI for IT but this is only limited to the IT data sets. To really drive value to the organisation it woudl be of great value for us to be able to pull all the infomation across all of the function into EXI for great visability and value to our org.Seems simple if you are pulling from tables within the same system, so would be great if that could be enabled

    0
    R
    Forum|Forum|1 month ago
    afleury
    afleuryInspiring

    Ticket Nudge - Structured “Still an Issue” Follow‑Up1. New

    Challenge• When Moveworks sends a ticket nudge (“Is this still an issue?”), users often reply yes with no context.• Analysts then lack actionable detail and must ask further questions, creating unnecessary back‑and‑forth.• The platform currently does not support enforcing or encouraging a structured explanation when a user indicates the issue persists. Proposed EnhancementAdd an optional “Reason Required” mode to the ticket‑nudge workflow.When a user selects “Yes, it’s still an issue”, Moveworks prompts the user with a structured follow‑up question such as:• “What’s not working? Please be specific.”• “What changed or what are you seeing now?”• “Add any new symptoms, screenshots, or error messages.”This could be implemented via:• A configurable follow‑up template in Moveworks.• A conditional “required field” before the bot updates the ticket state.• A lightweight form or message collector to capture context.Value• Reduces the ping‑pong between bot → user → analyst.• Improves ticket quality and accelerates resolution.• Ensures Moveworks captures meaningful data at the point of user friction.• Increases analyst trust in bot‑driven follow‑ups.Note: I’ve discussed this with the Moveworks Support team, they advised this functionality is not possible yet and to raise a feature request hence this request.

    0
    afleury
    Forum|Forum|1 month ago
    A
    anayak

    User Consent Auth 2.02. On Roadmap

    Make consent and authentication flows clearer, smoother, and more reliable for end users and developers.

    1
    kyril.remillard
    Forum|Forum|1 month ago
    D
    dhorvathCommunity Manager

    Stabilize Ambient Agent → Conversational Process Execution6. Delivered

    What is it?Customers can now trigger Conversational Processes (CPs) via Compound Actions (CAs) without publishing them as standalone conversational plugins.Why we built it?Previously, customers building Ambient Agents had to publish CPs as “dummy” plugins with random triggering examples just so system-triggered flows could invoke them in a CA. This was confusing, error-prone, and in some cases caused incorrect plugin routing in user conversations.How it works?A Conversational Process can now be published for system-triggered execution only and the webhook → plugin → CA → CP flows now reliably work! No need for the old “dummy CP plugin with random blabber” workaround.Key dates: Preview: January 2026

    1
    D
    Forum|Forum|1 month ago
    2613196
    2613196

    Selective Log Redaction Overrides for Specific Payloads and Fields4. Future Consideration

    SummaryMoveworks currently applies global log‑redaction rules that often remove sensitive data from all payloads uniformly. While this protects customer information, it can make troubleshooting, debugging, and rule development extremely difficult when certain payloads must be visible temporarily or permanently.This request proposes a controlled mechanism to disable or override log redaction for specific payloads and specific key/value fields, using an extension to the existing redaction DSL. Problem StatementToday, log redaction is fairly extreme, and not easily refined at the project level (that I can tell)Redaction is applied globally Redaction cannot be disabled for specific data objects Redaction cannot selectively reveal individual fields Debugging issues in pipelines, transformations, audits and DSL logic becomes challenging without visibility into certain parts of the payloadAs a result, teams often struggle to analyze issues effectively without temporarily weakening overall log safety.Proposed Solution: Redaction Override ruleExtend the existing Moveworks redaction rule to support a new structure that allows per‑payload and per‑field exceptions.{ "show": { "info": [ "data.anotherPayload.Name.First" ], "debug": [ "data.myPayload" ] }, "redact": [ "data.sensitive", "data.userPayload.user_choice" ]}How it would work show list Any paths listed under "show" are preserved in full. Full objects (e.g., data.myPayload) can be whitelisted. Individual fields (e.g., .Name.First) can also be whitelisted. show info/debug  Info or Debug settings mean that item will log in production mode or debug mode. For logging info mode there would be a simple log entry that shows just that payload, this might be similar to accessed_variables in the logs. redact list Specific objects or fields can still be forcibly redacted even if part of a visible payload. Final redaction behavior Redaction system evaluates "show" rules first (explicit allowlist). "redact" takes precedence for any subfields explicitly listed. Any data not mentioned falls back to existing platform defaults. at the kick off a plugin - the redaction rule would show in the logs on the info entry. BenefitsFor DevelopersCan fully inspect problematic payloads during debugging Reduces friction and time to resolution No need to disable global redaction settingsFor Security & ComplianceOverrides are explicit, documented, and controlled Redaction remains applied everywhere except where explicitly allowed Still enables field-level protection for sensitive subfield dataFor Platform ConsistencyBuilds on the existing redaction DSL Maintains an opt‑in model rather than broad “disable redaction” switches Minimizes implementation complexity while maximizing flexibility

    3
    2613196
    Forum|Forum|1 month ago
    afleury
    afleuryInspiring

    Alert Idea: Confluence Permission Ingestion Health Check1. New

    What it doesAutomatically flags any Confluence page where Moveworks fails to ingest permissions correctly.This helps us catch silent RBAC issues before users hit them.Why it mattersEnsures RBAC accuracy before and after go‑live Detects when Moveworks can’t read page permissions Prevents pages from being incorrectly blocked or incorrectly served Reduces manual spot‑checking across thousands of pagesWhen it should alertA page shows “Permission crawled: false” Moveworks finds 0 permissions where Confluence has permissions Access Lookup denies a user who does have access in Confluence A previously healthy page suddenly stops ingesting permissionsWhat the alert containsPage title + URL Current permission state Serving status When the ingestion last succeeded Optional: recommended next action (e.g., “re-crawl page”, “review connector logs”)Value to MoveworksSimple, low-noise signal that highlights ingestion gaps Helps customers maintain confidence in RBAC integrity Reduces support tickets for intermittent permission issues Aligns with how customers already monitor connector health I’ve discussed with Moveworks Support team already, there is nothing in place to capture this currently so they advised to raise this as an alert idea.

    0
    afleury
    Forum|Forum|1 month 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

    5
    afleury
    Forum|Forum|1 month ago
    nicholas.marr
    nicholas.marrNew Participant

    Structured Data Analysis (SDA) Plugin Level Toggle5. Not Enough Info to Make Decision

    Would be helpful to have an SDA on/off toggle on each plugin as we’ve noticed that it calls on some plugins that we don’t want it to run on. 

    2
    Ajay Merchia
    Forum|Forum|1 month ago
    DIANA.TWC
    DIANA.TWCInspiring

    Manage/minimize AI Assistant "Thinking" on screen7.0 Duplicate

    I want to be able to manage what text is displayed during the “Thinking” step of my AI Assistant.Currently, the name of all the plugins being used are showing up on the screen. In some cases, these plugin names can be shown on the screen as 5 or 6 different lines, which can be noisy and look very robotic.We’d like to have the ability to update the language used while the user waits for a response, or at the very least limit the visibility to 1 or 2 lines on the screen for all plugins. 

    4
    Ajay Merchia
    Forum|Forum|1 month ago
    afleury
    afleuryInspiring

    Native ServiceNow Form Support in Moveworks Web AI Assistant4. Future Consideration

    Vision:Enable full native rendering and interaction with ServiceNow forms—including Client Scripts, UI Policies, Catalog Client Scripts, and UI Actions—directly within the Moveworks Web AI Assistant. This would allow users to complete forms without leaving the assistant, creating a seamless self-service experience.Why Now?With ServiceNow acquiring Moveworks, there's a unique opportunity to align platform capabilities. Moveworks may now have the technical control to support JavaScript execution safely within its Web AI Assistant, and ServiceNow can provide the necessary form logic and rendering components.💼 Business Value PropositionFrictionless User Experience: Users can complete complex forms directly in the Web AI Assistant, reducing drop-off and confusion. Increased Adoption: More users will engage with self-service workflows when forms are accessible and functional. Platform Synergy: Leverages the shared ownership between ServiceNow and Moveworks to deliver deeper, native integration. Reduced Support Load: Fewer tickets and manual interventions as users resolve issues independently via intelligent forms.

    2
    S
    Forum|Forum|1 month ago
    afleury
    afleuryInspiring

    Moveworks Agent Interoperability - Integrate the Agent2Agent (A2A) protocol8.0 Possible Agent Studio Solution

    Great to see that MCP servers are on the roadmap. Would love to see Agent2Agent Protocol (A2A) support being added too. It’s Open Source https://google.github.io/A2A/#/ Idea: Integrate the Agent2Agent (A2A) protocol to enable Moveworks' AI agents to seamlessly collaborate with other AI agents across various enterprise platforms.  Key Features:Inter-Agent Communication: Allow Moveworks' AI agents to communicate and collaborate with other agents from different vendors. Capability Discovery: Use the "Agent Card" feature to identify and leverage the best-suited agents for specific tasks. Task Management: Support efficient task management with real-time feedback and notifications. Modality Agnostic Support: Extend support for various modalities, including text, audio, and video. Enhanced User Experience: Provide a unified interface for users to interact with multiple agents seamlessly.Benefits:Increased productivity Cost efficiency Innovation through seamless agent collaboration 

    7
    S
    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
    Terms & ConditionsCookie settingsAccessibility statement