We’re introducing a new Setup guide directly within Moveworks Setup Overview page to guide admins through the recommended sequence of configurations during onboarding. Instead of relying solely on help documentation to understand the recommended setup sequence, admins can now see the full journey and navigate directly to each configuration step from within the product.🧭 What’s new?For organizations currently onboarding to Moveworks, the Setup Overview now includes a 'Getting started?' banner that provides a direct entry point into the Setup guide. The guide brings the complete onboarding journey together in one place, with each step providing:A description of what needs to be configured An estimated time to complete the step A link to detailed documentation A Start action that takes you directly to the relevant configuration pageThe guide also includes a Jump to section navigation, making it easy to quickly understand the full setup journey and move between different stages of onboarding.⭐️ Why this mattersSetting up Moveworks spans multiple configuration areas, and understanding the recommended sequence can be difficult when guidance is spread across documentation and different Setup surfaces. The new Setup guide helps admins:Understand the complete setup journey and the recommended order of configuration Know where to start and what to do next during onboarding Navigate directly to each configuration page from the relevant setup step Access setup guidance without leaving Moveworks Setup📍How to access the Setup guideFor organizations currently in onboarding stages,Navigate to the Setup Overview page in Moveworks Setup. Select View setup guide from the Getting started? banner. Review the setup journey and select a section to see the recommended configuration steps. Select Start next to any step to navigate directly to the relevant configuration page and begin configuring.✋🏻 What to knowThe banner is shown only when an organization is in onboarding stages. A permanent Setup guide link is always available from the Setup Overview header, so admins can return to the guide whenever needed. The guide provides recommended setup guidance and navigation but does not currently track completion of individual configuration steps.📚 Learn moreFor additional details, see:Getting Started Guide Moveworks Setup HomepageHave questions or feedback? Please post them on the Moveworks Community, where our team will be happy to assist.Thank you, Moveworks Setup Team

 What’s newAgent Studio now provides Version History and Revert for Agent Studio assets, a new version-control capability that records every publish and makes it simple to inspect or return to a previous known-good state.Release type: New capabilityProduct area: Agent StudioAvailability: All customers, all data centers. No configuration required.🧭 What’s includedVersion History tab on Plugins, Conversational Processes, Data Types, Actions (HTTP and Script), Event and Webhook Listeners, and MCP Servers. Commit messages: the Publish modal accepts an optional message describing the change. Version chips in the editor header and in the tab strip to show which version is open. Open any earlier version directly in the editor to inspect its contents. Publish from an opened earlier version to create a new version based on that content. One-click revert with a confirmation modal that lists related child artifacts the revert will affect.🌟 Why this mattersBefore this release, publishing an update overwrote the prior asset immediately and teams needed external backups to keep a change history or recover from mistakes. With Version History and Revert:Developers get an auditable history of publishes (author, timestamp, optional commit message). Teams can easily inspect previous versions without rebuilding from scratch. Reverting to a previous version is simple and safe, reducing risk and speeding recovery from bad publishes.✋ How revert behavesRevert is additive and non-destructive:Reverting an asset, for example, currently at V4 back to V3 will create a new version V5 containing V3’s contents. V4 remains in the history and is still viewable. Nothing is deleted so a revert itself can be reverted later. The revert confirmation modal lists the child artifacts that will be impacted so you can confirm the downstream scope before proceeding.⚠️ Known limitationsRevert unavailable for some sub-configurations: plugin utterances, certain Data Type sub-configs, plugin triggering configuration, and slot resolution strategies inside Conversational Processes are versioned and viewable, but cannot be reverted today. Agent Studio surfaces inline flags where these limitations apply. Support for revert on these items is planned as a fast follow. Drafts are not versioned: Version History applies only to published assets. Platform updates are recorded: When Moveworks applies schema migrations or other platform changes to an asset, those updates appear as versions attributed to a Moveworks administrator. Version numbers can advance without a developer publish. No side-by-side diff: To compare two versions, open each one. A diff view is planned for a future release. No staged testing of drafts: You cannot test an unpublished Conversational Process in a staging mode that prevents immediate replacement of the live asset in this release. Staged testing is planned for a future update. One-asset revert only: There is no batch revert and no cross-asset activity log in this release.📌 Notes for developers and adminsEvery publish is recorded with an author and timestamp. Consider adding a descriptive commit message when publishing to make history easier to scan. Because reverts create new versions rather than deleting history, you can always traverse and restore any prior state. Review the revert confirmation modal carefully — it shows child artifacts that will be affected so you can understand impact before proceeding.📚 Learn moreDetailed documentation and usage guidance is available in the Agent Studio docs. If you have immediate questions or feedback, please post them in the community forum and our team will respond.Thanks,The Agent Studio Team 

We’re expanding Configuration Delete in Moveworks Setup, giving admins more control to remove configurations that are no longer needed.Starting August 25, 2026, Configuration Delete will be available for 10 additional configuration types, making routine configuration cleanup more self-service and reducing the need to contact Moveworks Support. 🧭 What’s new?You can now delete the following configurations directly from Moveworks Setup:Connectors SSO Chatbot User Identity Forms Software Access Live Agent Handoff Permission Rules Mirror Permissions Channel ResolverThis expands on the existing delete capabilities available for Enterprise Search (Max Capacity), Rich Ticket Filing (RTF), and Ticket Workflows.Where applicable, Moveworks Setup checks whether a configuration is referenced by other configurations before allowing deletion. If dependencies are found, you’ll be prompted to remove those references first before proceeding with the deletion. 🌟 Why this mattersConfiguration cleanup is a common need during implementation and after go-live, and many of these tasks previously required assistance from Moveworks teams. With expanded Configuration Delete, admins can now handle more routine cleanup directly in Moveworks Setup, including:Cleaning up configurations created during implementation and testing Removing configurations that are no longer in use Managing routine configuration cleanup directly from Moveworks Setup, reducing the need to contact Moveworks Support ✋ What to know before you deleteThe impact of deletion varies by configuration type. Please review the confirmation message and associated impact carefully before proceeding.Connectors A new connector cannot currently be created with the same name as a previously deleted connector. If needed, use a different connector name. Deletion may be blocked if the connector is referenced by another configuration that cannot yet be deleted through Moveworks Setup. If you’re unable to resolve the dependency, please contact Moveworks Support for assistance. Connector references defined through DSL configurations are not automatically detected. Review the DSL Configurations to Review before deleting a connector. User Identity User Identity deletion is available only for organizations that are not yet live. Deleting User Identity immediately removes all ingested users, including manually created users. Manual users are automatically added back within approximately 1 hour. User-associated data is permanently removed within 24 hours. Access to Moveworks Setup will be temporarily unavailable after deletion. Once manual users have been restored, admins can sign in using the magic-link login. If there are no manual users configured, admins will not be able to regain access through the magic-link flow. Verify that the required manual users are configured before proceeding. SSO SSO deletion is available only for organizations that are not yet live. Deleting an SSO configuration immediately disables sign-in through that identity provider. Admins can continue to access Moveworks Setup using the magic-link login, provided an eligible manual user is available. Chatbot Deleting a Chatbot configuration removes the associated chat platform. Users will no longer be able to access the Assistant through that surface. The default Web chatbot configuration provided by Moveworks cannot be deleted through Moveworks Setup. If you need to delete this configuration, please contact Moveworks Support for assistance. Forms Deleting a Forms configuration permanently removes all associated indexed forms data within a few hours. Permission Rules Deleting Permission Rules may immediately affect access to content from Knowledge Bases, Files, or Max Capacity, depending on the access controls configured for that content. Mirror Permissions Deleting a Mirror Permissions configuration immediately stops permissions ingestion for the associated ServiceNow Knowledge Bases or forms. Software Access Deleting a Software Access configuration means the associated software entity can no longer be used for software provisioning. Live Agent Handoff Deleting a Live Agent Handoff configuration makes the associated live-agent handoff unavailable immediately. Channel Resolver Deleting a Channel Resolver configuration stops channel resolution for the associated Slack channel.  🚨 Important NotesConfiguration deletion is permanent and cannot be undone. Associated configuration and data may be permanently purged as part of deletion. Before confirming, verify that you have selected the correct configuration and understand the downstream impact. Config Change History and SIEM logging for these delete actions are not yet supported. We plan to add this capability in future. 📚 Learn moreFor detailed guidance, see:Configuration Delete DSL Reference Guidance Reference Configuration Locator Have questions or feedback? Please post them on our community forum where our team will provide appropriate assistance. Thank you,Moveworks Setup Team

We are targeting September 9 for the Basic tier release of GPT-5.4, at which point all remaining customers will be upgraded. We adjusted the original release schedule to address plugin behavior caused by GPT-5.4 in the Plugin Duplicate Behavior Improvements update.Note: The Plugin Duplicate Behavior Improvements are already live in the Frontier and Standard tiers. On September 9, both the behavior improvements and GPT-5.4 will roll out to the Basic tier.Current status of Tiers:Frontier: GPT-5.4 and Plugin Behavior Improvements release Standard: GPT-5.4 and Plugin Behavior Improvements release Basic: GPT-5.2 (Will upgrade on 9/9 to both GPT-5.4 and Plugin Behavior Improvements release)Additional details are available in the following resources:Plugin Duplicate Behavior Improvements GPT-5.4 Upgrade to the Moveworks Reasoning Engine Reasoning Engine Upgrade Program  

Hi Moveworks Community! 👋Effective 7th August 2026, we've fixed all issues and made improvements to the New User Identity Journey in Moveworks Setup. Here's what's now better:Configure Source Mapping ScreenYou can now map internal fields using DSL mappings or JSON-based mappings (via the JSON editor) Edit pre-configured user_id_info fields (used for identity plumbing)Add a new user_id_info field (used for identity plumbing) -- especially useful for cross-mapping usecases (ex: I want to set the chat platform as web assistant for all users that are ingested from ServiceNow)  MS Graph comes pre-configured with default filters and attribute lists — so you get the attributes you need without extra setup   More fields are available for mapping, including user_id_info fields (user_email), password metadata (password_meta_info), and others.   Override Mapping ScreenYou can now map internal fields that weren't available before:user_id_info.user_email geocodes employment info field timezone password metadata manager resolver field   Test with User ScreenAll attributes now show in the final user profile — both system and custom attributes Geocodes now have a preview so you can see the data before your users are ingested   System attributes are grouped by integration source, so you know where each piece of data comes from for a sample user   All other internal fields are visible during testing, so you can verify everything works before going live▶️ Learn more Detailed Help Doc here. DSL reference for mappings (used in Configure source mapping and Override field mapping screens)Thanks,The Moveworks Setup Team

Starting today, Agent Studio’s generate_text_action and generate_structured_value_action use gpt-5.4-mini by default, replacing gpt-4o-mini.This brings a more capable default to common LLM Action tasks such as summarizing and comparing documents, generating content, classifying information, and extracting structured data. Explore OpenAI’s GPT-5.4 mini evaluations.See the LLM Actions documentation for usage guidance, supported models, and regional availability.If you have any questions, please drop a comment in the thread below!

What's newWhen a user accepts an attestation—a user acknowledgment form shown based on attestation form that is configured, the tracking of these interaction will be now available in the Data API.You can use this data to report on:Who accepted the attestation Which form they attested to When they accepted itThis change is not merged yet and will be added to Data API by 27th August What you'll seeAttestation acceptances appear on the interactions endpoint with the following fields:Field Value type INTERACTION_TYPE_USER_ATTESTATION actor user detail.detail Name of the attestation form, for example Acceptable Use Policy created_time When the user accepted the attestation  Conversation recordsA corresponding record also appears on the conversations endpoint with:type = CONVERSATION_TYPE_USER_ATTESTATIONAttestations happen outside a normal chat. This conversation record exists only to ensure that each attestation interaction remains linked to a conversation through conversation_id. Reporting note: If you track overall conversation or interaction volume, filter out these attestation types so your existing engagement metrics remain unchanged. 

We've released the Button-Click Response Language Fix model upgrade to Standard customers.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.Read more about the release here.Learn more about our model upgrade program here.

We've released the Plugin Duplicate Behavior Improvements model upgrade to Standard customers.When a plugin action runs in the background (e.g. creating a record or sending a confirmation), Moveworks briefly pauses the model while it waits for the result. On GPT-5.4, that pause could sometimes cause the model to run the same action a second time instead of waiting — creating duplicate side effects. We rewrote the instruction the model receives during that wait so it clearly understands the result is still coming and should not retry.Read more about the release here.Learn more about our model upgrade program here.

We're rolling out an improvement that makes plugin actions more reliable. In some cases the assistant could run the same plugin action more than once in a single request, occasionally producing duplicate results. This update significantly reduces those duplicate executions, so an action runs once and returns a single, clean response.Planned Release Dates by TierFrontier: 8/13Standard: 8/19Basic: 9/9What's improvingThe assistant is now much less likely to re-run a plugin action that's already in progress, giving you a single execution and a single response per action.Sample Duplicate Plugin ActionHow you can verify this ML upgrade:Once the update is live in your test environment, send a message that triggers a plugin which previously returned duplicate action responses. The assistant should now return a single response. Note that the issue happened sporadically, so you will want to test many times to ensure that the expected result is returned. Read more about the release here.Learn more about our model upgrade program here. 

Agent Studio didn't look or feel like the rest of Moveworks, and new builders hit friction in their first session: plugin names forced snake_case, validation only fired when you clicked Validate not after you’re done editing a field, abandoning a new plugin left an empty draft behind in the library, etc. The Facelift moves Agent Studio onto the Moveworks design system and fixes that friction.Here are some of the improvements:All icons have been swapped Background colors have changed Modified Typography Spaces are allowed in your plugin, actions, etc names. No more get_me_cool_mw_swag users can now name it Get me cool mw swag   Assets get a free-form display name. The snake_case name that pro-code references derives from it on save, and the editor shows it as a read-only technical-name preview.    Closing an asset will warn you if you haven’t saved it   Name and description validation fires when you leave a field

Hello, Moveworks Community,We’ve added a new field to the Moveworks Data API that makes the Bot Friendly Name configured in Moveworks Setup available through the API.Starting today, the /interactions API will capture this value in the platform_name field. This allows you to capture interactions happening on specific platforms.  To view the Bot Friendly Name configured for your chatbot, navigate to Moveworks Setup → Manage chat bots → Bot friendly name 

OverviewMoveworks is simplifying the Setup experience by removing configuration settings that are still displayed in Moveworks Setup but no longer affect how your instance behaves. The first set of these settings has now been removed. This cleanup is ongoing, and further updates will be shared as they roll out.What's ChangingThree settings that no longer control any functionality have been removed from Setup:Access Account — "Time waited before delivering link" and "Time waited before closing the ticket" Channel Resolvers → Channel Settings — "Enable skill in dry-run mode" (under Additional Controls)These settings were no longer connected to any active functionality, so their values had no effect regardless of how they were configured. You may notice they are no longer visible on these pages. What Stays the SameYour Moveworks experience is unchanged. Because these settings were not driving any behavior, their removal has no impact on how your assistant operates, and no existing configuration is affected. All other settings on these pages continue to work exactly as before. Required ActionsNo action is required. This cleanup is still in progress, and we'll share further updates as additional settings are reviewed and removed. If you have any questions or encounter any issues, please file a case through the Now Support portal.

We've upgraded the LLM Actions you already use, generate_text_action and generate_structured_value_action, with a boost in performance and a batch of powerful new capabilities. Best of all, it's a drop-in upgrade. Everything you've already built keeps working exactly as before, with nothing you need to change. ⚡ Better performance, no work requiredYour existing Compound Actions and Conversational Processes now benefit from improved model quality and efficiency automatically, especially on reasoning-heavy tasks. Same inputs, same outputs, better results.✨ What's new📄 File input Pass documents straight into the model, no preprocessing required. Supports PDFs, spreadsheets (Excel/CSV/TSV), rich documents (Word/RTF/ODT), presentations (PowerPoint/Keynote), and a wide range of text and code formats. 🎞️ Images and files together Combine images and files in a single request, and pass multiple of either as a list, from a single List[File] slot or mapped from separate File slots: file: [data.contract, data.addendum] 🌐 Web search Turn on enable_web_search to let the model pull live information from the web into its context instead of relying only on its training data. Want to keep it focused? Optionally scope results with web_search_allowed_domains or web_search_blocked_domains (up to 100 domains each). Available on all models except gpt-5 with minimal reasoning. 💡 TipFor image and file inputs, we recommend using gpt-5 or newer for the best results.🛠️ What you can build- OCR and document Q&A- Comparing multiple files (for example, contract vs. addendum)- Structured extraction from receipts, invoices, and forms- Answering questions that need up-to-date, real-world information🛡️ A note on safe useWeb search and file input let the model read content from outside sources. When designing flows that mix sensitive data, external content, and outbound actions, follow the security guidance in the docs to stay protected against prompt-injection risks.📖 Full details, examples, and the model reference: https://docs.moveworks.com/agent-studio/actions/llm-actions 

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

🎉Coming Soon: BriefMe Multimodal Understanding for PDFs. 🎉We're excited to share that an important upgrade to BriefMe will be available early-mid August! What is BriefMe Multimodal Understanding for PDFs?BriefMe can now "see" and interpret the image elements inside uploaded PDFs. Instead of just reading the raw text, your assistant can now contextually understand these types of images - pictures, charts, tables, and complex diagrams. This means you can upload visually enriched files and have a seamless, more accurate conversation with the assistant about the document. Who it’s for: Initially, this feature will be available to BriefMe (Slack/Teams) users in US, CA, and EU regions. In the coming months, we plan to make it available in all other regions. Also, we plan to extend Multimodal Understanding to DOCs and PPTs in the coming weeks. What this unlocks:Process Visual Data: Effortlessly extract answers from trend lines, stock curves, and complex tabular images. BriefMe can perform cell value lookups and accurately interpret X/Y plots. Complex Diagram Interpretation: Process flowcharts, IT architecture diagrams, and org charts are now fully readable. BriefMe understands blocks, directional arrows (top-down, left-right), dotted lines, and color schemes. Cross-Image Analysis: Upload multiple visual PDF files at once—like a generic process flow PDF and a specific departmental org chart PDF — and ask questions that require connecting the dots between images across files. Multilingual Support for Images also: We currently support multilingual abilities for text. We are extending that ability for images as well. We will be able to analyze and summarize visual flows even if the embedded text is in a non-English language. (For example, uploading a Spanish chemical plant flowchart and asking for an English summary). A few ways you can use this feature:HCM & HR: Upload a company org chart to instantly analyze reporting structures, or upload a complex holiday calendar PDF to filter mandatory vs. optional dates. IT & Engineering: Upload an IT support tier diagram to find the right escalation path, trace data paths in architecture diagrams, or even upload a PDF document with screenshots of code to get rewriting suggestions. Finance: Upload a chart from an annual report and ask BriefMe to calculate specific investment growth over time based on the trend line. Marketing: Upload a slide deck in PDF format and extract key insights from the entire deck.  Learn more here. Read how to get started here. Questions? Drop them in this thread! Our team and the broader community will jump in. Once you start using Multimodal Understanding for PDFs, we'd love to hear from you! 

We’ve rolled out an improvement to the AI Assistant that ensures a smoother, more natural experience for your non-English speaking users. Previously, when users conversed with the assistant in their preferred language, they would occasionally see English phrases during system-guided moments—such as status updates (e.g., "Filing your ticket..."), task confirmations, or live-agent handoff messages. This happened because the assistant was instructed to repeat those specific phrases verbatim.We have updated the AI Assistant's logic so these system phrases are now dynamically translated into the user's active conversation language.The Benefits A Seamless Localized Experience: Users will no longer see abrupt, untranslated system messages. Higher Clarity & Trust: Key information in the chat are now fully readable and clear to non-English speakers. Proven Accuracy: In our evaluations of previously affected conversations, the assistant successfully localized approximately 90% of these system phrases. This update is fully automated and requires no actions from admins or users.Note: This update is rolling out in a phased approach. Refer to this article for timing. A very small subset of fixed workflow status messages follows a separate system path and is not covered by this specific update, but the vast majority of conversational phrases will now be fully localized.

The Enterprise Search App will get smarter about the sources of your answers. It will now recognize the kind of question you're asking and give extra weight to the systems most likely to have the answer — so the most authoritative source rises to the top. Ask about a customer's ARR and Salesforce results lead; ask for a teammate's latest message and Slack comes first; ask about a bug fix and the relevant GitHub PR is front and center. For broad questions that could live anywhere, Search will keep its existing ranking — applying this new source awareness only when it's confident it will help.What this means for you: Even more relevant results — answers from the most authoritative system rise to the top. Reach the right answer with less scrolling across results. Works across all your connected systems, with minimal impact on search speed.This update will be rolled out by July 31, and requires no action from admins or end users. You'll simply notice even sharper results. 

Moveworks Enterprise Search now offers the Max Capacity journey for connecting your content at scale, generally available to all organizations. You will find it in Moveworks Setup under Search → Configure Search → Max Capacity. What Max Capacity offers, across nine systems (Box, Confluence Cloud, Google Drive, Outlook, ServiceNow, SharePoint Online & OneDrive, Slack, Unily, and Zendesk):Up to 100 million documents per connector. Automatic connector validation during setup, so access requirements issues are caught early. A single guided setup journey that uses your existing identity and sets up permissions for you, so there is no extra configuration to setup. Permission ingestion on every indexed connector, so employees only see content they are allowed to see. Live search on SharePoint & OneDrive, Slack, and Outlook — results are fetched from the source in real time, with nothing stored in Moveworks. Private-content search on Google Drive and Box. An Audience configuration that sits on top of mirrored permissions to roll out content in phases to your employees.Important Callouts:Identity configuration: the Max Capacity journey sets up identity automatically only if your organization already has an identity configuration and its joining key resolves to email. If you don't have an identity configuration yet, or you identify users by a non-email attribute (for example, an employee ID) that isn't mapped to email, please set up the identity configuration for the new connector manually — see Configure User Identity. Ingestion schedule: ingestion begins about 12 hours after you save a configuration; please allow 18-24 hours before testing search results. Nomenclature: in the Connectors page these connectors may currently show a "(Next Gen)" label. We'll be renaming it to "Max Capacity" this week.For new setups on any of the nine systems Max Capacity supports, we recommend the Max Capacity journey going forward.Each connector's setup guide lists its specific capabilities — review the guide for the system you're connecting before you start.Learn more:Choosing Your Journey: https://help.moveworks.com/ai-assistant/search-connectors#choosing-your-journey Max Capacity Setup: https://help.moveworks.com/ai-assistant/max-capacity-setup Per-connector setup guides: SharePoint and OneDrive ServiceNow Google Drive Box Confluence Cloud Slack Outlook Unily Zendesk Request a connector or share feedback: https://community.moveworks.com/ideas

MCP Workspace is going into controlled availability!You can connect MCP servers and bring more of the tools your team already uses into the assistant. That opens up a lot of useful stuff to build.Want to be considered? Sign up here.

Today we updated the Standard tier to GPT-5.4.Read more about the GPT-5.4 upgrade to the Moveworks Reasoning Engine here. Read more about the model upgrade program here.

Hello Moveworks community,We've improved how ambient agent notifications are represented in the Data API.What's changingAmbient agents that deliver plain-text notifications will now be correctly categorized in the Data API /conversations entity as CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION, with use-case details (usecase_id, usecase_name) populated.Previously, these plain-text notifications were not classified under this type and instead appeared as CONVERSATION_TYPE_UNSPECIFIED_SYS_EVENT without use-case details — making it difficult to identify and report on them.What you'll noticeAn increase in CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION volume. A corresponding decrease in CONVERSATION_TYPE_UNSPECIFIED_SYS_EVENT for the same records. Populated use-case details for these notifications going forward.Things to keep in mindForward-looking only — this applies from the release date onward. Historical data cannot be backfilled. If you have filters built on CONVERSATION_TYPE_UNSPECIFIED_SYS_EVENT or that count CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION, you'll see a one-time shift on the release date (starting today) . This is the intended correction, not an anomaly. Plain-text notifications contain no interactive elements, so only "notifications sent" counts are available — there is no click/interaction tracking for these conversations.

Hello Moveworks community,  Any Setup configuration that reads from or writes to an external system needs to point at a registered connector. Until now, most configurations let you pick that connector from a dropdown of your registered connectors — but a handful still asked you to type the connector name in as free text.That inconsistency was more than cosmetic. Free-text entries weren't validated until runtime, so a small casing difference, a typo, or a connector that had since been renamed would pass silently at save time and then fail later — causing ingestion failures and, in some cases, bot outages that were hard to trace back to the source.What's changedWe've standardized connector selection on the dropdown pattern everywhere. The following four configurations now use the same validated connector dropdown as the rest of Setup:- User Identity → Advanced settings → Bot account- User Identity → Advanced settings → Manual user management- Triage → Model retraining- Triage → Metadata cacheYou now select from your registered connectors instead of typing a name.What this means for you- No more silent failures — the connector is validated when you save, not at runtime. Typos and casing mismatches are eliminated.- Rename-safe — because configurations reference the registered connector itself, renaming a connector no longer breaks these configs.- A consistent experience — connector selection now looks and behaves the same across every Setup surface.Do I need to do anything?No. Your existing values were automatically migrated to the new dropdown — there's no action required and no interruption to your current configurations. Next time you open one of these pages, you'll simply see the connector dropdown in place of the free-text field.New connector selection   

Hello Moveworks Admins,We’re excited to announce that Self-Serve Validation Failure Alerts will be available in Moveworks Setup on 6th July 2026. This release introduces enhanced validation alerts for Users and Forms resources, giving admins greater visibility into ingestion validation failures along with the ability to safely override certain validation failures directly from Setup when appropriate. ▶️ Validation OverrideTo help protect against Large Data Changes (LDCP), Moveworks performs implementation validation checks on ingestions to detect significant or unexpected changes in data. For e.g., if the number of users decreases by more than a threshold compared to the previous ingestion, a validation alert is generated and the ingestion cannot proceed until the issue is resolved or the change (if expected) is overridden by Moveworks FDEs.A validation override is used when a validation alert is triggered, but the detected change has been reviewed and confirmed to be expected. Overriding the alert allows the ingestion to proceed and establishes the latest changed data as the new baseline.Note: Only override a validation alert after confirming that the underlying data is accurate and that the detected change is intentional. A validation override is irreversible—the updated ingestion state becomes the new baseline and cannot be undone. If the alert indicates an unexpected or unintended change, the underlying issue should be investigated and resolved instead. 🌟 Key BenefitsIdentify validation failures with detailed alert descriptions and actionable guidance. Safely override supported validation failures, with mandatory justification for every override action. Access resolved alerts to review override details, including the user who performed the override. Explore common causes and recommended actions to quickly troubleshoot alerts. 🧭 What’s New?1️⃣ Enhanced Validation Alerts: Moveworks now provides detailed validation alerts for common ingestion issues across Users and Forms, including:User Identity Significant change in user records Significant drop in user attributes Significant change in user record IDs Duplicate user records Schema validation errors Zero users ingested Record uniqueness failures Forms Significant drop in forms Significant drop in form field options Each alert includes a detailed description to help you understand the issue and determine whether the change is expected or requires investigation.2️⃣ Self-Serve Override FunctionalityFor supported validation failures, admins can now override the alert directly from Moveworks Setup by providing a mandatory justification. Override is available for:Significant change in user records Significant drop in user attributes Significant change in user record IDs Significant drop in forms Significant drop in form field optionsNote:If the change is expected, selecting Override accepts the current ingestion as the new baseline and resumes processing. If the change is unexpected, select Troubleshoot to investigate and resolve the underlying issue instead. 3️⃣ Redesigned Alerts ExperienceThe Alerts page has been redesigned to make validation failures easier to understand and act upon.New Impact columnInformational – An issue was detected, but Moveworks continues serving users from the previous successful ingestion. These alerts do not require an override and automatically resolve once the underlying issue is fixed. Blocking – Ingestion has been paused because a validation rule detected a significant or unexpected change. Resolve the issue or override the alert (where supported) to continue.Additional UI improvements include:Improved the alert screen with a more intuitive and streamlined user interface. One-click access to troubleshooting guidance and recommended resolution steps. Integrated Override action for supported alerts Renamed Archived Alerts section to Resolved Alerts Moved the Acknowledge button within the alert details dialog ✋🏻 Important CalloutsValidation Failure Alerts are currently available only for Users and Forms resources. Override is available only for supported validation failure types. Validation failures such as duplicate users, schema validation errors, zero users ingested, and record uniqueness failures require troubleshooting before ingestion can continue. Override actions are permanent and cannot be undone. After a successful override, the alert is moved to the Resolved tab. The new data baseline is accepted after the next successful ingestion. Have questions or feedback? Please post them on our Community Forum, where our team will be happy to assist you. Thank you,Moveworks Setup Team

We've released the Improvements to Bold Text in Responses model upgrade to Standard customers.Web chat responses used to over-apply bold — emphasizing IDs, ticket numbers, dates, metrics, and whole phrases of prose. When everything is bold, nothing stands out, and screen readers don't announce bold at all, so emphasis was lost for users relying on them. We replaced the permissive bolding behavior with a strict allowlist that treats bold as a structural signpost (headings and short run-in labels) rather than an emphasis tool. In a 250-sample side-by-side evaluation on real production traffic, this reduced inappropriate bold by ~88% (from 5.15 to 0.61 spans per response) with zero regressions. The result is cleaner, more scannable, and more accessible responses in web chat.Read more about the release here.Learn more about our model upgrade program here.