Answer 'Where Are We on My Job?' Before They Ask

The text lands around four in the afternoon. "Hey, any word on when you're coming by?" It's polite, it's fair, and it pulls you clean off the thing you were in the middle of. You're not even behind. You just never told them where things stood.

Here's the quiet truth about that message. The customer isn't upset about the timeline. They're upset about the silence. They handed you something that matters to them, a leaking roof or a custom order or a furnace that quit in a cold snap, and then the line went dark. So they fill the dark with a phone call, and now you're both burning time on a conversation one sentence could have headed off.

Multiply that by every open job on your board. The "just checking in" calls, the voicemails you owe people back, the texts that buzz while both hands are busy. Almost none of them are about the work itself. They're about not knowing. Answer the question before it gets asked, and most of those interruptions never happen.

Why the calls come when they come

Customers don't reach out at random. They reach out at a few predictable moments, and every one is a gap where they expected to hear something and heard nothing instead.

Think about when the phone actually rings. The morning of a scheduled visit, while they're deciding whether to burn a day off waiting on you. A day or two after they said yes, when they've heard nothing and start wondering if the order fell through the cracks. The long middle of a bigger job, when the house is torn up and progress is invisible from where they stand. And the minute after you finish, when they want to know what happens next and what they owe.

Learn those four moments and you basically have your update schedule. You're not sending more messages than before. You're just sending each one a beat before the worry shows up.

The milestones worth a message

Nobody wants a text every time you tighten a bolt. There are only a handful of moments that actually lower a customer's blood pressure, and they line up neatly with the gaps above.

Booked. "Got you down for Thursday the 14th, morning slot. We'll confirm the night before." Kills the "did that go through?" call.
Confirmed. Sent the evening before or first thing that morning: "We're on for today, should be there between 9 and 10." This is the one that saves someone a wasted morning by the window.
Started, or a mid-job checkpoint. "Framing's done, drywall goes up tomorrow." Progress they can't see from the kitchen.
A snag or a change. "The part's back-ordered to Monday, so we'll wrap Tuesday instead of Friday." Bad news early beats good news late, every single time.
Done, and what's next. "All finished. Invoice is on its way, and your warranty covers parts for a year." Closes the loop so nobody's left guessing.

Notice what's missing from that list. No "we're running twelve minutes late," no play-by-play. Just the points where a customer would otherwise start to wonder.

The one-line update template

Every good update answers three things, and it fits in a single text: where the job stands right now, what happens next, and whether the customer needs to do anything at all.

It looks like this: [where it stands] + [what's next, with a rough when] + [what you need from them, if anything]. A few real ones:

"Roof's done, gutters go on Friday morning. Nothing needed from you."
"Your table's in final sanding. Staining next week, ready for pickup around the 20th."
"Hit a wiring surprise behind the wall. Adds about an hour and $80 in parts, alright to keep going?"

That last one carries the whole reason to bother with any of this. When a surprise arrives as a calm one-liner while there's still time to decide, it reads as a courtesy. When it shows up for the first time on the final invoice, it reads as an argument.

Sending it without it becoming another chore

One catch is obvious. If staying in touch means stopping four times a day to thumb out texts, it won't survive your first busy week. It has to mostly run itself.

Most of these updates hang off things you already track. A booking on your calendar can trigger the confirmation the night before. Marking a job "complete" can fire the wrap-up note and the invoice behind it. You write the wording once, in your own voice, and the same three or four messages go out on every job without you retyping a thing.

Be honest about the line, though. A machine can send "we're on for tomorrow" straight off your schedule, because that's a plain fact. It can't tell a customer the tricky repair is "going well," because that's a judgment only you can make from the ladder. So hand off the predictable beats, the booked and confirmed and done, and keep the mid-job read on the work for yourself. Machines run the relay. You keep the judgement.

Prefer not to wire anything up yet? Canned messages get you most of the way there. Save three or four templates in your phone and paste them in as you go. Less tidy, still cuts the calls.

What this quietly does to your phone

This payoff is quiet, which is exactly the point. When people know what's happening, they stop calling to find out. In our experience the "any update?" calls are a real chunk of an owner's inbound, and a steady drip of one-liners takes most of them off the table.

Figure it saves you a handful of interruptions a day and a few callbacks you never have to make. That's not a headline number. It's your afternoons back, plus a customer who tells the neighbor you're easy to work with, because they never once had to chase you for an answer.

At TellRobots we build these small relay habits for busy shops, and the update loop tends to be one of the first ones owners actually feel.

Worth doing this week

List your last ten jobs and mark every spot where a customer called or texted just to ask where things stood. Those are your gaps.
Write your four messages: booked, confirmed, started or checkpoint, and done. Plain words, your voice, one line each.
Save them somewhere you can reach in seconds, whether that's phone text shortcuts or your scheduling tool.
Pick the single highest-value one, the day-before confirmation, and send it on every job for one week.
At the end of the week, count the "where are we?" calls. If they're down, set the rest to send on their own.