Skip to main content
Runbooks are natural-language instructions that guide your agents through conversations while allowing them to adapt to unique situations.

What is a Runbook?

A runbook is a set of instructions written in plain language that tells your agent how to handle conversations. Unlike rigid scripts, runbooks give agents flexibility to adapt while following a general procedure. Example:
When a customer asks about refunds:
  1. Acknowledge their request and express understanding
  2. Ask for their order number if not provided
  3. Look up the order using the Order Search tool
  4. Check if the order is within the 30-day refund window
  5. If eligible, process the refund and confirm the timeline
  6. If not eligible, explain the policy kindly and offer alternatives
  7. Ask if there’s anything else you can help with
The agent follows this structure but adapts its language and approach based on the specific conversation.

When to Use Runbooks

Runbooks are ideal when:

Runbook Structure

A good runbook includes:

Objective

What the runbook should accomplish:
Objective: Help customers with password reset requests while maintaining account security.

Steps

Sequential instructions to follow:
  1. Greet the customer and confirm their request
  2. Verify identity by asking for their registered email
  3. Check account status using the Account Lookup tool

Tool References

Links to specific tools when actions are needed:
Use the [Password Reset Tool] to send the reset email.

Conditional Guidance

Instructions for different scenarios:
If the account is locked, escalate to the security team. If the customer can’t access their email, offer alternative verification.

Snippets

Reusable instruction blocks included from your snippet library:
Insert the Verify Customer Identity snippet from the editor’s @ menu.

Runbooks vs Workflows

Choose runbooks when:
  • The conversation could go many directions
  • You want AI to handle edge cases intelligently
  • Instructions are easier to write than flowcharts
Choose workflows when:
  • Every step must happen in exact order
  • Compliance requires deterministic execution
  • Multiple tools must coordinate precisely

Example Runbooks

Customer Support Runbook

Order Inquiry Runbook

Next Steps

Create a Runbook

Build your first runbook

Snippets

Create reusable instruction blocks

Compare to Workflows

Understand when to use each