Use Cases and Playbooks
These playbooks walk through building real systems with subagents — the kinds of recurring, multi-system workflows that operations, finance, and account teams deal with every day. Each one starts in your AI client, builds out the tools the agent needs, configures the agent itself, and ends with the work running on its own.
Playbooks
Playbook: Build a Shared Toolbox for Your Organization
Before your team builds subagents, someone needs to build the tools those agents will draw from. This platform-level playbook walks the owner of the workspace's toolbox — a platform engineer, ops architect, or internal-tools champion — through setting up a vetted, versioned, observable set of tools that connects Assist to your internal systems. The result: every teammate building an agent pulls from the same trusted shelf instead of asking AI to re-invent the integration each time.
Playbook: Build an Ops Channel Concierge in Slack
Your operations team lives in one Slack channel. Every question that lands there — order status, customer credit, inventory, returns — pulls someone away from their actual work to answer it. This playbook walks you through building a subagent that lives in that channel, knows where to look in your internal systems, and answers the routine questions itself, escalating only what really needs a human.
Playbook: Build an Overnight Reconciliation Agent
The numbers in your warehouse system and the numbers in your ERP are supposed to agree. They almost never do. This playbook walks you through building a scheduled subagent that pulls a snapshot from each system every night, diffs them, keeps a running log of every discrepancy, and tells you which ones are new and which are still open from before — so finance can close the books without spending a week chasing mismatches.
Playbook: Build a Tier-1 Support Triage Subagent
Most support tickets are not new problems — they are the same handful of issues, asked again. This playbook walks you through building a triage subagent that handles routine questions itself by delegating to specialist subagents, and only routes a real ticket to a human when none of them can answer. The result is a Slack channel where 70% of inbound questions get a useful response in under a minute, and a real ticket only gets created when one is actually warranted.
Playbook: Build a Vendor Intake Coordinator
Onboarding a new vendor is a multi-step process: collect their info, route it to legal for review, collect a W-9, set them up in the ERP, notify procurement. Today, somebody copies and pastes between forms, email, and a spreadsheet. This playbook walks you through building a subagent linked to a sandcastle app that runs the whole intake flow — vendors fill out a form, the agent picks it up, drives every downstream step, and posts status updates to the procurement Slack channel.