AI Ticket Classification Will Change My Job Title, but Not My Job
Around 4 PM last Friday, I was crouched in front of an employee's monitor. The problem wasn't the VPN. It wasn't the printer, either. This person had been staring at the same error message for 30 minutes without knowing what they'd clicked wrong, and the real issue was a single DNS setting hiding behind the screen. I figured it out not by reading the system logs, but by asking, "Have you changed your Wi-Fi recently, by any chance?"
Here's what I've learned doing this job: half of all tickets are technical problems, and the other half are people problems. AI is quickly moving into that first half.
What AI does well — really well
A few months ago, our team started piloting an AI-based ticket triage system. Honestly, it's pretty good. When a ticket comes in saying "Outlook won't open," the system analyzes keywords and historical patterns to route it to the right category. I used to spend close to an hour a day opening tickets, reading them, categorizing them, and assigning priorities. Now that time is basically gone.

Getting freed from repetitive sorting work led to something I didn't expect. I actually started spending more time talking to people. Before, clearing the ticket queue felt like the whole point of the day, but now I have the bandwidth to think, "Why has this person submitted the same issue for the third time?" The answer is usually not technical. They haven't had enough training, their settings weren't updated after a department transfer, or they just had no one to ask.
The job title isn't disappearing — it's shifting
I don't think the title "IT support specialist" will still exist in exactly the same form five years from now. But that doesn't mean my job is going away. When the washing machine was invented, laundry didn't disappear — the definition of "the person who does the laundry" changed. Hand-washing skills became less necessary, but deciding what temperature and detergent to use is still a human call.
AI ticket triage works the same way. Routing gets automated, but the contextual judgment that "this isn't a simple password reset — it's an access rights issue for someone about to leave the company" is something the system still can't do. The two security-related issues I caught this month both looked like ordinary login failures based on the ticket content alone. I read them differently because I knew what was going on inside the company.

There are uncomfortable parts, too
It wouldn't be honest to only say good things. Junior-level hiring has clearly declined since AI triage was introduced. Ticket sorting was kind of a gateway for newcomers to learn the overall workflow, and once that's automated, they have fewer chances to build that intuition. I learned by reading tickets one by one early on, picking up things like, "Ah, so this kind of problem comes up a lot in that department."
That's a problem to solve, not a reason to block AI. I'm just not sure managers realize that when the tools change, the training methods need to change with them.
I'm not worried my job will disappear. But I'm pretty sure the words used to describe it will change. Today, I'm still walking over to someone's desk and asking, "Have you changed anything recently, by any chance?" I don't think any AI is picking up that question anytime soon.
Comments