Build better products with our product team.
Hello Team,It will be great to have a feature where the admins have possibility to provide read only access to users to moveworks setup where these read only access users can check and verify things like files ingestion limit sharepoint sites which are enabled for ingestion and other attributesÂ
We are looking for a way where chatbot and send response to any teams channel. The use case - The support team who are working different time zone and shifts, they like to get the chatbot messages (example : SLA Breach warning of tickets) directly to Teams channel / teams group so that these tickets / messages can be prioritized by teammates.  Sending individual messages to team members leads the chance of missing their own task , like approval, order status. Regards,Rajeev
Hi Team, Today we have an option to see last imported/ingested time of users and forms. Below - RefUsers Ingestion Details Forms Ingestion Details But we donât have a provision to see when is the last time knowledge ingestion (KBA, FAQ, policy) ran and we also donât know whether the user criteria associated to the knowledge is ingested or not. This information will help us to understand whether the knowledge and associated criteria is ingested, indexed and available or not. And then we can test and accordingly inform our team also.Knowledge Ingestion Â
Hi,As an admin for Moveworks setup, I am looking for an easy report which would show me what all Softwares are Enabled in the Bot along with if they require approvals. To achieve this, can we add 2 more columns in the software catalog page. The 2 columns I am looking areEnable software provisioning in the bot (True/False) Provisioning Method (Auto-Approval / Custom approval)Â Moveworks Setup - Access Management - Software Access - Software Catalog (https://xxx.moveworks.com/setup/setup-access-software/software-catalog.home)
Get Help is often overused simply because it provides an easy way out to submit anything.In our case, this is particularly happening with SAP, though itâs happening with other domains as well.I previously asked about the option to remove this option, when Red has a potential solution, and the response was, âwe canât, it must be retained as a fallbackâ.However, with the introduction of the new GenAI version, the situation has changed, so I want to revisit my original request.When Red proposes knowledge, an automation or a form, the "Get Help" option should be removed/hidden. If the proposed solution isnât satisfactory, the user can engage in a conversation to indicate that it doesnât meet their needs.Then Red would come back, if it did not find anything, then the standard response would be given and the Get help option would become available as this last resort.We have invested efforts in knowledge and forms to get the incidents and requests where they need to be, but I see this âGet Help â option is undermining some of these efforts. Now the question may be, why are your customers not using the presented forms?And we asked ourselves and our customer the same question, (even if we try to make the dedicated forms as easy to use as possible..) Some customer will ignore that and use the Get help link, because it's there.Customer will go for the path of least resistance, and that path is often Get Help,
To reduce wrong-turn answers and keep users engaged, weâd like the bot to: Ask Clarifying Questions ⢠When context is thin (e.g., a one-word request like âlaptopâ), prompt follow-ups such as âAre you looking to request new hardware, track an existing order, or troubleshoot an issue?â ⢠Only present forms or solutions once the intent is clear Add a Closure Check ⢠End each exchange with a quick confirmation like âDid I answer your question, or is there anything else you need?â ⢠This gently invites extra detail if the reply missed the mark. These two tweaks should lower mis-routes, surface richer user input, and ultimately shorten resolution time.Thanks for considering!
When performing a search, the answer provided can reference several citations whereby some of the citations are relevant and others are not (screenshot example below). This is a product request to allow the ability to up-vote/down-vote by citation instead of by the entire answer. There are cases where part of the citations are relevant and currently we only have the ability to down-vote an entire answer instead of by citation. Current ability to down-vote an answer will cause this answer not to appear even though part of the answer is relevant. Allow ability to up-vote/down-vote by citationÂ
Some organizations have limited how long you can re-open a incident. Today the bot will offer the ability to re-open the incident even if the case cannot be re-opened by policy. Apparently that message isnât customizable. Could we either enable the ability to match the ITSM re-open policy to the bot prompts so the re-open option isnât available? Another option could be to make the prompts customizable so the user can be notified they wonât be able to re-open the incident if itâs older than X days and to create a new case instead.
The thumbs up/down buttons are way smaller than the voting options in classic. Especially when dealing with users who have special needs it needs to be more accessible. Even regular users may not bother with giving feedback when it takes concentration to hit the button with the mouse. They should be a bit bigger than they are now.
Copilot understand when APIs are returning no records & handle the dialog appropriately. For Additional information - Please use - Â
Description:Adding the live chat interaction number (IMSxxxxx) and request ID to the analytics logs provided via Moveworks Data API for Smart Hand-off records is suggested.Business Need:These details are essential for accurately tracking live chat sessions, understanding user sentiment, and identifying areas for improvement. They enable more effective analysis of negative feedback and support the creation of reliable internal dashboards for performance monitoring.
It would be great if the Analytics provided in the Moveworks Portal could be integrated as a source with our Bot, allowing Admins and Analytics Users of Moveworks to query the Bot with questions vs. manually navigating to the portal and clicking through tabs and options. Example: Hey Bot, what has been the trend of active users over the last three months? Hey Bot, what are the top three feedback trends raised by users? This could even be extended to Roles and Permissions (does John Smith have access to analytics?) and Employee Experience Insights.
Requesting a new feature that would allow us to track the performance of the Interception skill ran on General Request, Work Request, and Incident tickets. Currently, we can obtain raw data from our Customer Success Team upon request. However, we all agree that this method is not sustainable in the long term as it is time-consuming for all parties involved.We believe it would be beneficial to have a feature that allows us to measure and track this skill. This would provide insights into the effectiveness of the Interception skill and aid in enhancing user interaction. Furthermore, it would help us understand whether our bot is providing the correct information/form or if users are disregarding our bot. This information would be invaluable in shaping our education strategy.Therefore, we kindly request that this metric be incorporated into the standard analytics dashboard for easy tracking. We believe this addition would greatly enhance our ability to monitor and improve the performance of our bot in the Interception Skill.
We noticed that Webhooks notifications do not have the option for users to react to them. This stops us from collecting feedback from users easily on their functionality.Would it be possible to have the option to have feedback đ/đ added to Webhook plugins as well? Maybe as a selectable option on the launch configuration page of the plugin.Iâm working around the issue by adding a feedback form on our notification. Thanks in advance for reviewing this idea đ
Allow users to toggle Dark Mode on and off.
Hi Team,Product Idea: ExecutionâRate Limits and User Verification Workflow for Plugin ActionsProblemPlugins can be triggered repeatedly within a short time windowâeither due to automation loops, misconfiguration, or unintended user behavior. When a Plugin executes more than an expected number of times in a defined period, it introduces risks such as:- Unintended system changes being applied repeatedly- Increased load on downstream systems- Potential security concerns if repeated execution indicates misuse or compromised credentials- Loss of user trust if actions occur without clear intentThere is currently no native mechanism in Moveworks to rateâlimit Plugin executions or to validate authenticity when abnormal execution patterns occur.Proposed CapabilityIntroduce a configurable executionâlimit framework for Plugins, allowing administrators to define:- Max execution count (e.g., 10 executions)- Time window (e.g., within 1 hour, 24 hours, etc.)- Trigger conditions (per user, per device, per workflow, or global)When the threshold is exceeded, Moveworks should automatically:- Pause further executions of the Plugin.- Notify the end user (or admin) that the Plugin has been triggered unusually often.- Request confirmation from the user to validate authenticity.- Resume or block execution based on the response. Regards,Sravani S
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.