The Quietest Revolution in IT
The AI service desk isn't coming β it's here. Australian MSPs are deploying generative AI agents for Level 1 and Level 2 support at an accelerating rate. Some estimate that by 2028, the majority of first-line IT support will be handled by AI without human involvement.
For the estimated 15,000-20,000 MSP service desk engineers in Australia, this creates an existential question: is AI your replacement or your promotion?
What AI Actually Does in the Service Desk
Current AI service desk deployments in Australian MSPs handle:
| Function | AI Capability | Human Impact |
|---|---|---|
| Password resets | Fully automated | Eliminates L1 ticket |
| Common queries (how do I, where is) | AI knowledge base | Reduces L1 volume 40-60% |
| Ticket triage & routing | AI categorisation | Reduces dispatcher role |
| Status updates | Automated | Eliminates tracking tickets |
| Basic troubleshooting | Guided AI resolution | Resolves 20-30% of L2 tickets |
| Escalation summaries | AI generation | Changes handoff documentation |
| RCA drafting | AI from time-series data | Changes post-incident work |
| Client reporting | Automated dashboards | Reduces manual reporting |
The pattern is clear: AI is not replacing all service desk roles. But it is fundamentally changing what those roles look like.
The L1 Engineer After AI
Before AI: Answer phone. Reset password. Log ticket. Route to L2. Repeat.
After AI: Monitor AI resolution quality. Handle escalations the AI cannot resolve. Train the AI on new issue patterns. Optimise knowledge base content for AI retrieval. Manage AI exception reporting.
The role shifts from 'doing' to 'supervising and improving.' The volume of tickets handled per human engineer increases. The complexity of remaining tickets increases. The number of engineers needed decreases.
The Two Tracks
MSP engineers face a binary choice as AI transforms the service desk:
Track 1: The AI Specialist
Engineers who embrace AI become the specialists who: - Build and maintain AI service desk integrations - Train and optimise AI models for specific MSP environments - Manage the human-AI handoff for complex issues - Develop automated resolution scripts - Consult on AI strategy for clients
These roles are in high demand and command premium salaries.
Track 2: The Commodity Support Engineer
Engineers who continue working at the same skill level β password resets, basic troubleshooting, ticket logging β will face: - Reduced headcount demand as AI absorbs volume - Pressure to justify their role against AI alternatives - Standardisation of remaining work into scripted processes - Wage stagnation as AI reduces the scarcity of basic support
What MSPs Are Actually Doing
Interviews with MSP technology leaders reveal the deployment timeline:
- 2023-2024: Pilot AI agents in controlled environments (5-10% of MSPs)
- 2025-2026: Active deployment of AI agents for L1 support (30-40% of MSPs)
- 2027-2028: AI handles 50-70% of L1/L2 tickets; humans handle exceptions (majority of MSPs)
- 2029+: AI plus humans as a single integrated support unit; distinction between L1/L2 dissolves
One Australian MSP delivery manager told us: "We're not laying off L1 staff, but we're not backfilling when they leave. Natural attrition has reduced our L1 team by 35% over 18 months. The AI handles what it can, and the remaining humans handle what it can't. Service levels went up, not down."
The Real Career Advice
If you're an MSP engineer in a service desk role:
- Get off the L1 treadmill β AI will handle what you're doing now within 24 months
- Learn AI tools β Understanding how to work with AI (not against it) is the most important skill you can develop
- Move up or sideways β Architecture, security, cloud, and client advisory roles are AI-resistant
- Document your expertise β The AI needs a knowledge base to work from; the engineer who builds that knowledge base has job security
- Watch for the squeeze β MSP margins will improve from AI, but that improvement may not translate to your salary
The Bottom Line
AI in the service desk is not a future scenario β it's a current deployment reality. For MSP engineers, the question is not whether AI will affect your role. The question is whether you'll be the one working with the AI, or the one being replaced by it.
The difference between those outcomes is entirely within your control.
Has your MSP deployed AI in the service desk? Share your experience.
Was this helpful?