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

    ElisaIsabellaNew Participant

    Rename "Re-open issue" to "Re-open ticket"1. New

    For now, the bot only proposes one button to reopen tickets, no matter what kind of ticket it is (incident, request, problem, task...). The button is called “Re-open issue”. This is not logical, because a simple request is not an issue.I propose we rename the button as “Re-open ticket” so that it is neutral and works with all kinds of tickets.

    0
    Forum|Forum|6 months ago
    deanatNew Participant

    Improvement Ideas for Zoom Chat Channel1. New

    Submitting this request to suggest some improvement ideas on the Zoom chat channel UI: 1.) Zoom formatting looks a bit different from the Embedded Assistant/Moveworks web app in terms of bulleting/spacing. If the Zoom formatting could be more consistent that would help with readability. 2.) Grant the ability for us to update the auto grey text in Zoom chat text box: for our company it says ‘Message [Company Name] Helper-Dev’ in our test environment. This would make it more employee friendly and uniform across the Embedded Assistant and Moveworks Web App. Thank you.

    0
    Forum|Forum|6 months ago
    deanatNew Participant

    Improvement suggestions for ServiceNow/Unily Embedded Assistant to improve employee experience1. New

    Submitting a few improvement ideas to the Moveworks ServiceNow / Unily Embedded Assistant:1.) The Moveworks ServiceNow / Unily Embedded Assistant window is currently quite small in the lower right hand corner. Chatbot responses with HR content tend to be longer, so the look and feel of the Embedded Assistant is too zoomed in. We always need to expand the window to see the full response more easily, so if the text/sizing of the chatbot can be adjusted this would be helpful. 2.) Grant the ability for us to edit the grey auto text in the text box where it says “Ask me any work-related questions!” to tailor to our company’s branding/more HR-related 3.) When new employees come in to the bot to chat for the first time, the Embedded Assistant just shows a blank screen, employee has to send bot a message so that it doesn’t appear blank anymore. The Moveworks web app has a “Good morning [Employee Name]” message which is more welcoming than a blank screen in the Embedded Assistant, so if there are options to edit this, this will help with employee experience. Thank you,Deana

    0
    Forum|Forum|6 months ago
    anayak

    Python Script Actions Support in Agent Studio6. Delivered

    Introducing Python Script Actions — now Generally Available in Agent Studio across all commercial regions! Building custom logic in your agents just got a massive upgrade. One of the most consistent requests from developers has been clear: "APIthon is too limited — I need real Python with real libraries." Until now, you were stuck with a restricted scripting subset, making complex data transformations, calculations, and text processing either impossible or painfully hacky.Python Script Actions fix that.You can now write full Python 3 code directly inside Agent Studio (screenshots of old and new experience attached) — with access to all built-in modules and a curated set of pre-approved external libraries. Python Script Actions plug into Compound Actions and Conversational Processes exactly like APIthon scripts do, but with dramatically more power. Define input arguments from slots or previous step outputs, write your logic, and the value of the last line of code becomes your output. That's it!What's included:Full Python 3 with all standard libraries (json, datetime, re, math, collections, etc.) 8 pre-approved external libraries out of the box:  pandas , numpy , scikit-learn , beautifulsoup4 , nltk,  plotly ,  seaborn , pycryptodomex Same integration model as APIthon — define input args, write code, last line = output Built-in testing in the Agent Studio editor before you deploy 6 supported data types for input arguments: string, integer, number, boolean, array, objectFull documentation: Python Script Actions ReferenceTry it out and let us know what you think!  

    0
    Forum|Forum|6 months ago
    Andrew
    AndrewInspiring

    Architecture Slide Repository1. New

    As a product owner/manager, I’m often presenting a roadshow deck to stakeholders at different levels of the organization. As Moveworks continues to evolve, it would be incredibly helpful to have a self-service repository of “default” architecture slides and marketing materials that we could pull from as needed. While I can always reach out to my CSM, having this content available on demand would make building internal decks much easier.

    0
    Andrew
    Forum|Forum|6 months ago
    mthameParticipating Frequently

    Enable Live Agent handoff to other systems while keeping interaction within Teams/Slack1. New

    Today we have agent live chat interaction in SNOW. We have a new MSP that wants to have live chat handled in Ring Central (they use InContact). The issue is the it would be via URL that would redirect the end user to a different web portal. This is a poor user experience. It would be great if MW had a way to interact with other live chat instances but keep the chat in the bot via Teams/Slack.

    2
    Forum|Forum|6 months ago
    vpawar
    vpawarCommunity Manager

    New ticketing setup experience6. Delivered

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

    3
    Forum|Forum|6 months ago
    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|6 months 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
    Forum|Forum|7 months ago
    dhorvathCommunity Manager

    Images in Plugin Responses6. Delivered

    Ability to display images from URLs in plugin responses.

    1
    Forum|Forum|7 months ago
    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|7 months ago
    vpawar
    vpawarCommunity Manager

    Ticket Gateway & Identity Gateway6. Delivered

    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|7 months ago
    rraj
    rrajCommunity Manager

    ServiceNow Enterprise Search Content connector4. Future Consideration

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

    0
    rraj
    Forum|Forum|7 months ago
    rraj
    rrajCommunity Manager

    Slack Enterprise Search connector4. Future Consideration

    Enables users to search for data from Slack in Enterprise Search

    0
    rraj
    Forum|Forum|7 months ago
    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
    Forum|Forum|7 months ago
    Ajay Merchia
    Ajay MerchiaCommunity Manager

    LDAP Actions6. Delivered

    Ability to execute LDAP commands from Agent Studio plugins.

    1
    Forum|Forum|7 months ago
    rraj
    rrajCommunity Manager

    Zendesk Enterprise Search connector4. Future Consideration

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

    0
    rraj
    Forum|Forum|7 months ago
    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
    Forum|Forum|7 months 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|7 months ago
    anayak

    User Consent Auth 2.04. Future Consideration

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

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