IT & MSP
AI agents for IT and MSP teams
Agents that switch off leavers' access, set up new starters and triage alerts across Freshservice, ServiceNow, Okta and SuperOps, with approval before anything changes and a record of every step.
Works with
Freshservice
ServiceNow
Okta
SuperOps
Slack
Microsoft Teams
Access changes are small jobs with big consequences
Someone leaves on Friday, and their accounts are still active on Monday because the ticket was waiting in a queue.
A new starter's first morning goes on waiting for an account that depended on someone reading a form.
An MSP technician starts the day with a wall of alerts across twenty clients, most of them known issues.
Each one crosses at least two systems, and each one needs a person to agree before access changes. Agents do the looking up and the typing; your team keeps the yes or no.
How the offboarding agent works
- 1
Picks up the request
a new offboarding request in Freshservice, or a new record in the ServiceNow table you choose.
- 2
Finds the person
looks them up in Okta by email and checks the account matches the request.
- 3
Finds their equipment
searches Freshservice for assets assigned to them.
- 4
Asks for approval
a card in Slack or Teams shows the person, their last day, the account and the equipment.
- 5
Makes the change
deactivates the Okta account and flags assets for return.
- 6
Records it on the ticket
a private note lists every change and who approved it.
Deactivation always waits for a person. The agent can't delete accounts: that action isn't in its toolbox.
New starters, ready on their first morning
- 1
An onboarding request arrives
in Freshservice or ServiceNow.
- 2
The agent checks Okta
so it never creates a duplicate account.
- 3
It asks for approval
in Slack or Teams, showing the name, role, manager and start date.
- 4
It creates the Okta account
with the details from the request.
- 5
It adds the access checklist to the ticket
as tasks for your team, based on your role-to-access list.
- 6
It tells the manager
in Slack or Teams that the account is ready.
The controls your security team will ask about
Approval before access changes
every deactivation and every new account waits for a person, in Slack or Teams.
Only the actions you add
the offboarding agent can deactivate accounts; it can't delete them, because that action isn't in its toolbox.
Pinned fields
values such as the department or user type on a new account come from your rules, not the agent's judgement.
Allowed values
limit what the agent may set, such as the ticket priorities or categories it can choose.
A record for audit
every run is in the Event Logs: the request, what the agent found, who approved it and what changed.
Works with the IT systems you already run
- Service deskFreshserviceServiceNow
- IdentityOkta
- MSP platformsSuperOpsNinjaOne
- Approvals and updatesSlackMicrosoft Teams
- Incident response
PagerDuty
incident.io
Using another tool? Connect any REST API, or, on the Enterprise plan, our team builds the connector within 5 working days.
IT and MSP templates
- AI workflow
Employee offboarding
Deactivates the leaver's Okta account and records it on the ticket.
Approval: Before deactivationUse template Employee offboarding - AI agent
Employee onboarding
Creates the Okta account and adds the access checklist to the ticket.
Approval: Before the account is createdUse template Employee onboarding - AI workflow
IT ticket triage
Categorises and routes new Freshservice tickets and leaves a suggested fix as a private note.
Approval: None (private note only)Use template IT ticket triage
SOC 2
ISO 27001
GDPR
HIPAA
Bring us your offboarding checklist
We'll build the agent with you on your Freshservice or ServiceNow and Okta, with your approval rules, and run it on a test request.