Build better products with our product team.
We were having high hopes and expectations for Triage 2.0 to help us in reducing manual routing efforts to an absolute minimum. What we have found that Triage works exceptionally well in highly specialized cases where we have a high ticket volume. But this is not scalable. We can either have really good Triage for one Service or really crappy Triage for all our Services. What we obviously want is good to really good Triage for all Services to actually reduce our workload instead of just shifting it to second or third level support. The good results of the specialized models need to be scalable for enterprise wide useTo solve this issue what we require is the possibility to define multiple Models or Indices that run for different groups of Tickets. Ideally we could even have multiple Triage Runs on the same tickets. I envision something like: General Triage runs through all incoming tickets and identifies based on the description the right Service and routes to the respective Service Offering Depending on the Service Offering selected a new model is triggered for Triage for that specific Service and potentially take into consideration more fields than just description to route to the accurate second level group. Meaning we would have multiple models for the different services all specialized in the specifics of each service On a second Triage run also outside information should be taken into consideration such as work instructions for SD Agents that already contain explanations on routing accurately etc. Lastly if Triage cannot identify any further routing but the Ticket still needs automated actions we want to be able to trigger AI Agents to work on the ticket, but that trigger should come from Triage so there is no interference.
We were having high hopes and expectations for Triage 2.0 to help us in reducing manual routing efforts to an absolute minimum. What we have found that Triage works exceptionally well in highly specialized cases where we have a high ticket volume. But this is not scalable. We can either have really good Triage for one Service or really crappy Triage for all our Services. What we obviously want is good to really good Triage for all Services to actually reduce our workload instead of just shifting it to second or third level support. The good results of the specialized models need to be scalable for enterprise wide useTo solve this issue what we require is the possibility to define multiple Models or Indices that run for different groups of Tickets. Ideally we could even have multiple Triage Runs on the same tickets. I envision something like: General Triage runs through all incoming tickets and identifies based on the description the right Service and routes to the respective Service Offering Depending on the Service Offering selected a new model is triggered for Triage for that specific Service and potentially take into consideration more fields than just description to route to the accurate second level group. Meaning we would have multiple models for the different services all specialized in the specifics of each service On a second Triage run also outside information should be taken into consideration such as work instructions for SD Agents that already contain explanations on routing accurately etc. Lastly if Triage cannot identify any further routing but the Ticket still needs automated actions we want to be able to trigger AI Agents to work on the ticket, but that trigger should come from Triage so there is no interference.
Conversational workforce intelligence spanning instant data-backed answers, interactive deep research, and validated agent workflows like Succession Planning and Talent Risk
How are we improving the product?Voice Assistant brings the Moveworks Assistant to call center integrations, giving employees a voice-based way to access enterprise knowledge, reasoning, and actions.How does it work?Employees interact through a supported call center experience, which connects to the Moveworks Reasoning Engine to understand requests, retrieve relevant information, and complete supported tasks.Licensing RestrictionsTo be confirmed before General Availability.Technical RestrictionsSupported call center integrations, regions, and technical requirements will be documented as the release progresses.DocumentationEnablement and validation documentation will be added before Controlled Availability.
As of now, multipart/form-data is not supported in http actions in agent studio. Therefore most of my requests have to be made using the application/x-www-form-urlencoded content type. This results in numerous encoding issues as Moveworks is not natively handling encoding like postman does. Can we get datamapper to support multipart/form-data alongside application/json?
Expose the chatbot / bot friendly name in the Data API so customers can attribute analytics by assistant.
It would be nice to be able to gather Analytics on Ambient Agent use cases we deploy such as link or button clicks. As an example, we currently have several plugins related to Clarity timesheets that are both conversationally triggered and scheduled triggered. The conversationaly triggered versions show up in analytics and we can see link and button clicks fine. The scheduled ones however don’t give us any analytics so we can’t update our stake holders to see if users are interacting with these notifications.
A best-in-class Slack experience — improving usability, increasing trust in assistant responses, and enabling users to complete more work directly within Slack.
Modernizing our Teams platform with new UI elements — chat threads, text streaming, and side buttons.
There are situations where an unexpected update or an urgent change occurs. In those situations it would be good to be able to create a immediate Question and Answer response available in the system. Creating a knoweldge article and waiting for it to ingest takes too long when an immediate response is required. Sending employee comms is also not always the best approach. It would be best if questions and answers could be setup.As far as I am aware this is an option but it has to be configured by moveworks support, it would be best if it could be easily configurable in the Moveworks settings so client can immediatley make change.
Discover and deploy a curated, vetted library with Pre-built Assistants, templates, and more.
On-demand talent insights for risks, performance, and succession gaps. Prepare for talent reviews with the same understanding as HRBPs.
Lead more and juggle tools & tasks less with help preparing for 1:1s, coaching for difficult moments, and better self-help for common questions.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.