IT support specialist / helpdesk — tasks, one by one

The ticket you have seen four hundred times

This is the single clearest automation target in an office, and it had already been half-automated by self-service portals before any model arrived: the problem is narrow, the resolution is a known sequence, and success is machine-checkable — the account unlocks or it does not. That last property is what lets a system retry without a person watching, which is the property that separates tasks that moved from tasks that did not.

Removing the easy tickets does not leave a smaller version of this job, it leaves a harder one: what remains is the queue's long tail, where the user's description is wrong and the fault is in the gap between two systems. Teams sized on ticket volume that automate the volume and keep the sizing end up with the same headcount doing work the metric no longer describes — and appraisals built on tickets-closed start measuring the wrong thing the week the tool lands.

Finding out what actually happened

The diagnostic input here is not the ticket, it is the correction of the ticket — asking the question that reveals the user did something they did not mention because it did not seem relevant. A tool given the same written report inherits the same wrong premise, and this occupation's whole skill is refusing to accept it.

Human-led here is about who can solve it, not about how many are employed to. A team that automates the easy half and shrinks by that half leaves the hard half to fewer people, and the hard half is where the burnout in this occupation has always been. The task surviving is not the same as the post surviving.

Going to the desk

Nobody is automating a hardware swap in an office, and the reason is economics rather than difficulty — the volume in any one building is far too low to justify a machine. What has actually reduced this task is not automation at all: remote work and cloud services removed the desk rather than the person who walks to it.

This half being safe from automation is what makes the whole occupation look safer than it is, because the physical half is small and shrinking for reasons unrelated to technology. Measure the ratio in your own week before reading any reassurance into it — in most organisations it is a minority of the hours and falling.

Being the one who says no

The service desk is the single most targeted entry point in most organisations precisely because it is designed to be helpful to a stranger under pressure. The judgement — this request is normal, that one is not — depends on knowing the organisation rather than the policy, and it is the reason the desk cannot simply be a workflow.

This is the task most likely to be automated badly rather than well: a verification step that a system performs is a step an attacker can learn exactly. And the authority to refuse is granted, not inherent — a desk measured only on resolution time will grant the access, and no technology is needed for that to happen.