Playbooks
Playbook Reviewed · not yet fact-checked
In short
What is a playbook page and how do I use one?
Each playbook page anchors to a specific sales situation — reviving closed-lost deals, founder-led outbound, a cold database, a lean team adopting an AI SDR, or inbound signals going cold — and walks from targeting through sequence structure, templates, and expected results to the exact steps that build it in Reply.
A playbook is anchored to a specific situation, never a keyword. Each page starts from a moment teams actually recognize — "our closed-lost pipeline is sitting untouched", "trial signups keep going cold" — and works forward: who the play fits, how to target, the sequence structure step by step, illustrative message templates, the results to expect, and the numbered steps that build the whole thing in Reply.
Playbooks (this section) vs Playbook (Jason AI object). These pages are human-readable outreach recipes. The Playbook object is Jason AI configuration — the machine version of a strategy. A page here may tell you which Playbook object to create.
The plays
Reactivate closed-lost pipeline
deals lost to timing, budget, or a competitor, reopened with what-changed messaging
Outbound for seed-stage founders
founder-led meetings from a small account list without burning the main domain
Re-engage a cold contact database
hygiene first, a permission-style reopener, prune whatever stays silent
AI SDR for lean teams
Jason AI with approval gates for a one-to-three person GTM team
Book meetings from inbound signals
fast follow-up on visitors, downloads, and trials before intent decays
Craft that carries across every play
Each play sets the situation, the targeting, and the cadence. The message still has to earn a click, and the levers for that are the same whichever play you are running:
- Personalize with real data. Use the prospect's first and last name in the body, as merge fields — see Templates and variables.
- Give one compelling reason to respond. Keep the email to five sentences or less so the prospect is not overwhelmed, name the recipient and their job title, and state plainly which problem your product solves and what they gain from replying.
- Segment before you write. The documented dimensions are referral source, job title, company type, region or city, desired outcome, and interest or problem. Smaller, more personalized sequences are also less likely to be marked as spam.
- Check grammar and punctuation. Poor grammar irritates recipients; running the copy through an editing tool such as Hemingway or Grammarly is the documented check before sending.
- Close with a professional signature. Visible contact details are what let a stranger trust the sender — full construction detail lives in Outbound for seed-stage founders.
Reply publishes no benchmark click rate to measure these against. Each play's expected-results table states exactly which numbers are documented and which are not.
Related
- Workflows — complete outcomes with every product rule on the path
- Core concepts — the mechanisms these plays depend on, from deliverability to reply classification
- Capabilities — what Reply can and cannot do at the task level