Employees ask in Slack or Teams.
AI agents get it done in Risotto, ServiceNow, Jira or Freshservice.
Risotto’s AI agents resolve 75% of requests, log every action on the ticket, and work within the approval rules you set.
IT teams at these companies run on Risotto
What Risotto does
Risotto is the AI-native ITSM that resolves employee requests in Slack and Microsoft Teams, with IT in control of every action. It handles access requests, password and MFA resets, troubleshooting and policy answers end to end, each with an approval, a ticket and an audit log, and it works on top of Jira Service Management, ServiceNow or Freshservice, or as your service desk.
| Your stack | Risotto works with |
|---|---|
| Chat |
|
| Ticketing |
|
| Identity | |
| HR | |
| Devices |
|
| Knowledge |
What customers measured
91% of access requests auto-solved at Ironclad. Read the story6.5 hours average AI resolution time at ThoughtSpot, against 31 hours for human agents. Read the story
68% of IT tickets advanced or assisted at Docker. Read the story
Turn the “ask IT” channel into your help desk
Employees keep asking in Slack or Teams, at 2 a.m. if that’s when the VPN breaks. Risotto answers from Confluence, Notion and Google Drive and logs each request as a ticket. When it needs a person, it hands over the thread and what it already tried.
Deploy AI in your ITSM
Keep Jira Service Management, ServiceNow or Freshservice. Risotto resolves requests in Slack and Teams, and every request becomes a ticket in your ITSM, synced both ways, custom fields included in Jira and ServiceNow. Your agents keep their queues, and Risotto’s resolutions show up in the reports you already run. Or run Risotto as your service desk, with its own ticketing.
Add me to design-team@
Activity
- Status
- Waiting for supportResolved
- Reporter
- Dana Reyes
- Request type
- Get IT help
- Caller
- Dana Reyes
- State
- Resolved
- Short description
- Add me to the design-team@ Google group
Activity
Properties
- Status
- Resolved
- Group
- Access
Access requests nobody has to chase
Someone asks Risotto for Stripe in Slack, and their manager gets an Approve button. One tap, and they’re in the Okta group, with an end date if your policy sets one. One page shows who has what, and until when.
Automations that work while you sleep
Tell Risotto’s Assistant what should happen when someone joins or leaves. It builds the runbook and shows you each change before it saves. After that, a hire or departure in Rippling, BambooHR or HiBob starts it, and you choose which steps wait for IT.
Escalations arrive already investigated
When a request needs your team, Risotto’s AI Assist reads the Okta logs, the device record and past tickets first, then writes a plan with a reason for each change. Approve it, and AI Assist does the work.
You probably already have a bot. Keep it.
Glean, Claude and your ITSM’s built-in AI are good at finding the answer. Risotto does what comes after it: the approval, the change in Okta, the ticket, and the follow-up when the first fix doesn’t work.
Where most AI stops
What Risotto does next
- ApprovalSam approves Figma (Editor) in Slack
- OktaDana is in the Figma group until Dec 12
- TicketIT-2402 resolved, each step logged
- Follow-upFigma still says no access? Risotto keeps going until it works
Resolved in 3 minutes, with no IT touch

4×
the auto-solve rate, after replacing Jira Assist
Your AI assistant
Set up Risotto for our pilot. Create an IT department, access rules for the apps in our Okta, and a draft runbook for laptop requests.
- Risotto
create_departmentIT - Risotto
create_access_rulesFigma, Notion, GitHub - Risotto
upsert_runbook_draftLaptop request
Done. The IT department and three access rules are set up. The laptop runbook is a draft: approve it in Risotto to make it live.
Limits your security team can test
SOC 2 Type II and HIPAA, with zero data retention at our model providers, OpenAI and Anthropic. Your reviewer can open each of these in Risotto.
- Approval policies. One rule, such as “contractors need IT approval”, covers access, tools and runbook steps, with an optional Okta Verify push first.
- An audit log. Who asked, who approved, what ran and when. Configuration changes stream to your security information and event management (SIEM) tool.
- Secrets the AI never sees. Credentials are write-only and go only to the hosts you approve.
Embrace AI enterprise-wide
Start with IT. Then HR, Finance, Legal, Security and Sales Ops get Risotto in the same Slack or Teams, each with its own permissions and a private queue. Jobber runs 12 departments on Risotto, including six People teams. Read the story
What IT teams say
Employees now get fast, efficient answers with the same precision as one of our professionals.
Our target SLA was 2 days and we’re now beating that, averaging only 1 day to ticket close using Risotto.
Risotto is one of the easiest tools I’ve implemented. We were up and running in less than a week and already seeing our first autosolves.
How teams roll out Risotto
Every rollout starts with a free 30-day pilot on your real requests, with our team beside you.
- Before day 1 Connect. Slack or Teams, your identity provider, your ITSM and your knowledge, and the requests Risotto takes first.
- Week 1 Go live. We build your first workflow with you on the call, and Risotto starts answering in your help channel.
- Weeks 2 to 4 Pilot. Your pilot group asks Risotto for help, we tune it together each week, and a readout on day 30 shows the results.
- After day 30 Expand. Add automations, then other teams.
Frequently asked questions
What is Risotto?
Risotto is the AI-native ITSM for IT teams that work in Slack or Microsoft Teams. It resolves requests, from access to MFA resets, in the chat where employees ask, and logs each one as a ticket. How Risotto works
Can Risotto replace Jira Service Management?
Yes, or it can run on top of it. Risotto has its own ticketing, with custom fields, routing rules and reporting, and it syncs both ways with Jira Service Management, ServiceNow and Freshservice. Ticketing
Does Risotto work in Microsoft Teams?
Yes. Employees ask in Teams channels or DMs, and managers approve requests right in Teams. The AI agent
Can Risotto automate onboarding and offboarding?
Yes. Risotto automations start when Rippling, BambooHR or HiBob reports a hire or termination, or when Okta reports an account change. IT describes the steps to the Assistant and chooses which need approval. Automations
How is Risotto different from Moveworks, Console, Serval and Ravenna?
Unlike Moveworks, Risotto answers in your help channels as well as DMs, and every request becomes a real ticket. Console, Serval and Ravenna also take actions; Risotto goes deepest on access requests, with approval policies, time-bound grants and one page of who has what. IT builds new automations by asking the Assistant, with code it can read. Switching from Moveworks
What does Risotto cost?
Risotto is an annual subscription priced by company size, with AI usage included. Every engagement starts with a free 30-day pilot on your real requests. Pricing
Show us the request your team is tired of answering
Built by a former IT engineering lead at Gusto and Dropbox.










