We’re happy to announce that Slack users can now add attachments to tickets in Slack itself! This is an optional configuration which applies to tickets filed via the Moveworks Assistant.

Relevant Configurations
This feature will require two configuration options: rich ticket filing with attachments enabled, and Slack file attachment enabled.
Prerequisite Slack permissions
Slack attachments require the file input block to be built on the Slack Modal, which requires a few permissions, notably files:read , which is used by the bot to construct the modal.
files:read ONLY grants the Moveworks Bot the ability to read file attachments that the user sends to the bot, in channels the bot is added to, and the ability to construct a modal that has file input as a field.
files:read Does not grant the Moveworks bot access to read file from your DM with others or any files that is shared in other channels channel.
These permissions can be enabled directly in the App Manifest page of the bot’s config.
In order to help you audit and limit access to the Moveworks Logs app, we added a new role to the Role & Permissions app in MyMoveworks. By default, users will NOT have this role enabled.
Who does this affect?
This only affects customers with access to Agentic Automation Engine. If you see a Plugins tab in your Agent Studio page then you have access to Agentic Automation Engine.

If you had Agentic Automation Engine enabled before 12/13/2024, then all of your developers that have access to Agent Studio will have the role by default.
If you have Agentic Automation Engine enabled after 12/13/2024, than all of your developers that have access to Agent Studio will NOT have the role by default.
What’s the Role?
The Role is called Agent Studio Logs Viewer

What does enabling this Role do?
If a user is granted the Agent Studio Logs Viewer role, they will be able to see and access the Logs app tile in the MyMoveworks menu.
What is the Logs app?
The Logs app lets you view all of the logs needed to debug Plugins, Compound Actions, and Actions created in the Plugins tab in Agent Studio.

How do I set Roles & Permissions?
You can follow our Roles & Permissions guide.
We are excited to launch the all-new User insights report. This is a new report launched for Assistant Analytics and provides insights on adoption and assistant usage.

Learn more about the report here.
We’re thrilled to share the release of two new quick start guides designed to make onboarding and learning quick and easy. For each feature, all the steps should take about 2-4 hours in total and can be completed at your own pace.
👉 See the complete Employee Comms Quick Start Guide in Community here.
👉 See the complete Knowledge Studio Quick Start Guide in Community here.
This update is to enable users who are looking for handoff to a human to get to file ticket or live agent more easily, without going to Get Help (i.e. the reference popup).
Background: How handoff works in the Assistant
The Assistant offers a handoff option in chat based on two key factors:
For example:
“I need to file a ticket for my VPN issue”
“Can I talk to an agent? I have a 401k question”
Limitation of the current experience
In some cases, the user may ask a question for which the Assistant is unable to predict the domain from the list of domains configured:
“Create a ticket for an issue with the sidewalk outside the office”
“Create a ticket for an issue”
Similar, in some cases, the user may ask a question where they don’t explicitly mention the way in which they need help:
“I need assistance with an HR question”
In both cases, since the Assistant was not able to predict both domain and item, it asked the user to click on Get Help to view more options and make their selection.
Upcoming improvements and user experience
With this update, the Assistant will offer easier access to handoff options even when either domain or item are not predicted.
If the domain is not predicted but the item is predicted with confidence, the Assistant will provide a list of all available items across different domains:


If the item is not predicted but the domain is predicted, the Assistant will offer a list of the items configured for that domain:


Note that if the user does not provide a description of the issue, the Assistant will still ask the user for more details before offering a handoff option:

In case neither domain nor item could be predicted, the Assistant will ask the user to click on “Get Help”:

Also, note that all handoff options will continue to be available on the reference page, which the user can access via Get Help.

We expect that these updates will greatly reduce the effort from users in getting help and will get them to a solution to their issue faster!
Required handoff configuration update (for some customers)
As explained above, when the item is predicted but the domain is not, the Assistant will now present a list of all available types of that item.
To enable users to select the most relevant type of file ticket or live agent handoff from the available domains, we will need to update the button labels for each of these from simply “File ticket” or “Live agent” to “File ticket - IT”, “File ticket - HR”, or “Live Agent - IT”, “Live Agent - Real Estate Services”.
This will be a small change enables users to more easily identify and access the best handoff option and gives them the control to make the selection. You can use Moveworks Setup to make this change as shown in this example:

which should be changed to the following with unique values:

We are introducing an easier way for Moveworks admins and stakeholders to report issues. Previously, you had to rely on screenshots, user IDs and dates of the interaction to share a specific issue with Moveworks Support, which was both time consuming and error-prone.
You can now get the conversation ID for any Assistant interaction, for any user - simply by clicking on the ℹ️ emoji in chat. This is a unique ID shared by a small number of interactions that are grouped as a conversation by the Assistant’s topic prediction model.
Using the conversation ID makes it simpler to pinpoint specific interactions and share their IDs with Moveworks Support when filing tickets. It will also help reduce the time taken to provide help by eliminating the clarification process that adds multiple back-and-forts between you and the Support team.
How to file a ticket with Support:

We are making a slight experience change to the access software self-service messages.
For context, there are 2 types of software access workflows.
This experience change only applies to the 2nd workflow type.
What is changing?
Before the change, the self-service message is sent to the user directly upon ask:

After the change, a confirmation step is added before the self-service message is shown to the user:

Why did we make this change?
Permissions change audit logs allow Admins to get a real-time view of roles & permission changes done within their org’s instance.
With Permissions change audit logs, Admins can:

How do I access Permissions Change Logs?
Learn more about the feature here.
User profile view provides a detailed view into ingested users and their corresponding attributes. The user profile view is an important screen within Moveworks Setup to conduct basic troubleshooting with regards to any bot access related issues for an employee.
How to access User Profile View?

What has changed with the experience?
Users can now control the list of users who have the ability to publish campaigns within Employee Communications. To provide this access to specific users, simply enter their identifiers, in the Moveworks DSL rule format, within the “Access Control Publish Campaign Enabled” field under Additional Controls in the Notifications Module and save the configuration.

This feature ensures that not all users who have the ability to create a campaign can publish it, giving administrators the opportunity to review and make changes, if necessary.]
We’re thrilled to share the release of a new EXI enablement course!
👉 EXI in Action - Use Cases and Workflows to Drive Impact.
This new content builds on our foundational EXI certification and delves deeper into the practical application of EXI within essential business workflows. Additionally, it suggests focus areas and cadences for each workflow, as well as how to measure the impact of your efforts.
Moveworks Assistant can now call multiple plugins in parallel, review the responses from them, and combine their individual responses into a single, summarized response!
This feature is called multi-plugin response and it enhances the user experience and utility from the Assistant by
Here is an example of a multi-plugin response that combines information from Knowledge Search with Software Provisioning for Figma:

You can see from the AI reasoning what plugins were accessed:

What does a multi-plugin response look like?
Here are the key characteristics:


Yes for Unlock Account, it proceeds with the selected action
How does this feature work?
Multi-plugin response comes with three key changes:
(1) Simultaneous Plugin Calls
Before multi-plugin, the Assistant almost always called one plugin to help with a request. The primary exception was multi-intent requests like “Do X AND help with Y,” which led to sequential plugin calls. Now, the Assistant identifies and uses all helpful plugins.
(2) Parallel Execution
MultiPlugin executes plugins in parallel. For single intent requests, this ensures MultiPlugin latency is comparable to current performance; for multi-intent requests, this decreases latency as the Assistant executes on all intents at the same time.
(3) Improved Buttons UX
With more plugins in use, calls to action have become more frequent. To improve this experience, we now include buttons for each separate call to action. Each group of buttons comes with a concise Assistant-generated description for button context.
What are some known issues and limitations?
These are some aspects of the first version of this experience that we are aware of, and will work on improving in future iterations:
How will this feature impact Assistant Insights?
The main impact will be an increase in plugin calls - both successful and unsuccessful.
We’re happy to inform you that it is now possible to add file attachments to comments in tickets, when adding the comment to a ticket from the Assistant! This is in addition to being able to add an attachment while filing the ticket, which was already available.
Moveworks offers the option to enable adding attachments through a configuration, and this was a feature available in Moveworks Classic. It is now available in the Assistant as well.
How to use this feature
Simply add a comment to the ticket as you would and then click on edit request to reach the popup to edit your comment. The option to add attachments will be available as shown below:


What do you need to do?
Upcoming enhancement
For Slack customers, we are working on a completely Slack-based experience to enable adding comments through a modal within Slack itself. Users will no longer be directed to a browser to accomplish this. This update is coming soon!
Brief Me within our Moveworks Assistant now supports PDFs, Word docs, and Powerpoint files! If you are already part of our limited preview program for Brief Me, your the Assistant already has this update. Go to your Moveworks Assistant and start uploading any combination of these files — up to 5 files at a time, each file can be up to 25MB.
Here are some scenarios you can try with Brief Me:
Want to get early access?
Current customers, please fill out our Community request form to be considered for our limited preview program.
Did you attend our webinar?
We took a deep dive into the Assistant and Brief Me, including live demos and a technical overview. If you missed it or simply want a refresher, don’t worry—the recording is now available for you.
What is the Agentic Automation Engine?
The Agentic Automation Engine is the new heart of Agent Studio. It is designed from its core to build integrations for AI agents.
Traditional iPaaS and middleware platforms were designed for connecting systems to systems, so when they tried to use these tools to connect agents (which use language) to systems (which expect well-formed data), it was extremely difficult for developers to create the plugins that customers want. It’s like trying to connect your iPhone to wired internet without using an adapter.
Agentic Automation Engine changes the way that developers build integrations between AI agents & business systems. With the Agentic Automation Engine, technology teams can…
What are the key capabilities of Agentic Automation?
The Agentic Automation Engine is built on 4 key pieces of technology
If you want the full breakdown of specific runtime capabilities that are available in the platform, see the Agentic Automation Engine — Product FAQs on Community.
How do developers build on the Agentic Automation Engine?
We have introduced a brand new Plugin Workspace in Agent Studio to make it easier to build plugins.



You can read more about the Agentic Automation Engine in our blog post, and get a full teardown in our **white paper.**
How can I get access to the Agentic Automation Engine?
See Agentic Automation Engine — Access & Rollout FAQs in Community for more info.
Note: The Agentic Automation Engine is only available on the Moveworks Assistant (not our Classic chatbot). See the Agentic Automation Engine — Product FAQs for more information.
We are excited to announce Plugin Promotion, which lets you move plugins between your sandboxes & your production instance, is now in Preview! In addition, to support Plugin Promotion, we are releasing Draft Mode, which lets developers save WIP work.
What are the capabilities of this launch?
How do I get access?
You don’t need to do anything to get access! This feature is available for all customers.
Where can I learn more about the Plugin Promotion?
See our documentation here.
Quickly set up and test API actions with our revamped, one-step API editor.

Permissions Change Audit Logs allows admins to get a real-time view of roles & permission changes done within their org’s instance with Moveworks Setup.
With Permissions Change Audit Logs, admins can:

How can users access Permissions Change Logs?
Learn more about the feature by reading our help documentation.
Choosing the right software entity for your software provisioning is important to ensure that your Moveworks Assistant responds with the correct software when a user asks for provisioning.
With entity search functionality, admins can now directly search and input the software entity name, while creating a new software provisioning configuration. This will reduce dependency on the Moveworks support team to get the exact entity name for configuring a new global software.

Important information regarding Software Entity Search
Learn more about configuring new software in our documentation.
We’re thrilled to unveil the Approval Looping feature in the Moveworks Assistant Approvals. This new functionality enables users to systematically address each of their pending approvals sequentially.
The Moveworks Assistant already provides a flexible, conversational experience, allowing complete navigation via natural language. However, for tasks like Approvals—where daily volume can be high for power users—we understand the efficiency clickable buttons can bring. That’s why we introduced Approval Looping, crafted to let you swiftly manage all pending approvals with just a few clicks.
What’s the experience like?
The Approval Looping feature attaches 2 buttons to the confirmation message of a processed approval request.
View next approval button shows you full details of the next open approval request.View all approvals button shows you the list of all pending approvals.Step 1: ask the Assistant for your pending approvals

Step 2: Type a number from the list to view more details, and take action.

Step 3: Click on “View next approval” to view the next open approval

Step 4: View the next approval details

The View next approval and View all approvals buttons are attached to every approval action confirmation message. You can start a looping experience after approving a request from notifications too!
What are some potential variations in this experience?
As a feature built on a Gen-AI reasoning engine, you might see some variations in the experience from time to time. This includes
View next approvals . The LLM uses approval ID stored in context to help find the next approval from the system. While this is usually reliable, the LLM might make mistakes on the approval ID, resulting in it not being able to find the next approval. If you see this error, you can try again, or type “Show all my approvals” to start fresh.To combat these variations, we are putting together ML evals to capture any potential regression proactively. If you notice any variations, please let us know through our support team, or post directly in the community.
We are pleased to announce that the ability to edit Moveworks Native Approvals has been restored for customer administrators.

Please exercise caution when changing Moveworks Native Approvals settings. Consult your Customer Success Engineer (CSE) or contact our Support Team for advice before making any adjustments to avoid unintended impacts on software provisioning.
We’ve updated our offering to include the new Plugin Library, a comprehensive and expanding collection of plugins for various enterprise systems like Workday, Coupa, and Salesforce. This library offers everything from inspiration to detailed guides and videos for building specific plugins.
Here’s how to leverage the Plugin Library effectively:
We’re constantly enriching the library with more plugins, videos, and guides. Remember to bookmark the page and check back regularly to see the latest additions.
We’re excited to announce the launch of Channel Resolver for Moveworks Assistant. This latest update empowers employees to leverage the advanced Assistant experience not only through private direct messages (DMs) but now in public Slack channels as well. You can read about it within the Help Site documentation.
We’re delighted to unveil the latest enhancements to Assistant Insights—now including Channel Resolver and Triage Analytics. With the introduction of Channel Resolver, gain deeper insight into how effectively issues are being resolved within Slack channels. Meanwhile, Triage Analytics offers a comprehensive view of problem categorization and resolution efficiency, enabling more informed decision-making and optimization strategies.
We’re excited to introduce verified entities in Assistant responses, a breakthrough feature designed to enhance referenceability and trust in the information provided. With this enhancement, users will notice a significant improvement in how references are displayed. Verified names, email addresses, URLs, and executed actions are now distinctly marked with a “+” superscript. This visual cue not only increases visibility into the utilization of entities in the Assistant’s answers but also allows users to quickly navigate to a reference section for verification. Empower your interactions with the Assistant through transparent and grounded responses, strengthening trust and efficiency in every exchange.


We’re thrilled to announce a significant UX enhancement to Ticket Details and Approval Records—the integration of structured cards into Lookups for Moveworks Assistant. This update transforms how information is presented; whether you’re retrieving ticket information or approval requests, each detail, from ticket ID and status to approval descriptions and involved parties, is neatly organized within a deterministic structured card format. This makes for a clearer, more accessible lookup experience, enabling faster, easier navigation and comprehension of crucial data.


Excited to announce Moveworks Assistant is now powered by GPT-4o, OpenAI’s latest GPT model! This upgrade significantly enhances user interaction through faster response times, improved non-English text processing, and superior efficiency in handling requests. Rolled out to all customers, GPT-4o ensures more natural, concise conversations and broader global support. Discover the future of efficient, AI-driven user support with Moveworks Assistant. Learn more on our Product blog.
We’re excited to announce the Preview release of our revamped Error Messages & Trace IDs for Agent Studio, designed to make debugging faster and more intuitive for all customers. After listening to your feedback, we’ve overhauled error messages across 14 different states to be clearer and more actionable, ensuring you can swiftly identify and resolve design-time errors. Each updated message now includes detailed descriptions, specific error codes for easy documentation reference, and Trace IDs for enhanced support assistance. Plus, for select errors, direct links to documentation are provided to streamline the troubleshooting process. Stay tuned for continuous enhancements as we aim to make your experience with Agent Studio increasingly seamless. Link to troubleshooting documentation

We’re thrilled to introduce an essential update to our Native Approval Workflows: the ability to add a comprehensive list of required and pending approvers directly onto tickets for Access Management. This enhancement addresses a critical visibility gap previously identified by our customers. No longer will Service Agents be left wondering about the next steps in an approval chain, as detailed worknotes will clarify the exact Approval Workflow and approver at every stage. This update not only simplifies tracking progress but also significantly expedites stalled processes, ensuring smoother operational flows for everyone involved. Available to all our ticketing customers using Native Approval Workflows, this change marks a significant leap towards more efficient access governance and management.

We’ve published a Community post with details on the planned fixes & timelines for Paths in the Assistant limitations here. Moveworks Assistant’s generative framework brings intelligent reasoning to your Agent Studio use cases. This means many out-of-the-box benefits (such as implicit slot filling, easy context switching & more). Check out our documentation for examples & details.

With this update, when an agent sends a KB number or ticket number (RITM, INC, etc.) during a live chat session, the message will first be passed immediately to the user, then it will be followed by a card containing a clickable direct link. If available, the resource’s short description will also be included. When the user clicks on the link, it will bring them to the resource in ServiceNow.


A “Close” button is being added to the maximized view of M4W. This button will be in the top right of the view, in addition to the existing “Exit Full Screen.” This “Close” button will directly close the M4W pop-up window and return to the “closed” state with the bot avatar icon in the lower right corner.

When a user fills out a Rich Ticket within chat, Moveworks would file the ticket with all custom fields, individually, in the ticketing system. Now, these custom fields will be consolidated into the ticket description. This is an additive change; we’ll still keep the structured fields in their familiar location while adding more into the ticket description. In the example below, the Short Description, Issue Description and Long Description are all added into the Ticket Description

Moveworks Academy is live this week on a brand new platform with a revamped user experience tailored to your learning needs. Whether you access Moveworks Academy from academy.moveworks.com or from my.moveworks.com, you’ll be automatically redirected to the new platform.
Note: Your up-to-date course progress and certifications will carry over by July 17.

We’re introducing the ability to file in-bot tickets for customers beginning with customers who have only one configured domain handoff and a single handoff destination (e.g., file an IT ticket, or URL handoff).
See more details on the Moveworks Community!
the Assistant now passes prior conversation context in a live agent handoff, or when a ticket is filed through the bot.
We’ve enabled users to file tickets and kick off live agent sessions without going to the reference page for simple actions.

See more details on the Moveworks Community!

Multi-Language Support is available in the Moveworks Assistant! This update adds:
See more details on the Moveworks Community!

We’ve rolled out an update to people lookups that provides the best of both worlds to users — summarized and structured responses. Starting today the Assistant will present a structured card response for queries like “Who is Carl?” to make it easy for the user to review at a glance. We’ve also brought back floor plans, directly in chat.
See more details on the Moveworks Community!
You can now track all user engagement with Employee Comms campaigns in the Moveworks Assistant, including:
See more details on the Moveworks Community!

Now, for every “Knowledge Update” recommendation, you can easily see which one of your existing articles may need an update. We’ll display relevant articles from your knowledge base to the topic at hand. For more, see our AI Powered Recommendations guide.
When you begin drafting a new article, Knowledge Studio will now automatically search for any existing content related to your topic. If similar articles are found, a “View articles to update” button will appear within the generation. This feature helps ensure that the new article you’re writing is unique and doesn’t already exist in your knowledge base. For more, see our Creating Knowledge Articles guide.


Access your Moveworks products and services like Community, Academy, and support from an easy-to-access interface featuring:
We heard feedback that your API often takes longer than 15-20 seconds to respond. Your APIs contain valuable information that users are willing to wait for, and so we’ve increased the Query timeout limit to 1 minute. Changes you’ll see:
GPT-4 Turbo is the latest generation model in the GPT series from Open AI, and Moveworks is leveraging it via both Open AI and Azure Open AI services.
GPT-4 Turbo brings a host of benefits to all Assistant users:
See more details on the Moveworks Community!

Understand user inputs: Generated implicit confirmations will modify based on user selections & capture their input more accurately.
Concise & proper grammar: The messages will use more straightforward and concise wording.

Manage Analytics Views: Enable developers to specify which use cases are in test versus in production, and as a result, included in analytics.

When a bot response is not yet received but in flight to a user, a typing bubble will be visible, similar to other chat experiences.

For Moveworks for Web users, we’ve moved the close button to be underneath the UI. Additionally, users have more options now in terms of sizing and color.

Query and retrieve knowledge from your Workday Help Articles by using natural language within your bot.

Take action on Approval Requests for your organization’s Salesforce Opportunities — set up through Approval Process workflows — based on single approvals, group approvals, and multiple steps, directly from within your bot.

We’re excited to announce that the Moveworks Assistant is now available in Preview. The the Assistant uses generative AI-powered reasoning to understand and resolve complex requests, providing direct, summarized responses drawn from your organization’s sources and integrations. It combines search and actions to provide a delightful, unified experience to users from across the company.
Contact your account team today to learn how you and your team can get started with the Moveworks Assistant, and experience the future of enterprise productivity!

File Search superpowers your Moveworks Search capabilities, by now supporting PDFs, Word Documents, and Powerpoints.
Starting with Sharepoint, Google Drive, and Box, your source ACL permissions are also fully supported out-of-the-box, so your users can only Search for content in files that they already have access to.
Reach out to your account team today to get started.
Read more about this feature here.

Interested in using generative AI to find and close gaps in your knowledge base? Then Moveworks Knowledge Studio is for you! Take a look at our product resources and reach out to your Moveworks account team to see a demo of Knowledge Studio in action.

Leverage step-by-step tutorials for your Agent Studio projects.
Our library provides granular, easy-to-follow instructions that guide you through various use cases and functionalities.
View the library here.

Control access to all your Moveworks applications with the help of Roles & Permissions! Administrators can now audit which users have access to Moveworks applications, and grant and revoke user access to these applications through My Moveworks.
Learn more about the three types of roles and how administrators can grant or revoke access to these roles through reading our docs.

Please note
Read more about logs in Agent Studio here.

What is it
Generated questions retain semantic info from question details (Paths design patterns only). This is a Agent Studio slots enhancement.
Features
Read more about this feature here.

What Is It
You can now configure PATCH, PUT, and DELETE Requests for APIs that leverage those methods!
Examples
Read more about this feature here.

What Is It
Features
Read more about this feature here.

What Is It
My Moveworks is your new unified portal for all your Moveworks products, documentation, community, academy, and support. It is a replacement for your Moveworks portal (trust.moveworks.com), which is being deprecated on Apr 30, 2024. It provides:
Features
Read more about this feature here.

We removed the extra message “Let me know if you need something” after API action completions. (Paths design patterns only). This is a Agent Studio actions enhancement.
Read more about this feature here.

Administrators can now add / revoke access to each licensed Moveworks product through the “Roles and Permissions” app in My Moveworks. You can now
Read more about roles and permissions in Moveworks Community here.

A new CSV file is available as part of your SFTP feed that share audit data about how Agent Studio is being used by your team and employees. It provides visibility over how your developers are connecting to external systems, and provides a way for security teams to audit and detect problematic access to systems.
Read more about details around SFTP Access here.

My Moveworks is your one-stop portal for accessing all your Moveworks products, documentation, community, academy, and support. It is a replacement for your Moveworks portal (trust.moveworks.com), which is being deprecated on Apr 30, 2024. It provides
My Moveworks has been enabled in your Agent Studio SSO app, if you have finished SSO setup. You can follow our resources below to learn more and configure SSO.
If you have not configured SSO, please follow our guides and resources below to configure My Moveworks:
Configure My Moveworks for Okta
Configure My Moveworks for Microsoft Entra (Azure AD)
Configure My Moveworks for Other SSO Providers

Your developers can now monitor API requests and responses made by your bot through Agent Studio logs. This allows them to troubleshoot any problematic API requests from your bot, and provides them tools to monitor your use case performance and launch more use cases. Please note: this applies to Paths and Queries use cases only.
Learn more about Logs here and read documentation here.

We are committed to listening to and incorporating your feedback to our Moveworks Product Roadmap. The Moveworks Product Ideas portal is a forum to collect product ideas from our customers.
To learn more about how the Product Ideas Portal works, click here (must be registered on Community).
Learn more about App Digests here.

For organizations with multiple ITSMs, we will show a URL for each ITSM when users wish to see a list of all their tickets. We also changed the wording for viewing tickets from “Click here to see all your tickets” to “View all your tickets”.

For Webex users, all plain text responses like button click messages such as “Okay, you clicked…” or system messages like “Working on it…” will now be rendered as adaptive card(s). This change will help us provide a more unified and consistent experience across our chat platforms.