Skip to content

TEAM ENABLEMENT — DISPATCHER & OFFICE PLAYBOOKS

When the one person who knows is away, the desk stalls.

Two or three people carry how the business actually runs, in their heads. When they are away standards slip; when they leave, you relearn it from scratch. These are those decisions written down — for somebody mid-shift with a phone ringing, not for a binder on a shelf.

Book a pilot call

Free · 20 minutes · no commitment

YOUR DAILY OPERATIONS

WHO THIS IS FOR

Operations where standards visibly slip when one or two specific people are away.

THE PROBLEM

It also puts a ceiling on everything else. You cannot automate a decision nobody has written down, you cannot hold anyone to a standard that exists only verbally, and you cannot hire into a role whose knowledge lives inside the person currently doing it. Writing it down is the prerequisite for most of what comes after.

WHAT IT LOOKS LIKE

Shared drive

EXAMPLE DOCUMENT

Service desk playbook

PLAIN FILES IN YOUR OWN DRIVE · LAST EDITED 28 SEPTEMBER BY NADIA

Extra work found on the hoist

ONE PAGE · READ IT DURING THE CALL

  • Get the tech’s note and one photo before you dial.
  • Give the customer one price, parts and labour together, and the new pickup time.
  • Their yes goes on the work order, by text or on a recorded call, before the tech starts.
  • No answer: try again in 20 minutes, then text the photo.

Who decides

You handle it
The customer’s recorded yes on any amount, and a discount up to $50
Pass it up to the service manager
A discount over $50, a declined brake or tire item, or no answer after two triesManager decides
Pass it up to the owner
A customer asking for the work free, or for money backOwner decides

One page per recurring decision

  • Extra work found on the hoist

    Open now · edited 28 Sep by Nadia

  • Car not ready at the promised time

    Edited 21 Sep by Sam

  • Comeback inside 30 days

    Edited 21 Sep by Sam

  • Parts late past the promised day

    Edited 14 Sep by Nadia

  • Customer declines a safety item

    Edited 14 Sep by Sam

  • Invoice questioned at pickup

    Edited 7 Sep by Nadia

6 PAGES · EACH FITS ON ONE SCREEN · THE DESK EDITS THEM

Running the desk to it is yours. When the work changes, change the page, or ask us to.

An auto repair shop’s service desk playbook: one short page per recurring decision, in the shop’s own words, saying what the advisor handles, what gets passed up and at what point, kept as plain files the shop owns.

What you get.

  • A procedure for each recurring decision, in the words your team already uses.
  • Escalation rules saying what gets handled, what gets passed up, and at what point.
  • A format short enough to be read during a shift, not before one.
  • Plain editable files you own, not entries in a system you would have to keep renting.

How it works.

Priced against the scope, after a Diagnostic that is small on purpose. The shape of the work we can tell you now.

THE SHAPE
One fixed-scope pass, ending with documents in your hands.
WHAT WE NEED FROM YOU
Time on the desk watching the work, and the two or three people who hold the knowledge.
WHAT YOU KEEP
The playbooks, and the prerequisite for automating any of those decisions later.

What this does not include.

Published because you should know before the call, not after the invoice.

  • A quality-management system or ISO documentation.
  • Enforcement. We write the playbook; running the desk to it is yours.
  • A promise it stays current. Revisit it when the work changes, or ask us to.

How we price this →

QUESTIONS

Is this just documentation?

It is documentation with a purpose. It standardises the work now, and it is the prerequisite for automating any of those decisions later — you cannot automate a judgement nobody has described.

Who writes it?

We do, from watching the work and interviewing the people who do it. Your team corrects a draft instead of facing a blank page — the only version that ever gets finished.

WHERE THIS APPLIES

The industries whose page names Team Enablement as one of the places we would start. Each one is written for that trade, with its own numbers.

Bring us one bad week.

Book a pilot call. Tell us where the week goes wrong, and we’ll tell you what an Operations Diagnostic would map and measure.

The first paid step has a clear scope and an end date, and the pilot after it is one workflow — not a platform, and not an open-ended retainer.

Free · 20 minutes · no commitment