News: 1772148129

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

ServiceNow boasts its AI bot is resolving 90% of its own help desk tickets

(2026/02/27)


ServiceNow claims it has created an AI agent that is currently solving 90 percent of the inbound IT tickets to the company's own employee help desk.

ServiceNow said, in addition to using the Autonomous Workforce bot internally, select ServiceNow customers are testing it as well. The firm expects to have the product generally available by the second half of the year.

The internal tickets include high volume issues such as password resets, account unlocks, software access requests, email issues, and VPN connectivity, handled end-to-end within defined permissions and escalation paths.

[1]

“In our own environment, over 90% of targeted Level 1 volume is handled autonomously, with resolution rates above 99% for those categories and materially faster than human-only workflows,” a ServiceNow spokesperson told The Register .

[2]

[3]

It accomplishes this by having the Autonomous Workforce operate on top of the live configuration management database (CMDB), active workflows, policy engines, approval chains, and real transaction history – all updated in real time every time a ticket closes, a workflow executes, or a policy changes, ServiceNow said.

ServiceNow could use a win as Salesforce is targeting its enterprise ITSM customers with its own Agentforce IT Service product. Salesforce CEO Marc Benioff [4]boasted of poaching five ServiceNow customers during the most recent quarter's earnings call.

[5]

Another challenge for ServiceNow is how the Autonomous Workforce will adapt to customer environments. While ServiceNow says its internal documentation is backed with 20 years of experience, documentation inside real world help desks traditionally has been poor to non-existent.

“The documentation problem is real, and frankly most vendors pretend it isn't. The reason ServiceNow can answer differently is the two decades of structured data that lives inside the platform itself,” according to group VP for AI products Nenshad Bardoliwalla. “This isn't a system that reads your Word docs and hopes for the best ... The pitch is ‘we're the control plane that aggregates signal from the tools you already have, and we fill the gaps with structured workflow logic built over two decades.’”

Bardoliwalla said, the Autonomous Workforce uses historic ticket information as the knowledge base when answering questions. So far the system has been tested internally by ServiceNow employees feeding it tickets.

[6]

ServiceNow broke those tickets down for The Register by type and subtype – which is how help desks organize and manage tickets - revealing that the Autonomous Workforce solved 90 percent of ticket types related to networking (46 percent), hardware (11 percent), and software (43 percent), as well as the following subtypes: enterprise app access, cloud authentication services (33 percent), collaboration tools issues (13 percent), VPN and network connectivity issues (7 percent), laptop and hardware performance issues (8 percent), and software installs and configuration (6 percent).

“How does it know it got the right answer? Because the outcome is measurable inside the same platform,” Bardoliwalla said. “Did the ticket resolve? Did the workflow complete? Did the approval get the right sign-off? ServiceNow closes the loop in a way that a standalone LLM sitting on top of a SharePoint folder simply cannot.”

Bardoliwalla said ServiceNow knows the device, the user, the identity, the access policies, and the historical incident patterns tied to a configuration item, but critically, he said, the Autonomous Workforce knows when it needs to stop and escalate a problem.

“When the gap genuinely exists, the autonomous worker will know what it doesn't know,” he said. “This is actually a differentiator: a system that says ‘I can resolve 70% of this autonomously and here's exactly why I'm escalating the other 30%’ is more trustworthy than one that hallucinates an answer.”

[7]ServiceNow can't seem to keep its wallet closed, snaps up small AI analytics company

[8]ServiceNow boasts about years of sweat equity that went into making its AI agents smarter

[9]ServiceNow lays out possible co-CEO structure, but says no change imminent

[10]ServiceNow eyes $100M in AI-powered headcount savings

Forrester vice president and principal analyst Charles Betz said if ServiceNow has managed to achieve autonomous execution in the Level 1 help desk, that is a “milestone,” since for years AI in the help desk was used for deflection, recommendation, or faster routing.

“End‑to‑end execution at scale is different; it does legitimize AI as operational infrastructure rather than just a productivity aid,” he said. “So yes, this returns real margin — but not simply by shrinking L1 headcount. The value shows up as faster resolution, fewer escalations, better utilization of skilled staff, and the ability to absorb growth without linear increases in labor. The limiting factor shifts from ‘Can the AI do it?’ to whether the organization has the data quality, workflows, and governance discipline to sustain that higher baseline.”

He said it also opens the door to the [11]automation paradox , which he said is similar to what Lisanne Bainbridge wrote about in her 1983 paper, [12]Ironies of Automation . For the help desk, this means what used to be basic support becomes table stakes and “users surface higher‑order needs once the friction is removed.”

“There’s a well‑known dynamic that kicks in once the low‑hanging fruit is harvested. Level 1 doesn’t disappear — the baseline rises,” Betz told The Register . “Routine, procedural issues get automated away, and what remains are harder, more ambiguous, more cross‑system problems. In systems terms, you get complexity creep rather than pure volume reduction.” ®

Get our [13]Tech Resources



[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aaEk9OQwGnFUsOJROngcbwAAAAo&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aaEk9OQwGnFUsOJROngcbwAAAAo&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aaEk9OQwGnFUsOJROngcbwAAAAo&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[4] https://www.theregister.com/2026/02/26/salesforce_q4_2026/

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aaEk9OQwGnFUsOJROngcbwAAAAo&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aaEk9OQwGnFUsOJROngcbwAAAAo&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[7] https://www.theregister.com/2026/02/14/servicenow_buys_pyramid_analytics_to/

[8] https://www.theregister.com/2026/01/28/servicenow_ai_agents/

[9] https://www.theregister.com/2025/12/30/servicenow_outlines_coceo_structure/

[10] https://www.theregister.com/2025/07/25/servicenow_100m_ai_savings/

[11] https://www.forrester.com/blogs/the-automation-paradox-strikes-again-lessons-from-woolworths-amazon-era-productivity-play

[12] https://ckrybus.com/static/papers/Bainbridge_1983_Automatica.pdf

[13] https://whitepapers.theregister.com/



Doctor Syntax

“How does it know it got the right answer? Because the outcome is measurable inside the same platform, Did the ticket resolve? Did the workflow complete? Did the approval get the right sign-off?

The fact that a ticket is closed doesn't mean it got the right answer. They'll discover that when an attacker gets a password reset or access authorised.

Did the approval get the right sign-off?

that one in the corner

Any metrics on how many get sent to the wrong people for sign-off, who are very aware of the pressure to make the LLM seem to work and are routing all its mistakes to the right person? Such as the L2 human who should have seen the ticket before it got anywhere near asking for signoff...

auto-close

Anonymous Coward

bugs and bloatware AI creates are so huge that it difficult to review them all. so it is easier just to use bot to auto-close them by " your problem look like this other one, so it is closed". many gits, specially AI ones, are doing this now. even real issues dont get looked at anymore. it makes no sense to use your time to report issues anymore.

Life is like an onion: you peel off layer after layer and then you find
there is nothing in it.
-- James Huneker