- What makes an IT agent different from a chatbot
- Three forks that decide the shortlist
- Agentic service desks that live in chat
- ITSM platforms with agents built in
- What's shifted in this category
- Run a pilot that proves something
- Mistakes that sink an agent pilot
- What you'll pay, described in words
- Which type fits your team
The best AI agents for an IT helpdesk are the ones that close a password reset or access request without a technician touching it. If your staff live in Slack or Teams, start with an agentic service desk such as Siit, Ravenna or Atomicwork. If you already run ITIL processes, add agents inside an ITSM such as SysAid, HaloITSM or Freshservice.
What makes an IT agent different from a chatbot
Most IT managers assume an AI agent is a smarter chatbot parked in front of the queue. The useful ones aren't. A chatbot replies; an agent acts. It resets the password, adds the user to the right group, raises the laptop request and closes the ticket, and that last step is the one you're paying for. If a product can only suggest a knowledge-base article, it deflects tickets rather than resolving them, and your technicians will still do the work.
So before you open a single vendor site, export last quarter's tickets and sort them by request type. You're hunting for the boring repeats: password and MFA resets, access to a shared drive or app, a new starter's accounts, a printer that won't map, a licence request. Count each one. That count is your business case, and it also tells you what to shortlist, because an agent that can't write to your identity provider can't close a reset however well it chats.
Three forks that decide the shortlist
Almost every buying decision in this category comes down to three questions. Answer them first and the list shrinks from eight to two.
| Your situation | Type to shortlist | Check before the demo |
|---|---|---|
| Staff ask for help in Slack or Teams, small IT team | Chat-first agentic service desk | Can it act in your identity provider, or only answer? |
| You already run incident, change and problem processes | ITSM platform with agents built in | Is the agent on your plan or an add-on? |
| IT, HR and finance all field employee requests | Multi-department agentic desk | Can each team own its own knowledge and approvals? |
| Few technicians, many employees | Seat-priced tool | What counts as a seat: technician, admin or agent? |
| Spiky volumes, finance wants cost per outcome | Credit or usage pricing | What draws a credit, and what happens when they run out? |
Where employees ask for help. Chat-first service desks sit inside Slack or Teams and treat the conversation as the ticket. Full ITSM platforms keep the portal, the CMDB and the change calendar, and add agents on top. If you've never run formal ITIL processes, the chat-first route is lighter to adopt. If you have, ripping out a working ITSM to get an agent is rarely worth it. Our guide to the difference between a help desk and a service desk is worth five minutes if your team uses the two words loosely.
How you're billed. Four of the eight tools below charge per seat, whether they call it an agent, a technician or an admin. One draws a credit each time an AI worker completes a job. One splits its bill in two, per employee for the self-service side and per fulfiller for the technician side. Two don't publish pricing at all. Per-seat pricing favours a small IT team serving a big workforce; per-employee pricing grows with headcount even when tickets don't.
Whether the agent is on your plan. This is where demos mislead. On at least two of these platforms the agent lives on the top plan or arrives as a paid add-on, and one vendor caps its assistant at ten conversations a week on its two lower plans. Ask which plan the demo is running on, in those words.
Agentic service desks that live in chat
Siit
Slack, Teams and email are where this one works, with agents that qualify and resolve requests across IT, HR and finance.
Atomicwork
An agentic service desk whose AI Coworkers handle employee support over chat, voice, email and portal, aimed at enterprise service teams.
Rezolve.ai
For IT, HR and finance teams who want one assistant, Sidekick, answering and acting on every channel, with a voice agent alongside.
Ravenna
Agentic service desk for IT, HR and operations that sits inside Slack and Microsoft Teams, where your staff already ask for help.
ITSM platforms with agents built in
SysAid
An ITSM platform where Dex, an autonomous IT engineer, and a set of Copilot agents work tickets for the service desk.
HaloITSM
ITIL-aligned teams get Halo AI, Emotion AI and a virtual agent for ticket handling inside one service desk.
Freshservice
One of the larger ITSM platforms, built on ITIL practice, with Freddy AI supplying both a technician copilot and an AI agent.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Serviceaide
Enterprise service management with the Luma AI engine and new agents for diagnostics, web, email and self-service incidents.
What's shifted in this category
The big change is consolidation. Moveworks, for years the name people meant when they said AI agent for IT support, now carries a ServiceNow acquisition notice on its homepage. Console, an AI-native ITSM, has joined Palo Alto Networks, and Aisera's homepage now carries Automation Anywhere branding. None of that makes those products worse, but it does mean your contract, roadmap and renewal terms may now be set by a much bigger company. That's why none of the three is in the list above.
The second change is how the bill is framed. Some vendors now sell the AI itself like headcount: you buy extra AI workers by the month, the way you'd add a technician. Others price the person who operates the agent rather than the tickets it closes. Neither is wrong, but they reward very different ticket volumes, so model both against your own numbers before a call.
Run a pilot that proves something
A demo proves the vendor can resolve a ticket they wrote. A pilot proves the agent can resolve yours. Keep it to four weeks and three request types. Pick the three with the highest count from your export, and make sure at least one needs the agent to change something, not just answer a question.
Spend the first two weeks in shadow mode if the tool supports it: the agent drafts the fix, a technician approves it. Spend the next two live, for one department only. Then measure four things against the same weeks last quarter: tickets closed with no human touch, tickets reopened within seven days, median time to resolution, and how many employees asked for a person straight away.
Here's what a pass looks like with real numbers. Say you get 200 password and MFA resets a month. If the agent closes 140 of them, fewer than 10 reopen, and the median fix drops from hours to minutes, you've freed a technician's week every month on one request type alone. If it closes 140 but 40 reopen, it hasn't resolved anything; it's moved the work to next Tuesday.
Do you make AI agents or service desk software for IT teams? Tool makers can ask to be considered for a featured place on this list.
Mistakes that sink an agent pilot
- Launching to the whole company on day one. One noisy failure in a company-wide channel will cost you more goodwill than a month of quiet wins earns.
- Feeding it a stale knowledge base. An agent answers from what you give it. Articles that still mention last year's VPN client will be repeated with total confidence.
- Giving it read access only. Without permission to act in your identity and device tools, you've bought a polite search box.
- Counting deflections instead of resolutions. A ticket the employee abandoned isn't a ticket the agent solved.
- Ignoring the handoff. Test what happens when the agent gives up. The technician should get the whole conversation, not a fresh ticket that says "user needs help".
What you'll pay, described in words
On the vendors' own pricing pages this month, seat-priced ITSM tools start at tens of dollars or pounds per agent per month, before any AI add-on. Agent features are often extra or limited to the top plan. At the far end, one agentic desk starts at a five-figure annual contract with a couple of AI workers included. What drives your bill is the model: number of technicians, number of employees, or number of jobs the AI completes. Run your ticket count through each before you compare headline figures.
Which type fits your team
If you're a team of one to five looking after a company that lives in Slack or Teams, go chat-first. You'll get value faster because there's no portal to train people on, and you can start with resets alone.
If you already run an ITSM and it works, switch on or trial the agent inside it before you look elsewhere. Migration costs months, and our roundup of ITSM tools will tell you if your current platform is worth staying on.
If HR and finance drown in the same kind of repeat questions as IT, pick a multi-department agentic desk and run the pilot across two teams. And if budget is tight and your team is technical, look at an open-source help desk for the ticketing side and add AI later, once you know which requests are worth automating.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
