How to Follow Up on an Estimate (Home Services): Templates + an Approval‑First Operator Workflow

If you’re losing jobs after sending estimates, there’s a good chance it’s not your pricing.

It’s the follow-up.

Home services is brutal: you send the quote, then you get busy, then the customer gets busy… and the competitor who followed up faster wins.

This post gives you two things:

1. Copy/paste templates (text + email) you can use today.
2. A simple estimate follow up system built for real home services ops: after-hours, weekends, multiple techs, and owners who want to approve messages before they go out.

We’ll keep it outcome-first: more replies, more booked jobs, fewer “no response after estimate” ghosts.

The “money leak” in plain English

Most small home services teams (pest control, HVAC, plumbing, electrical) don’t lose deals because they didn’t send an estimate.

They lose deals because:

• The estimate went out, but no one confirmed receipt.
• A follow-up was “supposed to happen” but didn’t.
• The follow-up happened, but it was late, awkward, or too pushy.
• The office did follow up… but it wasn’t logged, so someone else followed up again (duplicate texts are a trust killer).

Templates help.

A system wins.

When to follow up after sending an estimate (timing rules that fit home services)

These timings assume you’re quoting a job the customer wants soon, and the main competitor risk is speed + consistency.

1) 15 minutes: receipt + next step

Your first message isn’t a “nudge.” It’s customer service.

• Confirms they received the quote
• Offers a clear next step (call/text to book)
• Keeps the door open for questions

2) 24 hours: simple check-in

Short, no pressure. Your goal is a reply.

3) 72 hours: handle objections + add value

This is where you address the real blockers:

• Timing
• Price
• “Need to talk to spouse/partner”
• “Getting another quote”

4) 7 days: close the loop (“break-up” message)

This isn’t passive-aggressive. It’s operational cleanup.

You’re giving them a polite final touch and asking if you should close the quote.

After-hours and weekends

Home services customers request quotes at night and on weekends.

If you wait until Monday, you’re competing with whoever responded at 8:01 PM.

So you want:

• Immediate receipt message after-hours
• Owner/office approval before anything “salesy” goes out
• A next-day follow-up queued automatically

Copy/paste templates: follow up text after estimate (SMS)

Use these as written, then adjust to match your voice.

Tip: In SMS, keep it to 1–2 short lines. If you need more detail, ask for a quick call.

SMS #1 — “Did you get it?” (15 minutes)

Hi {{first_name}} — it’s {{your_name}} with {{company}}.
Just sent your estimate for {{service}}. Did it come through okay?

SMS #2 — Professional follow-up (24 hours)

Hi {{first_name}} — quick check-in on the estimate I sent yesterday for {{service}}.
Any questions, or would you like to get on the schedule?

SMS #3 — Friendly nudge (24–72 hours)

Hey {{first_name}} — want me to adjust anything on the quote, or are you good to book it?

SMS #4 — “Happy to adjust the estimate” (72 hours)

Hi {{first_name}} — if anything in the estimate doesn’t match what you had in mind, tell me what you’d like changed and I’ll update it.

SMS #5 — Schedule-fill urgency (72 hours)

Use this when it’s true (don’t fake scarcity):

Hi {{first_name}} — we have a couple openings {{day_or_window}}.
Want me to hold one for you for {{service}}?

SMS #6 — “No response after estimate” close-the-loop (7 days)

Hi {{first_name}} — should I keep your estimate open, or go ahead and close it out on my end?
No worries either way.

Pest control estimate follow up (optional add-on line)

If you’re in pest control and want a simple value reminder:

(Also — if you want, I can walk you through what’s included in the treatment + warranty in 2 minutes.)

HVAC estimate follow up text (optional add-on line)

(If you want, I can explain the difference between the options and what I’d choose if it were my home.)

Copy/paste templates: estimate follow-up email

Email works best when the quote is complex or high-ticket.

Email #1 — Receipt + next step

Subject: Your estimate from {{company}}

Body:

Hi {{first_name}},

Thanks again for reaching out. I just sent your estimate for {{service}}.

If you’d like to move forward, reply here or call/text me at {{phone}} and we’ll get you scheduled.

— {{your_name}} {{company}}

Email #2 — 72-hour value + objection handling

Subject: Any questions on your estimate?

Body:

Hi {{first_name}},

Quick check-in on the estimate for {{service}}.

If you’re comparing options, I’m happy to clarify:

• what’s included (and what isn’t)
• warranty/guarantee details
• timeline and scheduling

Want to book it, or should I adjust anything?

— {{your_name}}

Email #3 — Close the loop

Subject: Close out your estimate?

Body:

Hi {{first_name}},

I don’t want to bug you, but I also don’t want your estimate to fall through the cracks.

Should I keep it open, or close it out for now?

— {{your_name}}

Why templates alone don’t work (and what breaks in the real world)

Templates are necessary.

But if you only have templates, you still get these failure modes:

1. No trigger: the follow-up depends on someone remembering.
2. No “system of record”: nobody knows if a message already went out.
3. Wrong tone: one tech is friendly, one is aggressive, and the owner finds out after a bad review.
4. Weekend blind spot: the quote goes out Friday afternoon and gets no touch until Monday.
5. Duplicate messaging: two people follow up and the customer thinks you’re disorganized.

If you want consistent win-rate, you want a workflow that:

• detects when an estimate needs attention,
• drafts the right message,
• gets the owner/office to approve it fast,
• sends and logs it,
• and schedules the next touch.

That’s an ops loop.

The Approval‑First Operator Workflow (playbook)

This is the core idea nNode is built around: an operational AI layer (“operator”) that runs the admin loop, while you stay in control.

Not “set it and forget it.”

More like: “Draft it, show me, I approve it, and the system learns my preferences.”

Step A — Detect new and stale estimates

Define “stale” in simple rules:

• New estimate sent → confirm receipt within 15 minutes
• No reply + no scheduled job after 24 hours → follow up
• Still no reply after 72 hours → follow up with value/objection handling
• After 7 days → close the loop

Also add guardrails:

• High-ticket estimates get faster escalation
• Repeat customers get a shorter, more casual message
• “Do not contact” flags override everything

Step B — Draft a message matched to context

Your draft should incorporate:

• service type (pest control vs HVAC install vs plumbing repair)
• what they asked for
• quote amount range (optional)
• prior messages (don’t repeat yourself)
• preferred tone (short, friendly, direct)

A practical message generator prompt can be simple and consistent.

Here’s a lightweight example you can adapt (pseudo-code):

type EstimateContext = {
  customerFirstName: string
  serviceType: "pest_control" | "hvac" | "plumbing" | "electrical" | "other"
  quoteSummary: string
  lastContactAtISO?: string
  followUpStep: "receipt" | "24h" | "72h" | "7d"
  tone: "friendly" | "direct" | "professional"
}

export function draftFollowUpSMS(ctx: EstimateContext) {
  const opening = ctx.tone === "friendly" ? "Hey" : "Hi"
  const stepLine =
    ctx.followUpStep === "receipt"
      ? "Just sent your estimate"
      : ctx.followUpStep === "24h"
        ? "Quick check-in on the estimate"
        : ctx.followUpStep === "72h"
          ? "Wanted to see if you had any questions on the estimate"
          : "Should I keep your estimate open or close it out on my end?"

  return `${opening} ${ctx.customerFirstName} — ${stepLine} for ${ctx.quoteSummary}.`
}

You don’t need perfection. You need consistency + approval.

Step C — Request approval via SMS (Approve / Edit / Skip)

This is the trust unlock for owner-operators and office managers.

Instead of a hidden system blasting customers, your operator sends you a message like:

Operator → Owner (SMS)

Draft follow-up (24h) to Sarah M. “Hi Sarah — quick check-in on the estimate I sent yesterday for monthly pest service. Any questions, or would you like to get on the schedule?”

Reply: Approve, Edit, or Skip

If the owner replies:

• A → send + log it
• E → owner types a quick rewrite; the system uses that as tone feedback
• S → don’t send; set a reminder or mark the estimate as “manual handling”

Step D — Send + log back to your CRM/inbox

This is where most teams fail.

If the follow-up isn’t logged, it didn’t happen (operationally).

Minimum logging:

• message content
• timestamp
• channel (SMS/email)
• who approved it
• next follow-up scheduled

And if you’re already using a system like Jobber, ServiceTitan, Housecall Pro, or a shared inbox: don’t rip it out. Layer this on top.

Step E — Escalate edge cases (don’t let AI guess)

Some replies should never be handled “automatically.”

Escalate immediately when you detect:

• angry language or refund requests
• cancellation intent
• pricing disputes
• high-ticket estimate questions
• “call me” or scheduling constraints

In practice: route these to the owner/office with the original message thread and a suggested reply.

How to add this on top of your current stack (no platform switch)

You can implement the workflow using what you already have:

• Where the estimate lives: CRM (Jobber/ServiceTitan/Housecall Pro), spreadsheet, or email
• Where approvals happen: SMS (fastest), or email/Slack if you’re a larger office
• Where sending happens: your business phone/SMS provider + email
• Where scheduling happens: calendar/dispatcher

The critical requirement is not the tool.

It’s the loop:

Detect → Draft → Approve → Send → Log → Next timer

That’s why we describe nNode as an operator (an ops layer) rather than another “automation.”

Zapier automates. nNode runs operations.

KPI scoreboard: the few numbers that actually matter

If you want more booked jobs, track these weekly:

1. Follow-up SLA
   • % of estimates that got a receipt message within 15 minutes
2. Time-to-first-follow-up
   • median minutes/hours
3. Contact rate
   • % of estimates that got any customer reply
4. Booked rate
   • % of estimates that became scheduled jobs
5. Aging estimates
   • count of estimates older than 7 days with no decision

If these improve, revenue usually follows.

Week 1 implementation checklist (one page)

If you want a repeatable estimate follow up system in a week, do this:

• Pick your channels: SMS only, or SMS + email
• Pick your “stale” rules (15 min / 24h / 72h / 7d)
• Standardize your sender identity (one office number or a consistent template)
• Create 6 templates (use the ones above)
• Decide who approves messages (owner, office manager, dispatcher)
• Add a simple log (CRM notes, Google Sheet, or inbox labels)
• Add an escalation rule for angry/high-value messages
• Review and refine tone weekly (“shorter,” “friendlier,” “more direct”)

FAQ: quick answers you’ll get asked

“How do I professionally follow up on an estimate without sounding desperate?”

Make it about service and clarity, not pressure:

• confirm receipt
• ask if anything needs adjusting
• offer to schedule

Short messages feel confident.

“Should I follow up by text or email?”

If the customer texted you first, text.

If the estimate is complex/high-ticket, use email (and consider a short text that says “I emailed details — happy to explain options”).

“How many follow-ups is too many?”

For most home services quotes, 3–4 touches over 7 days is normal.

The real risk is not “too many.” It’s no follow-up.

If you want this loop to run itself (with approvals)

If you read this and thought, “We can do templates—but we won’t run the system consistently,” you’re not alone.

That’s the gap nNode is designed to fill: an approval-first operator that watches for stale estimates, drafts the right follow-up, asks you to approve it (fast), sends it, logs it, and learns your tone over time.

If you want to see what a 7‑day pilot looks like for your home services business, take a look at nnode.ai.