Build better products with our product team.
Unfortunately, we’ve been holding off on rolling out Channel Resolver due to ongoing challenges in displaying accurate bot responses. We frequently receive either incorrect answers or no responses back at all for inquiries that currently work well in direct messages. Integrating Creator Studio into Channel Resolver would be incredibly helpful in refining and directing responses to ensure accuracy.This feature is essential for us, as we were initially under the impression that Creator Studio would be compatible with Channel Resolver upon introduction.Is there any possibility of adding Creator Studio support for Channel Resolver soon?Thank you
We want to see the actual values of all the fields in response payload. It would be easier for us to debug in the futureCurrently we’re not able to see the values of response payload like action name, comments etc.
I’d like to be able to download my ingested files content the same way as the knowledge content. For example, when I go to download my knowledge content, I can download ALL my records at any given point.However, If I download the files content that MW has ingested, the download is capped at 250 records. We currently have ~3K files ingested. So I’d have to download several times to see all the files we’ve ingested. I’d like this to work similar to other content. Thanks!
Possibility around enable Ticket interception with Other Domains (ex: HR, Facilities etc)
One of the key challenges with our current copilot is the lack of synchronization between the Moveworks Teams environment and the Moveworks webchat. This disparity leads to issues, as the bot often loses critical context required to provide accurate and consistent answers. As a result, users experience problems such as knowledge not showing, inconsistent behavior, and frustration when switching between platforms.By implementing synchronized user chat history across both Teams and webchat, you could ensure seamless continuity and context retention, regardless of the platform the user is engaging with. This enhancement would not only improve the reliability and performance of the bot but also significantly elevate the user experience, fostering trust and efficiency in interactions.
We have multiple plugin examples where we don’t want context maintained - what machine am i logged into ? - do not retain this - need this updated / triggered at each call What tasks are assigned to me ? - do not retain this - want to have a fresh call to dataIn these scenarios we worked with Ryan @rgeroulo to add a demonstration for us - but it would be great if we had the ability to add this as a flag to all the plugins we created.
As Moveworks support Native approvals (Servicenow & workday).We created few other approvals via Creator studio, Can we club them all together.So If any users ask “What approvals do I have?".The Copilot will respond and summarize all approvals (Native + Custom build) approvals,
Control to enable/Disable skills in Platform (Teams, Slack, Webbot) Ex: As we enabled the webbot in SMART and customers can see the approvals in SMART as well in Navi chat windows.So from users experience we want to stop approvals (Skills) in our WebBot.
We’ve got a Workday use case where the ability to upload an attachment as proof of Legal Name change would be necessary to properly implement the use case. I built a purple chat example of what this might look like (see below). At present there isn’t a way to gather this type of documentation from the user within an Agentic automation.
We have our Moveworks bot enabled for both Slack and Gmail. However, we are noticing behavior where notifications/messages from the bot do not go to both channels but only the most recently used one.It would be great if the bot could send notifications to both so that users do not have to switch back and forth platforms to receive bot messages.
When there are no Live Agents available and a user receives the No Live Agents Available message it is being sent before the second LLM response confirming the request for live agent support has been submitted. This is a confusing UI/UX since its not clear whether or not a Live Agent will in fact contact the user. The order that messages are currently sent: (Confusing UI/UX) 1. I have initiated a request for an IT live agent to assist you…2. I’m sorry, there are no live chat agents available at this time...3. I have submitted the request for a live agent to assist you…The order that messages are sent should be: (Preferred) 1. I have initiated a request for an IT live agent to assist you…2. I have submitted the request for a live agent to assist you…3. I’m sorry, there are no live chat agents available at this time...
It would be helpful to edit the event message by including variables from user profile. at the moment it is not very useful. Regards,Rajeev
Problem Statement:Currently, the bot dynamically selects plugins to respond to user queries. However, even when custom use cases are available, they are not consistently prioritized. Multiple plugins often result in custom use cases appearing as secondary or tertiary options, while articles are sometimes prioritized instead. This behavior diminishes the importance of business-aligned custom use cases and negatively impacts efficiency.Description:We propose an enhancement to the bot's functionality to prioritize and trigger custom use cases (Creator Studio use cases) first, ensuring they take precedence in responses. This prioritization would then be followed by forms and articles, aligning with business-critical needs and enhancing the user experience.For any user utterance, the bot should always check CREST use cases first, followed by forms, and then articles if the bot lacks confidence in a CREST use case.In scenarios involving multiple plugin responses, if a CREST use case is available for the user utterance, it should always appear at the top (as the first record), followed by forms and articles. If no CREST use case is available, forms should be prioritized over articles.Plugin Priority Sequence:Creator Studio use cases Forms ArticlesCurrent Behavior:Custom use cases (Creator Studio use cases) do not consistently appear at the top of multi-plugin responses. The bot selects plugins dynamically based on its interpretation of the user's query, with no predefined priority sequence. This leads to unpredictable response ordering, which does not prioritize business-critical workflows.Expected Behavior:Custom use cases (Creator Studio use cases) should always be prioritized and triggered first in bot responses, ensuring alignment with business objectives. If no relevant custom use case is available, the bot should prioritize forms and then articles, based on the confidence score. This adjustment will ensure that business-critical workflows are given precedence, minimizing user frustration and improving overall efficiency.
I would like to be able to give access in Creator Studio to “Developers” who only have access to certain areas (Events and Queries) for example. They would be able to use creator studio only for those scenarios and not all of the capabilities. This would allow us to have “citizen developers” build their own use cases based on their skills.
I do presentations to some of our VP’s and Directors on bot Performance, and the Executive Insights Dashboard that was previously on Tableau was perfect for these presentations. It would be great add this back or the ability to create a customizable dasbhoard that could allow for some drill down or linking to other reports for a little more detail.
Background: During our discussions, it became evident that the current all-or-nothing approach to data retention poses challenges for my organization. Specifically, the inability to selectively delete certain fields or types of data from logs and analytics have raised concerns about data privacy. Proposed Enhancement: We propose the implementation of a feature that allows for selective data deletion within Moveworks's logs and analytics and to be able to set retention period. These features would enable users to specify which data fields or types should be retained and which should be purged. For example, while retaining essential analytical data, users could opt to delete sensitive information such as notes fields or specific user inputs.We believe that this enhancement would greatly benefit not only our organization but also other Moveworks customers facing similar challenges. We appreciate your consideration of this request and look forward to your feedback.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.