AI IT support for your own team
Most small IT teams are one person, and half their week is the same six questions. This job takes the first line: the password reset, the printer, the access request, the thing that is documented somewhere nobody can find. What it cannot fix becomes a ticket with the work already shown.
Concretely
- Answers employee IT questions in the channel people already ask them in.
- Troubleshoots the common issues by walking someone through the fix.
- Creates a support ticket when it cannot resolve something itself.
- Maintains the IT knowledge so the answer is written down after the first time.
- Hands off anything touching security, billing or a system it cannot safely reach.
The interruption is the cost, not the question
Nobody minds answering how to get onto the guest wifi. What costs something is being asked it while halfway through a migration, for the fourth time that week, by someone who genuinely could not find it. First-line support is not hard work; it is work that cannot be batched, and that is what makes it expensive for a small team.
It shows its working before it escalates
A ticket that says "it does not work" is a second investigation. When this job cannot resolve something, the ticket it opens carries what was tried, what happened and what was ruled out. The person picking it up starts from the middle rather than the beginning, which is most of what makes an escalation cheap or expensive.
Security is where it stops
Anything touching security, billing or a system it cannot safely reach becomes a ticket for a person rather than an attempt. That boundary is deliberate and it is not configurable by accident: the failure mode of a helpful support agent is one that resets the wrong credential confidently, and an internal helpdesk is exactly where that would happen.
The knowledge base writes itself, slowly
Every question answered once is a candidate for being written down. Maintaining IT knowledge is part of the job rather than a project nobody gets to, so the documentation grows out of the questions people actually ask rather than the ones somebody imagined they would ask when the wiki was set up.
The jobs this comes from
Sanaf holds thirty five written job descriptions. These are the ones behind this page.