EmployeeWorks & ServiceNow Otto

Why ServiceNow Bought Moveworks

Moveworks had built:

• an enterprise AI assistant;
• enterprise search;
• a Reasoning Engine;
• broad employee adoption across customer organizations.

At the December 2025 acquisition close, ServiceNow said Moveworks had 5.5 million employee users and approximately 250 mutual customers using both platforms. [S33]

The strategic fit was unusually direct:

EmployeeWorks

EmployeeWorks is the solution layer focused on employee interaction.

Its purpose is to create one AI entry point across enterprise applications.

The user should not need to know whether the final action runs in:

• ServiceNow;
• an HR system;
• an ERP;
• a collaboration platform;
• another SaaS system.

ServiceNow Otto

Otto is broader than EmployeeWorks.

It is the unified AI experience across ServiceNow, designed to bring together:

• conversational interaction;
• search;
• AI agents;
• workflow actions;
• enterprise context.

Otto should therefore not be treated as a renamed Moveworks company.

Moveworks is the acquired entity and technology base.

EmployeeWorks is an employee-facing solution.

Otto is the unified AI experience architecture.

October 2026 Evolution

By October 2026 ServiceNow extended EmployeeWorks so employees could build and customize AI agents, while developers gained ToolSmith for creating enterprise AI tools. [S55]

This moves EmployeeWorks beyond search and request intake toward a user-created AI work layer.

Front Door vs System of Action

A front door without execution can become another chatbot.

ServiceNow's differentiation depends on connecting the interface to:

• workflows;
• permissions;
• systems of record;
• AI specialists;
• governance;
• audit trails.

That creates a full loop:

Distribution Risk and Opportunity

The front-door position is contested by:

• Microsoft Copilot;
• ChatGPT;
• Google Gemini;
• enterprise search assistants;
• collaboration tools.

ServiceNow's answer is twofold:

1. own a strong native interface through Otto/EmployeeWorks;
2. expose ServiceNow actions headlessly into external assistants through Action Fabric. [S46][S47]

This means ServiceNow can still own execution even when it does not own the screen.

The Employee's Problem Is Not the Enterprise's Organization Chart

A person trying to complete work may not know whether the responsible application belongs to IT, HR or another team. Asking the user to identify the correct system shifts the coordination burden onto the person least equipped to navigate it. A conversational front door can reduce that burden by starting with the intended outcome.

The difficult part begins after the request has been understood. The system must determine the user's identity, the appropriate knowledge source and whether an action is actually available. A fluent answer can hide those unresolved questions. The front door becomes operationally valuable only when the request reaches the right service and returns a result that the employee can use.

Search and Action Need Different Evidence

Search retrieves information that may help answer a question. Action changes something: access, a case, an approval or another business record. The second operation needs stronger guarantees about identity, scope and completion. Finding a policy that describes access does not itself grant that access.

Moveworks' conversational and search capabilities therefore complement rather than erase the workflow layer. The acquisition supplied a way to understand and reach enterprise information. The combined proposition adds governed service execution, with the original source systems and customer policies still setting boundaries. The December 2025 completion announcement establishes the company relationship; it does not mean every later product name is a synonym for the acquired company. [S33][S42]

User-Created Agents Add a New Ownership Question

The October 2026 EmployeeWorks announcement extended the direction toward employee-built agents and developer tools. That can reduce the distance between noticing a recurring task and creating assistance for it. It also creates a maintenance responsibility: someone must know which tool the agent uses, which permissions apply and what happens when the process changes. [S55]

An employee-created agent is not automatically a separately governed enterprise application. The organization needs a route from useful experimentation to supported operation. Otherwise the front door can accumulate abandoned automations whose apparent convenience depends on credentials or assumptions that nobody owns.

Distribution and Business Value

The conversational interface can influence which system receives the next request. That makes the front-door position commercially important, but enterprises may use several interfaces. ServiceNow's headless-action partnerships acknowledge that work can begin outside its own screen. [S46][S47]

The economic opportunity is consequently broader than capturing every conversation. It includes remaining useful as an execution and control layer wherever the conversation starts. A customer still needs to assess actual supported integrations, completion quality and the effort of maintaining that connection. Neither a partnership announcement nor a count of interactions proves a completed business outcome.