The One-Page Communication setup guide for Techs

Everything a tech needs to know about customer communication on a single laminated page: the five texts, the exact timing, the phrases that build trust — and the lines nobody on your team ever crosses.

System 8 from the Leveraged Owner Starter Pack

Your best tech is a magician with a manifold gauge and a disaster with a phone. He shows up unannounced, works in silence for three hours, hands over an invoice the customer doesn't understand, and drives off — and then he's genuinely confused by the 3-star review that says "never told me what was going on." He doesn't need a communication seminar. He needs one page, in the truck, that tells him exactly what to send and when. This is the field-execution layer of the dispatch communication pillar: the setup guide (standard operating procedure) that makes every tech communicate like your best tech.

Why one page (and why techs ignore everything longer)

Techs don't read manuals. They read the thing taped to the visor. A 12-page communication policy gets filed in the glovebox and never opened; a single page with five text templates gets used daily. The constraint is the feature: one page forces you to decide what actually matters, and what actually matters fits in five texts and a short forbidden list. Print it, laminate it, put one in every truck and one on the shop wall. When you hire, it's page one of the field training packet.

The five texts (the entire setup guide in practice)

These are the only customer texts a tech needs to master. Each has a trigger moment, a template, and a timing rule:

Text 1 — En route (30 minutes out). Trigger: wheels rolling toward the job. This is the highest-value text in the setup guide — it eliminates "where's my tech?" and it's the touch customers name in reviews.

Hi [First Name], [Tech Name] from [Business Name] — on my way, about [30] minutes out. See you soon.

Text 2 — On-site arrival (at the door). Trigger: parked, before knocking. Short and warm — it tells the customer the clock has started and you're in control.

Hi [First Name], [Tech Name] here from [Business Name] — just arrived, taking a look at [the unit / the issue] now. I'll update you once I've diagnosed it.

Text 3 — The diagnosis update (before any work beyond the diagnostic). Trigger: you know what's wrong. This is the money text — it prevents the "he just started replacing parts" complaint and sets up the price conversation honestly.

Update from [Tech Name]: found it — [plain-language diagnosis, e.g., "the capacitor that starts your compressor has failed"]. The fix is [description], which runs $[amount] [parts + labor]. Want me to go ahead? Reply here or I'll come find you.

Text 4 — Running behind (the moment you know). Trigger: you realize you'll miss the window or the expected finish. Same-day honesty, with the new ETA — never silence.

Hi [First Name], [Tech Name] here — running about [45] minutes behind [on the repair / getting to you]. New ETA is [time]. Sorry for the shift — I'll keep you posted.

Text 5 — Job done (before leaving the driveway). Trigger: work complete, area cleaned. Summarizes what was done and what's next — the invoice pre-frame.

All done, [First Name] — [Tech Name] from [Business Name]. [What was fixed/replaced, parts used]. [What to watch: "keep an eye on X, call us if Y"]. Your invoice is [coming by text/email — $[amount]]. Thanks for having us out today.

The forbidden list (what never to promise)

The second half of the page is the "never" list — the lines that create liability, disappointment, or both. Every tech memorizes these:

The tone guide (three lines, not a seminar)

Techs don't need a writing course; they need three tone rules at the bottom of the page:

Rolling it out (the 20-minute training)

Don't email the setup guide and hope. Run a 20-minute rollout: gather the techs, walk through the five texts with real examples from recent jobs, role-play the diagnosis text once (the one they'll resist most), and hand out the laminated cards. Then enforce it for two weeks — the dispatcher checks that en-route texts went out, and you review one job-done text per tech per week. What gets checked gets done. After two weeks it's habit, and after a month the techs will tell you customers mention the texts unprompted. The setup guide also becomes your coaching tool: a communication complaint now has a specific, checkable standard behind it — "the setup guide says the diagnosis text goes out before work begins; walk me through what happened" — instead of a vague "communicate better."

One compliance note for the page footer: these texts go to customers with existing relationships about their active jobs — the lowest-risk texting there is. Still run them through your registered business number (10DLC business-texting registration: ~$15–$20, 1–7 day approval), keep opt-out handling active, and respect TCPA (federal telemarketing law) quiet hours (8am–9pm local). General information, not legal advice.

Related guides in this series

The one-page setup guide is the field-execution layer of the Full & Calm Calendar pillar — the office-to-field handoff tells the tech what to know, and this setup guide tells them what to say. Together they mean every customer gets the same professional communication whether your best tech or your newest hire is on the job.

Get System 1 free: the complete Missed-Call Safety Net

The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.

Stop missing calls and chase reviews on autopilot: the AI Automation Starter Pack is $27 one-time: https://leveragedowner.com/starter-pack/

The done-for-you version

This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step setup guide, every script, the worksheets, and complete setup guides for all 8 systems. The one-page tech setup guide is pre-written, print-ready, with all five text templates and the forbidden list formatted for lamination.

Stats sourced as labeled: no statistics used in this post.

Keep building your systems

Related guides from the Leveraged Owner blog: