Agent Library · By function · Service desk · Access · Assets

Three people run IT for a company of two hundred.

Mid-market IT is not a site-reliability problem. It is a service-desk problem, an access problem and a licence-spend problem, handled by a very small team who are always behind. That is the shape these agents are built for.

The desk never empties
Password resets, access requests and "is it just me?" arrive faster than three people can clear them.
Joiner-mover-leaver leaks
Access granted on day one is rarely revoked on the last day. Nobody discovers it until an audit does.
Licence spend drifts upward
Seats bought for people who left, tools nobody opened in six months, renewals that auto-charge unexamined.
The agents

6 agents. Each one earns its autonomy.

Agent
What it does
Autonomy
Human gate
Service Desk Triage
Classifies, prioritises and routes tickets, resolving the genuinely routine ones and drafting the rest.
Notify
Access Orchestrator
Runs joiner-mover-leaver provisioning against your role matrix and flags every drift from it.
Review
All grants and revocations approved by a human
Incident Summariser
Assembles the timeline, impact and draft RCA while the incident is still fresh, from your own logs and threads.
Review
Asset & Licence Tracker
Tracks seats, renewals and actual usage; flags unused licences and upcoming auto-renewals with the spend attached.
Flag only
Change & Release Notes
Drafts change records and release notes from merged work, in language the business can read.
Review
Alert Noise Reducer
Correlates and de-duplicates monitoring alerts so the ones that matter are visible.
Auto
Autonomy key — Auto: executes above 95% confidence. Notify: executes at 85–95% with notification and undo. Review: always queued for a human. Flag only: never acts, alerts a person.

Kamaan does not sell SRE, observability platforms or network automation. If you have a platform engineering org, you need a different vendor. This page is built for internal IT service operations at a 50–200 person company.

What changes

Three shifts, not a feature list.

The routine half of the desk clears itself
Your IT team stops spending mornings on resets and starts on the work only they can do.
Access stops drifting
Revocation becomes as reliable as provisioning, because both run through the same system.
Licence spend becomes visible
Not once a year at renewal, but continuously, with the unused seat named.
The eval bench

What these agents have to pass before they touch real work.

  • Triage accuracy against 200 historic tickets with known correct category and owner
  • Access matrix conformance: 100% of proposed grants tested against the role matrix before queueing
  • Zero autonomous permission changes — every grant and revocation human-approved
Written against your data, not ours. The bench is built during Blueprint and runs on every deploy from then on.
Related

Where this connects.

By platform
Freshdesk · Freshservice
Explore
By platform
Service desk · Requests · Incidents
Explore
By platform
Outlook · Teams · Excel · SharePoint
Explore

See it on your Freshservice.

A Blueprint maps which of these agents pays off first in your exact setup — and which to leave alone.

Apply for a Blueprint