I started my career on an IT helpdesk. Password resets, access requests, printer exorcisms, the occasional “my laptop smells funny.” I later built up that function and eventually led the global IT organization it belonged to. When I look at agents in IT service management, I recognize parts of my old queue.
A lot of the routine work could be automated with reliable access to the right systems. I would have welcomed that help. I also remember how much I learned from doing the work and talking to the people who needed it. Both things matter when deciding what a service desk should become.
Which parts of the work can change
An agent can combine a language model with tools that search knowledge, inspect a request or take an action. That allows more flexibility than a scripted conversation. It also creates more ways for an incorrect interpretation to reach another system. Performance depends on the instructions, tools and checks around the model; an agent does not automatically improve just because it has handled another ticket.
Some useful applications are straightforward to describe:
- Classifying and routing requests, then resolving defined routine cases where identity, permissions and the required action can be verified.
- Drafting a response, summarizing ticket history or finding a relevant knowledge article for a colleague to review.
- Inspecting logs and metrics, suggesting a diagnosis and carrying out an approved remediation when the conditions are understood.
- Drafting implementation, test and rollback plans, or grouping related incidents for a problem manager to investigate.
ServiceNow’s ITSM agent overview describes this move towards agents within service workflows. Its product documentation sets out specific capabilities. These are useful starting points for evaluation. A product description cannot tell you how well an agent will handle your requests or your systems.
Preventing an incident before a user reports it is an attractive goal. Having spent years looking at queue dashboards, I would be glad to see fewer tickets because fewer people were being interrupted. I would want to check that explanation before treating a falling ticket count as success.
How the operating model changes
If automation handles more routine requests, people need time and training to take on the work that remains. That may include investigating exceptions, checking the quality of agent decisions and improving the knowledge the system uses.
A service desk colleague who knows where users get stuck can help design better handovers. An incident manager can examine recurring patterns rather than spend so much time assembling the history. Someone still has to own the knowledge base, permissions and changes to the automated workflow.
Gartner’s 2024 predictions for IT organizations anticipated that 40% of CIOs would demand “guardian agents” by 2028 to oversee other agents’ actions. That is a forecast about a possible control mechanism. The immediate responsibility is to decide which actions may happen automatically, which need approval and how a person can intervene.
For a password reset, for example, the controls around identity and entitlement remain essential. For a production change, I would want explicit approval conditions and a way to recover. Agent activity should be recorded so it can be examined when something goes wrong.
What I would learn if I were starting again
I would still learn the systems and spend time with users. Alongside that, I would learn how to design an agent’s instructions, tool access and escalation rules, and how to test whether they work on the awkward requests as well as the routine ones.
Examining the data behind a recommendation would be another priority. A plausible diagnosis needs checking against the incident, and an apparently successful resolution needs checking against what happened to the user. Understanding those differences is useful both for operating the service and for improving the automation.
Understanding how the organization reviews risk and assigns responsibility is part of that work. A service desk needs a clear way to investigate a wrong classification, an inappropriate action or a request that should never have reached an agent.
Communication remains part of the job. Someone whose work is blocked may need an explanation or a person willing to understand an unusual situation. An obvious path to a colleague should be part of the service.
The people who have spent years resolving tickets carry knowledge that is easy to overlook in an automation plan. I would involve them in designing the new work and give them a credible route into it. Knowing the difficult cases is a useful starting point for deciding what an agent should do.
What I would put in the business case
A bot that gives a confident wrong answer can create more work for the service desk. It can also make someone less willing to trust the next answer. I would measure failed resolutions and repeat contacts alongside speed, and make it clear when a user is dealing with an automated system.
The service owner remains accountable when a ticket is closed incorrectly or an automated remediation disrupts a service. Agent actions need records, review and a way to stop them. I would be especially careful with sensitive HR or legal requests, deciding what data and actions were appropriate before granting access.
The helpdesk taught me to ask what the person on the other end needed. Sometimes that was a quick reset. Sometimes the request only made sense after a conversation. I would want an automated service to preserve the opportunity for that conversation.
