Help CenterPlatform · Onboarding

Playbook

Live strategy document per client: call scripts, emails, internal notes with bold/italic/strike formatting, a Meeting Handoff section for running and advancing meetings, launch plan with Weeks 1-12 meeting targets, team photos, grouped responder aliases, field-level comments with threaded replies and resolve/reopen, and shareable deep links.

Updated Jul 8, 2026 11 steps 17 questions answeredOpen this page in the platform
On this page

Overview

The Playbook is the live strategy document for each client engagement: positioning, ICP, personas, call scripts, email templates, launch plan with first-quarter meeting targets, team assignments with Google Workspace profile photos, responder aliases, and a Meeting Handoff section that covers how to run and advance meetings. Internal users edit and review here; clients see a trimmed view when the playbook is marked visible. The call-script and email sections have a light formatting toolbar (bold, italic, strikethrough), so a strategist can italicize a stage direction and an SDR reading it live can tell an instruction from what to say. The per-section internal note field (the AI rationale beneath each script block) now uses the same toolbar, so guidance you leave for the team can be emphasized too and never gets read aloud as part of the spoken script. Field-level comments support threaded replies and resolve/reopen, so a reviewer can answer a note in place and clear it once handled. You can open the Playbook from the client switcher or jump straight to a client with a shareable deep link.

How to use this page

  1. Open the Playbook for a client

    In Platform, go to Onboarding > Playbook. Pick the client in the header switcher first, or use a direct link: /platform/onboarding/playbook/{dealId}. The deep link syncs your session to that client automatically so sections and API calls load the right playbook without changing the switcher yourself first. A legacy ?dealId= query on the base URL redirects to the same deep link.

  2. Review your assigned team

    Open Your Team in the left rail to see strategist, director, onboarding manager, chief customer officer, sales rep, and SDR cards for this engagement. A playbook can also show extra people after the sales rep card (for example a second sales rep) when that has been configured for the client. Profile photos pull from Google Workspace when available (synced on each playbook load and refreshed on full regeneration). Team members without a Workspace photo show initials. Unassigned roles display a placeholder card.

  3. Browse sections

    Use the left rail to jump between sections (Your Team, Aliases, Overview, ICP, Personas, Stories, Meeting Handoff, Calling Script, Post-Call Emails, Launch Plan, and more). Orange comment badges show open notes on a section. Click a section title to scroll the main document to that block.

  4. Review the Meeting Handoff section

    The Meeting Handoff section sits just above the Calling Script and covers how meetings are run and advanced. As an internal editor, shape an Intro paragraph, then a Handoff Process block (always visible) of editable cards. Below it are three blocks you can remove and restore to default: Meeting Management (How To Hold Strong Sales Meetings) and First Meeting Best Practices (Cold Introductory Call Flow), each a set of cards, plus a two-column row of Decision-Making Questions and Recommended B2B Sales Books (one item per line). Each card has an eyebrow, title, and bullet list; use Add card to add one, the trash on a card to remove it, and the trash in a block header to hide a whole block (Restore default content brings it back). Every field saves when you click out. Clients see the formatted cards and lists in read-only mode. Each field has a comment button for notes.

  5. Edit and format a call-script or email section

    As an internal editor, click into a Calling Script or Post-Call Email section to edit it. Each section has a small formatting toolbar: Bold, Italic, and Strikethrough. Use italics or bold to mark stage directions and asides (for example an instruction like "pause, then ask") so an SDR reading the script live can tell what to say from what to do. Changes save automatically when you click out of the field. The formatting carries through to the dialer's live script tab and the PDF export. Sections written as plain text before this still render unchanged.

  6. Format the internal note under a section

    Beneath each Calling Script section is an Internal note field labeled "not shown to client". This is where the AI rationale for the section lives, and where you can leave guidance for the team. It now uses the same light toolbar (bold, italic, strikethrough) as the section itself, so you can emphasize a note without it ever being read aloud as part of the spoken script. Type your note, format as needed, and it saves when you click out. Use the clear button beside the note to empty it. Notes stay internal: clients never see them, even in the client view.

  7. Set weekly meeting targets in Launch Plan

    Open the Launch Plan section and scroll to Projected Meetings (Weeks 1-12 meeting targets). Each week shows a bar chart, a numeric target, and up/down controls for internal editors. Defaults ramp from 0 in week 1 to 4 meetings by week 8 and stay there through week 12 until you edit and save. Clients see the same chart in read-only mode. Google Doc export includes these targets.

  8. Review responder aliases

    Open the Aliases section to see client-facing outbound identities: display name, photo, role label, and every Primary or Sender inbox tied to that alias. Accounts that share the same linked responder or display name appear on one card with multiple mailto links, so prospects see one person even when outreach uses several inboxes. Alias notes at the bottom come from deal settings when present. If no Primary or Sender inboxes are configured yet, alias notes still appear on their own instead of showing the empty state.

  9. Generate a new playbook (internal)

    If no playbook exists yet, open the Generate section. For most clients you need a completed Playmaker value proposition first, or generation is blocked. Platform-only clients are exempt, so their playbook (and per-client migration agent) can be generated even without a Playmaker value prop. Choose model and style settings, add optional request details or a legacy Google Doc URL for context, and click Generate Playbook. This creates the strategy sections, email templates, and cold-calling script in one pass. Full regeneration also refreshes team profile photos from Google Workspace.

  10. Review, comment, and share with the client

    Internal users can leave field-level comments, toggle View as client to preview the client-facing cut, and turn on Visible to client when the document is ready. Use Copy Share Link to copy the stable deep link for Slack or email. Clients see sections without Generate, Active Comments, or History, and the section toolbars and internal notes are hidden for them. Use Copy Content or PDF / Print to export; Google Doc export groups aliases the same way as the page and includes weekly meeting targets. Open Campaign jumps to the linked outreach campaign.

  11. Resolve, reopen, and reply to comments

    Open a field's comment panel from the speech-bubble icon on any field, or use the Active Comments list in the left rail to jump to an open note. In the panel, each top-level comment has a Reply button to start a threaded reply: type in the composer that appears, then click Reply to post it (Cancel closes it). Replies nest under their parent with a left border and can be resolved or deleted but not replied to again, so threads stay one level deep. Use Resolve on any comment or reply to mark it handled: the text gets a strikethrough and dims, a Resolved date appears, and the note drops out of the Active Comments list and the section badge counts. Resolved comments stay visible in the panel for history. Reopen (the same button, now labeled Reopen) restores a resolved comment back to the active views. In the Active Comments list, each note also has a green Resolve button next to Open Thread for one-click clearing.

What the buttons do

Bold / Italic / Strikethrough
The formatting toolbar on each call-script and email section, and on the per-section internal note field (internal editors only). Bold or italicize text to mark stage directions and asides so an SDR does not read them aloud; strikethrough to cross text out while keeping it visible. Formatting saves on blur and shows in the dialer and PDF export.
Internal note field
The editable AI rationale beneath each Calling Script section, labeled "not shown to client". Now a formatting-enabled box (bold, italic, strikethrough) for team-only guidance. Saves on blur; never visible to clients.
Clear internal note
The button beside a section's internal note that empties the note field.
View as client
Internal preview toggle. Shows the same sections and copy a client user would see, hiding internal-only tools, the section formatting toolbars, and the internal notes.
Visible to client
When checked, clients assigned to this engagement can open the Playbook. When off, clients see a Coming soon message.
Show history
Internal toggle to surface the change log for playbook fields across the document.
Copy Share Link
Copies the stable deep link for this client Playbook so you can paste it in Slack or email. Internal users only.
Generate Playbook
Creates the full strategy document from Playmaker inputs and generation settings (internal only, when no playbook exists yet). Also refreshes team profile photos from Google Workspace.
Projected Meetings (Launch Plan)
Weeks 1-12 meeting target grid with bar charts. Internal users edit the number per week or use the up/down arrows; changes save on blur. Defaults show until edited. Included in Google Doc export.
Week goal up/down arrows
Increment or decrement a week meeting target by one. Saves immediately.
Copy Content
Copies the playbook JSON to your clipboard for backup or handoff.
PDF / Print
Opens the browser print dialog to save or print the current playbook view, with call-script formatting preserved.
Open Campaign
Jumps to the Platform campaign tied to this playbook.
Your Team (left rail)
Assigned team grid: strategist, director, onboarding manager, CCO, sales rep, and SDR, plus any extra team members configured for this playbook (such as a second sales rep), shown after the sales rep card. Photos sync from Google Workspace on load and regeneration.
Aliases (left rail)
Responder alias cards plus alias notes from deal settings. Notes render on their own when no Primary or Sender inboxes are configured yet.
Section comment badges
Orange speech-bubble counts on the left rail mark sections with open comments. Counts reflect only open notes; resolving a comment decrements its section badge and removes it from the Active Comments list. Resolve or reopen notes from the Active Comments list or a field's comment panel.
Meeting Handoff section
Sits above the Calling Script. Internal editors shape an Intro, a Handoff Process card block (always visible), and three removable, restorable blocks: Meeting Management, First Meeting Best Practices, and a two-column Decision-Making Questions and Recommended B2B Sales Books. Add card adds a card, the trash removes a card or hides a whole block, and Restore default content brings a hidden block back. Saves on blur. Clients see formatted read-only cards and lists.
Resolve / Reopen (comment)
Mark a comment handled or restore it. In the comment panel each top-level comment and reply has a Resolve button (it toggles to Reopen once resolved); in the Active Comments list each note has a green Resolve button next to Open Thread. Resolved comments get a strikethrough and dimmed style with a Resolved date, and drop out of the active list and section badge counts, but stay visible in the panel thread. Reopen puts them back.
Reply (comment thread)
Starts a threaded reply under a top-level comment in the comment panel. Opens a composer pre-addressed to the commenter; post with Reply or cancel. Replies nest under the parent (one level only) and can be resolved or deleted.

Common questions

The base /platform/onboarding/playbook route needs a client context. Pick a client in the header switcher, or open a deep link that includes the deal id: /platform/onboarding/playbook/{dealId}.
As an internal editor, click into the section and use the Bold, Italic, and Strikethrough buttons in the small toolbar above the text. It is meant for light emphasis, for example italicizing a stage direction so an SDR treats it as an instruction rather than something to read aloud. Your changes save automatically when you click out of the field.
Yes. The Internal note field beneath each Calling Script section (labeled "not shown to client") now has the same Bold, Italic, and Strikethrough toolbar. Formatting a note keeps it visually distinct from the script and makes sure the guidance is never spoken aloud. Notes stay internal and clients never see them. Older plain-text notes still render exactly as before.
Section formatting renders in the dialer's live script tab and in the PDF export, so an SDR sees it on the call. Clients viewing the playbook see the formatted section text too, but the editing toolbar is hidden for them and they cannot change it. Internal notes are never shown to clients at all.
They keep working exactly as they were. Plain-text sections and notes render unchanged, including their line breaks, and you can add formatting to them any time by editing the field.
Yes. Use /platform/onboarding/playbook/{dealId}. Anyone with access to that client can open it directly; the page syncs session scope before loading data. You can also click Copy Share Link in the hero bar.
Playbook pulls profile photos from Google Workspace for assigned team members. If Workspace has no thumbnail for that person, or the role is unassigned, you see initials or a placeholder. Photos refresh when the playbook loads and again on full Generate Playbook.
Yes. A playbook can carry extra team members beyond the standard strategist, director, onboarding manager, CCO, sales rep, and SDR slots. When configured for a client, those people appear as their own cards in Your Team right after the sales rep, with the role label set for them. This is set up per playbook, so most clients show only the standard roster.
New playbooks show a ramp: week 1 starts at 0, weeks 2-3 at 1, weeks 4-5 at 2, weeks 6-7 at 3, and weeks 8-12 at 4 meetings. Strategists can edit any week. The chart rescales bars relative to the highest week.
Primary and Sender inboxes that share the same linked responder or the same display name are grouped on one card. That matches what prospects experience: one recognizable person, even when outreach rotates across multiple mailboxes.
Some platform-only clients have alias guidance in deal settings (alias notes) before any Primary or Sender inboxes are provisioned. The Aliases section shows those notes even when there are no email cards yet. The empty state appears only when there are neither cards nor notes.
Either the playbook is not marked Visible to client yet, or your team is still preparing the document. Internal users control visibility with the toggle in the hero bar.
Playmaker captures intake and value proposition inputs during onboarding. Playbook is the generated, editable strategy document (scripts, emails, launch plan) built from that foundation.
For most clients, no: a completed Playmaker value proposition is required, and Generate Playbook is blocked until it is in place. Platform-only clients are the exception. They self-serve their outreach and often skip the Playmaker value prop, so the readiness gate is waived and their playbook can be generated right away.
It sits just above the Calling Script and holds the playbook for running and advancing meetings: an intro, a Handoff Process block, Meeting Management (How To Hold Strong Sales Meetings), First Meeting Best Practices (Cold Introductory Call Flow), Decision-Making Questions, and Recommended B2B Sales Books. Internal editors can add and remove cards, hide an entire block and restore its default content, and leave comments per field. All changes save when you click out. Clients see the same content as formatted, read-only cards and lists.
Resolve marks a comment as handled. The comment text gets a strikethrough and dims, a Resolved date is added, and the note drops out of the Active Comments list and the section badge counts so it stops demanding attention. The comment stays in the field's comment panel for history. Use Reopen (on the same comment, in the panel) to put it back into the active views.
Yes. In the comment panel, click Reply on a top-level comment to open a reply composer addressed to that commenter. Replies appear nested under the parent with a left border. Replies can be resolved or deleted, but you cannot reply to a reply, so threads stay one level deep.

Prefer it done for you?

Everything in these guides is work SalesHive can run for you: US-based SDRs and AI agents working your campaigns, calls, and inbox on one platform.

Explore the platform