What a real dispatch summary should look like

Most dispatch summaries fail one test: can the tech walk into the job and start working, or do they need to call the customer back to figure out what is going on?

If the answer is "call back," the summary failed.

A real summary has six fields. Every job, every time:

1. Customer name, address, gate code or access notes.

2. Phone number plus the best time to reach them.

3. The actual problem in the customer's words — "no hot water since last night," not "plumbing service requested."

4. Urgency level — emergency, today, this week, scheduled.

5. What the customer expects when you arrive — diagnostic, repair, replacement quote.

6. Notes on anything weird — dog in the yard, prior tech visited, warranty in play.

That is it. No more. No less.

What you do not need: a sales pitch script, a five-paragraph intake narrative, a list of every previous job. The tech needs to know what to fix and what the customer wants. Background noise costs time.

The hardest part is not writing the summary. It is getting one every time, on every call, including the 11 PM ones nobody is awake for. That is where most shops break. The owner writes great summaries when they take the call. The fill-in receptionist writes okay ones. After-hours generates nothing usable, so the tech shows up at 8 AM cold.

Fixing this is mechanical. Either you train every intake person on the six fields, or you put the intake on a system that captures them every time without you having to think about it.