How Moveworks Became the AI Front Door to ServiceNow

1. The Old Enterprise User Experience

Enterprise software assumes users understand organizational structure.

To solve a problem, an employee often has to know:

• which portal to open;
• which request type to choose;
• which department owns it;
• which keywords to search;
• which form fields matter.

The organization understands its own systems.

The employee just wants an outcome.

2. Moveworks Reversed the Interface

Moveworks let users start with natural language.

The system could interpret intent, search enterprise knowledge and connect to the appropriate system or action.

That creates an AI front door.

3. ServiceNow Already Had the Back End

ServiceNow had the other half:

• service catalogs;
• workflows;
• approvals;
• enterprise integrations;
• user/role context;
• audit trails.

The combined architecture is straightforward:

4. Close in December 2025

ServiceNow completed the acquisition on December 15, 2025. [S33]

At close, Moveworks had 5.5 million employee users and around 250 mutual customers with ServiceNow.

This mattered because the integration did not begin from zero. Many enterprises already used both products.

5. EmployeeWorks

In 2026, ServiceNow positioned EmployeeWorks as the AI front door for employees, combining conversational experience with enterprise workflow execution. [S18]

This turned the acquisition logic into a product strategy.

6. Otto

ServiceNow then introduced Otto in May 2026 as a unified AI experience across Now Assist, Moveworks and AI Experience. [S19]

That created a hierarchy:

7. Why Owning the Front Door Matters

AI assistants threaten traditional SaaS navigation.

If users stop opening individual applications, the assistant can decide which service gets called underneath.

That creates a new form of platform power.

ServiceNow therefore needs a strong native assistant.

But it also recognizes that customers may prefer ChatGPT, Gemini or other interfaces.

That is why Action Fabric is equally important: ServiceNow can expose governed actions into other front doors. [S46][S47]

8. The Strategic Resolution

ServiceNow does not have to choose between:

• owning the front door;
• being the action layer behind someone else's front door.

It is building both.

9. Search Reached Information Before Execution Could Begin

An employee's question may need several sources before the responsible action is clear. Search and conversational interpretation can reduce the effort of locating that information. But an answer still needs to respect the user's access, and finding relevant content does not establish a right to change a record.

The acquired capability was valuable because it addressed this first stage of the journey. Combining it with workflow execution could connect a request to a permitted action without forcing the employee to navigate the entire application landscape. The connection remained a product and implementation task after corporate ownership changed. [S33]

10. Context Had to Survive the Boundary Between Products

A front door can fail even when its individual answers are accurate. If the employee must repeat the request after it reaches a service team, much of the apparent convenience disappears. A useful handoff retains the relevant identity, task and permitted information.

It also limits unnecessary context transfer. A confidential HR request should not expose unrelated details merely because a general assistant initiated it. The architecture needs a coherent journey without making every participating system an unrestricted viewer of the same information. That balance is more demanding than placing a common conversational interface over separate tools.

11. External Assistants Made the Screen Less Exclusive

An enterprise may already use an assistant supplied by a cloud, collaboration or model provider. ServiceNow cannot assume that every request will begin in its own native interface. The Action Fabric partnerships address a complementary route: external experiences can invoke supported ServiceNow actions. [S46][S47]

The commercial logic is to remain useful where execution and control are needed, even if the user begins elsewhere. The constraint is that the integration has to exist and work for the intended task. A broad partnership is not equivalent to unrestricted interoperability with every external tool or every customer system.

12. The Adoption Test Shifted From Conversation to Completed Service

An attractive interface can increase interactions without reducing the work left unresolved. The stronger evidence is a recurring pattern in which employees reach the right service, receive a useful result and do not need to reconstruct the same request elsewhere.

That places operating quality at the center of the acquisition thesis. Search relevance, authorization, execution and escalation need to work together. Moveworks supplied an important part of that system; it did not make the remaining pieces unnecessary. The distinction is why the acquisition should be explained as capability combination rather than a single transaction that instantly solved enterprise usability.

Five Decisions That Changed the Business

1. Add a conversational and enterprise-search capability to an established workflow platform.
2. Complete ownership before treating the acquired company as part of the portfolio.
3. Develop EmployeeWorks around the employee's route into cross-system work.
4. Introduce Otto as a broader experience without confusing it with the acquired legal entity.
5. Support selected external entry points while retaining a role in governed execution.

Then vs. Now

What Most People Miss

Moveworks solved a problem ServiceNow's workflow depth did not automatically solve: how to make complicated enterprise systems feel simple to a normal employee.

The acquisition transformed ServiceNow's AI strategy from "put AI inside our apps" toward "let users ask for outcomes, then let the platform find and finish the work."