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

    1220 Ideas

    RyanPasca
    RyanPascaNew Participant

    Threshold of acceptability for enterprise search and knowledge articles1. New

    Goal: reduce frequency of bot responses that weakly match user intent. Reduce frequency of out-of-context bot responses.Product Idea: Would it be possible to add a feature allowing organizations using Moveworks to configure (perhaps within Moveworks Setup?) a threshold of acceptability for enterprise search?For example, a minimum matching score rating for knowledge matches to allow them to be surfaced. If there are no knowledge matches that meet the minimum matching score, then the bot would let the user know and offer to file a ticket or initiate live chat / agent handoff.I read about Moveworks Search “Ranking” at the link below, and understand Moveworks has specific ranking methodology to determine the priority order of which content to display.https://www.moveworks.com/us/en/resources/blog/enterprise-live-search-how-we-built-itHowever, this product idea addresses the scenario where Moveworks has nothing in its repository that meets the threshold and lets the user know, instead of citing a non-relevant or tangential topic. Instead, we would prefer the bot to reply with a statement along the lines of “I couldn't find a precise match for that. Would you like me to file a ticket for you?”We also envision this could workout when a plug-in triggers: It would be nice to have a threshold so that any enterprise search that comes up after a plug-in trigger, will have a very high likelihood of matching the plug-in content. So for example, when entering time, it would be best to only have articles that pertain to entering Time and not one for Expense (which it would most likely do in organizations where the two topics are so intertwined, and vocabulary across similar topic areas overlaps significantly.)I realize that if this feature existed, and an organization were to set the threshold too high, users could complain that the bot not knowing things. However if set too low, knowledge articles served would remain noisy, which can sometimes be the case currently.Here are a few Observations from Recent Chat Experience, testing interacting with the bot and asking it unique / obscure questions:The bot will occasionally ask the user to clarify if the question is unclear. It will say things like “It sounds like you may mean one of two things…”, without serving non-relevant articles. However, I did also find that the bot will tell the user when it cannot find a source that answers a highly-specific question, but it still will reply with links to articles that do not address the user’s direct intent. (happy to try to provide further examples if helpful)

    0
    RyanPasca
    Forum|Forum|2 days ago
    R
    ramapr1New Participant

    Sensitive data Redaction and Data Masking for Moveworks Interaction data in Analytics1. New

    Moveworks Analytics currently shows user inputs and bot responses in plain text. While this level of visibility is extremely helpful for developers investigating unexpected bot behavior or addressing negative user feedback, exposing raw conversation text can create privacy and compliance concerns.Submitting this as a proposal to introduce native, configurable data redaction and masking capabilities within the Moveworks platform for raw interaction logs and analytics dashboards.Suggested capabilities would include:Built in regex based and AI driven entity detection to automatically identify and redact common sensitive information, such as salary details, performance ratings, and similar confidential data.The ability for tenant administrators to define custom regex patterns, keywords, or rules tailored to their organization’s specific privacy and compliance requirements.

    0
    R
    Forum|Forum|2 days ago
    afleury
    afleuryInspiring

    Duplicate User Resolution & Account Prioritisation1. New

    Idea:Moveworks can already identify duplicate users, but there is currently no simple way for admins to resolve or prioritise which account should be treated as the authoritative record.ProblemMany organisations have multiple user records with the same email due to contractors, rehires, identity migrations, or HR system design. When duplicates exist, user attributes such as location, cost centre, manager, or department can be sourced from the wrong profile. Administrators must manually investigate and clean data in source systems.Suggested Enhancement Add a Duplicate User Resolution feature that allows admins to:Select the preferred record when duplicates are detected. Configure prioritisation rules (e.g. Team Member > Contractor > Short Term). Set source-of-truth precedence for user attributes. View and remediate duplicate users from a single admin interface.BenefitsReduces manual administration. Improves user identity matching accuracy. Prevents missing or incorrect profile attributes. Helps customers with complex identity environments without requiring perfect source-system data hygiene.I can provide a ServiceNow support case if you want to look into this further. DM me.

    0
    afleury
    Forum|Forum|2 days ago
    afleury
    afleuryInspiring

    Generative AI Search built into Moveworks Community portal.1. New

    Idea: Add a Generative AI Search capability into the Moveworks Community to assist customers and Moveworks team with quickly discovering information.Think of it like having a Perplexity or Google search built into the Community search page :) Benefits:AI-Powered Summaries: Generative AI can create concise summaries of search results, helping users quickly grasp the main points without having to read through multiple sources, Enhanced Search Experience: These summaries often include bullet points, images, videos, and citations, making the information more accessible and engaging.  Contextual Understanding: The AI adapts to user behaviour and preferences, offering personalized recommendations and insights. Interactive Features: Users can interact with the summaries, such as clicking on highlighted sections to get more detailed information or continuing the conversation with the AI for further clarification.

    1
    afleury
    Forum|Forum|2 days ago
    9
    9002467New Participant

    Moveworks Displays "Reopen Issue" Option for RITMs That Cannot Be Reopened1. New

    Description:Artey currently presents colleagues with an option to reopen a previously submitted ServiceNow Requested Item (RITM) during conversational interactions. However, the underlying integration does not support reopening requested items, resulting in a poor user experience where users are offered an action that ultimately cannot be completed. As a result, colleagues may attempt to reopen requests through Artey only to encounter an error or unsuccessful outcome, creating confusion and reducing confidence in the assistant. Requested Enhancement:Update the Moveworks ServiceNow request management experience to validate whether a request type supports reopening before presenting the option to the user. If reopening is not supported for a given record type (such as RITMs), Moveworks should:Suppress the "Reopen Issue" action entirely for Requested Items, or Display a clear message indicating that reopening is not supported and provide alternative guidance, such as submitting a new request or contacting the appropriate support team.Business Impact:Eliminates misleading action prompts within Artey. Reduces colleague confusion and failed interactions. Improves trust in the assistant by only presenting supported actions. Decreases unnecessary support inquiries related to request reopening failures.Current Behavior:Artey offers users the ability to reopen a requested item (RITM), even though the action is not supported by the underlying process. Expected Behavior:Artey should only present a "Reopen Issue" option when the associated record type and workflow support reopening. Unsupported request types should not display the option. Acceptance Criteria:Moveworks validates reopen capabilities before displaying the action to users. RITMs that cannot be reopened do not display a "Reopen Request" option. Users receive clear guidance when reopening is unavailable. No failed reopen attempts occur for unsupported request types due to a presented Moveworks action.

    0
    9
    Forum|Forum|3 days ago
    afleury
    afleuryInspiring

    Auto-map input arguments from HTTP Actions into Compound Actions and Conversation Processes1. New

    OverviewIt would be helpful if Agent Studio could automatically import or sync input arguments from an HTTP Action into the related Compound Action and Conversation Process.Today, inputs defined in an HTTP Action often need to be manually recreated or mapped again in the Compound Action, and then mapped again in the Conversation Process. While manageable for smaller actions, this becomes increasingly time-consuming and error-prone as actions grow in complexity.ExampleA ServiceNow Change Request action might require fields such as:short_description description start_date end_date risk_impact_analysisThese inputs are already defined within the HTTP Action, yet they must still be manually carried through multiple layers before the action can be used conversationally.This results in the same schema effectively being maintained three times: HTTP Action↓Compound Action↓Conversation ProcessSuggested ImprovementIntroduce an option such as:Import input arguments from HTTP Action Auto-map inputs Sync action schemaWhen enabled, Agent Studio would automatically propagate input definitions through the action chain while preserving:Field names Data types Descriptions Required/optional settings Default values Validation rulesBuilders could still override mappings manually if needed.BenefitsReduce repetitive configurationBuilders should not need to recreate the same inputs multiple times across different layers of the platform.Reduce mapping errorsThe more times a field is manually mapped, the greater the chance of:Missing fields Incorrect parameter mappings Out-of-sync schemas Placeholder values being accidentally passed throughFaster development and testingLess time spent maintaining mappings means more time spent:Building business logic Refining user experiences Testing new ideas Delivering value to end usersEasier maintenanceWhen an HTTP Action schema changes, updates could automatically flow through the action chain instead of requiring manual updates in multiple places.Why This MattersThis may be partially addressed by future capabilities such as Tool Architect, but there is still significant manual configuration required today when building actions.The biggest impact is not the time spent clicking through mapping screens. It's the interruption to the development flow.When experimenting with ideas, repeatedly recreating or remapping inputs across HTTP Actions, Compound Actions and Conversation Processes creates friction and slows iteration.For builders who enjoy exploring new use cases, prototyping solutions, or developing outside normal work hours, this repetitive setup work often becomes the limiting factor. Time that could be spent improving the experience, testing new patterns, or creating innovative solutions is instead spent maintaining mappings.Reducing this overhead would make Agent Studio more enjoyable to build in, encourage experimentation, and allow builders to focus on solving business problems rather than managing plumbing.Guiding PrincipleMap once, consume everywhere.Define an input once and have it available throughout the action chain, rather than maintaining the same schema across multiple layers.

    0
    afleury
    Forum|Forum|3 days ago
    C
    cfinelliParticipating Frequently

    Add Support For Multiple Files In Agent Studio File Slots3. Existing Functionality/Native Skill

    This blog post https://www.moveworks.com/us/en/resources/blog/file-slots-file-uploads#one-file-per-slot-no-overwriting states: “Right now, you can only upload one file per File Slot. And once it’s uploaded, the user can’t replace it — they’d have to start over.This is a limitation we built in, not something forced on us. We could support multiple files, we just haven’t yet.”I’m currently building out employee submitted expense reports in agent studio and would love if they could just bulk upload all their receipts at once rather than 1 at a time. Multiple file support in a single slot would also significantly simplify my conversational workflow design since I wouldn’t need to create a slot for receipt 2, receipt 3, receipt 4, etc.In fact, in the same blog post, expense reports are mentioned: “Think about what you can build: expense reports with receipts attached”This capability would be great. Thanks!

    15
    S
    Forum|Forum|4 days ago
    R
    ramapr1New Participant

    Ability to Customize User Consent Messaging for HTTP Connector Authentication4. Future Consideration

    When a user attempts to access a plugin connected to a user-consent based authentication connector for the first time, the Moveworks bot currently displays a default system generated message prompting the user to authenticate. However, this message does not clearly instruct users on the action they need to take to proceed.For many non-tech users, the prompt can be ambiguous and they may not realize that they must click the authorization button and complete the authentication process. This can lead to confusion, failed plugin usage, and additional support requests.Submitting this idea request to propose allowing customers (developers) to customize the authentication prompt message shown by the Moveworks bot during user consent flows. Providing the ability to modify or override the default system message would allow orgs to add clearer, more user friendly instructions tailored to their users.For example, the customized message would look like:Please click the button below and complete the authentication process to allow the Moveworks bot to securely retrieve information you requested.Allowing such customization would improve user experience.

    6
    Kevin Mok
    Forum|Forum|4 days ago
    V
    vinitbKnown Participant

    Simplify User Consent Authentication Flow1. New

    SummaryUsers are failing to complete the connector authentication flow because the current consent message is unclear and the button is easy to miss without a call-to-action .ProblemWhen a connector requires user consent, Moveworks displays a message that leads with what it can't do (e.g., "I can't do XYZ..."). User feedback shows that most people stop reading at that point and never see the button prompt — causing them to abandon the flow entirely.Two specific issues:Message framing — Opening with a negative statement causes users to disengage before reaching the action they need to take. Button label lacks a call to action — The button is labeled with the connector name only (e.g., "SYSTEM"), which doesn't signal to the user that they need to click it.Current Experience We also attempted a workaround by renaming the connector to "Connect With SYSTEM" to make the button more descriptive. However, this causes Moveworks to use the same name in the preceding sentence, resulting in grammatically incorrect messaging: "Connect with SYSTEM isn't connected." Attempted Workaround  Requested SolutionsOption 1 — Simplified Consent Message (Preferred)Replace the current message with a clear, action-oriented prompt: Please grant access to [Connector Name] by clicking the button below.[BUTTON] This approach is direct, positive in framing, and immediately tells the user what to do. Option 2 — Independent Control Over Button Label and Message TextAllow admins to configure the button label and the accompanying message text independently, so the button can have a meaningful call to action (e.g., "Grant Access") without affecting the connector name displayed in other parts of the message. ImpactThis change would directly reduce authentication drop-off. It improves the experience for all users who interact with connectors requiring consent.

    2
    DIANA.TWC
    Forum|Forum|4 days ago
    R
    RanjiniNew Participant

    Title: Routing multiple HTTP error status codes without deep try_catch nesting1. New

     Hi everyone,This is a continuation of my previous post: Extracting dynamic JSON error messages from 4xx/5xx responses in a try_catch block.Because the JSON payload is dropped when an HTTP action hits a 4xx or 5xx status code, we are discussing a workaround with our API team: having them provide highly specific, unique HTTP status codes for every single type of business error (e.g., 422 = “Error Message 1”, 423 = “Error Message 2”, 424 = “Error Message 3”). This would theoretically allow us to hardcode specific, static fallback messages for each error scenario.The Challenge:Agent Studio only allows one catch block per try. If the API returns 10 different status codes and we want to show 10 different static messages, we can't simply use a switch expression inside a single catch block because the HTTP status code of the failed action isn't exposed as a variable in the Data Bank.Because of this, we are forced to write deeply nested try_catch blocks using the on_status_code filter to route each specific error. If we have 10 different error codes, this results in massive, hard-to-maintain YAML nesting.My Question:Is there a cleaner design pattern or workaround to route multiple status codes to different static messages without this deep nesting? How are others handling granular, status-code-based error routing in Compound Actions?

    1
    Kevin Mok
    Forum|Forum|4 days ago
    V
    vinitbKnown Participant

    Configurable Cooldown Window for Webhook-Triggered Plugins/Notifications (Ambient Agents)3. Existing Functionality/Native Skill

    SummaryWe're building ambient agents that send notifications via webhooks from device monitoring tools (Zscaler, Tanium, Aternity). Since these tools re-fire alerts continuously while an issue persists, users get flooded with duplicate notifications for the same issue.We need a configurable Cooldown Feature — either new or an extension of the existing 1-hour de-duplication logic — that suppresses repeat notifications per user/issue over longer windows (7–15+ days), without requiring an external database.The ProblemWebhook storms: Monitoring tools fire repeatedly as long as a condition holds — they have no awareness of whether a user was already notified. De-dup window too short: Moveworks' current de-duplication caps out at 1 hour, but many device issues take days to resolve, causing repeated alerts. Costly workaround: Without native support, we have to build/maintain an external database just to track notification state and gate webhooks before they reach Moveworks — adding latency, complexity, and ongoing maintenance.Proposed SolutionLet devs/admins set a custom cooldown duration on webhook-triggered plugins natively in Moveworks. On each incoming webhook, a Cooldown Engine checks whether the target user already got a notification for that issue within the window:If yes → suppress the notification. If no → send it and reset the cooldown timer.Key RequirementsCustom cooldown windows — admin-configurable per plugin (hours or days, supporting 15+ days). Flexible uniqueness keys — cooldown logic based on combinations like User ID + Issue/Alert ID, or Plugin ID.Business ValueBetter UX: Cuts notification fatigue, reduces risk of users muting/ignoring the bot. Faster time-to-value: Enables proactive IT use cases out-of-the-box, no external middleware needed. Lower overhead: Keeps the entire logic loop native to Moveworks, reducing architecture and API costs. Note: This request seems related to the below 2 requests about notifications management. But I created a separate request because the other 2 are talking about USER preferences, while we are looking for developers to be able to set this cool down duration:End User Notification controls in Copilot | CommunityUser Preference & Notification Management Framework | Community

    4
    V
    Forum|Forum|4 days ago
    C
    christine.turgeonKnown Participant

    Persistent Smart Link in Employee comms1. New

    Links in employee comms currently expire after 14 days. For people going away on vacation and interacting with a comm upon their return, causes complaints!!!!

    0
    C
    Forum|Forum|6 days ago
    L
    lana.parmit

    Enhancements to Employee Comms1. New

    Links to be persistent for 90 days More formatting predictability in terms of not ignoring hard returns and/or soft returns HTML authoring and recognition; ability to import HTML-formatted messages Option for one heading at the beginning of a message Bullets with hanging indents Ability to use different fonts and font sizes Full control over image placement and sizes Ability to target by additional attributes (business, region, and other Workday fields) Option to specify different images by language (e.g., translated screen captures, or translated postcards for high-value internal marketing). User engagement reporting: Add "viewed" to metrics Other ways to measure? ie. Stayed in chat for more than 10 seconds?  

    1
    C
    Forum|Forum|6 days ago
    Penny Zhou
    Penny ZhouCommunity Manager

    Minor ML Update: MLS Response Language Consistency Rule6. Delivered

    Key DatesFrontier: July 15 2026Standard: July 20 2026Basic: July 22 2026Learn more about our model upgrades here.Non-English users sometimes saw responses that were mostly in their language but still contained stray English phrases — status updates ("Filing your ticket…"), confirmations, and live-agent handoff messages that the assistant had been instructed to repeat verbatim. We've updated the AI Assistant so these phrases are now produced in the user's own response language instead of being copied in English, for a more consistent multilingual experience.In offline evaluation on previously-affected conversations, the assistant went from leaking English in every case to correctly localizing ~90% of them, with no regressions. The improvement rolls out in a phased way across model-upgrade tiers. (A small set of fixed workflow status messages follows a separate localization path and isn't covered by this fix.)

    1
    C
    Forum|Forum|6 days ago
    J
    JonathanKnown Participant

    Por que no los dos - multiple default language support1. New

    I know this may be a particular Canadian thing but because we’ve got very specific language requirements it would be nice to be able to set a default language for a region of users based on say their location data.Because I’ve outed myself as Canadian let’s say everyone whose home office in Quebec could have their default language set to French and the rest of the country set to English.

    3
    C
    Forum|Forum|9 days ago
    D
    dhorvathCommunity Manager

    Catalog Interpreter2. On Roadmap

    Convert ServiceNow catalog items into conversational AI experiences — no changes to your existing catalogs required. What problem does this solve? Service catalogs contain complex business logic — conditional fields, custom validations, multi-step workflows — that makes them nearly impossible to automate conversationally. Less than 10% of high-volume catalogs work through any existing AI solution today. How does it work? Catalog Interpreter reads your catalog item's full schema and business logic, then creates a conversational AI experience that handles it end-to-end. Employees describe what they need in natural language; the AI collects inputs while respecting all underlying rules and validations.

    2
    afleury
    Forum|Forum|10 days ago
    afleury
    afleuryInspiring

    Dedicated Notifications Tab for Moveworks in Microsoft Teams (and Slack)1. New

    The ProblemToday, the Moveworks bot in Microsoft Teams (and Slack) only has a Chat and Shared tab. All notifications — ticket updates, approval requests, pending actions, comms — land directly in the Chat conversation alongside regular bot interactions.This creates a real problem:Notifications get buried. As soon as a user sends a new message to the bot, older notifications scroll out of view. There's no way to see a consolidated list of pending items without scrolling back through the chat history. Busy managers lose track of approvals. Managers with high approval volumes can't efficiently triage what needs attention. They're not going to have a back-and-forth conversation with a chatbot to filter down pending requests — they'll just open ServiceNow directly, which defeats the purpose of the bot. The problem gets worse at scale. The more notification types you enable (ticket concierge, approval reminders, comms, visitor alerts), the noisier the chat becomes, and the more likely critical notifications are missed.As one of our store managers put it when testing Bolt visitor notifications:" it kind of got lost between two others, so not necessarily obvious." What We WantWe'd love Moveworks to adopt the same tab structure that other Teams apps (like Workday) already use:Tab Purpose App Dedicated notification feed — ticket updates, approval requests, pending actions, comms. Structured, scannable, persistent. Chat Conversational interaction with the bot — questions, lookups, form submissions. Shared Shared files and links (already exists). The Workday Teams app is a great reference. Its "App" tab shows Quick Actions, tasks, and calendar events — completely separate from the "Chat" tab where users interact with the Workday bot. Notifications like time-off approvals appear in Chat, but the persistent task list lives in App. This separation keeps things clean and actionable.Why This MattersYou've already solved this on the web. The Moveworks Web Assistant (/assistant) has a dedicated Notifications panel — separate from the chat. It works well. But it pulls users away from their primary collaboration platform (Teams/Slack) and requires additional SSO app assignment (e.g. Okta), which is more admin overhead.  Microsoft Teams supports this pattern natively. The Teams platform provides Activity Feed Notification APIs and supports custom tabs within bot apps. The technical capability exists.  Meet users where they are. Moveworks' own mission is to "meet employees where they are." For most enterprises, that's Teams or Slack — not a separate web portal. The notification experience should live there too.  Approval velocity. Managers need a glanceable, structured view of what's pending — not a chat transcript to scroll through. A dedicated tab would significantly reduce approval turnaround time and friction.What This Could Look LikeNotification feed in the "App" tab — filterable by type (approvals, ticket updates, comms, reminders). Badge count on the App tab showing unread/pending notifications. Actionable cards — approve/reject, acknowledge, or deep-link to ServiceNow directly from the notification. Persistent state — notifications remain visible and accessible until actioned, not buried by new chat messages.Who This ImpactsThis isn't a niche request. Every Moveworks customer on Teams or Slack that uses ticket notifications, approval workflows, or employee comms is affected. The challenge scales with org size — the more users and notification types you enable, the worse the chat-noise problem becomes.TL;DRCurrent State Desired State All notifications land in the Chat tab Notifications in a dedicated App tab Notifications scroll away with new messages Persistent, scannable notification feed Managers must scroll or ask the bot to filter Structured view with filters and badge counts Web Assistant has this — Teams/Slack doesn't Parity across all surfaces Web Assistant requires separate SSO/Okta app Keep the experience in Teams/Slack If you're dealing with this same challenge — please upvote and comment. The more visibility this gets, the more likely it makes it onto the roadmap. 🙏Here’s what it could look like 

    2
    jmcginley
    Forum|Forum|10 days ago
    M
    Maciek LekowskiNew Participant

    Interaction domain available in Analyrics UI1. New

    Currently “interaction domain” is not available to be reported in standard Analytics UI - it is available only through data API (contrary to “conversation domain”). It would be great to bring “interaction domain” to Analytics UI so that it is readily available there and can help identify proper domain also for individual interactions.

    0
    M
    Forum|Forum|10 days ago
    M
    Maciek LekowskiNew Participant

    Forms: add Salesforce as supported integrations1. New

    It would be great if similar capability explained in this article Forms | Moveworks is also available with Salesforce integration for customers that are using Salesforce as their CRM

    0
    M
    Forum|Forum|10 days ago
    S
    ShrutiNew Participant

    Enable Usage Analytics for Specific KB Sections and SharePoint Sites1. New

    Currently, there is no visibility into how specific KB articles, KB sections, or files under a particular SharePoint site are being used within Moveworks. Content owners cannot determine which sections or documents are most frequently surfaced in responses or how a specific SharePoint site contributes to our agents self‑service.This enhancement would provide usage analytics scoped to a selected KB article/section or SharePoint site, including how often content is referenced by MIA and which sections or files are most impactful. These insights would help content owners optimize knowledge quality, and measure adoption and ROI integrated knowledge sources.

    1
    C
    Forum|Forum|11 days ago
    A
    andrewwhitleyInspiring

    Allow pagination in slot resolvers4. Future Consideration

    Currently, slot resolvers in conversational processes can be dynamic or static. With dynamic, we can call a action. However if I need to paginate on the action to get more results as possible values, that is not possible. Please enable pagination in some way for slot resolvers as I currently have to have some slots be static due to this limitation.

    6
    Kevin Mok
    Forum|Forum|11 days ago
    K
    KaviKnown Participant

    Enable Conversation ID Mapping for Agent Studio Use Cases4. Future Consideration

    I propose introducing a mechanism to pass the conversation ID to use cases created via Agent Studio. Since most ticket operations in our organization—such as ticket creation and notifications—are planned to be customized using Agent Studio, having the conversation ID available within these use cases would allow accurate mapping between bot interactions and downstream ticket actions. This would significantly improve tracking, reporting, and deflection analytics.

    4
    K
    Forum|Forum|11 days ago
    C
    cfinelliParticipating Frequently

    Image Support In Bot Conversations1. New

    We recently setup a channel resolver for IT Support and it’s working pretty well. However, the ability to have a user attach an image of their error message and have Moveworks understand what it means in context to the issue + to take into consideration in its responses would be fantastic.  Is there any plan to add support for images/OCR for bot conversations via Channel Resolver? At the moment we will have to tell users that their requests will only be understood if everything is entered via plain Text and screenshots aren’t supported.  In fact, if the slack message contains an image, Moveworks won’t even respond in thread + will completely ignore the message. 

    1
    J
    Forum|Forum|12 days ago
    K
    KaviKnown Participant

    "New Chat" option for end user6. Delivered

    Hi Team,I would like to propose a 'New Chat' option similar to Microsoft Copilot, where end users have the ability to start a fresh conversation with the bot. We've observed that when users repeatedly ask similar questions, the previous context remains in the background, and they don't have an option to start fresh. As a result, we often have to raise a support case (00026926) to clear the history for the user, which then allows them to receive accurate answers from the bot.This would improve User Experience: Users can start a new conversation without the influence of previous interactions, leading to more accurate and relevant responses.

    6
    V
    Forum|Forum|12 days ago
    nicole.hulst
    nicole.hulstKnown Participant

    End User Notification controls in Copilot4. Future Consideration

    I saw in the Copilot feature overview that the unsubscribe etc are no longer possible in Copilot. For us this is a really important feature as it helps retain the users that have a lot of tickets open because they act as kind of a superuser for other people and open tickets for them. They get overwhelmed with notifications and like to mute some of them but would without that feature mute the bot entirely. Which would lower our active users significantly.Please bring that useful feature back, I don’t understand why it was not considered. 

    16
    V
    Forum|Forum|12 days 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