Build better products with our product team.
We'd like the ability to filter Unily content ingestion by page/content type.Currently, all content types are ingested without the option to exclude specific categories. This creates a practical problem: content types like news articles have a short shelf life and, once stale, can cause the assistant to return inaccurate or outdated responses. The only current option is to exclude entire site sections, which is too blunt when the issue is type-specific.A page type filter — ideally configurable per connector instance in the admin UI — would allow teams to include only the content types that are appropriate for AI assistant retrieval (e.g. policies, how-to guides, FAQs) and exclude those that aren't (e.g. news, announcements, event pages).This would improve response accuracy and give admins more precise control over what the assistant surfaces to users.
Major upgrades to Data Crawling Viewer and Control Center with crawled records view, failed API call insights, record activity logs, improved indexing terminology and Redesigned UI/UX.
Key DatesFrontier: May 18 2026Standard: May 20 2026Basic: May 26 2026Learn more about our model upgrades here.Tool Response Rendering ImprovementsWe've made some updates to how the Moveworks AI Assistant presents tool responses!The Assistant now presents clean and concise results. Previously, some responses were excessively verbose or surfaced extra, unnecessary information, rather than synthesizing it into a helpful answer. Improvements include four changes that will make responses clearer:Relevance by default: When sharing information from a tool response, the Assistant surfaces only details relevant to your request. Raw data fields, internal identifiers, and technical values you can't act on are omitted. Synthesized answers: When multiple tools contribute to a response, results are combined into a single coherent answer. Plain-language errors: When a tool encounters an error, the Assistant describes the outcome in plain language. Clean output by default: The Assistant won't include verbose technical data in responses unless it's directly useful to you.To verify the improvementsAfter the update is live in your environment: Ask a question that normally triggers a verbose tool response. The Assistant should return a concise, relevant answer.
Automatically sends welcome emails to superadmins upon instance creation and allows admins to onboard additional users without requiring user identity setup. Reduces time-to-first-login and eliminates a key friction point in initial instance configuration.
It would be more efficient and impactful for there to be functionality to enable us to create our own company campaign objectives (templates) and be able to save them and access them via drop down list for “create campaign” in employee communications. Ideally the feature would enable the following:Admins can create and save templates for campaigns. Templates can be copies and edited. Templates can be individually named. Templates will show up in the drop down list for “Create Campaign” Templates can be deleted from the drop down list as needed with out impacting past communications utilizing that template. Audit history of the template for creation, edits, user name and timestamp. Nice to have: Visually identifiers like icons and emojis to distinguish the campaign.
As someone who is not using a lot of the OOB functionality (ticketing, approvals, access, etc) and instead building it in Agent Studio, the OOB functionality is still shown to the users which creates a poor user experience. Can we have more control to turn this functionality off or control how it works?Examples:I initiate a generic approval flow to a user to approve something. Once they approve or deny, they have buttons to see next approvals/all approvals. They would expect this to actually show all approvals in all systems which is not the case. Instead it is just what moveworks is aware of which may be stale as records are kept for 30 days. The best workaround I was provided by support was to have the buttons instead respond with a message saying what to type to initiate the plugin for approvals. I have a plugin to comment on a ticket. When I attempt to use it, instead the default functionality to comment is initiated and says I don’t have access as it is disabled. For “Get more help” on a error, I can have it do default ticket creation or a link. I would like it to be able to call a plugin instead. For a link, the button instead opens up a moveworks site which gives the link.
Build more fine‑grained RBAC for Level 1 Triage Service Desk teams to support least‑privilege access.Current roles are too coarse and require over‑provisioning (Admin) for basic triage tasks, creating governance, audit, and operational risk.
Simplified experience to set up user identity, offering attribute validation, profile review screen and much more
Currently, developers don’t have access to which interaction surface a request came from when Moveworks executes an action and sends the payload to the API. It would be great if we could customize the payload of an action to be able to send to the API where the interaction came from, example: ‘zoom’, ‘slack’, ‘movewebchat’, etc. Our use case is that we want to synchronize sending images across all interaction surfaces for a particular agent so if we had access to interaction surface, we could tell if it came to zoom send to the image to the user’s Moveworks chat in zoom, if it came from slack send the image to the user’s Moveworks chat in slack, etc.
Simplify and reorganize the left navigation in MW Setup for Enterprise Search to make key setup tasks easier to find and reduce configuration friction.
Alerts (email or notification to admin) - When customer pressed unhelpful Navi feedback
We are not able to see the start of bot interactions that were initiated by a proactive notification (i.e. password expiry, approval notifications, etc.) This makes it difficult to determine the context of an interaction, especially if one gets flagged as unhelpful.Is there a way to include those proactive notifications in the interaction logs?To reduce ignored notification logs, the initial notification log could just last the lifespan of the links to filter out ignored notifications.
Overview Currently, the platform’s analytics focus on user-initiated interactions with our Moveworks bot. However, as customer bots evolve to be more proactive—sending notifications and updates without direct user prompts—we lack visibility into the reach and effectiveness of these communications. To better understand the impact of bot-initiated messages, we propose the addition of analytics for proactive communications. This would provide insights into what types of messages are being sent, how frequently, and how users are engaging with them. Proposal: Implement Analytics for Bot-Initiated Messaging We request a new analytics capability to track and analyze any communication that originates from the bot, including but not limited to:• System-generated notifications (e.g., password reset alerts)• Employee communications tool messages• Creator Studio-initiated messages• Concierge or plugin-based notifications (e.g., ITSM status updates, comments)• External integration notifications (e.g., ITSM approval workflows) Key Metrics & Capabilities Requested:1. Message Volume Tracking – How many bot-initiated messages are being sent over time?2. Message Source Breakdown – Categorization by system, integration, or trigger type.3. Recipient Insights – Who is receiving these messages? Are certain groups more (or less) engaged than others?4. Engagement Metrics – How do users interact with bot-initiated messages? (e.g., click rates, dismissals, response rates)5. Impact Measurement – Correlation between notifications and user actions (e.g., did a status change notification lead to a follow-up inquiry?). Benefits:• Visibility – Understand the scale and scope of bot-initiated communications.• Optimization – Identify which messages are effective and refine strategies accordingly.• User Experience Improvement – Reduce notification fatigue by analyzing engagement trends.• Data-Driven Decision Making – Leverage insights to enhance proactive support efforts. By implementing analytics for proactive bot messaging, we can ensure that these communications are both meaningful and effective, ultimately improving the best possible user experience and the value of the Moveworks bot.
Raising this on behalf of clients who need to be notified whenever a user blocks a bot. We need a feature that detects that the bot is being blocked and either alerts an administrator or generates a report that can power an automated email to get those blocking users back on the bot.This feature should ensure that it checks the roster to stay up to date with current employees and do a check so that users that unblock the bot on their own get removed from the report.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK