Playbooks you can paste in today
A playbook is four fields: a description and routing hints the classifier reads, triage instructions the investigating agent follows, and the data sources it may use. These examples are complete. Copy one, paste each field into Playbooks in the portal, and change the table names to yours.
Accounts & Sessions
A deliberately narrow playbook for login, access and permission tickets, and an illustration of why narrow is good.
Catalog & Sync
A playbook for integration and data-sync tickets, the category where the root cause is usually an expired credential.
Checkout & Orders
A playbook for the buyer-facing half of payments: declines, failed checkouts, and orders that did not appear.
Payments & Payouts
A complete playbook for money-owed-to-merchant tickets, with the fields filled in exactly as you would paste them.
Platform Reliability
A playbook for "everything is slow" and "the site is down", scoped to infrastructure, and the one worth pairing with a scheduled report.
Write your own
- Generate playbooks from your codebaseOne prompt for your AI coding agent (Claude Code, Cursor, Copilot or any other) that reads your repository and drafts paste-ready playbooks.
- Anatomy of a playbookWhat each field is for, how the classifier and the investigator use them differently, and how to tell a good playbook from a bad one.
- Writing triage instructionsThe one field that decides whether an investigation is good, and a structure that reliably works.
Paste one in and point it at a ticket
Playbooks are included on every seat, as many as you need. No card to start.