Recently active topics

Key DatesFrontier: September 2 2026Standard: September 8 2026Basic: September 10 2026Learn more about our model upgrades here.We’re upgrading the AI Assistant’s toxicity filtering to consider the full context of a conversation rather than evaluating content in isolation. This provides a more accurate understanding of user intent and helps identify genuinely harmful content. The upgrade also reduces false positives, allowing safe conversations to continue without unnecessary interruption. Administrators can review the configuration steps for more information: https://help.moveworks.com/agent-studio/agentic-ai/conversational-safeguards-assistant/configure-moveworks-toxcity-filter#configuration-steps

How are we improving the product?Teams currently need to configure employee communications separately across EmployeeWorks and Moveworks.A unified API will allow teams to launch a single employee communication across both surfaces together. This reduces duplicate authoring and helps employees receive consistent, timely communications wherever they work.Why is this important?A connected workflow simplifies communication management and helps organizations deliver a consistent employee experience across EmployeeWorks and Moveworks.

How are we improving the product?Managed service providers (MSPs) often serve multiple customers through a single domain-separated ServiceNow instance, where each customer’s data is partitioned into a separate domain. EmployeeWorks does not support this deployment model today.This initiative will help MSPs extend EmployeeWorks to customers within shared, domain-separated ServiceNow environments.What is included in this milestone?This milestone adds domain-level filtering for the ServiceNow connector within Moveworks. This enables the connector to operate within the intended customer domain when connecting Moveworks to an MSP’s shared ServiceNow instance.Future milestones may expand support for domain-separated deployment models.

How are we improving the product?ServiceNow customers will have a ready-to-use EmployeeWorks instance available on day one.Automated configuration synchronization from ServiceNow to EmployeeWorks will establish the required baseline configuration, reducing manual onboarding work and helping customers get started faster with a consistent setup.How does it work?Required EmployeeWorks configurations are synchronized from ServiceNow.New customers receive an EmployeeWorks instance with the baseline configuration already available.Existing AI-native customers will be migrated using internal tooling operated by FDEs.Customer impactCustomers will spend less time waiting for manual configuration and can begin onboarding with a prepared EmployeeWorks environment.

How are we improving the product?Moveworks is introducing Configuration APIs to help enterprise teams move configurations safely across environments such as DEV → UAT → Production.This provides a controlled, repeatable alternative to manually recreating configuration in every organization. It also allows teams to incorporate Moveworks configuration changes into their existing source-control, review, and CI/CD processes.How does it work?Two APIs enable the configuration promotion workflow:Export API: Exports an organization’s complete configuration as a single manifest that can be stored, versioned, and reviewed.Apply API: Compares the manifest with a target organization and adds, updates, or removes configuration to bring the target into alignment.Teams can preview the proposed additions, updates, and deletions before applying them. Apply operations are validated and atomic—they either complete fully or make no changes.Technical restrictionsPromotion applies to configuration only, not

Overview Currently, the platform’s analytics focus on user-initiated interactions with our Moveworks bot. However, as customer bots evolve to be more proactive—sending notifications and updates without direct user prompts—we lack visibility into the reach and effectiveness of these communications. To better understand the impact of bot-initiated messages, we propose the addition of analytics for proactive communications. This would provide insights into what types of messages are being sent, how frequently, and how users are engaging with them. Proposal: Implement Analytics for Bot-Initiated Messaging We request a new analytics capability to track and analyze any communication that originates from the bot, including but not limited to:• System-generated notifications (e.g., password reset alerts)• Employee communications tool messages• Creator Studio-initiated messages• Concierge or plugin-based notifications (e.g., ITSM status updates, comments)• External integration notifications (e.

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.

Updating our Reasoning Engine to GPT 5.4.

Employee Communications campaign interactions (e.g., button clicks like "Good to know!") currently do not have a Conversation Topic assigned, which causes them to log with a <nil> value in the Conversation Topic field.In Analytics, this is inflating the <nil> Topic bucket in gap/intent-failure reporting — these interactions are being counted as unresolved or ambiguous intents (or in some cases appearing to overlap with feedback-related records), when in reality they are simply acknowledgment button clicks tied to Employee Comms campaigns. This isn't limited to "Good to know!" — any Employee Comms campaign button (e.g., "Reclaim my license" for a license-reclaim campaign) would log the same way, since none of these interactions currently receive a Conversation Topic.Request: Assign a dedicated Conversation Topic value (e.g., "Employee Communications") to all Employee Comms campaign interactions, regardless of the specific button/CTA text used. This would let customers reliab

Hi Moveworks Community,I’d like to suggest a usability improvement for Agent Studio.When working with multiple open items — such as Conversation Actions, Conversation Processes, and HTTP Actions — the top tab bar can quickly run out of space. Once many tabs are open, it becomes difficult to navigate between them because there doesn’t seem to be a clear way to scroll horizontally through all open tabs.Would it be possible to add a horizontal slider, scrollbar, or another tab navigation mechanism at the top, so users can easily move across all open CA, CP, and Action tabs?This would be especially helpful when building or debugging complex workflows with many related components open at the same time.Thanks!

Description: Dear Team,I would like to understand whether Moveworks currently provides any native capabilities within the Control Center, or via API, for the following monitoring and alerting requirements. Additionally, if any of these capabilities are already available, please let us know whether they are currently being utilized by any customer.1. Outage Monitoring and VisibilityOutage Notifications: Immediate alerts when the bot, or any of its critical connected integrations, experiences downtime.Root Cause Visibility: Detailed logs indicating what failed, when the outage started, and which specific service, system, or connector was impacted.Historical Uptime Tracking: Access to historical uptime data and incident logs for reporting and audit purposes.2. Integration Credential Expiration AlertsServiceNow: Proactive notifications (for example, 30/15/7 days in advance) for expiring service account passwords or API tokens.Microsoft Graph: Expiration monitoring for Azure AD / Entra ID c

Currently our company uses content ingestion, etc. for chat, but we also use the Employee Comms feature to send out notifications/announcements to our end users in Teams. It would be ideal if anything sent through Employee Comms could become part of the Knowledge/Content within MW so that previous announcements, etc. could be accessible through chat. Specifically, when reviewing transcripts from end user conversations, I see patterns where end users ask follow up questions about specific Employee Comms/Announcements and Moveworks chat does not innately understand or have knowledge of those announcements as they function as their own “Product” within MW suite.It would be great if an end user could query those Comms and get information/answers returned in chat rather than Moveworks telling them they were unable to find an answer. We have received feedback indicating that the end users don’t understand why they would be receiving Notifications/Comms in their MW chat if they could not then

What’s changing?Moveworks is introducing a dedicated On-Prem Agents experience in the Troubleshooting Hub within Moveworks Setup. It will give admins a central place to monitor agent availability, understand the health of connected on-premises systems, and investigate issues affecting employee requests.The experience will include:Agent health overview: See which on-prem agents are connected or disconnected and identify when deployment redundancy may be at risk.System health monitoring: Review connection health for configured LDAP and REST-based systems, including systems currently experiencing failures.Active issues and alerts: Surface important agent and system connection problems with clear impact, status, and recommended next steps.These changes are designed to help admins detect on-prem connectivity issues earlier, investigate failures more efficiently, and restore affected integrations with less reliance on Moveworks Support.

What’s changing?Moveworks is introducing a dedicated Users experience in the Troubleshooting Hub within Moveworks Setup. It will give admins and partners a central place to monitor user identity ingestion and investigate issues without switching between multiple tools or relying on Moveworks teams for routine diagnosis.The experience will include:Ingestion health at a glance: See the latest ingestion status, fetched and indexed user counts, and scheduled run information.User-level investigation: Search for individual users and understand why a user may be missing, excluded, or dropped during ingestion.Clear issue identification: Surface connector, configuration, processing, and partial-ingestion issues affecting user identity data.Guided troubleshooting: Review customer-friendly explanations, likely root causes, recommended actions, and links to relevant configurations.Centralized workflow: Move from identifying an ingestion problem to investigating and resolving it within one experien

What’s changing?Triage configuration is moving into a single, guided experience in Moveworks Setup. Instead of configuring metadata, fields, model training, rollout controls, and output guardrails across disconnected pages, admins will be able to manage the Triage setup journey in one place.The simplified experience will include:Unified setup journey: Configure prerequisites, choose fields, train the model, and manage outputs through one guided flow.One source of truth for shared settings: Manage rollout mode, delivery method, ticket eligibility, and analytics settings without duplicating configuration across multiple pages.Inline validation and safer defaults: Review ticket scope before training and use built-in guardrails to prevent invalid lookback windows or confidence settings.Clearer model controls: Set confidence thresholds, rollout behavior, allowlists, blocklists, and default values after reviewing model performance.Prediction insights: Use visual insights to understand model

Admins can configure and validate user identity faster with more flexible source mappings, preconfigured Microsoft Graph settings, expanded overrides, and richer test-user previews.

What’s changing?Smart Handoff configuration is moving into a single, guided experience in Moveworks Setup. Instead of configuring one handoff across separate Handoff Settings, Display Configurations, and Live Agent Handoff modules, admins will be able to manage the experience in one place.The simplified experience will include:Unified configuration: Define the trigger, action, user-facing content, and destination in one flow.Domain-based setup: Organize and configure handoffs by domain, with support for user-attribute conditions.Simpler action selection: Configure actions such as filing a ticket, connecting to a live agent, opening a URL, sending an email, or directing users to a chat channel.Less manual configuration: Reduce reliance on hand-entered technical keys and custom DSL for common handoff scenarios.Live preview: Preview how the handoff experience will appear to users while configuring it.These changes are designed to reduce configuration errors and make common Smart Handoff u