Electrician Dispatch: Keeping Customers Updated

The electrician-tuned dispatch system: diagnostic-to-fix updates that narrate the troubleshooting, the texts that make the invoice make sense, and the multi-job day coordination that protects a stacked schedule.

System 8 from the Leveraged Owner Starter Pack

Your tech arrives for a "dead outlets in two rooms" call. Forty minutes later he's still tracing circuits — the problem is a buried junction box behind drywall, and the fix requires opening a wall. The customer watches him pace between rooms with a meter, saying nothing, and starts doing mental math: how long is this taking, and what is it going to cost? When the invoice says $385 for what looked like "walking around with a beeper," she questions it — not because the work was wrong, but because nobody narrated it. Electrical troubleshooting is invisible work. Invisible work gets questioned. Narrated work gets paid.

This is the electrician layer of the dispatch communication system — the foundation is the appointment confirmation system (Pillar D: Full & Calm Calendar), and the en-route and update mechanics live in the communication guides in this series. The electrician twist: your core work — diagnosis — is the part customers understand least and question most. The communication system exists to make the invisible visible.

The diagnostic narration: your most valuable text

Electrical diagnosis follows a pattern the customer can't see: test, eliminate, narrow, find. Narrate it in plain language as it happens:

Hi [First Name], [Tech Name] here with [Business Name] — update on your [issue]. I've ruled out [what's been eliminated, e.g. "the breaker panel — that's all fine"], and traced it to [what's been found, e.g. "a failed connection in a junction box behind the drywall"]. The fix is [what you'll do, e.g. "opening a small section of wall, repairing the connection, and patching it"], which runs [price]. Want me to go ahead? Reply YES.

This text is doing four jobs: it proves the tech did real diagnostic work (ruled out X, traced to Y), it explains the fix in non-electrician language, it states the price before the work (no surprise invoice), and it captures the written YES (authorization on record). The "ruled out" line is the key — it turns 40 minutes of meter-reading from "walking around" into "systematic elimination."

The running-long text: protecting the stacked day

Electricians run 6–8 jobs a day, which means a diagnostic that runs long threatens every job behind it. Two texts handle it — one to the current customer, one (via dispatch) to the next:

To the current customer (when the job passes the quoted time):

Hi [First Name], [Tech Name] here — your [issue] is taking a bit longer than expected ([plain-language reason, e.g. "the wiring issue is deeper in the wall than it looked"]). I want to fix it right rather than rush it — looking at about [X] more minutes. Thanks for your patience!

To the next customer (from dispatch, proactively):

Hi [First Name], [Dispatcher Name] with [Business Name] — heads up that [Tech Name] is running about [X] minutes behind due to a complex diagnosis. Your new window is [new window]. He'll text when en route. Sorry for the delay!

The next-customer text must arrive before the window starts — a delay communicated early is an inconvenience; a delay discovered by waiting is a broken promise. This is the rule that protects the stack's reviews.

The multi-fix discovery: "while I'm here" done right

Electricians find additional issues constantly — the open ground, the double-tapped breaker, the aluminum wiring. The "while I'm here" text turns discoveries into approved additional work instead of awkward upsells:

Hi [First Name], [Tech Name] here — while fixing your [original issue], I noticed [discovery in plain language, e.g. "two breakers sharing one slot, which is a code issue and a fire risk"]. I can fix it while I'm here for [price] — takes about [X] minutes. Want me to take care of it? Reply YES.

Rules for the discovery text: one discovery per text (a list feels like a shakedown), plain language with the safety implication stated factually ("code issue and fire risk" — true, not hyped), and always optional ("want me to take care of it?" — never "I went ahead and fixed it"). The written YES is your authorization and your review protection in one.

The panel/safety-find photo text

When the tech finds something visual — scorched bus bar, melted wire nut, water in the panel — photograph it and text it with the explanation. This is the single highest-converting message in electrical communication:

[First Name], take a look at what I found in your panel: [photo]. See [what to look at, e.g. "the scorch marks on this breaker"]? That's [plain-language explanation, e.g. "heat damage from a loose connection — it's been arcing"]. This is the kind of thing that [factual consequence, e.g. "gets worse over time and can damage the whole panel"]. The fix is [what + price]. Want me to handle it now? — [Tech Name]

The photo does what words can't: it makes the invisible visible. Customers approve photographed problems at dramatically higher rates than described ones — and they show the photo to the spouse, which pre-sells the decision-maker who isn't home.

The job-complete summary: pre-framing the invoice

End every job with the summary text — it's the invoice's cover letter:

Hi [First Name], [Tech Name] with [Business Name] — all done! Here's what was completed: [1–3 bullet-style lines, e.g. "Traced dead outlets to failed junction box connection — repaired and tested. / Replaced double-tapped breaker — now to code."]. Total: [amount], invoice attached/emailed. Everything's tested and working. Thanks for choosing us!

The summary text eliminates the #1 source of invoice disputes: the customer not connecting the amount to the work. When the invoice arrives with the summary fresh in mind, it's a receipt, not a surprise.

Worked example: the dead-outlets day

Example: 2pm — "dead outlets in two rooms." Tech arrives 2:10, en-route text sent at 1:50. 2:35 — diagnostic narration text: ruled out panel, traced to junction box, $285 fix, "reply YES." Customer replies YES at 2:40. During the repair, tech spots the double-tapped breaker — discovery text with photo at 3:05, $95 additional, customer replies YES at 3:10. 3:45 — job-complete summary text with the full list and total ($380). Invoice emailed at 3:50. Five texts, two written authorizations, zero invoice questions, one 5-star review mentioning "great communication." The electrical work was competent. The narration was the differentiator.

Compliance note

Job-status texts are transactional (about work the customer requested) — the lowest-risk texting there is. You still need 10DLC business-texting registration (application-to-person 10-digit long code — the carrier system for business texting) before sending: 1–7 day approval, ~$15–$20 in fees. Include opt-out language in automated texts, and observe TCPA (federal telemarketing law) quiet hours (no texts before 8am or after 9pm recipient local time). Keep safety claims factual — "code issue," "fire risk" for genuinely hazardous findings — and never exaggerate a finding to sell the fix. General information, not legal advice.

Related guides in this series

The foundation is the appointment confirmation system (Pillar D). For the en-route text that starts every job, see the en-route guide in this series — and for the "job done" text that closes it, the completion-message guide.

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.

Get the AI Automation Starter Pack — $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 dispatch-communication setup guide, every script (including all trade-specific variants), the diagnostic-narration templates, the photo-text playbook, and complete setup guides for all 8 systems.

No third-party statistics cited in this post — all frameworks are operational. The worked example is labeled as an example, not a customer result.

Keep building your systems

Related guides from the Leveraged Owner blog: