Playbooks
Playbooks are repeatable, multi-step workflows that agents execute following a defined SOP. They combine the structure of a process document with the execution power of an AI team.
What playbooks are
A playbook is a Standard Operating Procedure (SOP) that agents can execute. Instead of a document that describes what should happen, a playbook is a living workflow that actually does the work. Define the steps, assign agents to each step, set checkpoints for human approval, and let the platform execute the process end to end.
Playbooks bring consistency to complex processes. Every quarterly business review follows the same structure. Every new employee onboarding hits the same checkpoints. Every client proposal goes through the same review stages. The agents handle execution; humans handle judgment.
Playbooks are parameterized. When you execute a playbook, you provide the inputs (client name, quarter, budget, etc.) and the agents fill in the details based on actual data from the knowledge base and connected systems.
Playbooks vs skills, workflows, and swarms
BOSS has several types of agent-executable patterns. Here is how they differ:
Think of it this way: skills are verbs, workflows are if-then rules, swarms are project teams, and playbooks are repeatable process templates. A playbook can contain swarms as individual steps -- for example, a QBR playbook might have a "competitive analysis" step that runs a parallel swarm.
Example: Quarterly Business Review
Here is a complete playbook for preparing and delivering a Quarterly Business Review (QBR) for a client. This is one of the built-in templates available in the playbook library.
Pull revenue, usage, support tickets, and NPS data from connected systems (Salesforce, Stripe, Zendesk). Compile into a structured dataset.
Output: Data table + metrics summary
Analyze quarter-over-quarter trends, identify anomalies, calculate growth rates, and flag at-risk metrics. Generate visualizations.
Output: Analysis document with charts
Create a presentation deck with executive summary, key metrics, trend analysis, wins, challenges, and recommendations for next quarter.
Output: QBR presentation document
Review the deck for messaging consistency, tone, and completeness. Flag any claims that need data backing or sections that need human judgment.
Output: Review notes
Account owner reviews and approves before client delivery
Create a briefing document with talking points for each slide, anticipated client questions, and suggested responses. Include expansion opportunities.
Output: Talking points document
Draft the client email with the QBR deck attached, scheduling link for the review call, and summary of key highlights.
Output: Client email
Account owner approves email before sending to client
Executing a playbook
Playbooks can be executed from the studio UI (click "Run Playbook"), from the API, or triggered by ambient agents on a schedule (e.g., run the QBR playbook automatically 2 weeks before each quarter end).
When a playbook hits a checkpoint, execution pauses and the designated approver is notified via their preferred channel (Slack, Teams, email, or in-app). The approver can review the outputs, provide feedback, and approve or reject. If rejected, the playbook loops back to the failed step with the feedback.
Checkpoint actions:
Creating custom playbooks
You can create custom playbooks from scratch, clone and modify a template, or have an agent generate one from a natural language description of your process. Custom playbooks support:
Built-in playbook templates: BOSS includes 20+ playbook templates out of the box: Quarterly Business Review, New Employee Onboarding, Client Proposal, Sprint Retrospective, Incident Response, Content Publication, Compliance Audit Prep, Board Meeting Prep, Customer Offboarding, and more. Browse them at /admin/playbooks/templates.