← Home/Agent library/Live demo · IT

IT Service & Operations Agent
in action.

See how the agent detects the root cause of a VPN outage impacting 47 users, deploys the fix autonomously and updates the knowledge base — in 3 seconds.

Agent active · Production🖥️ Automated L1/L2 tickets⚡ 3-second resolution🔒 LOOP™ Governance
Definition

The IT Service & Operations Agent is a Claude agent that handles level 1 and 2 support tickets: triage, root-cause search, applying the documented fix and updating the knowledge base. It escalates complex or sensitive incidents to your teams with full context, and every action on your systems is logged in LOOP™.

Under the hood

How the agent works

The agent works for IT support and operations teams. It absorbs the level 1 and 2 requests that come back every day, so engineers can focus on complex incidents and projects. It connects to your ITSM, monitoring and knowledge base through the MCP protocol, under your security policies.

01

What it takes in

Tickets from your ITSM tool, monitoring alerts, the directory of users and devices, and your knowledge base with its resolution procedures. It also knows the scope the IT department has given it: the systems it may act on and those it must leave to the teams.

02

What it does

It qualifies each ticket, groups requests that belong to the same incident and looks for the cause using alerts and history. If the fix is documented and within its scope, it applies it and checks that the service is back. Otherwise, it routes the ticket to the right team with its diagnosis and what it has already checked.

03

What it hands back

Resolved, documented tickets, users kept informed of progress, a knowledge base that grows with each new resolution and, for escalated incidents, a file the engineer can pick up without redoing the diagnosis. The IT department can see what the agent handled and how.

Who decides what

Green zone · the agent acts alone

Recurring, documented requests such as password resets and standard access, and known fixes within the assigned scope. Every action is logged.

Orange zone · a human approves first

A fix that affects several users or a shared system, and any configuration change. The agent prepares the intervention, and an engineer approves it before it runs.

Red zone · the agent stops and escalates

A security incident, a critical system or a cause it cannot find. The agent does not intervene: it escalates immediately to the on-call team with everything it has observed.

Three typical situations

01

A VPN outage

Several users can no longer connect. The agent groups their tickets, finds the cause in the alerts, applies the documented fix and notifies the people affected.

02

A locked account

An employee can no longer log in. The agent verifies their identity following your procedure, unlocks the account and closes the ticket.

03

A procedure to update

An engineer has resolved a new type of incident. The agent turns the resolution into a knowledge base procedure, which is reviewed before publication.

01What it takes in

Tickets from your ITSM tool, monitoring alerts, the directory of users and devices, and your knowledge base with its resolution procedures. It also knows the scope the IT department has given it: the systems it may act on and those it must leave to the teams.

02What it does

It qualifies each ticket, groups requests that belong to the same incident and looks for the cause using alerts and history. If the fix is documented and within its scope, it applies it and checks that the service is back. Otherwise, it routes the ticket to the right team with its diagnosis and what it has already checked.

03What it hands back

Resolved, documented tickets, users kept informed of progress, a knowledge base that grows with each new resolution and, for escalated incidents, a file the engineer can pick up without redoing the diagnosis. The IT department can see what the agent handled and how.

Who decides what
Green zone · the agent acts alone

Recurring, documented requests such as password resets and standard access, and known fixes within the assigned scope. Every action is logged.

Orange zone · a human approves first

A fix that affects several users or a shared system, and any configuration change. The agent prepares the intervention, and an engineer approves it before it runs.

Red zone · the agent stops and escalates

A security incident, a critical system or a cause it cannot find. The agent does not intervene: it escalates immediately to the on-call team with everything it has observed.

Three typical situations
01
A VPN outage

Several users can no longer connect. The agent groups their tickets, finds the cause in the alerts, applies the documented fix and notifies the people affected.

02
A locked account

An employee can no longer log in. The agent verifies their identity following your procedure, unlocks the account and closes the ticket.

03
A procedure to update

An engineer has resolved a new type of incident. The agent turns the resolution into a knowledge base procedure, which is reviewed before publication.

Documented ROI · Sourced figures

Results in production.

Deployed at Société Générale, the IT Service & Operations Agent handles L1/L2 tickets autonomously — diagnosis, fix, knowledge base — with N2 escalation on complex cases.

−80%reduction in L1/L2 ticket volume handled by human teams
ITSM Benchmark 2025
3.1saverage autonomous resolution time for an L1 incident
vs. 4h average manual
94%autonomous resolution rate without human intervention
Koneetiv client production
On requestdeployment time to production
Claude Ignite + Claude Ops
−80%
reduction in L1/L2 ticket volume handled by human teams
ITSM Benchmark 2025
3.1s
average autonomous resolution time for an L1 incident
vs. 4h average manual
94%
autonomous resolution rate without human intervention
Koneetiv client production
On request
deployment time to production
Claude Ignite + Claude Ops
Frequently asked questions

IT service & ops agent: your questions.

What does the IT service & ops agent do?
It triages and resolves IT tickets, handles level 1-2 incidents and uses your knowledge base — escalating complex cases.
Does it act on the IS on its own?
On high-confidence cases yes; sensitive actions go through human validation via LOOP™ trust zones. IT keeps control.
How does it integrate with our tools?
Through MCP it connects to your ITSM, monitoring and knowledge bases, under your permissions and security policies.
What gains can we expect?
Faster ticket resolution, 24/7 support on common cases, IT teams refocused. Metrics defined during Claude Ignite scoping.
Which tickets does the agent handle alone?
Recurring, documented requests such as password resets, access requests and known incidents whose fix is already in your knowledge base. Anything that affects several users, touches security or involves a critical system is escalated to your teams, with the diagnosis already prepared.
By function

Functions that use this agent

Ready to deploy this
agent for your team?

30 minutes to validate feasibility on your processes. No slides, no pitch — a concrete conversation.

Identify my use case →See Claude Ops →