Skip to main content

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

    Filter by idea status

    Filter by product

    1294 Ideas

    SarahbenaliNew Participant

    Bot reading images4. Future Consideration

    Are there plans on the roadmap to enable the bot to read images?For example, reading error messages uploaded by users and the bot being able to recommend corrective steps from their knowledge.

    2
    kyril.remillard
    Forum|Forum|1 year ago
    lalikuma
    lalikumaKnown Participant

    ServiceNow - Support client script3. Existing Functionality/Native Skill

    In the ServiceNow platform , Majorly forms uses the client scripts.The UI policies and Client scripts enhance the forms and create a great user experience.The challenge for us is we have 149 forms and nothing is supported by BOT.How we can overcome that challenge   ?Do Moveworks has any plan to improvise the product to support the UI policies and scripts.

    3
    Forum|Forum|1 year ago
    sujit gaikwadKnown Participant

    "Country" tab in SN Knowledge Article is not being ingested as a user criteria3. Existing Functionality/Native Skill

    Hi Team,Country tagging on the title works well however there are instances specially in HR wherein there are multiple countries are to be tagged and putting all of the country names in the title will sometimes exceed character limitations. We would like to request for the Country tab to also be ingested and identified as a criteria for knowledge when it is being served as a result. This ensures better accuracy as well as ensure that articles created will only be available to the users in the specified countries. HR articles have confidential processes that should not be visible from one country to another.RegardsSujit

    3
    andrew.mairena
    Forum|Forum|1 year ago
    onlyawaveNew Participant

    Okta Groups suppor for Creator Studio Workflow Access4. Future Consideration

    We are building out multiple creator studio workflows to support our Sales and Revenue teams, now.  Due to the nature of the data they can access via these workflows - we are looking to limit access to just those groups.   The strongest indicator of team membership in our Okta instance is represented in Okta groups.  If we could get support for that as a way to grant Creator Studio Workflows, that would help remove the manual nature of access today. 

    5
    Forum|Forum|1 year ago
    sheetalsNew Participant

    Data Validation for a Text input3. Existing Functionality/Native Skill

    In creator studio we want to have users add in a secondary owner for SharePoint sites and enter another email address. We have found that email addresses are easily mistyped and we would want to add some sort of validation to ensure they are in fact an email address and an active one.Is this currently possible?

    2
    kyril.remillard
    Forum|Forum|1 year ago
    navya.kandiNew Participant

    Enable redirect URL in bot and allow the user to give consent3. Existing Functionality/Native Skill

    We are working on a use case for SAP Approval. There is a Approval API in SAP ECC System, and the approver name should be on the actual user who approves it.To achieve the SSO we have configured Microsoft Azure AD as Identity Provider and SAP as Service Provider.Below is the end-to-end process of a user authentication:The user is redirected to the Azure AD tenant’s authorization endpoint (https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0/authorize) in order to authenticate and to acquire an access token for the API. The user has to enter their credentials and give consent to the requested permissions to access the API. Once the user is successfully authenticated, the redirect URI receives an access token for the API in response from the authorization endpoint. To allow the Azure AD authorization endpoint to issue an access token the OAuth2 implicit grant flow must be used. The user is now authenticated and the front-end has acquired an access token that can be used to call the API on behalf of the logged-on user. This token cannot be used to authorize the call to the backend service in SAP NetWeaver. Services in SAP only accept access tokens issued by their trusted OAuth Authorization Server. The SAP OAuth Authorization Server accepts the SAML Bearer Grant type, which allows the API in Microsoft Azure to request an OAuth access token from SAP with a SAML 2.0 assertion. Azure AD provides a SAML assertion by receiving an OAuth access token (issued by the Azure AD tenant to the authenticated user before) in exchange. The API App is using the SAML 2.0 assertion by sending a POST request to the SAP OAuth Authorization Server to receive Bearer token from SAP. Once the SAML assertion is exchanged with an access token, the final POST request can be sent to SAP e.g., service from SAP using the access token to authorize the call on behalf of the logged-in user in Azure.How can we implement this flow through Moveworks creator studio, with the current capabilities how can we allow user to open a browser link from the bot and give the consent? 

    2
    kyril.remillard
    Forum|Forum|1 year ago
    jerry.dominguezNew Participant

    Add ability to notify "Caller" on SNOW tickets3. Existing Functionality/Native Skill

    On a Service Now (SNOW) ticket, the “Affected User” and “Watchlist” users will get notified in AVA whenever the Proactive Notification skill is triggered.  However, we would also like to notify the “Caller” when updates are made to the ticket.

    2
    kyril.remillard
    Forum|Forum|1 year ago
    sujit gaikwadKnown Participant

    Enhanced Incident Status Messaging for Unauthorized Users4. Future Consideration

     Currently, when a user who is not the caller of an incident tries to check the status of the incident in the bot, they receive the response below (as show in the screenshot). However, the message lacks clarity and does not explain why they are unable to view the ticket's status.Can Moveworks, update this message to something more meaningful that informs the user they are not authorized or do not have the necessary access to view the details of the ticket they are searching for?  

    2
    kyril.remillard
    Forum|Forum|1 year ago
    sujit gaikwadKnown Participant

    Align Bot Input Character Limit with ServiceNow Restrictions to Improve User Experience4. Future Consideration

    Hi Team,We have noticed that the long descriptions users provide before starting a live chat through the bot are being trimmed.Upon analysis, we found that ServiceNow Workspace has a 160-character limit applied to the short description field. However, on the Moveworks side, the input box allows for more than this limit, causing issues when users enter details exceeding ServiceNow’s restriction. This forces users to repeat their issue to the agent, leading to a negative experience with the bot. Could we implement a character limit on the input box to align with ServiceNow's restrictions? Live chat option - long descriptionRegards

    2
    kyril.remillard
    Forum|Forum|1 year ago
    KaviKnown Participant

    We would like to display the "close Issue" only on certain ticket state4. Future Consideration

    We would like to display the "close Issue" only on certain ticket state like “New”, “InProgress”. 

    2
    kyril.remillard
    Forum|Forum|1 year ago
    jstapletonNew Participant

    Channel Resolver to include screenshots4. Future Consideration

    Hi,Would be extremely helpful if channel resolver could include posted screenshots in the ticket.  Todays behavior provides a URL to the screenshot, but would be a big efficiency gain if the screenshot actually showed in the ticket.

    2
    kyril.remillard
    Forum|Forum|1 year ago
    jchretienNew Participant

    Allow the Bot to add user to security group3. Existing Functionality/Native Skill

    The bot is actually able to create DL and add user to DL. The bot can also add user to group for software provisionning.If the bot is able to do both of those thing, it should be able also to add user to security group. Adding user to security group can reduce the number of ticket coming to IT service desk for users that require access to a group. That group can provide access to folder on an onPrem file server, but also can provide access to a 365 Sharepoint folder. This can be also a Microsoft Teams group.We manage a lot of things with groups and having the bot the functionnality to add or remove users to or from a group will help a lot service desk.Example: User 1 is asking to get access to Purchasing department group. The user should ask the bot, “Please add me to the Purchasing-Denvers group”. The bot follow workflow and request approval to Manager or specific user.Example: User 1 is asking to get access to Purchasing department. group. The user should ask the bot. “Please add me to the Purchasing group”. The bot could answer “We found multiple group containing Purchasing, which one should meet your requirement?” Actually the bot is only creating a request to the IT service desk and once we get the approval from the manager, we only need to add the user to that security group. If the bot can do it, send the approval the manager and once the manager approve, the bot can automatically add the user to that security group.The bot is already listing DL groups, users and other, that should not be a problem to list security groups and add user to a group when user is requesting it and got approved.

    3
    kyril.remillard
    Forum|Forum|1 year ago
    alvaro.paredesNew Participant

    Channel selection when Allowin Moveworks to send promotional messages.4. Future Consideration

    Hello when requesting a new feature (in our case “Brief me” feature”) we stumbled on the next option to “Allow Moveworks to send promotional message”. It would be great that there was also checkboxes to choose and limit the preferred way, for example Email, Bot Message, etc… so customers can chose for example Email distribution but avoid spamming Bot messages.   

    2
    kyril.remillard
    Forum|Forum|1 year ago
    Apsara
    Apsara

    Feature Request: Pull in other sources4. Future Consideration

    Right now summarization is based on Tickets.Can it scan our KBs in service now, the Google Sheet FAQ? and provide an indicator?Can we know what external sources are being using when triggered?

    7
    Forum|Forum|1 year ago
    Apsara
    Apsara

    Feature Request: Hide sensitive data4. Future Consideration

    Some of the gaps or recommendations contain sensitive data like people’s names, terminations, locking accounts. We’d like the Knowledge writer to exclude any sensitive data or people’s names when summarizing, showcasing gaps or updates.

    9
    Forum|Forum|1 year ago
    glambInspiring

    Buttons in Creator Studio Events4. Future Consideration

    Creator Studio Events (with no follow-up actions) should allow for buttons to appear at the bottom of the message. Execution would be similar to how Employee Communication messages allow for buttons.For example, I use Events to send proactive notifications to users to complete pending actions on our intranet. Instead of using hyperlinks inside the message for users to click to complete a pending action, I’d like to use a button that would contain a hyperlink to the same location.Buttons provide a better user experience than embedded hyperlinks because users tend to click buttons more than hyperlinks directly. 

    3
    Forum|Forum|1 year ago
    chaitanya.kothhaParticipating Frequently

    Emoji’s are not appending to the button ( in Event)4. Future Consideration

    I am trying to add emojis to a button, but it is not working as expected. This functionality was working in the Classic version, but it is not working in the Copilot version.Can you consider this feature and provide the solution 

    3
    Forum|Forum|1 year ago
    nageswararao_gourabathinaParticipating Frequently

    The "View All Option" pop up shows Slot name instead of the question detail in heading4. Future Consideration

    When there are multiple option buttons in a Paths use case the bot gives a "View all option" button on click of which a pop up opens up which shows all the multiple choice button options that we have configured in the path use case using ask a question action. For the Share Una Feedback path use case we have noticed that inside the pop up the bot shows the variable name instead of the question detail as a label for the multiple choice options.Expected: Question Detail should be shown in the pop up as labelActual: Variable name which we configure for the question is shown to the user as label  

    2
    Ajay Merchia
    Forum|Forum|1 year ago
    marissa.lacombeParticipating Frequently

    Remove Close Notes from ServiceNow Incident Resolution Notifications8.0 Possible Agent Studio Solution

    Hi Moveworks Team!Requesting an enhancement that allows us to hide ServiceNow Incident close notes from being shown during an Incident Resolved notification. Today, Incident close notes are not at all viewable to the customer. These close notes typically contain the fix the agent completed to resolve the issue, rather than a customer visible update. Impact: We would be exposing a field via Moveworks that colleagues dont have access to or see today. 

    2
    kyril.remillard
    Forum|Forum|1 year ago
    gmerrill
    gmerrillEmployee

    Add Lenovo documentation to external knowledge4. Future Consideration

    On behalf of Swire, could we please add Lenovo as a documentation source.

    2
    kyril.remillard
    Forum|Forum|1 year ago
    michael.prouty
    michael.proutyNew Participant

    Workday ID Masking for 'View next approval' and 'View all approvals'4. Future Consideration

    For customers who’ve integrated Workday approvals, users are presented with a very long Workday ID when they click on ‘View next approval’ or ‘View all approvals’. While this means something systematically to the Moveworks agent, it gives a poor user experience and could seem there is some sort of error. Request that this ID either be removed/hidden or masked to be user friendly. 

    2
    kyril.remillard
    Forum|Forum|1 year ago
    davrey04Participating Frequently

    Prevent multiple utterances from the same article4. Future Consideration

    Change how the bot interacts with each knowledge article.The chatbot looks at headers and then pulls utterances from them. Having more than 1 H2 heading in an article results in the bot pulling two links from the same article instead of two utterances from different articles.The issue is that some articles require a Table of Contents (ToC), which is built by headers. This current method prevents us from using ToCs or forces us to manually build the table of contents to avoid this issue.It would be great if the bot compares the article number it uses for one utterance and then disregards that article for other utterances when additional articles on the same topic are available. Having that would allow us to use ToCs again. 

    2
    kyril.remillard
    Forum|Forum|1 year ago
    sai.adigoppula
    sai.adigoppulaNew Member

    Request for Application Space to Manage Utterances4. Future Consideration

    Hello Moveworks Team,I would like to request the creation of an application space where we can directly add utterances to forms (record producers and catalog items), rather than raising a ticket each time to add them.Ideally, the template could be designed similar to how utterances are added for query and path requirements in Creator Studio. This implementation will not only assist us but will also be beneficial for all clients using Moveworks.Thank you for your consideration.

    2
    kyril.remillard
    Forum|Forum|1 year ago
    Nick PolianlisNew Participant

    Channel Resolver Feedback4. Future Consideration

    We recently launched Moveworks to the business which included the implementation of Channel Resolver. We could definitely see the value in this feature however have some feedback on how the experience could be improved for both the user and agent:How it currently works: Employee asks question in channel eg. peopleinfo-triage Bot identifies whether it has access to knowledge that could assist the employee If it determines with a high confidence that it can assist, it will DM the employee with a response At this point an emoji will appear below the original employee query in the channel Employee receives bot DM and is asked to rate the response as ‘helpful’ or ‘unhelpful’ If ‘helpful’ a tick emoji is added to the original message in the channel If ‘unhelpful’ a greenflag emoji is added to the original message in channel and GF agent reaches out to assist GF agent will then add a tick emoji once issue is resolved Challenges and feedback with current solutionBot DM - By design, the bot interacts with the user in DM. This presents a couple of challenges for agents: If employee rates response as unhelpful, agent has no sight on why that is the case and so has no context when the employee returns for more help There is a desire from teams outside of IT, HR etc to adopt Channel Resolver. However, in these instances, there is a lot more nuance to the issues they resolve. So, not having any visibility over the interaction between the bot and the employee is a blocker to adopting Channel Resolver. When testing the inclusion of ticketing in Channel Resolver we found that the flow was not as intuitive as it could be: User comes to channel Bot then redirects user to a DM to assist User rates response as unhelpful which then redirects them back to the channel again At which point they need to manually add a ticket emoji in order to raise a ticket Ideally the flow would be: User comes to channel and raises issue In the thread the bot attempts to assist If user rates response as ‘unhelpful’ they are immediately offered the option to raise a ticket Additional Feedback It would be helpful if an agent could be defined per channel. As it stands today, setting an employee as an agent is a universal setting. So, for example when a Finance agent, reaches out for help in the HR support channel, the bot will not respond. We’d like the ability to introduce other skills to Channel Resolver (eg. Creator Studio use cases)

    2
    kyril.remillard
    Forum|Forum|1 year ago
    ramon.espinosaNew Participant

    User Engagement Nudging4. Future Consideration

    It would be great if moveworks could proactively reach out to users who have never initiated an interaction with the bot or users who haven’t in over X amount of time, perhaps either 6 months or a year. The nudge would just be a reminder to the user that the bot is still around to help them with whatever capabilities are available. Another way would also be to find users whom have had X amount of Incidents or Requests created but had never interacted with the bot to create those Incidents or Requests. Again this would be the same nudge to remind them that they could use the bot to submit those easily for them and possibly provide an answer or get them access.Something like this might help drive up adoption for those that may not have used it before or possibly used it and didn’t have a good experience but after so long new functionality may be available or more knowledge to help them.

    2
    kyril.remillard
    Forum|Forum|1 year ago

    Filter by product

    • All products
    • Analytics
    • AI Assistant
    • Agent Studio
    • Employee Experience Insights
    • Knowledge Studio
    • Moveworks Setup
    • Enterprise Search
    • Content Integrations
    • Content Gateway
    • Other Integrations
    • Next Gen Triage (2.0)
    • MW4Web
    • Service Management
    • AI Agent Marketplace
    • Agentic Reasoning Engine
    • EmployeeWorks
    • General
    Terms & ConditionsAccessibility statement