Escalations arrive investigated, with a fix to approve

Some requests need a person. Risotto’s AI Assist makes sure that person starts with the answer. The moment a ticket escalates, it digs through Okta logs, device and HR data, past tickets and your knowledge, writes a plan, and waits in the ticket for your approval on the first change.

Book a demo

How AI Assist handles an escalation

Risotto’s AI Assist does the digging. Your team okays the fix.

  1. It reads the whole case: the ticket, the conversation and what Risotto already tried.
  2. It investigates across your systems, read-only: identity logs such as Okta’s system log, MDM device data, HR context, past tickets and your knowledge base.
  3. It writes a plan, with the reason for every proposed change, such as the log entry that points to the cause.
  4. It starts on the plan. Read-only steps run right away. Each change waits for your team: approve it, redirect AI Assist in chat, or take over.
  5. It keeps its work beside the ticket. The investigation, the plan and each approval stay in the ticket’s private Assistant tab. Anything for the requester goes on the ticket as a comment, once you approve it.
  6. It captures the fix. When a request keeps coming up, AI Assist suggests a runbook, so Risotto resolves it at tier 1 next time.

It starts before anyone opens the ticket

Turn on auto-start for a department, and Risotto’s AI Assist picks up every escalated ticket there on its own, even before you’ve built a single runbook. Each department can add its own rules, like which log to check first when someone can’t sign in.

The requester, already looked up

Risotto’s AI Assist starts with the person behind the ticket: their manager and team from your HRIS, their groups from your identity provider and their devices from your MDM, in one card at the top of the Assistant tab. It keeps only what bears on this ticket, so the macOS version shows up when the problem is a Mac that’s out of date.

Nothing changes until your team says so

Risotto’s AI Assist looks things up on its own, but every tool that changes something, from a Slack DM to an Okta MFA reset, waits for approval. Each approved step is logged under the person who approved it.

From tier 1 to “never happens again”

The AI agent resolves routine requests in Slack and Microsoft Teams. AI Assist handles escalations and turns fixes into runbooks. Insights shows what to automate next.

At Docker, Risotto advanced or assisted 68% of IT tickets. Read the Docker story

Frequently asked questions

Does AI Assist resolve tier 2 tickets, or only suggest fixes?

Both, with your approval. Risotto’s AI Assist writes a plan for an escalated ticket. Your team approves each change and AI Assist runs it, or asks in chat for a different plan, or takes over.

Is AI Assist the same as the Assistant?

Yes. AI Assist is Risotto’s Assistant working an escalated ticket, and in the dashboard it lives in the ticket’s Assistant tab. The same Assistant also sets up Risotto by chat and runs bulk work in Code Mode. The Assistant

Who sees AI Assist’s work on a ticket?

Risotto admins and managers, and the supervisors of the ticket’s department, in the ticket’s Assistant tab. The requester never sees that conversation, only the comments your team approves.

Can AI Assist start on an escalated ticket by itself?

Yes, with auto-start on for the department. Without it, someone on your team starts AI Assist from the ticket’s Assistant tab.

What can AI Assist take action on?

Any tool you connect to Risotto: native integrations such as Okta, Jamf, Iru, Google Workspace, Slack, Jira, Freshservice, Workday and HiBob, custom API tools and MCP servers. Integrations

Watch a live escalation run through AI Assist

Book a demo