Use case

Automate the IT tasks that keep coming back

Password resets, lockouts, recovery keys, app access, new hires and leavers. Risotto resolves these requests end to end in Slack and Microsoft Teams, and starts the rest on its own when Okta or your HR system reports a change. You set the inputs and the approvals. Every action is on record.

Book a demo

The requests that keep coming back

Risotto takes on the requests your IT team answers every week. None of them is hard. Together, they push out the project work.

Request Systems What Risotto does
Password and MFA resets Okta, Microsoft Entra ID Resets the password or MFA, after an identity check in your Okta if you require one
Account unlocks Okta Unlocks the account
Device lookups and recovery keys Jamf, Iru, Microsoft Intune Finds the requester’s device and returns its FileVault or BitLocker recovery key
Software and group access Okta, Entra ID, Google Workspace Applies your approval policy, adds the group and sets an end date
Onboarding Rippling, BambooHR, HiBob, Okta Activates the Okta account, adds groups and Slack channels, and opens the laptop ticket
Offboarding Rippling, BambooHR, HiBob, Google Workspace Ends Okta sessions, suspends Google Workspace and moves files to the manager

“Historically, ticket work overshadowed strategic project work. We were spending our days trying to keep the wheels on.”

Two ways the work gets done

Risotto runs repeat IT work in two ways, with the same tools.

On request. An employee writes “I’m locked out of Okta” in Slack or Teams. Risotto’s AI agent follows your runbook for that request: it asks for an Okta Verify push, unlocks the account, replies and resolves the ticket. If a step needs approval, the agent waits for the approver in Slack, Teams or email.

On its own. An automation starts when Okta reports an account change, when Rippling, BambooHR or HiBob reports a hire or termination, on a ticket event, on a schedule, or from an authenticated webhook. No one has to ask.

Both use the same editor, tools and approvals.

IT sets the limits

Risotto acts only inside the limits your IT team sets.

  • Fixed inputs. Choose who sets each tool input. Fix the values that must not change, such as the Okta group. The agent fills in the rest.
  • Approvals where they matter. Attach an approval policy to any tool or runbook step, such as “contractors need IT approval, employees do not”. The approver can be the requester’s manager.
  • Verified requesters. Before a sensitive change, the employee confirms who they are in your Okta.
  • A record of every action. Each step is logged on the ticket. Each automation run is logged with the event that started it.

Steps that run the same way every time

Risotto runs the strictest steps as code. Offboarding must end Okta sessions, suspend Google Workspace and move files to the manager, in that order, every time. A script tool does exactly that: TypeScript the Assistant writes and you can read.

  • One tool, every path. The same script tool runs from a runbook, an automation or the Assistant.
  • Every run on record, with its result and the version that ran.
  • Writes need approval. Any script tool that changes data in your connected tools waits for approval.

Build it by asking

Risotto’s Assistant builds runbooks, automations and script tools when you describe the task.

  • Every change is a draft, with tracked changes, test runs and version restore.
  • Templates for Okta and Entra password resets, Entra MFA resets, and FileVault and BitLocker recovery.
  • Custom API tools from a vendor’s API spec or docs.

No code needed; code when you want it.

Results from IT teams like yours

At Docker, Risotto auto-resolves 27% of IT requests end to end each month. Read the story

“We needed to handle a high volume of requests while remaining lean. I didn’t want our senior engineers fixing someone’s Wi-Fi when they could apply that time to more valuable, fulfilling work.”

Jeffrey Strauss, Director of IT and Workplace Operations, Docker

Frequently asked questions

Which IT tasks can Risotto automate?

Risotto automates the IT requests that repeat: password and MFA resets in Okta and Microsoft Entra ID, Okta unlocks, device lookups and recovery keys from Jamf, Iru and Microsoft Intune, software and group access, and onboarding and offboarding. Each one runs end to end, with approvals where you set them. IT solutions

Can Risotto run IT tasks without an employee asking?

Yes. Risotto automations start on Okta account changes, on hires and terminations in Rippling, BambooHR or HiBob, on ticket events, on a schedule or from an authenticated webhook. Automations

Can an AI agent reset passwords and MFA in Okta or Entra?

Yes. Risotto resets passwords and MFA in Okta and Microsoft Entra ID, and unlocks Okta accounts, from a message in Slack or Teams. It can verify the employee in your Okta first. Okta · Entra

Can I build IT automations without writing code?

Yes. Describe the task to Risotto’s Assistant, and it drafts the runbook, automation or script tool for you to review and test. Script tools

Hand Risotto the requests you could close in your sleep

Book a demo