Docs

Learn / Basics

How runbooks work, with three examples (video)

A three-minute video of how runbooks work, then three examples: access with manager approval, a new hire equipment form, and unlocking an Okta account.

Watch how a runbook tells Risotto how to handle one kind of request: when it applies, and the steps and tools to run. Then see three ways to use one, each built in the dashboard and run in Slack. Each part below links to its written guide.

Before you start, make sure you can create runbooks: Org Admins and Org Managers can create any runbook, and a department Supervisor can create runbooks for their own departments. See Runbooks.

How runbooks work

  1. Open Runbooks

    Open Runbooks in the sidebar. Each runbook shows its tools, how often it's been followed, and an Enabled switch. Click Create runbook.

  2. Pick a match condition

    Give the runbook a title. Then pick a Match condition. Request match is the default: Risotto compares each request to the Description you write. Department request applies to every request routed to one department. See How runbooks are matched.

  3. Write the agent instructions

    Under Agent instructions, write numbered steps in plain English. Type # to add a tool, and @ to tag a person, a group, or an approver. See Using tools in runbooks.

  4. One step, one turn

    Each step is one turn in the conversation. Risotto either replies or uses a tool, then moves on to the next step. To reply and act together, put both in one step.

  5. Save, test, turn it on

    When you save, the runbook starts out disabled. Open Test Match, type a sample request, and check that it matches. Saved Matches keeps up to 20 examples you can run again. Then turn on Enabled. See Testing matches with saved matches.

Example 1: Access with manager approval

The description says: an employee asks for access to Looker.

  1. Step one asks why they need it.
  2. Step two uses Request Approval, with Requestor's manager as the approver.
  3. Step three uses Add User to IdP Group to add them to the Looker group, then resolves the ticket.

On the Tools page, set that tool's Approval to Not required, so the manager's approval is the only one. See Add User to IdP Group and Require approval.

In Slack, the employee asks for Looker and says why. Their manager gets a direct message with Approve and Deny. One click, and the employee is in the group.

Example 2: New hire equipment form

Under Forms, click Add form. Name it, then add the fields: employee name, start date, laptop, accessories, and shipping address. The form lands in your instructions. Next, Risotto reads the answers back, waits for a yes, and escalates the order to your hardware team. See Runbook forms.

In Slack, the form appears right in the thread. The manager fills it in, clicks Submit, and confirms.

Example 3: Unlock an Okta account

  1. Step one asks the employee to confirm they're locked out.
  2. Step two uses Unlock Okta User.
  3. Step three tells them to sign in again, and resolves the ticket.

If the unlock fails, Risotto escalates to IT. As in example one, set that tool's Approval to Not required on the Tools page. See Require approval.

In Slack, the employee says they're locked out, replies yes, and their account is unlocked.

Start from a template

You can also start from a template. Click Browse templates for ready-made runbooks for Okta, Jamf, Intune, and your HR system, then open one and click Use this template. See Create a runbook.

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