Blog/Comparisons/Article

Moveworks vs ServiceNow Virtual Agent: IT AI Compared (2026)

Moveworks is now owned by ServiceNow. How do the two IT AI products compare, where are they converging, and what should enterprises that need AI beyond employee self-service consider?

Nov 27, 2025By the Nexus team11 min read

Comparisons

Moveworks vs ServiceNow Virtual Agent: IT AI Compared (2026)

ServiceNow acquired Moveworks for $2.85 billion in December 2025, completing the largest acquisition in ServiceNow's history. What began as a comparison between two competing IT AI platforms is now a question about a single converging product — and whether its scope covers what your enterprise actually needs.

Here's an honest look at where both products stand, what the acquisition means, and where the combined platform's ceiling sits.

Side-by-side: Moveworks vs ServiceNow Virtual Agent

Dimension	Moveworks (now ServiceNow)	ServiceNow Virtual Agent
What it is	AI-powered employee self-service. Understands natural language requests, resolves known IT issues, routes the rest. Expanded to HR, finance, facilities.	ServiceNow's built-in chatbot for employee self-service. Pre-built conversation flows for ITSM, HRSD, and facilities.
AI approach	Large-scale NLU trained on hundreds of millions of employee interactions. Dynamic resolution without pre-built conversation trees.	Flow-based conversation design with AI enhancements. Pre-built topics for common ITSM scenarios. Improving with Moveworks technology post-acquisition.
Resolution method	Understands the request and resolves or routes dynamically. Doesn't require pre-defined conversation paths for known request types.	Follows pre-built conversation flows. Handles scenarios that have been configured. Routes everything else.
Scope	IT, HR, finance, facilities. Employee-facing only.	IT, HR, facilities. Employee-facing only. Deepest in ITSM workflows.
Integrations	Historically broad: ServiceNow, Jira, Okta, AD, Workday, and others. Post-acquisition, deepest investment favors ServiceNow.	Native to ServiceNow. Deepest integration with Now Platform modules. Limited outside ServiceNow.
Deployment	SaaS. Typically deployed by IT. Setup involves connecting systems and tuning.	Native to ServiceNow. No separate deployment. Activated within existing instance.
Analyst position	Listed as a Challenger in the 2025 Gartner Magic Quadrant for AI Applications in ITSM, recognized for AI assistants and enterprise search.	ServiceNow named the only Leader in the 2025 Gartner Magic Quadrant for AI Applications in ITSM for the second consecutive year.
Independence	No longer independent. Product direction serves ServiceNow strategy.	Always part of ServiceNow.
Pricing	Per-employee, typically $100–200/year. Shifting toward bundled ServiceNow SKUs post-acquisition.	Bundled with ServiceNow ITSM/HRSD licenses. No separate cost for existing ServiceNow customers.

What both do well

IT self-service. Both products handle the core use case effectively. An employee asks a question about VPN setup, password resets, software access, or HR policies, and the AI resolves it or routes it. For known request types with clear resolution paths, both deliver real reduction in ticket volume. ServiceNow has publicly reported that its AI agents now autonomously resolve 90% of internal IT requests and 89% of customer support requests, with resolution times reduced nearly sevenfold.

Employee experience. Both provide a single front door for employee requests. Instead of navigating portals, searching knowledge bases, or guessing which team to contact, employees ask in natural language and get a response. That's a genuine improvement over the status quo.

ITSM integration. Both sit natively within (or are becoming native to) the ServiceNow workflow engine. Tickets get created, updated, and resolved within the ITSM framework IT teams already use.

The convergence: what happens next

With the acquisition complete, the real question isn't which one to choose. It's what the combined product becomes.

Short-term (2026): Both products continue to operate. Moveworks retains its brand and product identity while integration work proceeds. ServiceNow has publicly committed to supporting existing non-ServiceNow customers throughout the transition. ServiceNow customers can use Virtual Agent as before.

Medium-term (2026–2027): Moveworks' NLU, agentic Reasoning Engine, and AI capabilities get absorbed into the ServiceNow platform. Virtual Agent becomes significantly more capable. The combined product handles employee self-service with better AI than either offered alone. ServiceNow cited Moveworks' hundreds of AI experts as a key driver of its AI roadmap acceleration.

Longer-term: The products converge fully. "Moveworks vs ServiceNow Virtual Agent" becomes a historical comparison. The combined platform becomes ServiceNow's unified employee AI layer.

What this means for buyers:

If you're a ServiceNow customer: You'll get the benefits of both products natively. No action required. The platform gets better.
If you're a Moveworks customer NOT on ServiceNow: This is where it gets complicated. ServiceNow has committed to supporting existing non-ServiceNow customers. But product roadmap, integration investment, and pricing incentives will naturally favor ServiceNow's ecosystem over time.
If you're evaluating both for the first time: You're evaluating one product at two different stages of convergence. The decision is really about whether you want to commit to the ServiceNow ecosystem.

What Moveworks and ServiceNow don't cover: the gap

Here's the part most "Moveworks vs ServiceNow" articles skip.

Both products are designed around the same use case: employee self-service for IT (and, to a growing extent, HR and facilities). They automate the conversation layer. An employee asks, the AI responds. That's the 10% of the problem.

The other 90% — the multi-step work behind those conversations — still lands on humans.

When an employee requests access to the analytics platform, the conversation ("Which analytics tool do you need?") is the easy part. The work behind it is harder: verifying the employee's role and clearance, checking whether their manager pre-approved analytics access, determining which license tier fits their function, provisioning credentials, updating the access log in the compliance system, notifying the security team for elevated access, and handling the exception when their department code doesn't match any approval template.

Both Moveworks and ServiceNow Virtual Agent handle the conversation. The complex work gets routed to a human.

And both products are limited to employee self-service. They don't address:

Customer-facing workflows: Customer onboarding, order processing, complaint escalation, account management.
Sales operations: Pipeline monitoring, account research, proposal generation, competitive intelligence.
Compliance: Audit execution, regulatory monitoring, exception remediation across systems.
Marketing: Campaign operations, lead qualification, content coordination.
Cross-department processes: Anything that spans organizational boundaries with different systems, rules, and stakeholders.

For enterprises where the biggest AI opportunities are inside the IT helpdesk conversation, the combined Moveworks/ServiceNow product addresses the need.

For enterprises where the biggest AI opportunities are in the work behind those conversations, or in departments beyond IT, the scope ceiling is the constraint.

Capability comparison: what the combined platform covers vs what's needed for the 90%

Capability	Moveworks + ServiceNow VA	What's needed for the 90%
Understand employee requests	Yes	Yes, plus customer, partner, and system-initiated requests
Answer from knowledge base	Yes	Answer is just the starting point, not the end
Create/update tickets	Yes	Tickets are tracking mechanisms, not the work itself
Route to correct team	Yes	Handle the work so routing isn't needed
Multi-system data validation	Limited	Validate across CRM, ERP, HR, compliance, and custom systems
Decision-making with guardrails	No	Make decisions within defined rules, escalate when uncertain
Exception handling	Route to human	Detect, adapt, and handle exceptions in real time
End-to-end workflow execution	No	Complete entire processes autonomously
Customer-facing workflows	No	Onboarding, support, account management, order processing
Sales workflows	No	Pipeline monitoring, research, proposal generation
Compliance workflows	No	Audits, regulatory monitoring, remediation tracking
Cross-department processes	No	Workflows that span IT, sales, compliance, HR, operations

When the combined Moveworks/ServiceNow is the right choice

Be direct about where it's strong.

Your primary AI goal is reducing IT ticket volume. If the conversation (the 10%) is genuinely your biggest bottleneck, and the work behind tickets is already handled well by your IT team, the combined product addresses this effectively. Years of training data, proven deployment, strong ITSM integration — and now a Gartner-recognized Leader position backing the platform.
You're committed to the ServiceNow ecosystem. If ServiceNow is your platform of record for ITSM, HRSD, and workflow management, the converged Moveworks/Virtual Agent product is the natural choice. Native integration, no additional vendor, improving AI capabilities.
Employee self-service is your primary scope. IT, HR, facilities. If these are where you need AI and you don't need customer-facing workflows, sales automation, or cross-department process execution, the scope fits.

When you need something different

Enterprises that find themselves limited by the Moveworks/ServiceNow scope tend to share a pattern: their biggest AI opportunities aren't in the conversation. They're in the work behind it. And they span more departments than IT and HR.

Most of these enterprises have already tried something. Copilot. A workflow tool. An internal build. They ran a pilot, got partial results, and are now looking for what actually completes the work — not just understands the request.

Nexus is what enterprises choose when they need autonomous agents that complete entire business workflows, across IT and every other department, with Forward Deployed Engineers embedded alongside their team.

How it's different:

Scope: Any department, any workflow. Customer-facing and internal. Sales, support, compliance, marketing, HR, IT, operations. One platform.
What it completes: End-to-end business processes. Not conversations. Not tickets. The actual work: data collection, validation, decision-making, exception handling, execution.
Service model: Forward Deployed Engineers embed with your team. They identify use cases, design agents, handle integrations, run pilots, and manage the organizational change. Not software-and-goodbye.
Integrations: 4,000+ systems. CRM, ERP, ITSM, communication platforms, custom APIs. System-agnostic by design.
Pricing: Per-agent, tied to value delivered. Not per-employee, not bundled with an ecosystem.

What it looks like in production:

Orange Group (multi-billion euro telecom, 120,000+ employees): Customer onboarding agents deployed in 4 weeks. 50% conversion improvement. ~$6M+ yearly revenue impact. 90% autonomous resolution. Also freed 40% of customer service capacity. Business team built and owns the agents.
European telecom (13,000+ employees): Spent 6 months with Copilot Studio, zero production use cases. Deployed a dozen Nexus agents. 40% support volume freed across millions of interactions.

100% POC-to-contract conversion rate. Every pilot converts because the engagement model — platform plus embedded engineers — is designed to deliver measurable value before the contract is signed.

The real decision framework

The Moveworks vs ServiceNow question is becoming moot as the products converge. The more useful question is about scope and ambition.

Question 1: Where are your biggest AI opportunities?

If they're in IT ticket deflection and employee self-service, the combined Moveworks/ServiceNow product fits. If they're in the work behind those tickets, or in customer-facing workflows, sales, compliance, or operations, you need a platform designed for the 90%.

Question 2: How many departments will need AI in the next 12 months?

If it's just IT, a purpose-built IT AI tool makes sense. If it's IT plus two or three other departments, deploying an IT-only tool means a separate evaluation for each additional department. Or you start with a platform that covers everything.

Question 3: Do you need vendor independence?

The Moveworks/ServiceNow combination ties your AI layer to one vendor's ecosystem and pricing trajectory. If procurement strategy, negotiation flexibility, or multi-vendor architecture matter to your organization, platform independence is worth considering. Nexus connects to 4,000+ systems without ecosystem lock-in.

Question 4: Do you need a partner or a product?

Deploying AI at scale is 10% technology and 90% organizational change. If you need software you can configure, the Moveworks/ServiceNow product works. If you need engineers embedded with your team who help identify the right use cases, build the agents, manage change, and optimize continuously, that's a different model.

Frequently asked questions

Did ServiceNow buy Moveworks?

Yes. ServiceNow completed its acquisition of Moveworks on December 15, 2025, for $2.85 billion in a combination of cash and stock. The deal, announced in March 2025, was the largest acquisition in ServiceNow's history. Moveworks continues to operate under its brand while integration into the ServiceNow platform proceeds.

What is the difference between Moveworks and ServiceNow Virtual Agent?

Moveworks was built as a standalone AI assistant trained on hundreds of millions of employee interactions, designed to dynamically resolve requests without pre-built conversation flows. ServiceNow Virtual Agent is flow-based, relying on pre-configured conversation topics within the ServiceNow ecosystem. Post-acquisition, Moveworks' NLU capabilities are being integrated into the ServiceNow platform, making the distinction less relevant over time.

What happens to Moveworks after the ServiceNow acquisition?

ServiceNow has stated it will support existing Moveworks customers, including those not using ServiceNow. In the medium term, Moveworks' technology — its agentic Reasoning Engine, enterprise search, and NLU — is being absorbed into the Now Platform. ServiceNow cited Moveworks' AI talent base as a key driver of its product roadmap acceleration.

Is Moveworks still available as a standalone product?

As of 2026, Moveworks continues to operate as a distinct product under ServiceNow ownership. However, the product roadmap, pricing incentives, and integration investment are now aligned with the ServiceNow ecosystem. Customers evaluating Moveworks independently should factor in the trajectory toward platform convergence.

How does the Gartner Magic Quadrant position ServiceNow and Moveworks?

In the 2025 Gartner Magic Quadrant for AI Applications in IT Service Management — Gartner's current framework for this market, having retired the traditional ITSM MQ — ServiceNow was named the sole Leader for the second consecutive year. Moveworks was positioned as a Challenger, recognized for its AI assistant capabilities and enterprise data search. Post-acquisition, Moveworks' capabilities are being folded into the ServiceNow Leader position.

Worth exploring?

If the Moveworks/ServiceNow combination handles your IT conversation layer well but your enterprise is ready to tackle the 90% behind those conversations — across every department — it might be worth a conversation.

Every Nexus engagement starts with a 3-month proof of concept tied to measurable outcomes. Forward Deployed Engineers work alongside your team from day one. You see the value before you commit.

Talk to our team — 15 minutes

See the full Nexus vs Moveworks comparison →