Build better products with our product team.
When permission ingestion is failing Answers may serve knowledge to users that is not meant for them. While the links to the documents still validate the access, the summary may already contain information that is not to be shown to the users. To monitor this and avoid potential data breach issues the customers should be informed about such failures.
I would like to propose enhancing the bot experience by enabling native image support within bot conversations, rather than rendering images through an iFrame in MS Teams.Key Benefits: Improved User Experience for IT Support Use-Cases Allowing images within conversations will help visually guide users through resolution steps especially useful for IT-related issues where screenshots can simplify instructions and reduce confusion. Support for Image Generation via LLMs Enabling image rendering would unlock use-cases such as internal branding or design content creation, where images are generated based on user input using integrated LLMs. Downloadable Visual Assets Native support would allow users to download images directly from the chat, which is currently not possible with the iFrame-based rendering. This also adds better control over image formatting and display. Proven Feasibility This is technically achievable, as seen in the current implementation of “Employee Communications” messages, where the bot can display images alongside text. Extending this functionality to AAE plugins, Paths, Events, FAQs, etc., using HTML formatting or inline support, would bring consistency across all bot experiences. This enhancement will make bot interactions more intuitive, visually engaging, and functional across a broader range of enterprise use-cases.
I’d like to propose a feature enhancement to allow bots to natively render graphs and tabular data within conversations, rather than returning plain text responses. This would significantly improve the clarity and usefulness of data-centric interactions.Key Benefits: Improved Data Visualization Displaying charts, graphs, and tables directly in the chat would allow users to better understand trends and summaries, making responses more actionable and insightful. Dynamic Output from Excel or Backend Data When bots fetch data from Excel files or backend databases, having the ability to render that data visually can greatly enhance comprehension and reduce the need to switch between tools. Support for Business-Critical Use-Cases Functions like Sales, Finance, and Operations often rely on structured data. Rendering information visually within the conversation can boost productivity and reduce interpretation errors. Modern and Intuitive User Experience Providing rich, visual responses aligns with evolving user expectations from conversational platforms and makes data interactions more intuitive and engaging. Suggested Areas of Application: Response generation based on uploaded spreadsheets Output from API calls or internal dashboards KPI or metric summaries within structured workflows This feature would open up a wide range of data-driven automation and support scenarios, making chatbot interactions far more powerful and user-friendly.
Key DatesPreview: Q1 2025What is itCheck the IP addresses of your Moveworks Assistant & allowlist specific IPs to your business systems
Following on from Ability To Change Font Size and Bold Copilot Disclaimer? | Community I was advised by the support team to raise another idea for this. Using emojis currently to get attention but it’s still a bit too small. Additionally if the user doesn’t interact with the bot and only receives ticket updates and requests approvals they won’t see the disclaimer. In the example below, I’m receiving a ticket update. I would like to have an option to display the disclaimer there as well. Currently the disclaimer only appears when you interact with the bot by asking a question.
As more and more actions, conversational processes, data types are created it can make your screen quite full. While naming conventions do help, the amount of entries can make searching for the required object to take a bit of timeIf a grouping tab would be created that relates to specific group of functions, or some sort of tagging can be done, that would allow to filter what is shown to quickly view only those functions you need to make changes to. If multiple tags could be added for common functions that would also be beneficial
Our team is looking to track our Events use cases via Analytics for our NextGen Copilot/AI Assistant. I’ve found multiple posts regarding Event Analytics but am not sure what the status of this product enhancement is:Event Analytics / Logs | CommunitySupport Creator Studio tab in Analytics for Copilot | CommunityMore Analytics on Creator Studio Events | Community It’s crucial that we have data around these Events notifications to monitor that the use cases are triggering as well as overall effectiveness. Right now, there is no way within the Moveworks system to track Event notifications.
Dear Moveworks Support Team,I hope this message finds you well.We are exploring options to seamlessly integrate our ServiceNow catalog items with Moveworks, and I wanted to check if there is any out-of-the-box functionality available that allows us to directly use catalog forms within Moveworks. Specifically, we are looking for a method where we can simply provide the sys_id of a ServiceNow catalog item, and the bot would automatically: Fetch the associated variables/questions, Present them to the user conversationally, and Submit the request on their behalf by mapping the responses to the respective variables in ServiceNow. While we are aware that this can be achieved using Moveworks Paths, we are hoping to avoid manual field mapping and setup for each catalog item, especially since we manage a large number of them.Could you please let us know if such a capability exists natively, or if there are any upcoming features or recommended approaches that could help us achieve this level of automation with minimal configuration?Looking forward to your guidance.
Hello! After we had an upgrade launch, we found that having something available that is immediately ingested by our bot would be very helpful for known issues we are experiencing. I would imagine this would need to be an article that is editable within the Moveworks Setup, to allow for immediate ingestion. But we would love a feature that allows us to update immediately with known issues we are experiencing (in general, but specifically with IT). Since we were doing a major update, we found there were multiple issues that some users were experiencing, but we didn’t want to flood them with announcements all throughout the day. Having something available that if users were to reach out to the bot, we could have the information on what we know is going on, and provide next steps. These would be different than a normal knowledge base article, as they are only temporary bits of knowledge that will go away once we fix whatever the known issue is.
Ticket Interception should also Serve Agent studio answers as well
Key DatesLimited Preview: 2025What is it Import new HTTP actions via an OpenAPI Specification FeaturesTBD
Key DatesLimited Preview: 2025What is itSave prompts from your LLM actions as templates that can be invoked by multiple pluginsFeaturesTBD
Key DatesLimited Preview: 2026What is it Empower citizen developers to add their own scheduled prompts FeaturesTBD
Key DatesLimited Preview: April 2025What is it Manage conditional slots in the Agentic Automation Engine. FeaturesSee https://help.moveworks.com/docs/control-flow#plugin-decision-policy
Key DatesLimited Preview: April 2025What is itValidate slots that are filled before they are submitted for executionFeaturesSee https://help.moveworks.com/docs/slots#slot-validation-policy
Key DatesLimited Preview: April 2025What is it Convert unstructured user input to a structured system value FeaturesCustom Data Type Resolution - Create custom data types that automatically convert user inputs into structured objects your system understands (e.g., "my next meeting" → GoogleCalendarEvent, "my salesforce account" → SalesforceAccount) Multi-Parameter Resolution - Build powerful resolvers that can extract multiple pieces of information from a single user input (e.g., "create a high-priority bug ticket for the mobile app" → {priority: high, type: bug, component: mobile}) Contextual Understanding - Resolve ambiguous inputs based on conversation context and user preferences (e.g., resolving "John" to the correct JiraUser based on recent mentions or team membership). Validation & Error Handling - Automatically validate resolved values and gracefully handle ambiguous or incorrect inputs with user-friendly clarification prompts. Some relevant documentation:https://help.moveworks.com/docs/data-types https://help.moveworks.com/docs/resolver-strategies https://help.moveworks.com/docs/slots#slot-data-types
Key DatesLimited Preview: April 2025What is it Use content actions (e.g. forms, articles, or rich text responses), similar to the Paths Workspace FeaturesSee: https://help.moveworks.com/docs/activities#content-activities
We’ve gotten feedback that while using multilingual support, targeted employee communications sent via our bot don’t translate as well, “Some of the translations are very literal and in the context they don't make much sense or they can easily confuse people”.The user suggested that for employee comms messages that are translated that there be a visible option/button to “Show original message” or something similar.
SailPoint IdentityNow Integration - New Features. TodayMonitors access request approvals and sends an approval notice through the MoveWorks Bot to the approver Approve / RejectFutureThese features are available in the public SailPoint APIs and can be quickly implemented by MoveWorks through the Bot. These features are not ideal to be built separately with creator studio because the experience will be disconnected.Would like to see a complementing message sent to the requested for where as approvals are sent out they get a notice that who is currently working on the approval. Sending the list of the governance group members, today there is no way in SailPoint for the requested for to see the governance group members Certification Assigned Notice Sending a message when a outstand access certification requires review of approver Initiate Access Request through bot using slash notation /idn request * and chat Allow expiration date on the access to be defined which is available in the SailPoint API.
The setup page for Multilingual support could be improved/simplified in a couple of ways:After upgrading from Classic to AI Assistant, the box that shows languages added to Classic should go away, with any languages being automatically added to the AI Assistant language picker box. This not only puts all chosen languages in one place, it also gives complete control to the customer (I can add and remove from the AI Assistant language picker box, but not the Classic one). The languages are shown in a format (ES_MX) that is perhaps guessable, but not always intuitive. To understand these codes you have to click on the link to documentation in the upper right corner, which takes you to https://help.moveworks.com/docs/multi-lingual-support, you then need to scroll down and click on a second link (https://help.moveworks.com/docs/multilingual-support-assistant) to actually see the names of the languages, which are displayed in a jumbled paragraph. If these names could just be in Setup, ie “Spanish (Latin America) (ES_MX)”, that would vastly reduce the amount of digging to understand how to use the page.
Integrate brief advertisements or updates about new functionalities within ticket updates provided by the bot to increase user awareness and adoption of new features.Ticket Creation Update: "Your ticket has been created successfully! 🎉 Did you know you can now perform an exchange voucher lookup and view its history directly through the bot? This new feature streamlines the process, making it simple and immediate. Give it a try next time you need to check a voucher!”Submitting this idea on behalf of Leon Van Romburgh
We're currently working on customizing the notification UI for HR Case tickets in the My Assistance interface, specifically for scenarios when:An HR Case operator comments on a ticket A ticket is awaiting acceptance from the userGoal:We would like to display only the following fields in these notification states:When HRC Operator comments: HRC Number & Title Status Last Activity When ticket is awaiting user acceptance: HRC Number & Title Status Last Activity Current Behavior:Moveworks currently displays standard ticket fields in all such notifications if those fields have values — even if some of them are not relevant to our users in this context.We reached out to Moveworks support and learned that:These fields are mapped at the platform level, and not customizable at the individual use-case level. Steerability was tested, but the model couldn't override the field inclusion. Therefore, removing or limiting fields displayed in the notification UI for particular use case isn't currently supported.Why This Matters:Customizing visible fields based on ticket state or context would:Improve clarity for end users. Reduce visual noise in the notification UI. Increase adoption and satisfaction with the My Assistance interface.Request:If others have found workarounds or custom configurations to manage visible fields in ticket notifications, please share your experiences. If this is a common need, we’d love to see Moveworks consider adding this as a platform-level enhancement
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.