Plain-English runbooks. Exact where it matters.

Write the procedure the way you’d brief a teammate, and type # to add the tools the agent can use. Then choose what the AI decides: you set the inputs that must never change, and the agent fills in the rest from the conversation.

Book a demo

You choose what the AI decides

Every tool in a runbook shows each of its inputs, and who sets it.

  • Set by author. You type the value once, such as the Jira project, issue type and priority. The agent never sees it as a choice: Risotto adds it when the tool runs, so the request always lands in the right project, channel or group.
  • Set by agent. The agent fills it in from the request, such as the summary, the reason or the person’s email.
  • Same tool, different jobs. Use a tool twice with different fixed values, and give each use its own name, such as “Open the hardware request” and “Open the security review”.

When a whole step must run exactly the same way every time, make it a script tool: TypeScript the Assistant writes and you can read.

Write it the way you’d brief a teammate

A runbook is a numbered list of steps in plain English. The editor does the rest.

  • Type # to add a tool, from your connected systems, your custom API tools or Risotto’s built-in tools.
  • Type @ to name who or what a step involves: a person, an identity provider or Slack group, a channel, an approval policy or an approver role such as Manager.
  • Type / for everything else, from headings and lists to tools and people.
  • Send a form. Add a native Slack form or Teams card when you need exact details from the employee.
  • Choose which requests it covers. Describe them in plain words, pick a department, or match requests that another system creates.

Hover any tool in the runbook to see its row and its inputs. You can see exactly what the agent can do before the runbook goes live.

Approvals at the steps that matter

Add the Request Approval tool to any step and name who decides, including the requester’s manager. The agent stops there until they approve, and follows your rejection steps if they deny.

Each use of a tool can also carry its own approval policy. Reading a ticket and closing every ticket in a project can be the same tool, but they don’t need the same approver.

# it-help
  1. Dana Reyes9:12 AM

    My laptop's battery barely lasts an hour. Can I get a replacement?
    ✅ 1
  2. RisottoApp9:12 AM

    Using tool Look Up Jamf Computer…

    Is it your MacBook Pro with the serial number ending in 7QHX?
  3. Dana Reyes9:13 AM

    Yes, that one.
  4. RisottoApp9:13 AM

    Waiting for an admin approval

    Replacing a laptop that's less than three years old needs approval. I'll let you know as soon as it's decided.
  5. RisottoApp9:31 AM

    Using tool Create Jira Issue…

    Approved. I've opened IT-4182 for your new laptop, and the hardware team has it.
Risotto · Direct message
  1. RisottoApp9:13 AM

    🔒 Risotto is requesting approval for a step of a runbook.

    Reason: Dana's laptop battery barely lasts an hour, and she's asking for a replacement.

    Condition met: The laptop is less than three years old.

    ApproveDeny

    ✓ Approved by Priya Shah

Build by asking. Review every change.

Brief the Assistant, and it drafts the runbook, adds the tools and sets their inputs.

  • Every change is a draft with tracked changes. Approve it, or say what to fix.
  • Test before you publish, against past requests, including ones that shouldn’t match.
  • Restore any version. Every runbook keeps its history.
  • Start from a template for common requests, such as Okta and Entra password resets, Entra MFA resets, and FileVault and BitLocker recovery. Browse the library

Runbooks outlast vacations, promotions and “the one IT person who knows how this works”. Anyone on the team can read and update them.

Runbooks answer requests. Automations start on their own.

A runbook tells the agent how to handle a request an employee makes. An automation starts without anyone asking: when Okta or your HR system reports a change, on a schedule, or when a webhook fires. Both use the same editor, the same tools and the same “Set by author” inputs.

“We wanted to implement more standardization and automation in our help desk, but there wasn’t an easy way in Slack without clunky custom work. Risotto helped us do that.”

Vergil Smith, IT Manager, Vidyard

Frequently asked questions

What is an AI runbook?

An AI runbook is a written procedure that an AI agent follows to resolve a request. In Risotto, a runbook is a plain-English list of steps with the tools the agent may call, the inputs you fixed, and the approvals it must get.

How do I control what an AI agent does in an IT workflow?

In Risotto, you list the tools a runbook may use and choose who sets each input. Values you set never change at run time, and any step can wait for an approval. Every runbook change is a draft you review before it goes live.

Can I fix some tool inputs and let the AI fill in the others?

Yes. Each input of each tool in a runbook is “Set by author” or “Set by agent”. Risotto adds the values you set when the tool runs, so the agent cannot change them, and the agent fills in the rest from the request.

Do I need to write code to build a runbook?

No. Runbooks are plain English, and the Assistant can write them for you. When a step must run exactly the same way every time, you can make it a script tool, which is TypeScript you can read and test.

What is the difference between a runbook and an automation?

A runbook tells Risotto how to handle a request an employee makes. An automation starts on its own, from an Okta or HR event, a schedule, a ticket event or a webhook. Automations

Write down how IT works. Let Risotto follow it.

Book a demo