Skip to content

Document · reads article

Playbooks

Repeatable procedures.

Long-form text, written and read in place.

A trigger on every one. A playbook without a trigger never gets opened at the right moment.

Late delivery

Order 2+ days overdue · 5 · Tomas

Damaged on arrival

Customer reports damage · 4 · Camille

Supplier misses a date

Lead time slips · 6 · Tomas

New trade account

Wholesale enquiry · 7 · Camille

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Tells you what to do right now, in order, when something is going wrong — which a wiki does not.

Every playbook has a trigger, because one without a trigger never gets opened at the right moment.

The same situation is handled the same way regardless of who is on shift.

How it works

  1. 1

    A playbook is written after the second time a situation is handled differently.

  2. 2

    The trigger is what connects it to the moment — the agent offers it when the situation arises.

  3. 3

    Steps are ordered and meant to be followed in order under pressure.

  4. 4

    Running one does not require deciding anything, which is the point.

Best for

Briefs, notes, policies, anything read as prose.

Not the right choice for

Structured fields pretending to be prose.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
PlaybookrequiredtextThe situation it handles, named as the thing that goes wrong.
TriggerrequiredtextWhat makes somebody open it. Required — one without a trigger is never opened in time.
StepsrequirednumberHow many steps, so the reader knows what they are committing to.
OwnertextWho maintains it, and usually who runs it.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • No enforcement or tracking. Nothing records that a playbook was followed.
  • No branching. A situation with two real paths is two playbooks.
  • Steps are text, not tasks, so nothing is assigned or ticked.
  • A playbook nobody rehearses is a document, not a capability.

Before it works

What you have to provide, if anything.

  • Write the trigger first. A playbook without one is a wiki page.
  • Pair with Wiki for how things work, which is a different question from what to do now.

In practice

A shop where complaints were handled differently by each person.

What do we do when something arrives damaged?
What was said to the agent

What the agent built

A four-step playbook triggered by a customer reporting damage, with an owner.

What changed

Resolution went from a day and a half to under two hours, mostly because nobody spent time deciding what to do first.

Questions

What data does the Playbooks page use?

It reads article records the agent has collected. Repeatable procedures. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a document the wrong choice?

Structured fields pretending to be prose. It is best for: briefs, notes, policies, anything read as prose.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ