Our API Mocker now support custom TTL & protected routes so you can build more long-lasting APIs for your test plugins. You can also “protect” your APIs if you’re logged in, and prevent other users from overwriting the endpoints you create!
We now support both Gemini 3 Pro and Gemini 3 Flash in Agent Architect. No action needed from customers.
A data bank where you can see all of the data available for mapping between steps in your plugins. Read more about this feature here.
Invoke an Ambient Agent on a scheduled cadence (daily, weekly, or custom). Read more about this feature here.
This is available in US & EU on OpenAI Direct + US on Azure OpenAI. Azure is still working to get GPT-5.2 up in the other data centres. Once available, we’ll expand support! Nothing needs to be done to turn it on, just slip the right model ID in your LLM actions.
Read more about LLM Actions here.
Enable developers and admins to connect to business systems that require user permission to act on their behalf. You can read more about how to configure User Consent Auth here.
OpenAI released GPT-5.1 on November 13. We’re excited to share we’ve conducted a full set of evaluations to assess its performance relative to GPT-5 and GPT-4.1.The GPT-5 series of large language models stands out for delivering state-of-the-art reasoning. Better reasoning (i.e. thinking and decision making) represents a major leap for agentic tasks, offering improved instruction following, more effective plugin (tool) use.
We’ve upgraded the AI Assistant’s reasoner to GPT-5.1. No setup work or downtime is required to see this change, as this has already been made in your AI Assistant.
See our updated Community post here.
This release combines enhanced RBAC controls with flexible, customizable views—giving super admins more control over sensitive data and enabling teams to share only the insights that matter to the right stakeholders. This means:
Read our community post around this feature here.
Introduces a mechanism to define blocking actions within conversational processes, ensuring critical steps complete before proceeding — improving reliability and control in multi-step flows.
Developers can write compound actions (required for Ambient AI agents) without learning our pro-code YAML-based syntax. Learn more about compound actions and how to trigger the Low-Code Editor view here.
Detailed debug logs for your slot resolvers.
Agent Architect can now render mermaid diagrams.
Users can now toggle YAML or JSON for Bender generation in the Agent Architect.
Connect Moveworks to other systems following a JSON Web Key Sets authentication approach. Read more about it here.
All customers got access to Agent Studio 2.0 on September 24th. No action is required from customers. Read the new Agent Studio overview here.
You can now embed Purple Chat conversation mocks in external websites, documentation, presentations, or anywhere you need to showcase AI assistant interactions!
/purple-chat with /embed/purple-chat in the URLTo give customers more immediate signals regarding user feedback, we are upgrading how we track feedback received in your Assistant.
Customers can expect a substantial increase in their captured feedback volume.
QuickGPT & Brief Me are now configurable via self-service. Read more about configuring Productivity Boost here.
All customers now have access to Agent Studio 2.0.
Triage 2.0 now supports US, EU, CA, AU, and GovCloud regions. If you are an existing Triage customer, Triage 2.0 will be part of your upgrade as part of the next model retrain.
The AI Assistant will now provide fewer, more concise progress updates for backend tasks like ticket creation, password resets, and custom plugin actions. This change reduces conversational clutter and keeps the focus on the task’s outcome, ensuring a cleaner and more efficient user experience.
This feature is now available to all Slack and Microsoft Teams customers.
Before / After Example:
For more info, read our AI Assistant UX Upgrades post in Moveworks Community.
API Playground is a new tool in Moveworks Setup designed to help users test and validate API requests. Think of it as a sandbox environment where you can interact directly with the APIs of external systems without affecting live data, all from within the Moveworks platform. It’s built with a curated library of vetted API endpoints called API Collections, which provides a ready-to-use set of common API calls for major integrations. This is a crucial tool for anyone building or troubleshooting custom plugins.
Key Features and Benefits:
The API Playground offers several key advantages for both customers and partners:
Accessing the API Playground:
To access this new feature,
The feature is now available to all customers on both Slack and Microsoft Teams. It represents a significant step forward in giving developers and administrators the tools they need to build and maintain robust integrations.
For more info, read our MW Setup: API Playground doc on Help Site, and also go through our API Playground announcement in Moveworks community.
We’ve streamlined the process for managing Slack tokens, making your setup and maintenance easier and more reliable.
Previously, you had to update Slack tokens in two separate places: the Connectors screen and the Chatbot configs. We have now consolidated token management to a single location: the Slack Connector screen.
Benefits
This update offers a number of key benefits:
This change is automatic and requires no action on your part. All existing Slack integrations will continue to function normally. Future token updates can be managed exclusively through the Slack Connector screen.
For more info, read the MW Setup: Consolidated Slack Token Setup post in Moveworks Community.
We’re excited to announce the launch of our new Moveworks Setup Homepage. This feature provides a centralized overview of all your AI Assistant capabilities, giving you a single source of truth for your entire configuration.
The homepage reflects the current state of your configurations only. It does not reflect commercial agreements or guarantee operational health. A skill marked as Enabled simply indicates it’s configured.
For more info, read the MW Setup: Home Page doc in Help Site, and go through our Home Page announcement in Moveworks Community.
We’re excited to announce the launch of the Data Ingestion View in Moveworks Setup. This new beta feature gives admins unprecedented visibility into how data from enterprise systems is ingested by Moveworks, enabling proactive monitoring and faster troubleshooting.
Moveworks relies on up-to-date data from your systems to power its AI Assistant capabilities, such as Enterprise Search and Forms. The Data Ingestion View provides visibility into the crucial first phase of this process: the raw crawling and fetching of resources.
This helps admins:
Key Features
With the Data Ingestion View, you can:
How to Access? The Data Ingestion View is available now. Simply log into Moveworks Setup and navigate to the Core Platform section in the left navigation menu.
Note: The metrics in this view show the health of raw record ingestion and should not be compared with the “Ingested Knowledge, Files, Users, or Forms” screens, which show records available in the index after all internal processing.
For more info, read the MW Setup: Data Ingestion View doc on Help Site, and go through our Data Ingestion View announcement in Moveworks Community.
We’ve made a significant update to how ServiceNow articles are handled, which will drastically improve the efficiency of content synchronization.
Previously, a content indexing method caused a lengthy blackout period of up to 24 hours when new article versions were published. This meant new or updated content was not immediately available to your AI Assistant.
We have now resolved this issue by changing the indexing method (for article sys_id). The new process will significantly reduce the blackout period to a much shorter duration, ensuring that new articles and their updates are available in the AI Assistant far more quickly. This keeps your knowledge base more current and reliable.
This update is now fully deployed and requires no action from you.
For more info, read this post in Moveworks Community.
Added comprehensive logging for built-in/default actions in Agent Studio, providing enhanced visibility into internal action execution within plugins and compound actions. Key Changes
This is now live for all customers using Agent Studio.
We’re updating how the AI Assistant formats its messages to make them easier to read. Instead of dense blocks of plain text, responses will soon include structure like section headers, bullet points, code lines, code blocks, and bolded key details. These improvements make it easier for employees to scan information quickly, understand what matters, and act with confidence.
Before / After Examples:
Employees will now see which systems the Assistant is searching in (ex. Confluence, ServiceNow, or SharePoint) and what steps it’s taking to generate a response. You’ll also see improved copy and wording in these progress messages, with additional visual polish coming soon.
What’s changing:
Before:
After:
Moveworks AI Assistant intelligently interprets user messages in public Slack channels and responds based on relevant knowledge and configured workflows. However, there are instances where a software is not yet integrated, or no helpful articles or workflows are available. In such cases, the AI Assistant now offers smart handoff to continue the conversation in a direct message (DM), giving end users a clear path forward—without waiting for a human agent to join the original thread.
With this feature, users can choose to either:
This feature is not compatible with automatic ticketing configurations. In such setups, the system directly files a ticket without attempting handoff.
We’re excited to introduce a brand-new resource designed to make your life easier:
Moveworks Setup: Module How-To Guides — your go-to collection for step-by-step implementation guides across Moveworks’ OOTB modules! 🛠️✨
Whether you’re just getting started or diving deep into complex use cases, these new and updated guides are here to empower self-service configuration like never before.
Check them out here 👉 Moveworks Setup: Module How-To Guides
These guides are designed to give customers the confidence to configure modules independently by offering clear, step-by-step instructions. With less reliance on Moveworks teams, you can move faster and smarter. Here’s what makes these how-to guides special:
We’ve made some UX changes to help streamline the user experience by providing a consistent entry path into MW Setup across all access points.
org_name.moveworks.com/manage). Users will now be automatically redirected to the System Connectors page in Setup via the login page app drawer. Additionally, the gear icon has been removed from the login page.
org_name.moveworks.com/assistant, org_name.moveworks.com/search)
https://org_name.moveworks.com/setupWe’re thrilled to introduce our brand-new Moveworks Agent Studio Developer: Level 1 Certification course, designed to empower you to build powerful, production-ready Plugins using Agent Studio. Whether you’re a developer just starting out or looking to elevate your automation skills, this beginner-friendly course is your gateway to creating AI agents that drive real business value.
This hands-on, guided learning experience covers the essentials of building Plugins in Agent Studio. You’ll dive into:
✅ Core Concepts: Understand important terms, including triggers, launch rules, conversation processes, and activities.
✅ Practical Skills: Configure slots, resolvers, and user attributes to personalize experiences.
✅ Automation Power: Leverage HTTP and built-in actions to streamline workflows.
✅ Best Practices: Learn syntax, debugging, and deployment tips to ensure success.
✅ Marketplace Mastery: Install and deploy pre-built plugin templates from the AI Agent Marketplace.
By the end, you’ll build and deploy your own agent, interact with it through your AI Assistant, and submit a screenshot to earn your Level 1 Certification! 🎓
This course isn’t just about learning—it’s about doing. You’ll walk away with:
Plus, you’ll join a growing community of certified developers who are transforming how work gets done with Moveworks. 🌟
We’re excited to announce the rollout of Script Logs, a new log type designed to improve visibility into executions of Apithon-based Script Actions (our internal, customer-safe Python scripting interface).
Script Logs capture debug-level traces of scripts executed via the action.script.trigger API, including:-
You’ll see these under the “Script” log type with plugin names like Mfm_Google_Calendar_Events, and clear summaries (e.g., “Script executed successfully”).
Read more about our Log Types here.
Fetch live web results using Quick GPT in your AI Assistant. This new capability in Quick GPT allows the Assistant to pull in web results with citations when answering questions that require up-to-date information. Think of it like Google’s AI Overview, but embedded in the place where you find company info or take action at work.
Web search gives you the latest insights you need about current events, market news, or trend shifts while staying in the flow of work. Citations are included, so you can verify important details. Web search is covered by Moveworks’ zero day data retention for a trustworthy search experience.
For more info, read our:
Moveworks AI Assistant is now using GPT‑4.1 as part of its Reasoning Engine. This model upgrade brings smarter responses, better reasoning, and faster performance — helping your assistant get even better at solving complex tasks across your enterprise.
For more info, read our GPT 4.1 upgrade post in Moveworks Community.
New support for handoff through Channel Resolver is now available. Previously, when the Moveworks AI Assistant couldn’t find relevant knowledge or helpful workflows via the Channel Resolver, it would simply add a “no resolution” emoji to the thread, requiring end users to wait for a Slack agent to manually assist.
With this new enhancement, the AI Assistant can now initiate a smart handoff directly in a DM when no relevant information is found in the channel. This allows end users to immediately request additional help by either connecting with a live agent or filing a ticket (provided automatic ticketing is not enabled).
Key Features:
For more details, read our Smart Handoff for Channel Resolver post in Moveworks Community.
A total of 50 new installable plugins are now available in the Moveworks AI Agents Marketplace. Below is the summary of new plugins across different systems👇
The new raw interactions table comes with enhanced data quality, new accessibility and extensibility features.
We have enhanced data quality of three important entities across MW analytics. Plugins, Domains & Topics. This is done via implementing a semantic data layer that translates raw data in conceptual formats for user to consume.
The new semantic layer data provides us with new plugin statuses, that helps in understanding what happened in a conversation, was a user successful or end up filing a case. What are scenarios where your AI assistant falls short & scenarios where it’s performing great.
👉 New Plugin Statuses introduced : Unsuccessful, Served, and Used plugins.
A single domain per conversation powered by new domain detection model that comes with better prediction and configurability.
All interactions in the new raw interactions table will be tagged with a primary conversation domain, representing the overall domain of the entire conversation, which may include multiple interactions. All interactions within the same conversation share this domain.
We now predict topics by considering the entire conversation.
To enhance topic classification accuracy and overall coverage, we have started attributing topics at the conversation level. This approach boosts topic coverage to approximately 86%, with precision around 97% (based on manual annotation).
We’ve also added 6 new topics to cover previously unpredicted scenarios:
Additionally, a new Conversation Topics column provides a comma-separated list of topics representing the entire conversation, rather than individual interactions.
There are no longer any restrictions on filterable entities. With the new filtering feature, users can search through any data seamlessly. Whether a data column has 100 unique items or thousands, users can easily filter interactions to pinpoint the exact data point they need.
Users can now export the raw interactions data for upto 200K rows. A 10X increase from the existing limit.
For more information on this feature, please read our help documentation on Raw Interactions Table. For global availability, read the Introducing new interactions table post in Moveworks Community.
Moveworks entities help AI assistant in detecting key elements of a user utterance (E.g. software apps, hardware devices, locations, events & more), thereby powering downstream skills like software provisioning, topics in EXI & Analytics, and more.
Entity Catalog serves as the repository of custom entities within MW Setup. It is designed to empower admins to independently create and manage custom entities within Moveworks Setup.
At the moment, we only support Software Entities within Entity Catalog. More entity types will be available in the future.
👉 Login to Moveworks Setup → Entity Catalog → Create New Entity (or) Edit existing Entities.
For more info, please read our help documentation on:
For more details on the global availability, please read the Entity Catalog Release post in Moveworks Community.
To improve user experience with the Moveworks bot, we have introduced a new feature within the Ingested Users screen in Moveworks Setup that identifies duplicate users in your organization.
What are duplicate users?
Duplicate users occur when key attributes such as Email Address, ITSM Identifier, or Chat Identifier are not unique across your source systems (e.g., ITSM, Chat, IDAM). This causes Moveworks to import conflicting user identities.
Why is this important?
Unique user attributes are essential for accurate user import and management. When duplicates exist, Moveworks cannot properly import these users, leading to inconsistent bot interactions and potential loss of access.
How does it work?
When Moveworks detects duplicate attributes, it halts the user import process until the duplicates are resolved, ensuring data integrity.
How to fix duplicates? What if duplicates are not fixed?
You can resolve duplicates by either deleting one of the conflicting user identities in your source system or filtering out the duplicate user within Moveworks. For detailed guidance on duplicate users filtering, please refer to our help documentation on How to filter out duplicate users in Moveworks Setup.
If duplicates remain unresolved, Moveworks will not import identity information for users with conflicting attributes. This results in those users experiencing inconsistent bot behavior and eventually losing access. This feature enhances visibility into user identity issues and helps maintain a seamless experience with the Moveworks bot.
For more details on the global availability, please read the Duplicate Users Release post in Moveworks Community.
CSV downloads from Imported Forms now include detailed insights into form fillability issues, helping you troubleshoot and resolve errors more efficiently.
👉 Login to Moveworks Setup → Ticketing → Forms → Imported Forms → CSV Download
Details Included:
How does this improve your experience?
This optimizes the troubleshooting experience of fixing fillability issues by allowing bulk review of errors impacting form fillability – no longer need to click into each form individually to view them. This is especially valuable when managing a large volume of forms, saving time and reducing manual effort.
For more information on the feature, please read our help documentation on Imported Forms. For more information on the global availability, please read the Form Fillability Issues in Imported Forms post in Moveworks Community.
To streamline access to the Employee Communications tool within Moveworks, we have implemented a system that relies only on the Roles and Permissions that are granted to users.
👉 Login to MW Setup → Roles and Permissions App, verify who has access to Employee Communications User and Employee Communications Admin roles and make any changes necessary.
For more information on the global availability, please read the Simplifying access to Ecomms tool within Moveworks Setup post in Moveworks Community.
A new AI Assistant section has been added to the left navigation bar under Core Platform within MW Setup.
The AI Assistant Plugin Management (formerly Assistant Plugin Management) has been relocated to AI Assistant → Plugin Management for centralized access, allowing admins to manage MW AI Assistant capabilities more efficiently.
A new Conversation Settings configuration has been introduced under AI Assistant → Advanced Settings, enabling control over conversation history look-back for the AI Assistant.
This restructuring consolidates all AI Assistant-related configurations in one place, improving navigation and usability within the Core Platform.
For more info regarding Plugin Management, please read our help documentation on AI Assistant Plugin Controls.
Why was it built/what problem did it solve?
When a user takes a screenshot of an error message, they want to immediately paste the image into the file a ticket flow (without the need to save the image / file).
This is important for Slack customers in the classic version of the AI Assistant - Clicking on “File a ticket with RTF” or “adding a comment” will take them out to web instead of keeping the user in-modal.
We have deprecated the domain label previously attached to knowledge base (KB) articles ingested by Moveworks under Setup → Answers → Ingested Knowledge → Internal Knowledge, Files.
Key reasons for this change:
For more info about the UX Change, please read the Domain Removal from Ingested Knowledge post in Moveworks Community.
Internal Knowledge and FAQs have been split into two separate pages within the Answers module for improved usability and clearer differentiation:
There are no changes to the core functionality or behavior of these modules.
The number of top topics displayed in the third pane has been reduced from 100 to 20.
This change has been implemented to reduce wait times and improve performance following the recent migration of EXI to a new database. The top 20 topics cover 80% of the issues, and customers can still access all topics via the “Download All” option.
The new feedback mechanism in Employee Comms ensures capturing of all user feedback with 100% guarantee.
The current mechanism of users sharing feedback in chat is fraught with the risk of AI assistant assuming the text to be a start of a new conversation.
To mitigate this, when an user clicks on a button meant to capture feedback, we will display a follow up message with a “Submit Feedback” button which will open an in-chat modal within which users can type their feedback.
When chat history gets too long, it can confuse the LLM (large language model), leading to less accurate, less relevant, or slower responses. To tackle this, we’re excited to introduce a new feature within our AI Assistant: Automatic Conversation Clearing!
We’ve created an Employee Comms template you can use to spread the word here.
Interacting with our AI chatbot used to mean scrolling through a long, sometimes overwhelming page to find what you needed — whether it was citations, feedback, or support options. We’re making it much easier to navigate by breaking things into simple, clear sections.
What’s New:
Now, everything is just a click away with our new 3-tab experience:
👉Note: This is just a visual update — the AI Assistant behavior and responses aren’t changing. The entry point for this experience also does not change. Depending on which entry point you select (ex. Thumbs up/ Thumbs down) you’ll be automatically navigated to the right tab (ex. “Feedback” tab).
We rolled out two updates that will improve the Smart Handoff experience — making it more customizable and less disruptive for your employees.
Customize the “Get Help” Link Label 📝
You’ll now be able to rename the “Get Help” link to better match your company terminology. Prefer “File Ticket”, “Live Chat” or “File ticket/Live chat”? Go for it — it’s all up to you. We’ll share configuration details soon.
No Redundant “Get Help” Links 🖇
We’ve improved the logic behind when the “Get Help” (or your custom label) link appears. If a user is already confirming they want to file a ticket or chat with a live agent, there’s no need to show the link again — so we don’t.
👉Note: If you’ve customized the label from “Get Help” to something like “File a Ticket,” “Live Chat,” or “Need Support,” the same logic applies: the link will be hidden in situations where it would be redundant.
Earlier this year we encountered an issue with Microsoft Teams that caused problems for all our Microsoft Teams customers. We’ve been partnering closely with Microsoft Teams about this issue and they recently rolled out an update that would fix the problem.
Unfortunately the solution requires that all of your employees to update their Moveworks AI Assistant application. We’ve been informed by Microsoft Teams that this update has now been rolled out to all of our customers. Below is a screenshot showing a banner with an “Update” button that will appear for all your employees within your assistant application.
We understand this is not ideal and apologize for any issues that have been caused due to this update.
What was the issue? Microsoft Teams rolled out an update in February 2025 that caused issues with the attachment button within our Moveworks AI Assistant application. Customers started reporting that the following issues with the attachment button within their assistant:
Now when your employees are using Brief Me, any files that are uploaded with your AI Assistant are automatically deleted across all of our backend services within 24 hours.
Within the experience you’ll notice these updates:
DSL Builder and Evaluator is a feature designed to simplify the creation, modification, and testing of DSL rules across the Moveworks Setup.
What’s new?
Please refer to the following ressources to start using this feature:
Enable WQL checkbox and Report URL for Approvals config are now available under Setup → Connectors → Built-in connectors → Workday System Connector
JIRA Cloud Identity App Secret and Upload Attachments as Activityare not available under Setup → Connectors → System Connectors → Jira Service Desk.
Hide Default Agent Imageis now available under Snow Handoff Config in Setup → Handoff → Live Agent Handoff → Agent Broker Handoff configuration.
Bot Access added under User Identity
A dedicated Bot Access page has now been introduced under Setup → User Identity, allowing users to configure the Bot Access Rule.
This was previously located under User Identity → Advanced Settings → Plugin Settings.Respect Geocode configuration moved under Ticketing
The Respect user geocode when resolving weekend hours configuration has now been moved to Ticketing → Concierge Settings → Notification Settings, since it is a notification setting rather than a bot setting.
NAT Gatewayis now available in the GovCloud environment under Setup → Tenant Settings → General Information → Network details Section. The NAT Gateway section lists the Static IPs that identify requests originating from Moveworks core platforms & services.
For more information on IP Address allowlisting, please read our Network Allowlisting documentation.As we move to a new infrastructure, the config and permission logs data before March 11th 2024 will no longer be available under MW Setup → Audit → Configuration Logs, Permission Logs
👉Note our data retention period remains 60 days. The first full retention cycle will end on May 11th, after which data will be retained on a rolling basis.
We’re excited to share that you can now delay the execution of actions! For developers building with APIs that have asynchronous behavior (e.g. a “start job” endpoint and a “get job results” endpoint), you’ll be able to “sleep” the action for a period of time.
For more details, please see our Compound Action Reference in Agent Studio docs, or check out an example for a reminder plugin below:
⚠️ Ticket interception is a legacy plugin for the Moveworks AI Assistant
❗Important - This feature is only available to customers who had previously enabled Ticket Interception in Moveworks Classic. For more information, please contact your account team.
For more details, please read more in our Ticket Interception in Moveworks Classic docs!
A dedicated Bot Access page has now been introduced under Setup → User Identity, allowing users to configure the Bot Access Rule. This change was made to enhance the experience of configuring bot access rule in Moveworks Setup since it is a crucial configuration.
This was previously located under User Identity → Advanced Settings → Plugin Settings.
To learn more about the bot access rule, please see our Bot Access Rule in User Identity Plugin docs!
The Assistant Plugin Management page under Setup contains a large number of DSL Editors, which was causing performance issues, including slow loading times and frequent browser session crashes.
To improve usability, configurations have now been grouped and in-page sections have been introduced, resulting in significantly faster load times and better responsiveness.
UX Change with In-Page sections and grouped configs
We’re excited to share that all customers now have access to the Agentic Automation Engine in Agent Studio! Our new engine is purpose-built to bring powerful AI agents to life — fast. It interprets natural language, can plan actions, and help you execute complex tasks, enabling you to create AI agents that can transform the way teams work across your organization.
For more details on what the Agentic Automation Engine is capable of check out these resources:
How do I access this new workspace in Agent Studio?
Do I need to do anything to get this enabled?
No, the Plugins tab will appear in your Agent Studio app automatically.
I’m still on Moveworks classic experience, can I still build?
Any plugins built will not trigger in the Moveworks classic experience. Plugins only operate in the Moveworks Assistant.
We recommend reaching out to your success team & upgrading to the Moveworks Assistant in order to start building & using plugins.
How can I get started?
What else should I know?
To accelerate your AI agent development, our Professional Services team offers hands-on training for key enterprise systems through a program called Activate — sign up or let your Success Manager know you’re interested.
We’re thrilled to announce that you can now verify entities mentioned by action plugins (e.g. Software, Add to Distribution List, Unlock Account plugins) directly on the citations page. Just as you can validate sources from knowledge searches, this feature is now extended to action plugins. Review details about distribution lists, software, and identity systems before taking action, ensuring full confidence that the Assistant will execute the right tasks seamlessly. See below for some examples.
Adding someone to the distribution list
Sometimes, there might be multiple possible options that matches your request. If you want to see more details and be sure about the distribution list to pick, click on the citations and view the description, security policy, and group type.
Request access to a software
Get more details about the requested software, including the approver, the roles available, etc.
Unlock an account
As you may recall, you can configure instructions and self-service messages for the Reset Password, Password Expiry, Unlock Account, and Reset MFA plugins. This allows the Moveworks Assistant to provide users with self-service messages or links to relevant portals, rather than directly executing actions on external systems.
We’ve improved the performance of self-service messages in triggering consistency, summarization, as well as analytics tracking.
For end users, the experience remains largely unchanged. They will continue to see the same self-service messages, but with improved reliability in triggering and summarization.
For admins, you will see changes in the analytics. With the update, all self-service messages will be tagged with their corresponding native plugins. For example, if user asks to reset their password and you’ve configured a self-service message, you will see that interaction being logged with a reset password plugin call.
Self-service messages configuration are not yet available in Moveworks Setup yet. We plan to make them available for admins in Moveworks set up in the coming months.
Exit this mode.
You can now view and download additional user attributes such as full name, role, manager email, and more in Ingested Users within Moveworks Setup.
How to view user attribute list in Ingest Users?
To download the user attribute list in CSV format, Click on the download button below in All Users widget.
Moveworks now allows customers to configure multiple custom domains, each with unique handoff instructions.
There is a limit of 7 total domains, which could be a mix of out-of-the-box or custom domains. This limit exists because the handoff UI is limited to reduce the options for employees to select the handoff destination. For example, a list of 25 domains for an employee would be overwhelming and not useful in the product.
For details on how to configure a custom domain, read here.
Developers have built a TON of example chats with our Purple Chat Builder (over 10,000 mocks!). We’re excited to keep the energy flowing with Purple Chat V2!
apiBlock component. Your Connector Image. Your Method. Your Body. In an IDE you’ll LOVE.reasoningSteps to citations to the feedback tray at your disposal.Go play with itNOW! (aka.mw/purple-chat).
secondary color set in M4W Customization -> It will now be either white or black depending on the contrast to the Response Card background (also set in M4W Customization)button primary color.See the screenshots below for examples of light vs dark contrast and the before and after in each case.
