AI in ITSM and support has moved from a vendor talking point to a live operational reality in most ANZ mid-market IT environments. Every platform claims to have it. Every vendor promises faster resolution and smarter teams. And inside most IT service management operations, the results are underwhelming. Not because AI cannot deliver, but because it is almost universally being deployed the wrong way.
This article covers what AI in ITSM and support actually does well in internal IT environments, where most adoption attempts stall, and how ANZ mid-market IT leaders can sequence adoption to get genuine operational improvement rather than another piece of expensive shelfware.
Not sure where AI actually fits in your ITSM operation? Book a diagnostic call and we will identify the highest-value AI use cases for your specific team in 30 minutes.
Why AI in ITSM and Support Delivers Less Than Expected
The most common sequence for AI adoption in ITSM is: deploy a chatbot, set deflection targets, measure how many contacts the chatbot handles, discover the chatbot is routing users in circles, and conclude that AI does not work for ITSM. This sequence is wrong from the first step.
Chatbots are the most visible AI application and the one with the highest failure rate in ITSM environments. They fail because they are deployed at the point of customer contact before the service model behind them is well-designed. A chatbot that routes to a broken self-service portal, or that cannot find the knowledge article the user needs because the knowledge base has not been maintained, does not deflect contacts. It creates frustrated contacts who require more handling time than the original issue would have.
The AI adoption gap
According to the State of AI in IT 2026 report, 74% of organisations already have AI working inside at least one service management team, and 82% of those that have invested in AI report tangible results. Yet Ivanti’s 2024 research found that only 46% of organisations currently use ticket automation despite it being available on virtually every modern ITSM platform. The gap between AI availability and AI outcomes reflects how it is deployed, not whether the technology works.
The problem is almost never the technology. It is that AI is being asked to compensate for unclear processes, unmaintained knowledge bases, and poorly designed service catalogues rather than to enhance a foundation that is already working. When the foundation is right, AI amplifies it. When the foundation is wrong, AI amplifies that instead.
What AI in ITSM and Support Actually Does Well
The most reliable AI applications in ITSM operate in the background rather than at the customer interface. They handle the mechanical elements of ITSM work so agents and IT administrators can focus on the elements that require human judgement. The five ITSM-specific use cases where AI consistently delivers value are worth examining individually because each has different preconditions and different metrics.
Incident Classification and Routing
AI classifies incoming incidents by type, urgency, and affected component, and routes them to the right team or individual without manual triage. For teams handling 200 or more incidents per week, the manual triage step that AI replaces typically consumes 15 to 20 minutes of a first-line agent’s time per hour. Automated classification also improves consistency: AI applies the same categorisation logic to every incident, which produces more reliable reporting and more accurate SLA application than human triage at volume.
IT Self-Service Deflection
AI surfaces relevant knowledge articles to employees as they describe their issue in the self-service portal, before they submit a request. When the article answers their question, the contact is deflected without a ticket being created. This is distinct from a chatbot: it does not involve conversational AI. It is a search and recommendation layer over a maintained knowledge base. According to Freshworks’ 2024 benchmark data, teams using this capability achieve ticket deflection rates of 53%. The precondition is a knowledge base aligned to actual contact reasons, not one structured around IT team categories that users cannot navigate.
Change Risk Assessment
AI assesses the risk profile of proposed changes by analysing historical change data, affected CI relationships in the CMDB, and the timing of similar past changes. This assists change managers and CAB members in making faster, more consistent risk decisions without having to manually cross-reference historical records. In practice, AI-assisted change risk assessment reduces the time the CAB spends on each normal change review and improves the consistency of risk classification across change types.
Recurring Incident Pattern Detection
AI identifies recurring incident patterns across ticket data and surfaces them for problem management review before a human review cadence would catch them. When the same component generates 25 incidents in a week, AI flags it immediately rather than waiting for the next weekly operations review. This feeds the problem management process that reduces preventable incident volume over time. Seagate achieved 32% ticket deflection in under a year after implementing structured problem management supported by AI pattern detection on Freshservice. Source: Freshworks customer case study.
Agent Assist and Knowledge Suggestion
AI surfaces relevant knowledge articles and suggested resolution steps to agents as they read an incoming incident or request. The agent reviews, adjusts, and applies the suggestion. This reduces the time agents spend searching for solutions to contact types they handle repeatedly, reduces the quality gap between new and experienced agents, and improves first contact resolution rates by ensuring agents have the right information at the point of resolution rather than after escalation. According to Freshworks’ 2024 benchmark data, teams using AI-assisted knowledge management achieve first contact resolution rates of 77%.
Where Most ITSM AI Adoption Goes Wrong
Three failure patterns account for the majority of underwhelming AI outcomes in ANZ mid-market ITSM environments.
Deploying AI before the service model is stable. AI applied to unclear categorisation logic produces unreliable classification. AI applied to an unmaintained knowledge base produces unhelpful suggestions. AI applied to a poorly designed service catalogue produces confused deflection. The most reliable predictor of AI success in ITSM is not the sophistication of the AI capability but the quality of the operational foundation it is deployed on. Stable workflows and maintained knowledge are the preconditions, not the outcomes.
Measuring AI success through deflection rate alone. Deflection rate is a useful operational indicator but a poor primary success metric because it does not distinguish between contacts that were genuinely resolved and contacts that were deflected without resolution. A high deflection rate accompanied by a rising repeat contact rate means AI is redirecting contacts rather than resolving them. The downstream metrics that confirm AI is working are first contact resolution rate, repeat contact rate, and CSAT trend.
Rolling out AI without agent involvement. AI recommendations that agents do not trust get ignored rather than acted on, which means the efficiency gain never materialises. Agents who participate in identifying AI use cases, reviewing AI outputs during a trial period, and providing correction feedback produce AI that improves faster and adoption rates that sustain. In practice, the fastest route to agent AI adoption is addressing the specific manual tasks agents find most tedious rather than the tasks that look most impressive in a vendor demo.
How to Sequence AI Adoption in ITSM Successfully
The sequence that produces reliable AI outcomes in ANZ mid-market ITSM environments is consistent regardless of platform or team size.
Start by stabilising the workflows that AI will operate on. Clear incident categorisation, a maintained knowledge base aligned to actual contact reasons, and a service catalogue designed for user navigation are preconditions rather than parallel workstreams. Teams that try to deploy AI and fix the foundation simultaneously consistently find that the AI produces exceptions that consume the capacity the team was trying to recover.
Then identify the specific manual decisions agents make repeatedly for high-volume contact types and deploy AI on those decisions first. Incident classification, knowledge suggestion, and routing prioritisation are the applications with the fastest adoption because they visibly reduce work rather than adding complexity. These applications also produce the correction data that improves AI accuracy over time.
Expand to self-service deflection and change risk assessment only after the simpler use cases are producing consistent results. Self-service AI that surfaces accurate knowledge reliably builds user trust that makes subsequent, more ambitious AI deployments easier to adopt across the organisation.
AI in ITSM works best when it supports the decisions agents and IT administrators are already making well, rather than attempting to make decisions the operation has not yet learned to make consistently. The technology amplifies what is already there.
What AI Adoption in ITSM Looks Like in Practice
Databricks implemented structured self-service and AI-powered knowledge management on Freshservice and achieved 23% ticket deflection through self-service alone. The outcome came from aligning knowledge base content to actual contact reasons from ticket data, then deploying AI to surface that content at the point of need. The deflection was genuine: contacts were resolved rather than redirected, which meant the deflection rate held rather than producing a corresponding rise in repeat contacts. Source: Freshworks customer case study.
Seagate: 32% ticket deflection in under a year
Seagate replaced its legacy ITSM platform with Freshservice and implemented AI-powered self-service, automated incident classification, and structured problem management. Within one year, Seagate achieved 32% ticket deflection. The outcome came from the combination of a well-maintained knowledge base, AI that surfaced it reliably, and problem management that used pattern detection to reduce preventable incident volume over time. Source: Freshworks customer case study.
Both outcomes reflect the same principle: AI deployed on a stable operational foundation with clear success metrics produces measurable, sustained improvement. AI deployed as a fix for an unstable foundation produces a more complicated version of the same problems.
Quick Self-Check: Is AI Helping or Hindering Your ITSM Team?
If three or more of the following describe your current ITSM operation, AI is either being underused or deployed on an insufficient foundation.
- AI is available on the platform but has not been configured for any ITSM use case
- A chatbot was deployed and abandoned because users found it frustrating
- Ticket classification is still done manually by first-line agents
- The knowledge base exists but is not actively maintained or aligned to current contact reasons
- AI deflection rates are reported but repeat contact rate for deflected contact types is not tracked
- Agents bypass AI recommendations because they do not trust the output
Our ITSM Platform Optimisation service covers AI configuration and deployment as a core component for ANZ mid-market IT teams. For teams evaluating which platform best supports their ITSM AI requirements, our ITSM Platform Selection service provides a vendor-neutral assessment before any commitment is made. You can also read our articles on ITSM automation recipes for the specific automation patterns that produce the highest deflection rates, and our article on reducing support tickets for the structural approaches that determine whether AI deflection delivers genuine volume reduction.
Book a 30-minute diagnostic call. We will tell you honestly what is broken, what is not, and what to fix first.
Frequently Asked Questions
Automated incident classification and agent knowledge suggestion are typically the highest-return first use cases because they reduce agent effort on the most common ticket types without requiring employees to interact with AI directly. Both are available in Freshservice at the Enterprise tier and can be configured within a day. Self-service deflection is the highest-volume use case but requires a well-maintained knowledge base before it delivers reliable results, which makes it a better second use case than a starting point for most teams.
For teams with a well-maintained knowledge base aligned to actual contact reasons, 20 to 35% self-service deflection on eligible contact types is achievable within 90 days. Freshworks’ 2024 benchmark data shows teams using AI-powered self-service achieving 53% deflection across all contact types. The gap between the conservative and optimistic ranges reflects knowledge base quality and how well self-service content is aligned to the actual contact reasons employees have. Teams that invest in knowledge base alignment before deploying AI consistently achieve the higher end of the range.
Freddy AI is included in Freshservice Enterprise at US$119 per agent per month. It covers automated incident classification, knowledge article suggestion for agents and employees, change risk assessment, pattern detection, and AI-assisted analytics. The Pro tier at US$95 per agent per month includes some AI features. The Growth tier does not include Freddy AI. For most ANZ mid-market teams deploying AI seriously, the Enterprise tier is the right starting point because it includes the full AI feature set without separate AI licensing fees that other platforms charge.
The primary metrics are first contact resolution rate, repeat contact rate on AI-deflected contact types, and average handling time for the ticket categories where AI assist has been deployed. Self-service deflection rate is a useful leading indicator but must be accompanied by repeat contact rate tracking, because deflection rate alone does not distinguish between contacts that were resolved and contacts that were redirected. CSAT trend and agent adoption rate are the downstream metrics that confirm whether AI is improving the service experience rather than just reducing queue volume on paper.
ITSM AI operates on structured, process-oriented work with defined categories, SLAs, and escalation paths. It excels at classification, change risk assessment, problem pattern detection, and structured knowledge management. CX support AI operates on more variable, relationship-oriented work where sentiment and empathy are significant factors. The use cases overlap on routing, knowledge suggestion, and self-service deflection, however the context differs: ITSM AI works with employee service relationships and ITIL-aligned processes, while CX AI works with customer relationships and experience-oriented outcomes. Teams running both should configure AI separately for each function rather than applying a single AI deployment across both environments.