Rules, AI triage and AI agents: what each one automates on a service desk

Vendors use "automation" and "AI" loosely, but on a service desk there are three distinct layers. Knowing which layer a feature belongs to tells you how much setup it needs and what it will save.

What do rules automate?

Rules are if-this-then-that workflows: when a ticket in category X arrives, assign it to group Y; when an SLA timer reaches 80%, notify the lead; when a request is approved, create the fulfilment task. They are predictable and auditable, but someone has to write and maintain every rule. A rules-only desk with dozens of categories builds a large maintenance load.

What does AI triage add?

AI triage reads incoming tickets and categorises, prioritises and routes them without a rule for each case. Vendors in this comparison document it in different terms:

• monday service describes an Intake & Triage Agent that "classifies and routes tickets instantly", and puts AI Ticket Triage on every plan, for one board on Standard.
• Halo AI offers suggestions for categorisation, prioritisation and team routing.
• Zendesk AI detects intent and tone; Intelligent Triage is listed on Suite Enterprise.
• Ivanti documents automatic classification and routing of incoming tickets.

Triage reduces the number of routing rules you maintain, but it still depends on good categories and good intake.

What do AI agents do differently?

AI agents try to finish the work. Examples from vendor pages: ServiceNow ITSM describes "autonomous AI specialists" for password resets, access provisioning and VPN troubleshooting; monday service names IT Help, Device and Access agents; SysAid includes pre-built AI agents on both plans and tailor-made agents on Enterprise; Halo (formerly HaloITSM) describes process agents that auto-resolve known issues. Agents need knowledge they can rely on and permissions to act in the systems involved, which is where most of the setup sits.

How should a mid-market team sequence them?

Start with rules for the handful of things that must always happen the same way, such as approvals and SLA alerts. Turn on AI triage once categories are stable, and check its decisions for a few weeks. Add agents for the two or three request types with the highest volume and the clearest resolution, such as password and access help. Measure the share they resolve rather than trusting a headline figure.

How do you read vendor figures?

Treat any percentage as the vendor's statement. SysAid states its AI can resolve more than 60% of incidents before they become tickets; Freshworks states Freddy AI agents can handle up to 80% of routine queries in a general service context. Neither is a measurement by this site, and your result depends on your knowledge base and request mix.

What keeps agents useful over time?

Knowledge upkeep. Some platforms now help: monday service describes a Knowledge Agent that flags stale and missing articles, and Halo and Ivanti generate knowledge from resolved tickets. Whatever the tool, assign someone to review agent failures weekly.