Picks up the request
a new offboarding request in Freshservice, or a new record in the ServiceNow table you choose.
IT & MSP
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 withFreshservice, ServiceNow, Okta, SuperOps, Slack, Microsoft Teamsand 200+ more apps
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.
a new offboarding request in Freshservice, or a new record in the ServiceNow table you choose.
looks them up in Okta by email and checks the account matches the request.
searches Freshservice for assets assigned to them.
a card in Slack or Teams shows the person, their last day, the account and the equipment.
deactivates the Okta account and flags assets for return.
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.
in Freshservice or ServiceNow.
so it never creates a duplicate account.
in Slack or Teams, showing the name, role, manager and start date.
with the details from the request.
as tasks for your team, based on your role-to-access list.
in Slack or Teams that the account is ready.
every deactivation and every new account waits for a person, in Slack or Teams.
the offboarding agent can deactivate accounts; it can't delete them, because that action isn't in its toolbox.
values such as the department or user type on a new account come from your rules, not the agent's judgement.
limit what the agent may set, such as the ticket priorities or categories it can choose.
every run is in the Event Logs: the request, what the agent found, who approved it and what changed.
Your service desk
Using another tool? Connect any REST API, or, on the Enterprise plan, our team builds the connector within 5 working days.
Deactivates the leaver's Okta account and records it on the ticket.
Creates the Okta account and adds the access checklist to the ticket.
Categorises and routes new Freshservice tickets and leaves a suggested fix as a private note.
SOC 2
ISO 27001
HIPAAWe'll build the agent with you on your Freshservice or ServiceNow and Okta, with your approval rules, and run it on a test request.
In a demo, we'll map one of your processes to a workflow, AI workflow or agent, using the apps you already run.