Moveworks

Moveworks sells a single AI assistant that employees reach where they already work, with two jobs: find content across the systems a company runs, and finish the request. The homepage describes it as searching and acting across business applications, and names the search surface concretely: Slack, OneDrive, Google Drive, SharePoint, Confluence, Outlook, and 50+ others. The service-desk heritage shows in the documentation, where access requirement guides exist per system for ServiceNow, Jira Service Management, Zendesk, Freshservice, BMC Remedy, Ivanti and ManageEngine, plus identity systems (Okta, Microsoft Entra, Active Directory, SailPoint) and Workday for HR cases.

Four build paths sit behind the assistant. Tool Studio distinguishes Search for finding content, Plugins for write actions with business rules enforced, MCP for live reads and reversible actions in productivity apps, and agent-to-agent delegation. The vendor's guidance is that plugins suit mission-critical multi-step workflows and MCP suits bounded lookups, which is a useful sorting rule when scoping a first deployment.

There is no rate card. The pricing page is a form with three talking points: an ROI assessment, scalable packages, and flexible pricing tailored to a buyer's requirements. No seat price, no per-conversation rate, no tier names, no minimums. The only number on the page belongs to a Forrester study the vendor commissioned, quoted as 256% ROI and savings of $11.5M over three years, which is a claim about outcomes rather than a price.

Nothing published says how the contract is metered either, so a buyer cannot tell whether the meter is employees, resolved conversations, or a platform fee with usage on top. No contract length, renewal term or cancellation condition appears: a terms of service page under the legal path returns 404, and the privacy policy page renders only a last-updated line of December 2025 in a browser, so the legal detail a procurement team wants is not on the public site.

The interesting part of the platform for anyone wary of autonomous agents is where it stops. The Agentic Orchestrator runs each request at the lowest tier that covers it: a direct answer from context, up to three ad hoc tool calls, or a plan the user reviews before anything executes. Destructive, irreversible or broad-reach actions require explicit sign-off, and the documentation states that instructions cannot turn off plan review or the sign-off rule.

The other direction is also documented. Ambient agents run on events and schedules without anyone prompting them, which is what the marketing means by agents that act on their own. Memory is deliberately short: a new conversation starts empty and nothing carries over between sessions, with large tool results held as session variables instead of being pushed into the prompt. Both the Orchestrator and its planning behavior are marked controlled availability, reaching the Enterprise Assistant in Q1 2027, so a buyer evaluating today should ask which engine their tenant will actually run.

Moveworks is an MCP client rather than an MCP server for its own platform: an admin connects a remote server in MCP Workspace, the workspace retrieves its tool inventory, and the assistant calls those tools with the configured credentials. Authentication choice decides whose permissions apply, per-user authorization using the employee's own credentials and application credentials using the application's.

Two warnings in the documentation deserve repeating. The first is that Moveworks does not review, approve or vet MCP servers or their tools, and that a server decides which tools and guardrails it exposes, including write and destructive actions. The second is the feature's status: the marketing page for Tool Studio advertises MCP support as a way to bring any system with an MCP server into an agent's reach, while the docs put MCP Workspace in controlled availability for a limited set of customers with capabilities and limits liable to change. The documentation site itself does publish an MCP endpoint, at docs.moveworks.com/_mcp/server, but it serves documentation to AI clients and not the assistant's own tools.

The certification list is longer than most: SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001, ISO 27017, 27018 and 27701, CSA STAR Level 2, GDPR, CCPA and FedRAMP. Hosting is AWS, in named regions (US Commercial, EU, US GovCloud, Canada, Australia, UK, Japan) with data stated to remain in region, and the API reference backs that with a separate base URL per data center, warning that credentials are registered per data center. On model training the page is explicit: no customer data is used to train global generative models.

What is missing is retention. No configurable retention period or deletion control is published, and the only documented windows are platform-set, such as plugin logs reachable a maximum of fourteen days back. No uptime commitment or service credit scheme is published either, and the certification reports themselves sit behind a Whistic profile the vendor releases through an account executive rather than publicly.

The two halves of the site disagree about how much engineering a build takes. A webinar promotion on the Tool Studio page promises specialized assistants across the enterprise "all without a single line of code", and a ServiceNow press release linked from the homepage says every employee can build AI agents, no code required. The same Tool Studio page calls the build environment "a unified, low-code environment" and "a purpose-built, low-code workspace", and the developer docs bear that out: real builds use DSL rules and Data Mappers, two configuration languages with their own references, playground and operator precedence.

It fits an organization with a busy tier-1 service desk, an ITSM already in place, and chat as the default employee surface. The named customer evidence runs that way: BambooHR on ticket volume, Instacart on time to resolution, Coca-Cola Consolidated on not having to grow its service desk.

It fits badly in three cases. A buyer who needs a price before a sales cycle will not get one. A small team cannot start, because there is no self-serve path, no free plan and no published trial. Anyone who needs the platform inside their own infrastructure is out, since hosting is Moveworks-operated AWS and only a connector-side on-prem agent reaches systems in a private network. Contractual retention limits and an uptime commitment are open questions for procurement rather than documented features.

One more contract question: the site positions Moveworks as part of ServiceNow, with a homepage section describing the two "working together as one" and ServiceNow EmployeeWorks presented as built using Moveworks, so pin down which product is being licensed.