NormalNormal

Estimate follow-up that doesn't sound like a robot

Estimate follow-up that doesn't sound like a robot

Short answer: follow up like your best office person does — promptly, personally, and with the customer's actual job in front of them — and let the software do the remembering and the drafting, not the talking.

Every contractor knows the number that never shows up on a dashboard: the estimates that went out and just… sat there. Not a no. A maybe. The homeowner meant to call back. Then two weeks pass, and calling feels awkward for both sides, and a job worth thousands evaporates without anyone saying no to anything.

You already know calling back works. What you don't have is spare hours for it. That's the actual problem — and it's a software problem the way a wheelbarrow is a software problem: the tool should carry the weight, not change the trade.

Why most automated follow-up backfires

Owners try to solve this and get burned by two common products:

The blast. "Your estimate is expiring!" texts that go out on a timer, identical for everyone. Customers can smell a mail merge. The message that was supposed to look attentive instead tells them they're a line in somebody's CRM.

The robot voice. An AI calls or texts in perfect script and asks questions it doesn't know the answers to. "Just checking on your estimate!" — which estimate? For what? The customer has to do the work of remembering, and now your company feels like a call center.

Both fail the same way: they follow up without knowing anything.

What a follow-up should know before it speaks

A follow-up written by software that has actually read your records looks completely different:

  • It knows which estimate — the condenser replacement quoted on the 14th, not "your estimate."
  • It knows the customer's history — they've been on a maintenance plan since 2021, or this is their first call.
  • It knows the state of the job — quoted, rescheduled, partly done, waiting on the customer's decision.
  • It knows what your company sounds like — because the draft goes to your office to approve, edit, and send.

That last one is the whole trick. The software's job is to hand your person a ready message with the customer's actual situation laid out. Your person reads it, maybe changes a word, and hits send. Ninety percent of the labor removed, zero percent of the judgment outsourced.

A cadence that doesn't burn trust

  • Day 2: a short, human-sounding note referencing the specific work. Drafted, approved, sent by your office.
  • Day 7–10: one more nudge with something useful — an opening in next week's schedule, or the note that the quoted equipment price holds through month-end.
  • After that: the estimate goes on a list your office sees — not an endless drip. Three touches max, then a human decision about whether to call.

Contrast with what customers complain about: eleven automated texts and a survey. Restraint reads as competence.

The questions to ask before you buy any follow-up tool

  1. Does it read our estimate and job history, or does it send the same message to everyone?
  2. Who approves what gets sent?
  3. Can it work through the channels we already use — our text number, our email — instead of teaching customers a new app?
  4. What happens to the customer list if we stop using it?

A realistic first step

Take the estimates that are sitting open right now — every company has them. Have the assistant draft the follow-ups from your records, have your office approve and send, and see what closes this month. Your customers won't know software was involved. Your office will notice Wednesday afternoon got quieter.

That's how we set this up: learning your company first, drafting from your records, your people pressing send. Talk with us — or start with the missed-call problem, which is where most companies begin.

More on how this fits together: AI for home services companies.

Talk with us

Let's see if your business is a good fit.

Book a 30-minute conversation with us. We will ask how your business runs and where your records live, then tell you plainly whether this makes sense and what a first step would look like. If it is not a fit, we will say so.