Docs

Learn / Set up

How Risotto works (video)

A three-minute video that follows four requests from Slack: an access request, a question, a request your own runbook handles, and one that Risotto escalates to your team.

Watch four requests go through Risotto: an access request, a question, a request only your own runbook can handle, and one that Risotto hands to your team. The stage rail on the left of the video lights up as each request moves, so you see each stage and what shapes it. Each stage below links to the guide that sets it up.

An access request

  1. Request

    Priya posts in #ask-it: "Can I get Figma? I'm joining the brand redesign." Risotto opens a ticket for it, IT-1042. Every request becomes a ticket, so nothing gets lost. See Request sources.

  2. Department

    Risotto routes it to a department. #ask-it isn't tied to one team, so Risotto reads each department's description and picks the one that fits: IT. See Departments.

  3. Access rule

    Figma is one of your applications, and its Figma Editor rule says how to grant it: add the person to the Figma Users group in Okta. See Access rules.

  4. Approval

    The rule also says who approves. It uses an approval policy, and for Priya, her manager approves. So Marcus gets a direct message in Slack, with Approve and Deny. He clicks Approve. Risotto adds Priya to the group in Okta, tells her she's in, and resolves the ticket. Every step is logged on it. See Approval policies.

Microsoft Teams works the same way, with approvals as Teams cards. See Creating tickets in Microsoft Teams.

A question

  1. Knowledge

    Maya asks how to set up the VPN on her new laptop. Risotto searches the knowledge you've connected, finds the VPN guide in Confluence, and answers with the steps and a link to the page. Risotto answers only from what it finds. See Connect knowledge.

A runbook with your own tools

  1. Runbook

    Runbooks take it further, with actions that are unique to your company. Tom lost his badge. IT has a runbook for that, and its steps use Suspend badge, a tool Northwind built from its badge vendor's API. Risotto suspends the lost badge and tells Tom to pick up a new one at the front desk. Risotto has no integration for that badge system, and it doesn't need one. See Runbooks and Tools.

A request your team takes

  1. Escalation

    Daniel posts: "The Zoom Room in Maple says it's not registered." No access rule, article or runbook covers it, so Risotto doesn't guess. It escalates to your team.

    Every request has a thread in IT's agent channel in Slack. Risotto posts there that it needs help, with a summary of what Daniel needs and why it escalated, and tags your escalation contact. Daniel hears that someone from the team is on it.

  2. AI Assist

    With AI Assist on for IT, it starts on the ticket right away. It reads the ticket, looks Daniel up in your connected systems, and posts a plan for your team. Before any step that changes something, it asks for approval. See Set up the Assistant for a department.

  3. Your team replies

    Jordan from IT replies in the agent channel thread, and Risotto posts the reply in Daniel's thread, under Jordan's name. Then Risotto steps back, and Jordan takes it from there. See Escalations.

That's the whole path: request, department, access rule, approval, knowledge, runbook, and escalation. How Risotto works covers each stage in more detail.

Next, install Risotto in Slack.

Something wrong or missing? Report an issue · View as Markdown