Events
Groups
Documentation
Developer
Academy
Support

Post something
Login

Have you saved your spot? Join us at now[dev]26!

1 month ago

Product Ideas

Build better products with our product team.

Home
Ideas

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...

2 years ago

4421

Filter by idea status

Filter by product

1344 Ideas

Most replies

Most votes

Newest first

Maciek LekowskiNew Participant

Analytics: interaction table anonymization1. New

I feel that above update under “related topics” created additional challenges from data privacy perspective. We need to have a way to configure that for some analytics users, such identifiable information like e-mail address are not accessible through “view all interactions” button. Our employees may share sometimes things that are little sensitive and allowing everybody having access to Analytics accessing it and then link given interaction to individual person is just not right. I feel that this relates to another idea Permissions to restrict Interaction data in Bot analytics | Community . Permissions on Analytics must be much more granular and configurable so that people get access to the data they need and not to everything or nothing.

11 days ago

JishnuEmployee

Handoff Simplification4. Future Consideration

What’s changing?Smart Handoff configuration is moving into a single, guided experience in Moveworks Setup. Instead of configuring one handoff across separate Handoff Settings, Display Configurations, and Live Agent Handoff modules, admins will be able to manage the experience in one place.The simplified experience will include:Unified configuration: Define the trigger, action, user-facing content, and destination in one flow.Domain-based setup: Organize and configure handoffs by domain, with support for user-attribute conditions.Simpler action selection: Configure actions such as filing a ticket, connecting to a live agent, opening a URL, sending an email, or directing users to a chat channel.Less manual configuration: Reduce reliance on hand-entered technical keys and custom DSL for common handoff scenarios.Live preview: Preview how the handoff experience will appear to users while configuring it.These changes are designed to reduce configuration errors and make common Smart Handoff use cases easier for admins and implementation partners to set up and maintain.

14 days ago

yashCommunity Manager

Insights for custom Agents4. Future Consideration

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

15 days ago

minoru.nagaoNew Participant

Extend Multimodal Image Understanding to Enterprise Search Indexed Knowledge (Standalone Images and Images Embedded in PDF/PPTX/DOCX)1. New

We are deploying Moveworks as an enterprise AI assistant. Many of our existing manuals and knowledge articles contain critical procedures only as screenshots (annotated UI captures, step-by-step images) or as diagrams embedded in PPTX, PDF, and DOCX files. We are glad to see that Brief Me now supports multimodal understanding of images inside uploaded files (Product Update, Idea: Multimodal Support for Brief Me). However, for knowledge that is indexed through Enterprise Search (KB articles and files from connected systems), our support case confirmed that Moveworks does not perform OCR on images. The recommended practice is to add a text description of any important image content to the article body (Writing AI-Ready KB Articles).This creates a real adoption barrier for organizations with image-heavy knowledge:Existing manuals often hold key procedures only in screenshots. Rewriting them at scale is costly and slow. Questions whose answers exist only in images, whether standalone or embedded in PPTX/PDF/DOCX, cannot be answered from indexed knowledge. Content owners must maintain duplicate text next to every image, increasing maintenance effort and the risk of inconsistency.Image understanding for enterprise knowledge is also becoming a baseline expectation across enterprise AI assistants and search products, so closing this gap matters for side-by-side evaluations. Requested capabilityExtend multimodal image understanding to Enterprise Search ingestion, so that images embedded in PDF, PPTX, and DOCX files, and in KB articles from connected systems, are understood and used for answers. Support standalone image files (JPG/PNG, etc.) in indexed knowledge sources. An admin setting to enable or disable image ingestion per knowledge source, for governance and cost control. As an interim step, clear documentation of supported file formats and limitations for Enterprise Search. QuestionsIs extending multimodal understanding from Brief Me to Enterprise Search on the roadmap? When will Brief Me’s multimodal understanding be available in the Japan region? (The product update mentions US, CA, and EU first.) Expected benefitFaster time-to-value, since existing content can be used as-is Better answer coverage for procedural, UI-based questions Lower authoring and maintenance burden A stronger competitive position in enterprise evaluations

15 days ago

jared.zabelNew Participant

Feature Request: Source-Filtered Embedded Assistant1. New

Feature Request: Source-Filtered Embedded AssistantWhatEnable customers to create an embedded assistant experience that is restricted to a defined set of approved knowledge sources. When a colleague interacts with the embedded assistant, responses should only be generated from those configured sources rather than the broader set of content available to the user through Artey.For example, CVS Health could create a Policy & Procedures Assistant, connect only approved policy and procedure sources, and embed that assistant within a relevant experience. The assistant should answer questions using only those sources and clearly indicate when an answer cannot be found within them.WhyThis would allow us to create focused, trusted AI experiences for specific use cases while maintaining the broader Artey experience for enterprise capabilities. It gives colleagues confidence that answers within a specialized assistant are grounded specifically in the authoritative content intended for that experience.Acceptance Criteria Admins can configure an embedded assistant with a defined set of knowledge sources. Users interacting with that assistant can receive answers only from those configured sources. Content available elsewhere in Artey is excluded from retrieval for that experience. Existing user permissions and source-level access controls continue to apply. If the configured sources do not contain an answer, the assistant does not fall back to other Artey sources. Responses retain appropriate source citations. The experience can be embedded within a customer-owned web application or digital experience. Configuration can be reused across multiple users without individually configuring the experience for each colleague. Potential Technical ApproachThe Conversations API may provide the underlying conversational interface because Moveworks documents it as supporting custom user-facing chat surfaces embedded in customer-owned applications.

16 days ago

SudheerCommunity Manager

Moveworks Setup Configuration Cleanup6. Delivered

How are we improving the product?We’ve simplified Moveworks Setup by cleaning up duplicate, obsolete, and unused configuration controls. This reduces situations where administrators or partners encounter multiple controls for the same capability, settings that no longer have an effect, or outdated terminology.The result is a clearer and more reliable configuration experience that helps teams deploy and manage Moveworks with greater confidence.How does it work?Duplicate enablement controls are consolidated so Plugin Management serves as the single source of truth for supported plugin enablement.Obsolete and unused settings are removed after dependency checks confirm they are no longer required.Settings that remain functional but use outdated language are relabeled for clarity.Configuration removals are staged so changes can be safely validated and reversed if needed.Existing Plugin Management enablement values are preserved as part of this cleanup.Licensing restrictionsThis update does not introduce new licensing requirements.Technical restrictionsNo additional technical restrictions are required to use these improvements. The specific settings visible in Moveworks Setup depend on the products and capabilities configured for an organization.AvailabilityThese improvements apply across supported Moveworks environments where the affected configuration controls are available.DocumentationFor additional details about the configuration changes, see Setup configuration cleanup — removal of unused settings.

17 days ago

mishiiNew Participant

Plugin Deployments Do Not Scale Beyond Two Environments1. New

Our organization currently operates Moveworks across two environments (Sandbox and Production). In the near future, we plan to adopt a more standard enterprise deployment model with three environments: Sandbox, Test, and Production.As we prepare for this transition, we have identified a significant operational challenge: Export/Import does not support overwriting existing assets during plugin promotion. Because existing assets cannot be updated in place, changes made and validated in Sandbox cannot simply be promoted to higher environments. Instead, every release requires a manual review of the assets contained within a plugin to determine what has changed and what must be migrated.For example, we currently have to manually inspect modules such as:Conversational Processes HTTP Actions Script Actions Compound Actions Data Typesand determine which assets have been modified and require updating.Once identified, the updates must be applied manually in the target environment. Depending on the asset type, this may involve copying scripts, copying YAML definitions, recreating HTTP Action configurations, or manually updating Data Type schemas and resolver settings. The root cause of this operational burden is that there is no supported way to overwrite existing assets through Export/Import. As a result, we cannot reliably promote a tested plugin from Sandbox to Production as a single deployable unit. While we are currently managing this process across two environments, it is already time-consuming and error-prone. Expanding to three environments (Sandbox → Test → Production) will significantly increase the complexity of release management and environment synchronization. In its current form, we believe this approach will become very difficult to sustain at scale.This limitation introduces several risks:Manual deployment errors Missed updates Environment drift Configuration inconsistencies Increased release effort Higher production riskTo address this, we would strongly like to request:Support for overwrite updates during Plugin Import A true promotion mechanism between Sandbox, Test, and Production Environment comparison (diff) capabilities Dependency-aware deployment validation Packaging and deployment of related assets as a single unitEven the ability to overwrite existing assets during Import would significantly reduce operational effort and deployment risk.For organizations managing multiple Moveworks environments, this is not simply a convenience feature. It is a critical capability for maintaining a reliable and scalable release process. We strongly encourage Moveworks to prioritize this enhancement.Thank you for your consideration.

17 days ago

davrey04Participating Frequently

Training Knowledge Studio1. New

Is there a way to help train Knowledge Studio? Of interest to me is the ability to indicate when a suggestion is Not Helpful. If for example, I often see suggestions to add a new article, or a sub-topic to an existing one. These article and sub-topics already exist in our knowledge base. Marking them unhelpful will help train the bot so it reduces the number of these redundant offerings.If I dig deeply enough, I can rate the articles. However, a toolbar with rating or training controls would make it much easier. Navigating and trying to find useful information has a steep learning curve.Specifically, add an option to “Remove this recommendation” from the rating component below: How do you feel about this recommendation? Rate the usefulness *Not useful at allSomewhat usefulVery useful Select all that applyThis identified a knowledge gapThis is a good starting pointThis article already existsThis is too specific

18 days ago

sarthakEmployee

SCIM Syncing with Moveworks Roles4. Future Consideration

Let us know if you would like to see role-based provisioning from your IDAM to various My Moveworks roles! This would allow your IDAM administrator to define a group and manage access to various Moveworks applications directly from their IDAM portal!

18 days ago

kyril.remillardCommunity Manager

Chunk Context Enhancement6. Delivered

Improve AI answer quality by gathering more context surrounding specific sections of a document, not just the passage that matched your question. That means more complete responses on policies, handbooks, and multi-step procedures, with no change to search relevance and no configuration required.

21 days ago

dhorvathCommunity Manager

User Consent Authentication UX Improvements6. Delivered

Give employees a clearer user consent authentication experience with connector details, improved chat cards, in-app success confirmation, and other UX enhancements.

21 days ago

willmurphyCommunity Manager

A2A Client Support4. Future Consideration

Invoke Now Assist-based AI Agents & other 3P AI agents over A2A.

21 days ago

rrajCommunity Manager

Deep Research Assistant2. On Roadmap

Assistant that can deep research on internal knowledge, search the web, and analyze uploaded files

21 days ago

rrajCommunity Manager

Enterprise Search plugin in GovCloud, AU and CA6. Delivered

Upgrade all GovCloud, AU and CA customers to the new Enterprise Search plugin

21 days ago

afleuryInspiring

Plugin Access Governance Hub: Centralised Audience Reporting and Bulk Management1. New

ProblemAs Moveworks deployments mature, organisations often have:Legacy Creator Studio plugins (Events, Paths & Queries) Agent Studio (Classic) plugins Tool Studio pluginsAccess management becomes increasingly difficult because audience rules are distributed across individual configurations.Administrators cannot easily answer:Who has access to what? Which plugins target a specific department? Which plugins are available to a given user? Which plugins are no longer aligned to current organisational structures? What changed over time?Proposed SolutionCreate a Plugin Access Governance Hub that provides:Centralised ReportingSingle view of all plugins and agents Audience definitions Launch criteria Status (enabled/disabled) Creator/owner Last modified dateUser Access LookupSearch by:User Group Department Role LocationReturn:All plugins available to that audience Effective access based on launch conditionsImpact AnalysisBefore making a change:Show how many users will gain access Show how many users will lose access Highlight affected departments and groupsBulk AdministrationUpdate audience rules across multiple plugins:Replace department Replace location Replace group Replace role Enable/disable multiple pluginsExample:"Department Technology Services renamed to Digital & Technology. Update all plugin launch criteria that reference the old department."Governance DashboardOrphaned plugins with no owner Plugins with overlapping audiences Unused plugins Recently changed permissions Access review recommendationsExport CapabilityExport to CSV/Excel:Plugin name Type Owner Audience rules Estimated audience size StatusBusiness ValueImproves governance and auditability Reduces administration effort Supports security and least-privilege access principles Simplifies organisational restructures Enables easier migration from Creator Studio and Agent Studio (Classic) to Tool Studio Gives administrators visibility across the entire automation estateAs customers adopt Tool Studio while continuing to operate legacy Creator Studio events, queries & paths, Agent Studio (Classic) plugins, audience management becomes fragmented. A centralised access governance experience with reporting, search, impact analysis and bulk updates would significantly improve administration, compliance and platform scalability.Here’s what it could look likeExample - Plugin Governance Hub (created by Copilot)

22 days ago

KellyMVCommunity Manager

Calendar Assistant2. On Roadmap

How are we improving the product?Calendar Assistant helps employees manage everyday calendar work through the Assistant, reducing the effort required to coordinate schedules and meetings.How does it work?Employees can ask the Assistant to help with calendar tasks such as checking schedules, finding availability, and coordinating meetings through supported calendar integrations.Licensing RestrictionsTo be confirmed before General Availability.Technical RestrictionsSupported calendar providers, regions, and administrative requirements will be documented as the release progresses.DocumentationEnablement and validation documentation will be added before Controlled Availability.

22 days ago

souzacmNew Participant

Sentiment Analysis KPIs1. New

The out of the box Analytics reports capabilities are too limited.It is contradictory using someone else's AI solution to get more meaningful insights.Moveworks as an AI platform should offer AI flexible and scalable data analytics features.

22 days ago

souzacmNew Participant

Native translation for Interactions and Feedback reports raw data1. New

Moveworks platform lacks native translation for the interactions raw data.Translating massive interactions table takes time and money as well adds an unnecessary layer of complexity.

22 days ago

jmcginleyCommunity Manager

EmployeeWorks Mobile App5. Controlled Availability

How are we improving the product?EmployeeWorks Mobile brings EmployeeWorks into the Now Mobile app, giving employees access to ServiceNow Otto-powered conversational experiences and a personalized mobile workspace. Employees can find information, access services, and manage work from their iOS or Android device.How does it work?Within the Now Mobile app, employees can:Use conversational experiences powered by ServiceNow Otto.View a personalized canvas tailored to their work.Browse catalog items and knowledge.Access and manage tasks and requests.Licensing RestrictionsThis capability is available to customers with EmployeeWorks.Technical RestrictionsTechnical and regional restrictions have not yet been confirmed.DocumentationHelp-site and setup documentation is not currently available.

23 days ago

kyril.remillardCommunity Manager

EmployeeWorks Mobile App5. Controlled Availability

🎉 Now in Controlled Availability. Sign up here. How are we improving the product?We’re bringing EmployeeWorks to mobile with an experience designed around the AI Assistant. Employees will be able to access workplace help from their phone through a mobile-optimized interface that prioritizes conversation and makes it easier to get support while they’re away from their desk.How does it work?The mobile experience uses an assistant-first information architecture, with conversational input as the primary way to ask questions and get help. Navigation is being designed specifically for mobile so employees can move between the Assistant and key EmployeeWorks experiences without relying on a desktop interface.Licensing RestrictionsLicensing and entitlement details will be shared before general availability.Technical RestrictionsServiceNow Platform version AP6 or BP0 (September 2026 release) is required. The EmployeeWorks Web App must be deployed in at least a sub-production environment. Now Mobile must already be deployed to your users and updated to the September release. This release is intended for sub-production or production deployments where Controlled Availability limitations are acceptable.DocumentationSetup and end-user documentation will be published as it becomes available.

24 days ago

AnishNew Participant

Show the RITM reference in ticket ID1. New

Currently when an INC is raised this is displayed in the Ticket ID. However, this is not the case when a RITM ticket is created. This idea is requesting that both are displayed in the ticket ID field when raised.

24 days ago

dhorvathCommunity Manager

Catalog Interpreter2. On Roadmap

Convert ServiceNow catalog items into conversational AI experiences — no changes to your existing catalogs required. What problem does this solve? Service catalogs contain complex business logic — conditional fields, custom validations, multi-step workflows — that makes them nearly impossible to automate conversationally. Less than 10% of high-volume catalogs work through any existing AI solution today. How does it work? Catalog Interpreter reads your catalog item's full schema and business logic, then creates a conversational AI experience that handles it end-to-end. Employees describe what they need in natural language; the AI collects inputs while respecting all underlying rules and validations.

24 days ago

hershdParticipating Frequently

Query tickets - improve bot response when users have multiple open tickets1. New

Currently, when a user have multiple tickets open (e..g 10+) » when user asks Moveworks (MW) to show their tickets, it only shows the ticket numbers. This is unhelpful (self-explanatory) - ticket numbers by themselves don’t mean much. At bare minimum, Moveworks should show ticket short description (and, preferably, status).If open tickets cross a certain threshold, but refuses to display any details at all and asks for further filters to narrow things down.Additional context - This was observed in one of my implementation projects. Steerability controls were tried out by a MW FDE but didn’t work as expected. I’m logging this idea after consulting with the MW team (incl the MW CSM).

25 days ago

andrew.mairenaCommunity Manager

MSFT365 Agent Marketplace Experience4. Future Consideration

This is the AI Assistant as an agent within the Microsoft Copilot experience. Right now, this is a Closed Controlled Availability and not accepting new customers at this time.Read more - https://www.moveworks.com/us/en/company/news/press-releases/moveworks-third-party-agent-for-microsoft-365-copilot

25 days ago

dhorvathCommunity Manager

Tool Approval Policy for MCP Servers6. Delivered

Control when MCP tools require employee approvalEvery MCP server now has a tool approval policy that controls whether an employee must approve a tool before it runs. The policy applies to all tools on the server, can be selected when the server is connected, and can be changed later.This gives admins a practical safety control for MCP tools while preserving a smooth experience for trusted, read-only actions.Choose the right policy for each serverFollow server guidance — defaultThe MCP server's tool annotations determine whether approval is required for each tool. A tool runs without asking only when it is explicitly:Read-onlyNon-destructiveNot open worldEvery other tool asks the employee for approval before it runs. This is the recommended starting point for most servers.Always ask userEvery tool call from the server requires employee approval. This is the most cautious option and is appropriate for servers that can update a system of record or have not yet been evaluated.Always allowedTools from the server run without an approval prompt. This option is intended for read-only servers that the organization trusts completely, such as documentation and reference lookups.How server guidance is evaluatedWhen Follow server guidance is selected, Moveworks evaluates three MCP tool annotations:| Annotation | How it affects approval || --- | --- || Read-only | Must be explicitly true to run without approval. If omitted, it is treated as false. || Destructive | Must be explicitly false to run without approval. If omitted, it is treated as true. || Open world | Must be explicitly false to run without approval. If omitted, it is treated as true. |The idempotent annotation is not used for this decision. It indicates whether a retry is safe, not whether the first action is safe.Annotations are supplied by the MCP server's developer, not by Moveworks. If a server supplies no annotations, its tools require approval by default. When Moveworks cannot determine that a tool is safe, it asks the employee.What employees seeWhen approval is required, the assistant shows the employee what it is about to do and asks for permission before running the tool. If the employee declines, the tool does not run.Configure the policyIn Agent Studio, go to MCP Servers and open the server.Find Tool approval policy in the server configuration.Select Follow server guidance, Always ask user, or Always allowed.Confirm the change when prompted for Follow server guidance or Always allowed. Always ask user applies immediately because it is the most restrictive option.Save and publish.Changes take effect on the next tool call. Employees do not need to authenticate again.Existing MCP serversExisting servers default to Follow server guidance. If a server publishes annotations, trusted read-only tools continue to run without interruption while tools that modify data or reach outside the connected system ask first. If a server does not publish annotations, every tool asks for approval.Admins should review the policy for each connected server and select the option that matches its capabilities and risk profile.Learn moreSee Connect and Manage Servers for configuration guidance.

28 days ago

Show more activity