> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Playbooks

> Your organisation's rulebook for what REX flags and what it ignores: plain-language rules that shape every signal, and that learn from what your team dismisses.

A Playbook is your organisation's set of custom rules for how REX behaves across every deal, specifically what it pays attention to when generating [signals](/rex/signals) and recommended actions.

Instead of every org getting the same generic AI judgment, a Playbook lets you tell REX what matters to your business: what should always be flagged, what should never be raised, and how your team prefers to be nudged into action.

It's a living document. You can edit it directly, and REX also learns from your team's behaviour over time, proposing new entries whenever a pattern in dismissed signals suggests a rule would help.

***

## How it works

A Playbook is an ordered list of plain-language rules, each one a short title and description. For example:

> Don't flag pricing objections from procurement as high-risk.

> Always flag when a deal has gone quiet for more than 10 days.

There's one Playbook per organisation, and it applies across every deal room your team works in.

### Shaping signal generation

Every time REX generates signals for a deal, it reads your organisation's Playbook first and uses it to decide what to raise and what to skip.

This is how two organisations selling similarly can end up with meaningfully different signal feeds. One org's Playbook might suppress noisy competitor-mention signals, while another's prioritises them.

### Learning from dismissals

When someone on your team dismisses a signal and gives a reason, REX looks for a pattern. If a certain kind of signal keeps getting dismissed for the same reason, it proposes a new Playbook rule that would prevent similar low-value signals from being raised again.

These proposals show up as **suggested edits**: a queue of add, update, and delete operations you can review, approve, or dismiss.

<Warning>
  The Playbook never changes without your say-so. Every suggested edit sits in a review queue until someone explicitly approves or dismisses it.
</Warning>

### Manual editing

You're never limited to what REX suggests. The Playbook editor lets you add, edit, or remove rules directly at any time: write a new rule, tighten the wording on an existing one, or delete something that's no longer relevant.

Every change takes effect on the next signal-generation run.

***

## How different roles use this

<AccordionGroup>
  <Accordion title="Sales reps">
    You won't typically edit the Playbook yourself, but it's worth knowing it exists.

    * If you notice REX consistently flagging (or missing) the same kind of thing across your deals, that's a Playbook conversation to have with whoever manages it on your team.
    * When you dismiss a signal, take a second to pick an accurate reason. That feedback is what feeds the suggested-edit loop and improves the signals everyone sees going forward.
  </Accordion>

  <Accordion title="Onboarding & CS teams">
    The Playbook applies to every room, so use it to tune the signals you get on onboarding and account work, not just sales deals.

    * If the default signal feed is too noisy or too quiet for the things you care about post-sale, such as a stalled setup step, an admin who's gone quiet, or an unused feature, write a rule for it. The same Playbook governs every room type.
    * A good rule to co-own with whoever runs sales: what counts as an adoption risk worth flagging during onboarding versus what's normal ramp-up noise.
    * Dismiss onboarding-specific signals with a real reason when they're not useful. That feedback shapes future suggested edits the same way it does for sales signals.
  </Accordion>

  <Accordion title="Managers">
    * Use the Playbook to encode team-specific judgment calls once, instead of correcting the same kind of signal repeatedly across every rep's deals.
    * Review the suggested-edits queue periodically. It's a useful pulse check on what kinds of signals your team is finding unhelpful, which can surface both Playbook gaps and training opportunities.
    * If reps across your team are dismissing the same category of signal for the same reason, that's a strong candidate for a Playbook rule rather than a one-off dismissal.
  </Accordion>
</AccordionGroup>

***

## FAQ

<AccordionGroup>
  <Accordion title="Who can edit the Playbook?">
    Anyone with access to the Playbook settings can add, edit, or delete rules directly at any time.
  </Accordion>

  <Accordion title="Does the Playbook affect every deal, or just one?">
    It applies organisation-wide. Every deal room's signal generation reads the same Playbook.
  </Accordion>

  <Accordion title="How do suggested edits get created?">
    When your team dismisses signals with a reason, REX looks for patterns and proposes Playbook rules that would prevent similar low-value signals in the future.
  </Accordion>

  <Accordion title="Do suggested edits change the Playbook automatically?">
    No. Every suggested edit sits in a review queue until someone explicitly approves or dismisses it.
  </Accordion>

  <Accordion title="Does the Playbook control the recommended actions REX suggests, too?">
    The Playbook's primary job is shaping which signals get raised or suppressed. Recommended actions are generated per-signal based on what's actually actionable in that moment.
  </Accordion>

  <Accordion title="What does a Playbook rule actually look like?">
    Just a short title and a plain-language description, with no special syntax or configuration format required.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.