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

    1344 Ideas

    Back to top of the list
    ShrutiNew Participant

    Expose FAQ Resource Analytics Through Plugin Resources Data API1. New

    The Plugin Resources Data API (Resource Type: Knowledge) currently does not provide visibility into FAQ content usage or identify which FAQ sheets are being accessed.Adding FAQ-specific resource details to the API would enable customers to:Track FAQ sheet usage and adoption across the organization. Identify the most frequently accessed FAQ content.

    0
    1 month ago
    vinitbKnown Participant

    Configurable Cooldown Window for Webhook-Triggered Plugins/Notifications (Ambient Agents)1. New

    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

    8
    Kevin Mok
    1 month ago
    JonathanKnown Participant

    Dynamic Translations in Communictions1. New

    We’ve run into this issue and wanted to make a suggestion for this.We know that the app can take English text and translate it out to other languages based on a user’s individual settings.However, the system isn’t capable of understanding that a text would be in another language, like French, and have it be translated into the default language for users.Example:I have a text in French that I’d like to send as a communication. I prepare it and Austin, who has his default language in English, will get the communication in English. 

    4
    2 months ago
    jgilmourNew Participant

    Capture feedback from Feedback button in employee communications campaign within campaign report1. New

    We recently did a company wide survey to capture feedback on our moveworks deployment and used the ‘Feedback button’ as one of the configuration items, and found that its not captured in the campaign detail reports (only user interaction). Product enhancement should be either:Add feedback captured from the campaign to the campaign report Update Feedback button informational modal to state accurate location to view feedback submissions from the campaign.  

    0
    2 months ago
    Ajay Merchia
    Ajay MerchiaCommunity Manager

    Actions: Python2. On Roadmap

    Key DatesTBDWhat is it Our current set of script actions only allows for APIthon scripts. These are safe for LLMs to generate, but they lack the same power as Python (functions, libraries, memory, etc). This new capability lets developers build with the full power of Python, including custom libraries. FeaturesNative Python Support - Write Python code exactly as you would anywhere else, without platform-specific restrictions or modifications. Expanded Library Access - Use a wider range of Python libraries and functions to build more powerful integrations. Familiar Development - Leverage your existing Python knowledge and standard Python tools without learning custom syntax. Simplified Debugging - Test your scripts locally using standard Python debugging tools before deploying them.

    8
    eberteo
    2 months ago
    JacekU
    JacekUNew Participant

    Create RBAC for Chat Playback or Move it out of Setup1. New

    The Chat Playback option is very helpful when analysing an interaction in Moveworks. This functionality helps to analyse tehcnical issues as well as resources used and see the general conversation flow in a single easy to view manner.Hower the Chat Playback is currently in the Setup section of Moveworks. This means that if anybody needs access to it they also have to receive very high level permissions, this creates a risk.We see 2 possible solutions here:Create RBAC permissions for the Chat Playback so only permissions there could be granted instaed of the entire Moveworks Setup. Move the Chat Playback function out of Moveworks Setup.This improvement could have a large positive impact as it would allow for more people to support interaction review and trovuleshooting, without having too high level access.

    2
    2 months ago
    KellyMVCommunity Manager

    Productivity Assistant Builder2. On Roadmap

    How are we improving the product?Work does not stop at finding information, completing a standard workflow, or filing a ticket. Many of the most valuable tasks employees perform are contextual and nuanced: preparing for an important customer meeting, analyzing candidates, writing a performance review, researching a market, coordinating a complex project, or producing an executive-ready deliverable.Productivity Assistants are purpose-built AI assistants designed to excel at work like this. An assistant can be tailored to a particular task, role, team, or business domain—with focused knowledge, tools, instructions, and access—so it understands the context of the work and helps drive it toward a useful outcome.Employees and administrators will be able to create Productivity Assistants without code, start from approved templates, or adopt prebuilt assistants for common use cases. Examples may include calendar management, recruiting coordination, customer preparation, RFP responses, onboarding, performance reviews, research, and team operations.What can Productivity Assistants do?Depending on how they are configured, Productivity Assistants can:Long-Running Tasks: Complete complex work that requires multiple stages of research, analysis, planning, and execution—such as deep research, account preparation, or creating a comprehensive report.Contextual Behavior: Focus on selected enterprise or external sources, follow task-specific instructions, and apply the right context for a particular role, team, domain, or workflow.Skills: Use reusable skill packages—including SKILL.md instructions and supporting resources—to consistently perform specialized tasks according to an organization’s preferred methods and standards.Enterprise Knowledge and Web Research: Search, compare, and synthesize information across selected company sources and current public information, with citations back to the supporting material.Tools and Actions: Use approved plugins, integrations, and enterprise tools to retrieve information, update records, initiate workflows, and take authorized action across connected systems.Artifact Generation: Turn completed work into polished, shareable outputs—including interactive experiences, reports, presentations, documents, PDFs, tables, charts, dashboards, and prototypes.Conversational Refinement: Let employees review an answer or artifact, request changes, explore details, and continue iterating without restarting the work in another application.No-Code Creation: Create an assistant from scratch or customize a template by selecting its purpose, instructions, knowledge, tools, skills, conversation starters, and intended audience—without writing code.Prebuilt Assistants and Templates: Start quickly with vetted assistants and reusable templates designed for common roles and use cases, then tailor them to the organization’s needs.Governance and Sharing: Share assistants with the appropriate individuals, teams, roles, or groups while giving administrators control over who can create, configure, publish, and broadly distribute them.Permissions-Aware Operation: Respect existing enterprise permissions so employees only access information and perform actions they are already authorized to use.Cross-Channel Access: Use Productivity Assistants through EmployeeWorks web and supported enterprise messaging experiences, allowing employees to access focused assistance where they work.Availability and rolloutCapabilities may be introduced in phases. The assistants, knowledge sources, tools, skills, artifact formats, channels, sharing options, and administrative controls available during controlled availability may differ from the complete planned experience.Licensing and documentationLicensing, packaging, configuration guidance, and getting-started documentation will be shared before broader availability.

    0
    2 months 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. 

    17
    2 months 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 

    6
    2 months ago
    ShreyaNew Participant

    Broken Link Validation and Link Health Monitoring1. New

    Current behaviorMoveworks retrieves links from the knowledge source. Links are surfaced to users without validating whether they are still accessible.Proposed behavior Before displaying a URL to a user:Verify the URL is reachable. Detect redirects. Identify expired/obsolete pages. Suppress or flag invalid links. Suggest an alternative source when available.Expected Benefits:Increase user trust in AI responses Reduce failed user journeys Improve knowledge quality Enable proactive content maintenance Reduce support volume related to stale links

    0
    2 months ago
    2613196
    2613196

    HTTP Action - Response Schema is unintentionally overwritten by Test/Publish, with inconsistent behavior1. New

    Context:In the HTTP Action config,  the Response Schema starts as an open/accept-all schema ({}). Running Test replaces this schema with whatever payload shape came back from that specific test call. If the user then hits Publish, that test-derived schema overwrites the previous (intentional) schema — with no confirmation or way to prevent it.Problems:No way to save/apply a schema independently of Publish There's currently no dedicated "Save Schema" or "Apply Schema" action. The only way a schema gets set is as a side effect of running Test, which is not obvious and easy to trigger by accident. Publish silently overwrites the schema after a Test run If a user runs Test (even just to check something) and then hits Publish, the schema from that one test call replaces whatever schema was previously defined — even if that test payload wasn't meant to become the new schema. Since different test calls can return slightly different payload shapes, this makes it very easy to unintentionally wipe out a correct, working schema with an incomplete or one-off version. Inconsistent schema behavior across repeated tests Even with a schema already defined in the Response Schema section, results are inconsistent. Running the same test multiple times — with zero changes to the HTTP action or any republishing in between — sometimes returns the expected payload, and sometimes returns a null/empty response instead when ran from a conversational process for example. Requested fix:Decouple schema updates from both Test and Publish — schema should only change when a user explicitly chooses to save/apply it or possibly links a data type to it. Add a clear "Save Schema" or "Apply Schema" action so users control when the schema is updated, rather than it happening automatically as a side effect of testing. Investigate the inconsistent null-response behavior on repeated test calls with no config changes — this points to something unstable outside of user action, not just a UI/schema issue.

    0
    2613196
    2 months ago
    eberteo
    eberteoKnown Participant

    ServiceNow Nexus conference in Santa Clara1. New

    I'll be attending Nexus conference at ServiceNow HQ Santa Clara from Oct 20 - Oct 22!Where: Building H, 2250 Lawson Lane, Santa Clara, CA @ 9AM - 5PM daily.Let's talk about ServiceNow Architecture and AgenticAI. I can help you with the below topics so bring your eagerness! 1:1#ServiceNow #ITSM #ITOM #AgenticAI #Sailpoint #Moveworks #IGA #IAM #CMDB #CSDM #StudioAI #ServiceNowStudio #ServiceOperations #Cisco #Webex #Neuralink #NeuralinkHireMe

    0
    eberteo
    2 months ago
    davrey04Participating Frequently

    Resolving blank feedback1. New

    Currently most knowledge article feedback is a simple thumbs up or thumbs down, with no comments indicating what that user found helpful or unhelpful. What would help is, since Moveworks can access ServiceNow’s tables, having the bot check a feedback item.If the item has a comment, it sends it directly to the ServiceNow Feedback table.If the item does Not have a comment, the bot emails the user and asks them to comment on what they liked or disliked about the article. After sending that note, the bot forwards the feedback to ServiceNow, adding a “Comment requested” like to it.This would help companies that get a lot of feedback improve their knowledge articles. Thank-you.

    0
    2 months ago
    Arnaud CLAVEAUNew Participant

    Teams bot with the same look and functionalities as Webchat assistant1. New

    Hello,Currently the Teams bot, does not have the same look and functionalities as the chatbot assistant.Should be good to have the same look / behavior between all Moveworks chats bots (notification tab, chat tab...) and especially in Teams to have confusion between notification and chats / exchange with the bot.Or just propose the chatbot assistant page to be compatible to be embedded in TeamsRegards,Arnaud 

    0
    2 months ago
    Arnaud CLAVEAUNew Participant

    SharePoint integration in a site instead of in a page1. New

    Hello currently the Moveworks for Web web part needs to be manually added to each individual SharePoint page. We'd like the assistant to appear automatically on every page across our site(s), without having to add the web part page by page. In SharePoint, the standard way to achieve this is via an SPFx Application Customizer (deployed tenant-wide through the Tenant Wide Extensions list), rather than a page-level Web Part - it injects into a page placeholder (e.g. Bottom) automatically on every modern page, with no per-page setup needed.It is should be good to have Moveworks offering an Application Customizer variant of the SharePoint integration, instead of or in addition to the current Web Part.Regards,Arnaud

    0
    2 months ago
    mandarmarkandeyaNew Participant

    Feature Request: Manage Moveworks Support Tickets Directly in the Bot1. New

    Hi everyone,We currently use the Moveworks bot to manage our organization's internal ServiceNow tickets, and it's been a great experience for our team to view statuses and update tickets directly in chat.Since Moveworks recently migrated its customer support ticketing to ServiceNow, I wanted to see if there are any plans to allow us to manage our Moveworks Support Tickets directly from our own bot?Ideally, we would love the ability to:Check the status of our open Moveworks support tickets. Add comments or updates to the tickets directly in the chat interface. Receive proactive notifications when a Moveworks support agent updates our ticket.Having a single pane of glass for both our internal IT tickets and our Moveworks support tickets would streamline our workflow tremendously. Has anyone else built a custom Agent Studio plugin for this, or is this something on the product roadmap?Thanks!

    1
    hundleymf
    2 months ago
    afleury
    afleuryInspiring

    Saved prompts and prompt gallery for Moveworks AI Assistant4. Future Consideration

    One of the challenges as a Moveworks Admin and Dev is sharing with the users what prompts they have access to. There is no easy way to export all of them (even via the Support route) and keeping prompts up to date in a document or KB article requires manual effort.Microsoft has taken steps to resolve this issue for users with their Prompt Gallery. As of July, Microsoft will be building the Prompt gallery into the Copilot chat for even easier access.Changes to the Copilot Prompt Gallery app - Microsoft SupportFor best user experience, I would love to see Moveworks implement a solution like this in the AI Assistant as well. https://copilot.cloud.microsoft/en-US/prompts/all?ocid=CopilotLab_M365Chatofficeweb

    6
    afleury
    2 months ago
    nicholas.marr
    nicholas.marrNew Participant

    Chatbot iFrame Open Functionality from Hosting Website1. New

    Allow the hosting website presenting the chatbot i-frame to dynamically open the i-frame chat window. In our ServiceNow instance, we have our ColleagueZone page that presents outage information to the user. There are buttons on each individual outage that trigger a Moveworks plugin to provide A.I. insights about the outage to the user’s chat window in Teams. We’d also like it to pop open the i-frame chat window on the ColleagueZone page. We see in the Network console the following event that might drive this behavior, we just want to be able to trigger it from the hosting webpage if possible: {events: [{url: "https://webchat-kprod.moveworks.io/chat", startTime: "2026-08-14T15:37:40.208Z",…}]} events: [{url: "https://webchat-kprod.moveworks.io/chat", startTime: "2026-08-14T15:37:40.208Z",…}] 0: {url: "https://webchat-kprod.moveworks.io/chat", startTime: "2026-08-14T15:37:40.208Z",…} action: {actionType: "OPEN", name: "host_page"} actionType: "OPEN" name: "host_page" namespace: "movewebchat" source: "USER" startTime: "2026-08-14T15:37:40.208Z" url: "https://webchat-kprod.moveworks.io/chat" webMetaInfo: {,…} webappNamespaces: "MOVEWEBCHAT"

    0
    nicholas.marr
    2 months ago
    MikeINew Participant

    Include option to remove "thinking" process4. Future Consideration

    The visual created by the “thinking” process occurring and then being replaced by the answer/response can be jarring or distracting. I’d like to have the option to chose a single line of text such as “Working on your request. You’ll see your response here soon...” or simply responding with an emoji to show that the bot has your request. 

    17
    DIANA.TWC
    2 months ago
    JacekU
    JacekUNew Participant

    Ability to create NPS and multi question Surveys within Moveworks1. New

    It would be great to improve the Employee Comms Survey functionality to be more NPS inclusive.Currently within Employee communications a survey campaign could be created. However the response is limited to 5 buttons mirroring the CSAT methodology, however many organizations utilize the NPS methodology during surveys. It would be good if there would be the option to have more buttons. It would also be good to have the option of adding multiple questions to a campaign rather than just one. Finally it would be great if after a ticket is resolved, an NPS survey could be sent from Moveworks directly to the user utilizng the above mentioned functionalities.

    3
    2 months ago
    afleury
    afleuryInspiring

    Allow Policy Enforcement and Validation for Distribution List Provisioning1. New

    SummaryMany organisations use self-service provisioning to create distribution lists, groups, and collaboration resources. While access controls determine who can request these resources, there is often no way to enforce organisational standards during the provisioning process itself.ProblemToday, administrators can control who is allowed to create resources, but they cannot define and enforce policies that govern what is created.Common requirements include:Naming convention enforcement Approved domain validation Pattern or format validation Resource classification requirements Automatic standardisation of user input Custom business rules based on organisational needsWithout policy enforcement, organisations must rely on user training, manual reviews, or post-creation remediation to maintain standards.Proposed EnhancementIntroduce a policy validation framework that is evaluated as part of the provisioning workflow.Administrators should be able to:Validate user input before resource creation Define required naming standards Restrict values to approved formats or domains Apply automatic transformations where appropriate Display clear validation messages when requirements are not met Configure different policies for different resource typesExample Use CasesEnforcing naming standards for distribution lists Restricting email domains to approved corporate domains Requiring specific prefixes or suffixes Enforcing department or region identifiers Standardising display names and aliases Validating group ownership requirements before creationBenefitsImproved governance Consistent resource naming and structure Reduced administrative overhead Better compliance with organisational standards Fewer provisioning errors Better end-user experience through immediate feedbackWhy This MattersSelf-service provisioning is most effective when organisations can trust that resources created through automation comply with their internal standards. Access control answers who can create a resource, while policy validation answers whether the resource itself meets organisational requirements. Both capabilities are needed for scalable governance.Voting ask: If your organisation uses self-service provisioning and has naming, compliance, governance, or standardisation requirements, please upvote this idea to help prioritise policy enforcement capabilities within provisioning workflows. PS: I’ve already tried Moveworks/ServiceNow Support and Engineering teams advised to raise a Product idea.

    0
    afleury
    2 months ago
    ramapr1New Participant

    Improve translation and label clarity for request submission and help options1. New

    There are two areas causing confusion for employees interacting with Moveworks bot in Japanese language.First, the button label currently used across forms - “Complete this request”, is being interpreted too literally. In Japanese, the wording gives the impression that the action will finalize or close a process, rather than simply submit information for a question or request. Users feel this creates the wrong expectation and may discourage users from submitting their HR case request. A more neutral term, such as “Make” or another phrase that clearly indicates submission or creation, would better reflect the intended action.Second, the Get Help link is causing confusion because the Japanese translation appears as Support Request. Users see Get Help referenced in Moveworks bot, but they cannot find that exact option because the translated label is different. This becomes even more confusing when Moveworks bot explains that support request is not the same as Get Help. As a result, users are left unsure which option they should choose.We understand that Get Help is part of Moveworks out of box functionality. We would like to ask if there is any appetite to review or update this terminology for better clarity.In addition, request to make the wording "Complete this request" customizable.Requested outcome: We would appreciate Moveworks reviewing these terms from a localization and usability perspective so the labels are easier to understand for Japanese users and reduce confusion during request submission and help navigation.

    0
    2 months ago
    priya.kornalius
    priya.kornaliusKnown Participant

    Proactive Monitoring and Health Dashboard for MW Chatbot Skills4. Future Consideration

    We recently encountered an issue where MW chatbot failed to return relevant articles for a specific query. After reaching out to the support team, I learned that the bot didn’t trigger the knowledge skill plugin, which is responsible for searching related articles. Support team made the necessary adjustments, and the fix worked.However, this raised a concern: how can we proactively track and measure the health of the knowledge skill? We can’t always wait for users to report issues, as this impacts engagement and overall user experience.Wouldn’t it be beneficial if MW offered a health dashboard for all configured skills, allowing admins to monitor performance and make informed decisions? Additionally, having the option to subscribe to status notifications for specific skills would help us catch and address issues in real-time, ensuring smoother operations and exception handling.

    3
    2 months ago
    Penny Zhou
    Penny ZhouCommunity Manager

    Minor ML Update: Button-Click Response Language Fix6. Delivered

    Key DatesFrontier: August 17 2026Standard: August 19 2026Basic: August 24 2026Learn more about our model upgrades here.Previously, if you had your assistant set to a language other than English, clicking a button — like responding to a notification, approving a request, confirming an action, or following up on a ticket — could cause the assistant's next reply to unexpectedly switch to English, even mid-conversation. We've fixed this so the assistant now stays in your preferred language throughout these interactions. This applies across all button-based actions, for anyone using a non-English language, whether it was explicitly chosen or set as their default. Typed messages are unaffected — the assistant continues to respond in whatever language you're actively typing in.

    0
    Penny Zhou
    2 months ago
    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!

    18
    2 months ago
    Show more activity

    Filter by product

    • All products
    • Analytics
    • AI Assistant
    • Tool 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
    • Channels
    • Assistant Platform
    Terms & ConditionsAccessibility statement