The customer's been waiting eleven days. Her compressor is on backorder at the supply house, the ETA has slipped twice, and nobody at your shop called to say so. So she calls you, hot, and the first thing your front desk does is apologize for a delay it didn't even know existed.
Here's the thing. That backordered part isn't really what made her angry. The silence did. A customer who knows the compressor lands Thursday can live with it, maybe run a couple of window units a few more days. A customer who hears nothing assumes you forgot her, or that the whole job fell through a crack.
You can't make the supplier ship faster. What you can control is whether the delay gets handled quietly, ahead of time, or whether it detonates on your front desk at 4:45 on a Friday. The fix is a habit, not a better vendor: flag every open job that's waiting on a part, and push the customer a plain update whenever the date lands or moves.
Track the part, not just the job
Most of this falls apart because the part lives in someone's head, or on a sticky note stuck to the tech's dash. The job is in your system. The part you ordered for it usually isn't, at least not anywhere a dispatcher can see at a glance.
For every open job waiting on something, you want a short record you can pull up in five seconds. Keep it boring and keep it complete:
- What the part is, and which job and customer it belongs to.
- Where you ordered it, with the PO or order number, so nobody's digging through email to chase status.
- The promised ETA, and just as important, the date that ETA was last confirmed.
- What you've told the customer so far, and when. One line is plenty.
- Whether they've already paid or left a deposit, because a paid customer sweating in the heat is your first call, every time.
That last field matters more than it looks. When three parts slip in the same week, it tells you who to call first.
Send on the event, not on a schedule
You don't need a daily blast. You need one message to go out when something actually changes, and one to go out when nothing has for too long.
Three triggers cover almost everything:
- The ETA lands. The part ships or gets a firm date. Tell them the date and what happens next.
- The ETA moves. The supply house pushes it a week. This is the one everybody skips, and it's the one that saves the job. A moved date the customer hears from you is a shrug. The same date they stumble onto themselves feels like a betrayal.
- Nothing has moved in X days. Pick a number, say five. Silence that long reads as abandonment even when you're working the problem hard.
Keep the first message short, and send it the day you order, not the day it's late. Something like: "We ordered your compressor today, the supplier is quoting next Thursday, and we'll call you the minute it ships." Thirty seconds of work that buys you two weeks of patience.
Be honest about a date you don't own
The trap is sounding more certain than you really are. If you promise Thursday and the part shows up the following Monday, you've just taught the customer that your dates mean nothing. Say only what you actually know.
A few rules keep you honest without sounding wishy-washy:
- Name the delay plainly. "The manufacturer has it on backorder" is fine. Customers know parts run short, especially in the stretch of summer when every compressor in Houston is running overtime.
- Give the date you were given, and say so. "The supplier is telling us the 14th" is honest. "It'll be here the 14th" is a promise you can't keep.
- Say what you're doing in the meantime. Checking other suppliers, offering a temporary fix, calling them every morning. Even that last one counts.
- Never go quiet to dodge bad news. A slipped date delivered on time beats a good date delivered late.
Give them an out, too. Some customers will want to cancel, and that's their call. Better they decide with the full picture than feel trapped and leave you a one-star review about it later.
Let the system do the watching
You can run all of this on a whiteboard and a sharp dispatcher, and plenty of shops do. The trouble is the watching. Someone has to notice that today is day five, or that the supply house quietly changed a date in a portal nobody opens. That's exactly the kind of boring, every-single-day task that gets dropped the second the phones light up.
This is where a little automation earns its keep. A simple setup can watch your open-parts list and do the nagging for you:
- Flag any job that's hit your silence threshold, so a person knows to call.
- Draft the customer update in plain English from the fields you're already tracking, ready for someone to glance at and send.
- Log what went out and when, so the next person who answers the phone isn't flying blind.
Be clear about what it won't do. It won't call the supply house and negotiate, it won't know the ETA slipped unless someone or something tells it, and you shouldn't let it fire a message to a customer with no eyes on it. The date is too sensitive and the tone matters too much. Treat it as a reminder and a first draft, with a human hitting send. Done that way, it turns a task everyone forgets into one that mostly runs itself.
Worth doing this week
You don't need software to start. You need a list and a habit. Knock these out in order:
- Make the list. Pull every open job waiting on a part into one place today, even a shared spreadsheet. One row per part.
- Add the five fields above, and backfill the last-contact date from memory. Ugly is fine. Complete is what matters.
- Set your silence number. Decide how many days of no news triggers a call, and write it where the front desk can see it.
- Send the updates that are already overdue. You almost certainly have a few customers who've heard nothing in over a week. Call them first.
- Pick one trigger to automate once the habit sticks. If you want a hand wiring that up, that's the kind of thing we set up for Houston shops at AI Agency Houston, 617-398-0033.
Do that and the backordered compressor stops being a landmine. It's just a date you're managing, out loud, before anyone has to call in hot.