Generating playbooks using Glyphic

Last updated: April 19, 2026

Glyphic generates living sales playbooks from your team's actual call data — discovery patterns, objection handling, demo scripts, persona maps — and lets you regenerate, version, and reference them across the platform. Playbooks are self-served from the Playbooks page.

What's in a generated playbook

Each playbook is generated as a single Markdown document with the following sections:

  • Pitch — strategic narrative built from your actual call language.

  • High-level playbook — company overview, buyer personas, value proposition, competitor differentiation.

  • Discovery playbook — qualifying questions your top reps actually ask, with the reasoning behind each.

  • Demo script — how to walk a prospect through the product, grounded in real demo calls.

  • Objection handling guide — common objections and responses that worked.

  • Personas and pains — detailed map of the personas in your ICP.

  • Common questions — FAQ grouped by persona, with the calls each question came from.

The output is grounded in real calls in your Glyphic workspace, so the examples — discovery questions, objections, language — are your team's, not generic templates.

How to generate a playbook

  1. Open the Playbooks page from the left navigation.

  2. Click Request a New Playbook. This opens an Agent prompt prefilled with "Generate a sales playbook."

  3. Optionally refine the prompt to scope the playbook — e.g. "Generate a sales playbook for our enterprise AEs based on calls in the last 90 days tagged Discovery". You can pass:

    • A date range (default: last 60 days).

    • A list of users to include (default: all reps).

    • A list of call tags to filter by (default: all tags).

  4. Submit. The agent collects up to 500 calls across up to 20 calls per company, generates each section in parallel, and saves the result as a new playbook version. Generation typically takes a few minutes; you'll get an email when it's done.

You need at least 30 matching calls for the agent to generate a playbook. If there aren't enough, the agent will tell you which filters to relax.

Versions and regeneration

Each playbook keeps a full version history. Click any past date in the Version history sidebar to view that version. Click Regenerate to run the same prompt again against fresh call data — the new output is added as another version on the same playbook so you don't lose the previous one.

Regenerating with the same prompt is the most common way to keep a playbook current as your messaging, ICP, or competitive landscape shifts.

Using playbooks across Glyphic

Once a playbook exists in your workspace, other Glyphic features and agents can read it:

  • Ask Glyphic and Agents can pull the latest playbook content as context. For example, an agent drafting an email can ground its tone and competitor positioning in your playbook.

  • Agents can search inside playbook content for specific positioning, competitor mentions, or named plays.

Monitoring playbook adherence and freshness

Playbooks are most useful when you can tell whether reps are following them and whether they still reflect what's actually working. Both can be done with Agents:

Adherence

  • Use a recurring agent to compare recent calls against the playbook and flag where reps are skipping discovery questions, missing objection responses, or going off-script. Schedule it weekly and route the output to a Slack channel for managers.

  • If you want adherence tracked per skill across every call, define a coaching scorecard using the playbook's discovery questions and objection responses as the rubric. The scorecard then scores every matching call automatically.

Freshness

  • Run an agent that compares the current playbook against the last month of calls and flags where reality has diverged — new objections that aren't in the guide, deals where the listed differentiators didn't land, personas appearing on calls that aren't in the persona map.

  • When the divergence is meaningful, hit Regenerate to produce a refreshed version.

Permissions and feedback

Anyone in the workspace can request and view playbooks. Playbook generation runs on the calls the requesting user is allowed to see (private calls are excluded).

The Send us feedback link on the Playbooks page opens a Pylon ticket — let us know if a generated playbook missed something important or read off, so we can tune the generation process.