The Parts-Delay Text: Delivering Bad News Proactively

The control board for the customer's furnace is backordered two weeks. The tech knew at 10am. Nobody told the customer. At 4pm she calls the office: "Is my heat fixed?" — and learns for the first time that it isn't, and won't be, for fourteen days. She's not angry about the backorder. Backorders happen. She's angry that she spent the whole day believing her heat was being fixed. The delay didn't damage the relationship. The silence did. This is the bad-news layer of the dispatch communication pillar: a three-part script that turns the worst moment of a job into a trust-building one.

The tell-before-they-ask rule

Every delay has two timelines: when you learn about it, and when the customer learns about it. The gap between those two moments is where trust dies. The rule is absolute: the customer hears about the delay within one hour of you knowing, and always before they have to ask. A customer who learns about a delay from your text thinks "they're on top of it." A customer who learns about it by calling you thinks "they were hiding it." Same delay, same facts, opposite conclusions — determined entirely by who spoke first. Put this on the tech setup guide as a hard rule: diagnose the delay, text the office, office texts the customer. No waiting to "see if it resolves."

The script: honesty + new ETA + option

Every delay text has the same three components, in this order. Miss one and the message fails:

• Honesty: what happened, in plain language, no jargon, no minimizing. "The part is backordered" — not "we're experiencing supply chain challenges."
• New ETA: the revised timeline, specific. "Two weeks" is specific; "as soon as possible" is a dodge and customers know it.
• Option: something the customer can choose. A temporary fix, a reschedule, a loaner, a partial completion. The option returns control, and control defuses anger.

Notice what the option does: it converts the customer from a victim of the delay into a decision-maker about the delay. People don't leave 1-star reviews about problems they helped solve. They leave them about problems that happened to them in silence.

Parts delays vs. schedule delays (different messages)

Not all delays are parts delays, and the message changes with the cause:

• Parts backordered: the script above. The customer's frustration is with the situation, not you — your job is to show you're managing it aggressively (checked with three suppliers, expedited shipping, temporary workaround).
• Schedule slip (running behind): shorter fuse, same structure. The honesty is about your operation, which stings more — so the option matters more. Offer the reschedule you suggest, not one they have to negotiate.
• Discovery delay (found more damage): this is really a change-order conversation wearing a delay costume. The update announces the discovery and the revised timeline; the pricing conversation happens separately with a signature. Never combine "it'll take longer" and "it'll cost more" in one text — that's two pieces of bad news, and each deserves its own handling.
• Weather delay: the easiest one. Nobody blames you for rain. Still tell them before they ask — the habit is the point, and weather delays are free practice for the hard ones.

The follow-up cadence during a long delay

A two-week backorder with one text and then silence is just a slower version of the original sin. Long delays need a cadence:

• Day 1: the delay text above (honesty + ETA + option).
• Midpoint: a status text even if nothing changed. "Still on track for [date] — checked with the supplier this morning, no change." The message isn't information; it's proof you're still watching.
• 2 days before the new ETA: the confirmation. "The [part] is confirmed arriving [date], we're scheduled to finish [day]." This rebuilds the anticipation the delay destroyed.
• Day of completion: normal job-done communication. The delay is history; don't relitigate it.

If the ETA slips a second time, call — don't text. A second delay by text reads as a pattern; a second delay by voice, with a human explaining what they're doing about it, reads as a problem being managed. The channel escalation is itself a signal of how seriously you take it.

What never to do (the four delay sins)

• Blame the supplier by name in a way that sounds like excuse. "Our supplier dropped the ball" makes you sound like a victim of your own supply chain. "The part is backordered — here's what I'm doing about it" keeps the focus on your action.
• Give a fake ETA to buy time. "It'll be here Friday" when you don't know is the most expensive sentence in contracting. When Friday comes empty, you've converted a delay into a lie — and lies get reviews, delays get understanding.
• Go silent hoping it resolves. The tech's instinct: don't tell them until you have good news. The customer's experience: abandonment. Tell them at hour one, update at the midpoint, confirm before the finish.
• Offer a discount unprompted. Discounting a delay trains customers to see delays as compensation events. If the delay genuinely cost them something (a hotel night with no heat), make it right specifically and proportionately. Blanket "sorry for the delay" discounts just price your reliability downward.

Making it stick: the delay protocol on one page

Add this to your tech communication setup guide as the delay protocol: (1) diagnose the delay; (2) text the office within the hour with the facts; (3) office sends the honesty + ETA + option text to the customer the same hour; (4) calendar the midpoint check and the pre-completion confirmation; (5) if the ETA slips twice, the owner calls. Five steps, one page, laminated in every truck. Example: an electrical shop institutes the protocol after a panel backorder fiasco costs them two 1-star reviews. Six months later they have four more backorder delays — and zero bad reviews from them, because every customer got the text at hour one with an option. The delays didn't stop. The damage did.

Related guides in this series

Proactive delay communication is the crisis layer of the Full & Calm Calendar pillar — arrival windows set the expectation, daily updates maintain it on long jobs, and the delay protocol protects it when reality intervenes. Together they mean the customer never has to wonder what's happening, which is the entire foundation of a 5-star reputation.

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 screen-by-screen setup instructions for all 8 systems. The delay text templates, the long-delay cadence, and the one-page delay protocol are pre-written and ready for every truck.

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