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

    986 Ideas

    Jared
    JaredInspiring

    Feature Request: Analytics for Proactive (“Pushed”) Bot Communications1. New

    Overview Currently, the platform’s analytics focus on user-initiated interactions with our Moveworks bot. However, as customer bots evolve to be more proactive—sending notifications and updates without direct user prompts—we lack visibility into the reach and effectiveness of these communications. To better understand the impact of bot-initiated messages, we propose the addition of analytics for proactive communications. This would provide insights into what types of messages are being sent, how frequently, and how users are engaging with them. Proposal: Implement Analytics for Bot-Initiated Messaging We request a new analytics capability to track and analyze any communication that originates from the bot, including but not limited to:• System-generated notifications (e.g., password reset alerts)• Employee communications tool messages• Creator Studio-initiated messages• Concierge or plugin-based notifications (e.g., ITSM status updates, comments)• External integration notifications (e.g., ITSM approval workflows) Key Metrics & Capabilities Requested:1. Message Volume Tracking – How many bot-initiated messages are being sent over time?2. Message Source Breakdown – Categorization by system, integration, or trigger type.3. Recipient Insights – Who is receiving these messages? Are certain groups more (or less) engaged than others?4. Engagement Metrics – How do users interact with bot-initiated messages? (e.g., click rates, dismissals, response rates)5. Impact Measurement – Correlation between notifications and user actions (e.g., did a status change notification lead to a follow-up inquiry?). Benefits:• Visibility – Understand the scale and scope of bot-initiated communications.• Optimization – Identify which messages are effective and refine strategies accordingly.• User Experience Improvement – Reduce notification fatigue by analyzing engagement trends.• Data-Driven Decision Making – Leverage insights to enhance proactive support efforts. By implementing analytics for proactive bot messaging, we can ensure that these communications are both meaningful and effective, ultimately improving the best possible user experience and the value of the Moveworks bot.

    12
    DIANA.TWC
    Forum|Forum|3 months ago
    S
    Saranya MInspiring

    Request for SharePoint List Integration Support1. New

    Hi Team, As per today’s feasibility check in MW, there is currently no feature available for integrating SharePoint Lists. While we do have a “File Search” feature, it does not support SharePoint List integration. Kindly consider enabling a feature or leveraging Agentic AI to support this integration.Thanks

    0
    S
    Forum|Forum|3 months ago
    W
    whitehead.jasaniNew Participant

    Allow End Users to Opt-out of Approval Mirroring or ticket updates1. New

    Our engineering teams are in large approval groups, we just went live with our bot ‘Penny’ and early feedback suggests that while the proactive notifications are helpful, approval notifications can become spammy in nature. I want our users to be able to “snooze” these notifications for specific time intervals 

    2
    J
    Forum|Forum|3 months ago
    K
    Kiran ReddyNew Participant

    Authorizations/access based on workspace within a instance4. Future Consideration

    Since Move Works is a shared instance, when implementing use cases for HR and ITSM groups, it is critical to separate  underlying components (connectors, actions, plugins etc) with some kind of permission so that developers or admins have access only to their respective workspaces.This is important functionality so that non-HR users who would normally not have access to HR data are not able to execute plugins/http actions etc. or have visibility to logs/data that is tied to HR instances and potentially expose sensitive data.

    2
    kyril.remillard
    Forum|Forum|3 months ago
    K
    KaviKnown Participant

    Enhancing Triage Analytics with tickets marked with drop off reason “CREATED_BY_AGENT”1. New

    To improve visibility into the effectiveness of the triage process in ServiceNow, we propose enhancing the Triage Analytics Report by including tickets that have the drop-off reason marked as “CREATED_BY_AGENT.” Currently, the Triage Analytics Report does not account for tickets that has opened by and assigned to as same person this creates a data mismatch with source data.

    0
    K
    Forum|Forum|3 months ago
    J
    JRofinNew Participant

    Include Initial Trigger Content in Raw Interactions for Each Conversation ID1. New

    In the Raw Interactions report, we’d like to see a column that shows the initial content or message that triggered the Conversation ID.Right now, we can see multiple user interactions under the same Conversation ID, including when users say “No, I need help.” However, we can’t see what started the conversation, which makes it impossible to analyze the root cause of user frustration or failed resolution.Without visibility into the first message or trigger per conversation, we’re unable to connect user feedback with the specific entry point, and therefore can’t take meaningful action.If we understand what triggered the user to click “No, I need help,” we can trace it back to the original content—allowing us to improve the related articles, documents, or knowledge base entries that may be falling short.

    0
    J
    Forum|Forum|3 months ago
    M
    Mike HonNew Participant

    Use Resolved Tickets as source for Knowledge1. New

    We’d like to see MoveWorks leverage the content added to resolved tickets to solve similar issues going forward.  Instead of having to create a Knowledge Article and formally document the work around or solution, it would be more effective to just use the knowledge from the agents captured in the ticket.   Preferably working with Jira Service Management. 

    0
    M
    Forum|Forum|3 months ago

    Channel Resolver for MS Teams4. Future Consideration

    Build Channel Resolver capability to reduce the manual workload by IT helpdesk agents from the requests coming into this channel

    4
    hundleymf
    Forum|Forum|3 months ago
    Jbirney
    JbirneyNew Participant

    Context locking1. New

    We need the ability to context (or session) lock. We are migrating from a home grown solution to the moveworks platform. One nice feature we have lost is all of our custom AI bots as with the old solution we were able to use specific utterances to then enter a “chat mode” with that other bot until the user exit out (by typing in exit) or the session timed out. This way we did not have to build a bunch of different Bot Front ends, they could all come into one place. We have not found a way to do this with the moveworks platform at this time. Yes you can fire off a one shot prompt to a different bot or LLM. But any follow up questions will not have the context/history. Thoughts?

    0
    Jbirney
    Forum|Forum|3 months ago
    D
    DanSpenglerNew Participant

    Include Employees who did not interact with Campaign in report1. New

    It would be very useful to include a list of users who did NOT interact with a campaign in the download reports.  We’ve started to use campaigns to gather information from employees, where we consider a response mandatory.  Employees who don’t interact with the campaign need more direct followup through other channels.Currently comms details only show delivery status and positive interactions, so campaign leaders have to manually infer those usernames from the difference between the total audience and the users who interacted.It seems obvious that this data should be included in campaign details, since it’s highly relevant and actionable.

    0
    D
    Forum|Forum|3 months ago
    N
    npenalverNew Participant

    Knowledge Studio - Enhancements to the Editor and Publishing Workflow1. New

    Request: Enhancements to the Editor and Publishing WorkflowGoal: Improve the editor experience and enable direct publishing to our preferred knowledge platform (ServiceNow). Requested Improvements:Editor Enhancements Add comprehensive rich text formatting tools, including: Text styles (headings, subheadings, paragraphs) Font formatting (bold, italic, underline, bullet/numbered lists, hyperlinks) Implement a unified prompt/editor design that allows for quick text edits while still supporting AI-assisted content generation. Include export options: Direct export to Google Docs HTML export for compatibility with tools like Confluence and ServiceNow Publishing Workflow Integrate with ServiceNow Knowledge Space to allow direct publishing from the editor to the desired knowledge base.

    0
    N
    Forum|Forum|3 months ago
    S
    snavaleNew Participant

    Table format support for notifications4. Future Consideration

    Hi Team,I have noticed that the current Agent Studio does not support notifications in a tabular format. We should consider adding this feature in the future, as it would enhance the clarity, style, and overall presentation of notifications for better understanding.Reference image: 

    1
    samujala
    Forum|Forum|3 months ago
    S
    sgrimesNew Participant

    Embedded AI Assistant - Informational Banner1. New

    Hello all, Was wondering if we could get something like shown in these quickly made mockups? Ideally a way to specify additional support options and hours up front. Possible even could be utilized to show FEM outage messages like “X Application is down” to minimize a flood of calls/chats.  Icon Image Main Text (Email to Customer Support)  Secondary Text (Email@email.com)  

    0
    S
    Forum|Forum|3 months ago
    G
    goncalo.conceicaoNew Participant

    Avoiding On-the-fly Translation of Codes1. New

    In conversations related with IT Support, upon engaging in the Live Chat with an Agent, it is typical that Remote Desktop tools are used. Typically these tools require a code to be shared by the Agent with the Caller, in order to establish the remote connection. On some occasions, we’ve observed that these Codes sent by the agent are being translated on-the-fly, which then do not work and do not allow the session to be established.   Requesting a product enhancement so the AI Assistant can recognize the context as being a support call and corresponding Codes for the remote session being shared, thus not translating these.Referrence to Case Number: 00031445

    2
    A
    Forum|Forum|3 months ago
    J
    jkuharNew Participant

    Ability to set custom notifications1. New

    If users tell Moveworks Bot, to stop communications, it should prompt for which items.IE:  If they want to suppress messages for a particular Ticket Type,  System Integration, General Announcements in Employee Comms module, etc.  

    1
    J
    Forum|Forum|3 months ago
    Y
    yashEmployee

    Enhanced feedback telemetry - RELEASED TO ALL1. New

    Hello analytics community,  We are happy to announce that we have rolled out a significant update in analytics. The feedback counts are set to increase, since now it captures the exact button click of thumbs up / down. For example: [1] On the feedback table (accessible via the overview page),You will find the thumbs up and down clicks to be increased, these are the exact count of button clicks that your users made on the AI assistant.   [2] On the aggregated reports , the widgets that showed feedback counts are set to update to the latest telemetry as well.   Previous announcement post  

    0
    Y
    Forum|Forum|3 months ago
    bcovington
    bcovingtonEmployee

    JSM Forms (dynamic forms) fillable for Jira users5. Not Enough Info to Make Decision

    Peloton requests that Moveworks partner with Atlassian Jira to enable JSM Forms to be fillable in-bot. Jira has 2 types of forms. JSM Forms (dynamics forms) is the version that is currently not supported to be fillable because Jira Cloud Forms does not yet have APIs which will allow Moveworks to fill a form in the bot and submit it to create a new ticket. NOTE: This is specific for Jira cloud instances Gateway recommendation is not an acceptable alternative. Having the native integration is the desired outcome.

    5
    M
    Forum|Forum|3 months ago
    satheesh.kumar1
    satheesh.kumar1Participating Frequently

    People lookup search basaed on the Role or Title3. Existing Functionality/Native Skill

    Currently, users are able to search based on Name, Email, Department, and Manager Name. However, enabling Role search would bring more flexibility and help users find colleagues based on their specific roles

    4
    satheesh.kumar1
    Forum|Forum|3 months ago
    Jared
    JaredInspiring

    Organizing Plugins in Agent Studio7.0 Duplicate

    We are approaching 100 different Plugins, Actions, Paths, etc., within our environment. As you can imagine, this is leading to a cluttered interface!It would be advantageous to find a solution for organizing these elements.One possible approach could be to implement folders for categorization by Domain and other criteria. An even more effective solution would be to integrate custom variables or categories within the plugins themselves, enabling us to sort and filter by Domain, Plugin type, and other attributes.Perhaps the Community could help brainstorm the best solution? I believe that without intervention, this situation will soon become unmanageable, and we will need a strategy to maintain a more organized environment.

    6
    Jared
    Forum|Forum|3 months ago
    A
    AntonNew Participant

    Confluence Excerpt macro1. New

    Hello team!In Confluence, the Excerpt macro lets you reference a block of text from a single source of truth on other pages. This makes it easy to reuse text without needing manual updates.https://support.atlassian.com/confluence-cloud/docs/insert-the-excerpt-macro/Right now, the MW bot doesn’t detect text inside the Excerpt macro. This means the referenced block has to be copy-pasted and updated manually whenever the source changes.It’d make our workflow much simpler if the bot could recognize content within the macro.Thank you!

    0
    A
    Forum|Forum|3 months ago
    M
    malabika.mukherjeeNew Participant

    QuickGPT1. New

    When can we expect multimodal support for QuickGPT? Images, videos and graphical visualization support? Is this part of upcoming roadmap

    1
    M
    Forum|Forum|4 months ago
    G
    glambInspiring

    Agent Studio 2.0 Timeout Limitations and Workflow Flexibility Compared to 1.03. Existing Functionality/Native Skill

    We’ve been working closely with Moveworks Support and Engineering and wanted to share some feedback regarding process timeouts in Agent Studio 2.0.Background:In Agent Studio Classic / 1.0, compound actions allow for asynchronous API calls. Each action within a compound action has a 60-second timeout, but there’s no overall timeout for the compound action itself. This has enabled us to build plugins that perform multiple API calls efficiently. In Agent Studio 2.0, conversational process replaces compound actions. However, the process is synchronous, and there’s a 60-second timeout for the entire conversational process.Issue: We’re encountering PLUGIN_ERROR_TIMEOUT in 2.0 like a user in this thread is experiencing:The suggested workaround from Moveworks Engineering is to use a compound action within the conversational process, allowing us to run actions asynchronously OR to just use compound action for the entirety of this plugin. We cannot optimize / use faster APIs to avoid timeout thresholds entirely due to our security architecture.Concern: While this workaround technically resolves the timeout issue, it seems to defeat the purpose of migrating to 2.0 for processes that require multiple long API calls. The synchronous nature of conversational processes in 2.0 limits us compared to the flexibility we had in 1.0. Additionally, if we need input validation of 2.0, then we must use conversational process + compound action which gets difficult to manage.Request: Is there any discussion internally of either increasing the timeout threshold beyond 60 seconds for conversational processes, or to enable (even specific actions within) conversational processes to be asynchronous? Currently, the main advantage we see in 2.0 is input validation, data types, and UI, while 1.0 remains more flexible for most workflow requirements.

    4
    Ajay Merchia
    Forum|Forum|4 months ago
    Andrew
    AndrewInspiring

    Add thumbs up/thumbs down to raw interactions1. New

    It would be great to see if a thumbs up or a thumbs down was applied to the interaction in the raw interactions. 

    1
    J
    Forum|Forum|4 months ago
    J
    jaime.rennKnown Participant

    Data API odata query parameter for aggregation1. New

    Our Dev team is recommending a new parameter to help with aggregation and reduce the number of calls to the API -  The moveworks API currently supports some odata query parameters but is missing one that would make the data metrics collection process more efficient which is the $count query option. Usually, this is used with a filter to aggregate and return a number of items that matches the filter requirement. This option would allow us to only need to call the API once.

    0
    J
    Forum|Forum|4 months ago
    F
    FrantzCFNew Participant

    Employee Communications Message Variable Text Fields1. New

    Current Functionality:The Employee Communications application currently sends identical messages to all designated targets. Proposed Enhancement:Introduce the ability to send customized messages to each target by incorporating variable text fields in the body of the message. This enhancement will allow message content to dynamically adapt based on a CSV file or another external data source.Template-Based Messaging: We can define message templates with placeholders and define the content for placeholders in a source file or database. Dynamic Content Injection: At runtime, the system replaces placeholders with corresponding values from each target’s profile or data source.

    0
    F
    Forum|Forum|4 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
    Terms & ConditionsCookie settingsAccessibility statement