Short answer
An IT service desk agent resolves password resets and standard requests, processes access requests through the right approvers and triages incidents with enriched context. Privileged access, security incidents and changes to production stay with IT staff. kalAIDoCreate builds and operates these agents with identity checks and full logging.
On this page
Level 1 is full of repeatable work
Every IT service desk knows the pattern. A large part of the tickets are password resets, locked accounts, MFA device changes, requests for software or shared mailbox access, and "it does not work" messages without details. First-level staff spend their time asking the same follow-up questions, looking up the same knowledge articles and forwarding tickets to the same resolver groups. Meanwhile, real incidents wait in the queue.
An agent that owns these patterns end to end gives the service desk room for problems that need an engineer's attention.
Responsibilities in detail
| Area | Agent | IT staff |
|---|---|---|
| Password reset and account unlock | executes after identity verification | handles failed verifications |
| MFA device re-registration | prepares and guides | approves and executes |
| Software and access requests | collects details, gets owner approval, provisions standard items | approves non-standard and privileged access |
| Incident intake | asks clarifying questions, collects logs and device data, sets category and priority | resolves, decides on major incident |
| Known errors | applies documented workarounds, informs users | maintains known error database |
| Security incidents | recognises and routes immediately | owns investigation and response |
Two rules are non-negotiable. First, the agent verifies identity before any account action, using the methods your security team defines, and never accepts identity claims from chat alone. Second, privileged accounts, admin rights and anything touching production systems are outside the agent's permissions.
Connected to ITSM, identity and endpoint tools
The agent works inside the tools your service desk already uses: an ITSM platform such as ServiceNow, Jira Service Management or TOPdesk, the identity provider (Microsoft Entra ID, Okta or on-premises Active Directory), endpoint management such as Microsoft Intune, and Teams or Slack as the conversation channel. It reads configuration items, user and device data and the knowledge base, and performs only the actions it has been granted.
Access requests follow your existing approval chain. The agent identifies the resource owner, asks for approval in Teams or by email, waits, provisions the access if approved and closes the ticket with a record of who approved what. For periodic access reviews, it can prepare lists for owners to confirm.
If you need a connector to an in-house application, a self-service portal extension or automation scripts for your environment, our sister company OnlineAppCreator builds them with defined SLAs.
From pilot to daily operations
Our AI Code Engineers use the AI agent development approach:
- Ticket mining. We analyse historical tickets to find the categories with the highest volume and clearest resolution path.
- Runbooks as code. Knowledge articles and resolver steps are turned into explicit, testable procedures for the agent.
- Security review. Your security team reviews identity checks, permissions and logging before anything goes live.
- Staged rollout. One department or location starts, with first-level staff watching every resolution.
- Run. Our managed AI agents team monitors the agent, handles incidents and updates procedures when your environment changes.
Underneath, the kalAIDoCreate platform provides SSO, role-based permissions, audit trails and integrations with collaboration tools such as Slack, with data kept in the EU.
What improves
Users get password resets and standard requests done in minutes at any time of day. Tickets that reach resolver groups contain the information engineers need. Access provisioning becomes traceable, which helps with audits under ISO 27001 and similar frameworks. First-level staff move from repetitive work to complex cases and user enablement.
Upskilling service desk staff
When the agent takes over routine tickets, service desk roles shift towards supervision, knowledge management and automation. We support that change with hands-on workshops by neooutput, including sessions on writing good runbooks and on agentic coding for automation engineers.
Further reading: AI agents for HR onboarding covers the people side of joiner processes, and ServiceNow and Jira AI agents goes deeper into the ITSM integration.
FAQ
Is it safe to let an AI agent reset passwords?
Yes, if identity verification is strict. The agent uses the verification methods your security team approves, logs every reset and hands over to staff when verification fails.
Can the agent grant admin rights?
No. Privileged access, admin rights and production changes are outside its permissions and always handled by IT staff.
Which ITSM tools does it support?
Common platforms such as ServiceNow, Jira Service Management and TOPdesk, plus identity and endpoint tools, through APIs and governed connectors.
How does the agent handle major incidents?
It recognises patterns such as many similar tickets in a short time, links them and alerts the on-call team. Declaring and managing a major incident remains a human task.