Setting up Playbook

A section-by-section guide to configuring Playbook — your team, the way you sell, what "good" looks like, and what Brevity should watch for. Playbook defines the framework; Meeting Analyzer applies it to your meetings.

Home

The Home tab is your setup hub. It opens with a short description of Playbook, a guided setup checklist, and a Playbook Coverage panel.

The checklist walks you through getting your org running, in order:

1. Roster import — the people with a Brevity seat populate your roster automatically; there's nothing to add by hand.
2. Assign positions — the first piece that needs your input: give each person a position (AE, SDR, CSM…). A position is what tells Brevity which processes and rubrics apply.
3. Assign processes to positions — link each position to the sales motions it runs. A position with no process has nothing to be scored against.
4. Map meeting types and stages — make sure each process has the right meeting types, and each meeting type breaks into the right stages.
5. Set scoring criteria — give every stage its milestones and rubric criteria so Brevity can score against what good looks like.
6. Configure coaching rules — set the tone and length of feedback, then tailor coaching by position, process, or meeting type.
7. Set up signals and alerts — define the phrases and moments Brevity watches for, and where to route them.

The Playbook Coverage panel tracks your progress at a glance — how many positions are in use, how many processes are live, and how many meeting types have stages — alongside how many setup tasks are complete.

People

The People tab is your roster — the people who have a seat in Brevity and will be evaluated. It has three sub-tabs.

People — the list. Your roster populates automatically from everyone who has a Brevity seat, so you don't add people here — you assign their positions. Each person shows their name, their role in Brevity, the teams and user groups they belong to, and their position (chosen from a dropdown of the positions configured for your org).

Teams & Groups — a faster way to assign positions in bulk. You can set a default position for a team or user group, so everyone in it inherits that position. Anyone not in a team or group is assigned individually on the People tab. Individual assignments always take precedence over a team or group default.

Positions — where you define the positions themselves (and their categories). Positions are the connective tissue of Playbook: a person's position determines which processes, coaching rules, and signals apply to them.

Meetings

The Meetings tab is where you define how you sell. It has two sub-tabs: Processes and Meeting Types.

Processes

A process is a sales motion (for example, an enterprise sales cycle). Each process can be active or inactive and brings together:

• the positions that run it,
• the meeting types it includes,
• the coaching rules tied to it, and
• the signals and alerts tied to it.

From a process you can add meeting types (from existing templates), add coaching rules, and associate signals — so a process is a single place to see everything that applies to that motion.

Meeting Types

A meeting type (for example, a discovery call) is attached to one or more processes and breaks down into stages. Each stage carries its own scoring criteria, and the stages together make up the meeting's score.

Opening a stage reveals its milestones and scoring criteria in a side drawer:

• Each stage's criteria are weighted, and the weights add up to 100% (for example, 40% / 35% / 25% across a stage's items).
• Each scoring criterion is graded on a 1–100 scale with defined anchors that describe what each level looks like — for example: 0 (not done at all), 20 (vague), 50 (solid but generic), 75 (tailored to the prospect), 100 (exceptional). You write these anchors so Brevity scores against your definition of good.
• Criteria can include context (such as "the first three minutes of the call") to guide how they're evaluated.

Like processes, a meeting type can also carry its own coaching rules and signals — so you can configure these broadly (at the process level) or specifically (at the meeting-type level).

Coaching

The Coaching tab is the home for all your coaching rules — the complete set you've configured, where you can add new rules or edit existing ones. (You can also reach coaching rules from within a process or meeting type; this tab is the full library.)

A coaching rule is made up of:

• Trigger — when the rule fires: always on, in the first N days, after N days, when scored below team average, when scored above team average, or first coaching at the scope.
• Scope and target — where it applies: team, user group, user, position, process, or meeting type (you can add more than one scope).
• Coaching effect — what changes: tone, length, custom instructions, or banned words (words Brevity shouldn't use in coaching).
• Tone — a preset such as encouraging, direct, mentor (warm), or analytical (neutral) — or a custom tone.

You can stack multiple rules; together they shape the coaching Brevity writes.

Signals & Alerts

The Signals & Alerts tab is the home for everything Brevity should watch for and how to respond. (Like coaching, signals can also be set within a process or meeting type; this tab is the full set.)

A signal is defined by:

• Type — a mention, a sentiment shift, or a behavior.
• Definition — what Brevity is watching for and how to recognize it.
• Phrase to detect and precision — exact, close, or loose matching.
• Where it applies — real meetings and role plays, real meetings only, or role plays only.
• Scope and target — same options as coaching rules.
• Severity — info, warning, or critical.
• Actions — what happens when it fires: flag it in the recap, alert the manager, alert the team member, or notify a channel, each with a priority. You can stack multiple actions; they run top to bottom.

Personas — coming soon

Personas are the simulated counterparts your team practices against — customers, candidates, direct reports, and stakeholders. When available, you'll be able to build a persona library, map personas to your meeting types and processes, shape how they look, sound, and behave, and define their knowledge boundaries (what they do and don't know) so role plays stay realistic.

Data

The Data tab is where you upload materials and review what's been extracted. Each section has a downloadable sample, and you can export your current roster:

• People & Positions — a roster CSV (expected columns: name, email, team, position, skill level). Because your roster imports automatically, this upload is mainly a fast way to set or update positions and skill levels in bulk — not to add people.
• Processes — a sales playbook or process doc.
• Meeting Types — a meeting-types doc, transcript, or recording.
• Coaching Rules — a coaching guide or coaching samples.
• Signals & Alerts — a phrase list, compliance doc, or annotated transcript.

Every upload is extracted into structured items and shown in your upload history, where you review and apply or reject each result before it's committed — so nothing goes live until you approve it.

Settings

• Scoring Thresholds — set the org-wide Green / Amber / Red score boundaries used across scoring and analytics.
• Data Sufficiency — minimum and provisional sample sizes, and options to suppress rankings or trends below a set number of meetings, so you're not drawing conclusions (or firing alerts) from a single call.
• Meeting Classification — choose how meetings are categorized: above a confidence threshold Brevity can classify automatically; below it, a meeting is flagged for manual review.
• Skill Levels (coming soon) — coach people differently as they grow.

Need help? Reach out to your Customer Success Manager.