Plumber Dispatch: The Parts-Run Update Text

Your tech diagnoses a failed water heater at 10am. The replacement unit is at the supply house 20 minutes away. He tells the customer "I'll be back in a bit," drives off — and doesn't return until 12:30 (line at the counter, wrong unit pulled, traffic). The customer has spent two and a half hours wondering if the plumber quit the job. She doesn't complain about the water heater. She complains about the silence. In plumbing, the #1 review-killer isn't the work — it's the unexplained gap in the middle of it.

This is the plumbing 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. Plumbing's twist: jobs routinely pause mid-visit — parts runs, supply-house trips, waiting on water to drain — and every pause is a silence the customer fills with anxiety.

The silence problem: why plumbing jobs go quiet

Plumbing has more mid-job pauses than any trade:

• Parts runs. The truck doesn't carry every valve, heater, and fixture. Supply-house trips are normal — but to the customer, the tech just left.
• Drain-and-wait cycles. Water heaters drain, lines depressurize, sealants cure. Dead time is built into the work — and the customer watches the clock.
• The "let me check something" disappearance. The tech goes to the truck, the basement, the crawlspace — and the customer has no idea what's happening or for how long.

The fix isn't faster work — it's narrated work. Every pause gets a text. The texts take 20 seconds; the silence costs reviews.

The parts-run update text

The flagship message. Sent the moment the tech decides a parts run is needed — not when he's already been gone 30 minutes:

Four elements: what (the part — specificity builds credibility), how long (the round trip — honesty beats optimism), when back (a time, not "soon"), and reassurance (the explicit "under control"). If the run stretches — line at the counter, wrong part — one follow-up text: "Still at the supply house — running about 20 minutes behind. Sorry for the wait!" The follow-up is what separates professionals from ghosts.

The diagnostic narration: making the invoice make sense

Plumbing invoices get questioned more than most trades' — because the customer can't see what was wrong or what was fixed (it's all inside walls and under floors). Narrate the diagnosis by text as it happens:

The text authorization does double duty: it gets the written yes (dispute protection), and it gives the customer the explanation in writing — which is what they forward to the spouse who asks "what did the plumber say?" When the invoice arrives, it's not a surprise; it's the number they already approved.

For bigger jobs, add the photo: a picture of the corroded valve, the cracked fitting, the failed element — texted with the diagnosis. A photo of the problem is worth more than any verbal explanation, and it ends price objections before they form.

The mid-job status texts: the complete set

Build these into the tech setup guide (standard operating procedure) — one text per pause, every time:

• Water draining / system depressurizing: "Hi [First Name] — draining the [water heater/lines] now, which takes about [X] minutes. Then we'll [next step]. All normal!"
• Waiting on a part delivery: "Quick update — waiting on [part] to arrive, expected around [time]. I'll get started on [other task] meanwhile."
• Job taking longer than quoted: "Hi [First Name] — this is taking a bit longer than expected ([reason in plain language]). New estimate: done by [time]. Sorry for the stretch — want to make sure it's done right."
• Job complete, wrapping up: "All done! Just testing everything and cleaning up now — [Tech Name] will walk you through it in a few minutes."

Notice the pattern: what, how long, what's next. Every text answers the three questions the customer is silently asking.

Worked example: the water heater day

Example: 10:00am — tech arrives, diagnoses failed water heater. 10:15 — diagnostic narration text with photo of the corroded tank bottom, price, "reply YES." Customer replies YES at 10:20. 10:25 — parts-run text: "grabbing the new unit, back around 11:15." Supply house line runs long — 11:05 follow-up: "running about 20 behind." 11:35 — "back on site, draining the old unit now, about 30 minutes." 12:30 — "new unit in, filling and testing." 1:00 — "all done, walking you through it now." Six texts, 90 seconds of tech time total. The customer never wondered, never worried, never called the office. The review, left that evening: "Great communication the whole time." The work was standard. The narration was the product.

Compliance note

Job-status texts are transactional (about an in-progress job 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); tech-sent manual texts during a job are conversational, but keep the opt-out in your templates. 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.

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 tech texting checklist, the diagnostic-narration templates, and screen-by-screen setup instructions 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: