A Playbook is an automation — a routine dpaperwork runs for you. You don't
configure one in a builder; you describe what you want in plain English and Chat
drafts it, structured and ready to review. Every Playbook is saved inactive
so nothing runs until you've read it and switched it on yourself.
The loop: describe, review, activate
Say what you want to happen and when. Chat drafts the Playbook and saves it,
paused, for you to check.
In Chat
Every Friday afternoon I want you to check each active client project, find anything that slipped this week, and draft me a short status note per client that I can review before sending.
Great idea — this is a classic end-of-week pulse check. Your Weekly Client Status Review Playbook is drafted and ready for your review. Every Friday afternoon it scans all active projects and cycles, identifies slipped tasks (anything due Mon–Fri that didn't get marked done), drafts a short status note per client, and bundles everything into one review doc.
Drafting doesn't switch it on. You review the four-section body — When to
trigger, Description, Steps, References — and activate it yourself.
PlaybooksWeekly Client Status Review
Open the drafted Playbook to read its Steps and References, edit anything that
isn't quite right, then flip it from Inactive to Active. Nothing runs until you
do.
Three ways a Playbook can trigger
The Friday report runs on a schedule. That's one of three trigger types —
and you pick between them just by how you describe the routine.
On demand — a routine you run by hand, when you decide.
In Chat
Also make me one I can run by hand: when I say so, put together an onboarding checklist for a named new client and send it to me to review.
Done! The New Client Onboarding Checklist Generator Playbook is drafted and waiting in your Playbooks for review. When you trigger it, it asks you for the client name, pulls their workspace context (company record, linked contacts, deals, and projects), generates a tailored onboarding checklist, and creates a Document you can review.
Event-driven — a routine that fires on its own when something happens in your
workspace.
In Chat
And one that fires on its own: whenever a deal moves to Closed Won, create the kickoff project and a task to schedule the kickoff call.
Done! The Closed Won → Project & Kickoff Setup Playbook is drafted. The moment you mark a deal as Closed Won, it reads the deal details, creates a project named for the client and deal, creates a high-priority task to schedule the kickoff call due in 3 business days, and notifies you with a summary so you can review before anything kicks off.
See them all in one place
Chat drafts Playbooks; the Playbooks section is where you review, activate, and
manage them.
In Chat
What playbooks do I have now?
Here are your 3 Playbooks — all currently drafted and pending activation: Weekly Client Status Review (every Friday afternoon); New Client Onboarding Checklist Generator (manual, on demand); Closed Won → Project & Kickoff Setup (automatic on Closed Won). Head to your Playbooks section to review and activate any of them.
Playbooks
All three sit here as Inactive drafts. Open each one, check what it will do, and
activate the ones you want running. The scheduled one starts on its next
Friday; the event-driven one waits for the next Closed Won; the on-demand one
runs whenever you trigger it.