ServiceNow resolves 90% of its own IT requests autonomously. Now it wants to do the same for any enterprise

Source: VentureBeat

ServiceNow’s Autonomous Workforce Announcement

ServiceNow is handling 90 % of its own employee IT requests autonomously, resolving cases 99 % faster than human agents. On Thursday it announced the product technology it wants to use to do the same for everyone else.

Organizations have spent three years running pilots that stall when AI gets to the execution layer. The agent can identify the problem and recommend a fix, then hand it back to a human because it lacks the permissions to finish the job or because no one trusts it to act autonomously inside a governed environment.

The gap most teams are hitting isn’t capability. It’s governance and workflow continuity.

ServiceNow’s answer is a new framework called Autonomous Workforce; a new employee‑facing product called EmployeeWorks built on its December acquisition of Moveworks; and an underlying architectural approach it calls “role automation.”

From Ticketing System to AI Workforce

ServiceNow has been building toward this for two decades.

1. Ticketing system – the original platform.
2. Workflow automation engine – the next evolution.
3. Now Assist – AI layered on top of the workflow foundation over the last two years.

What’s different now is that the new approach stops treating AI as a feature sitting on top of workflows and starts treating it as a worker operating inside them. That shift—from AI that assists to AI that executes—is where the broader enterprise market is headed. ServiceNow is making a specific architectural bet about how to get there.

The three‑part announcement

Most enterprise AI assistants (e.g., Microsoft Copilot, Google Gemini) require employees to know which tool handles which problem. Moveworks—5.5 million enterprise users before the December acquisition—was built around a single entry point that routes across that ambiguity automatically.

“Over the last two years, organizations have raced to adopt AI, but in many cases that rush has created fragmented tools, disconnected AI experiences and employees bouncing between systems just to get simple things done,”
— Bhavin Shah, founder of Moveworks and SVP at ServiceNow

Why Role Automation Is Different From a Regular Agent

ServiceNow proposes a new architectural layer called role automation, which differs from the agents most enterprises already run.

• Conventional AI agents – task‑oriented: given a goal, they reason toward it and determine at runtime what they’re allowed to do. This creates problems in enterprise environments where governance, audit trails, and permission boundaries are non‑negotiable.
• Role automation – an AI specialist inherits the same access‑control framework, CMDB context, SLA logic, and entitlement rules that govern human workers from the moment it is deployed. It cannot exceed its defined scope and cannot self‑escalate privileges based on what it learns mid‑task.

ServiceNow draws a three‑tier distinction:

1. Task agents – handle individual automation steps.
2. Agentic workflows – mix deterministic and probabilistic execution.
3. Role automation – sits above both as a fully virtualized employee role with defined responsibilities and pre‑inherited governance.

The first product built on this architecture, the Level 1 Service Desk AI Specialist, handles common IT requests end‑to‑end (password resets, software access provisioning, network troubleshooting), documents each resolution, and escalates to a human only when it encounters something outside its defined scope.

“Don’t Chase Butterflies”

Alan Rosa, CISO and SVP of Infrastructure and Operations at CVS Health, has seen what happens when AI governance fails in healthcare. He manages AI deployment across 300,000 employees, where compliance isn’t optional.

“Boring is beautiful. Predictable. Stable. You have to start with responsible, explainable AI. No bias, no hallucinations, clear guardrails. Everyone understands the rules.” – Alan Rosa

Speaking at the same briefing, Rosa’s framework for scaling AI maps directly onto what ServiceNow is claiming architecturally. CVS Health was already a customer of both ServiceNow and Moveworks before the December acquisition. Rosa said the combination of the two platforms is encouraging and that the potential is “coming to life,” though CVS Health has not publicly committed to deploying Autonomous Workforce.

Rosa’s advice

• Don’t chase butterflies. Focus on gritty, unsexy, operational use cases—the ones with real ROI that impact people’s lives.
• Treat AI as a continuously evolving set of capabilities requiring dynamic (not static) testing.
• Run every AI use case through clinical, legal, privacy, and security review before it touches production.

“Static review doesn’t cut it when AI is learning and adapting. Wash, rinse, repeat.” – Alan Rosa

Rosa’s approach embeds governance in the deployment architecture from the start, rather than retrofitting it after a problem surfaces. That is precisely the claim ServiceNow makes about role automation: AI specialists that inherit existing enterprise permissions and workflow logic are structurally less likely to break governance boundaries than agents that determine their own scope at runtime.

What This Means for Enterprises

For any organization evaluating agentic AI, regardless of vendor, the practical question is simple:

Does the solution embed governance and workflow continuity into the AI’s core architecture, or does it rely on ad‑hoc permissions and post‑hoc controls?

Enterprises that need trustworthy, auditable, and permission‑aware automation should look closely at ServiceNow’s Autonomous Workforce, EmployeeWorks, and especially the role automation layer as a blueprint for scaling AI responsibly.

Question
Your AI governance lives inside your execution layer, or is it sitting on top of it as a policy document that agents can reason past?

Answer
That is what ServiceNow is trying to solve with Autonomous Workforce and EmployeeWorks, baking governance and workflow context directly into the agentic layer rather than bolting it on afterward.

For practitioners, the starting point is governance architecture, not capability. Before deploying any agentic AI, map where your permissions, workflow logic, and audit requirements actually live. If that foundation isn’t in place, no agent framework will hold at enterprise scale.

“Scale and trust go together,” Rosa said. “If you lose trust, you lose the right to scale.”