Quote follow-up: the playbook for estimates that never closed

Segment before you write a word

A single sequence sent to every unsold estimate underperforms because the rows aren't the same kind of lead. Split the list along three axes and you end up with a handful of groups that each deserve different words.

Value: estimates above your average job size justify a phone call and a personally written email. Everything below it gets the standard sequence. The split point is your own average ticket, not a rule of thumb.

Reason for silence: an estimate marked as revision-requested stalled mid-conversation. One that was sent and never opened may never have arrived at all — that's a deliverability problem wearing a sales problem's clothes. One that was viewed repeatedly and then went quiet is a price or timing decision. Three different messages.

Age: a six-week-old estimate can be reopened as if the conversation never stopped. A two-year-old estimate cannot, and pretending otherwise reads as a mail merge. Older rows need an explicit acknowledgment that time has passed.

A starting cadence

For a months-old estimate, three email touches across roughly two weeks is a restrained default: enough to distinguish a missed message from a decision, and short enough that nobody feels pursued. Add a phone call for the high-value segment where the business has a lawful basis to call. Treat all of this as a testable starting point rather than an optimum — your list, trade, and average ticket will move it.

Use SMS only where consent, carrier registration, identification, timing, and opt-out handling are all satisfied. Channel eligibility is a decision to make before the sequence is built, not a rescue attempt after email fails to get a reply.

What to write (steal these)

The rule underneath all three: a reactivation email should read like it came from the person who priced the job, because it should have. A message formatted like a campaign invites the reader to treat it like one. That's a hypothesis about tone, not a delivery guarantee — inbox placement is a separate problem covered in the deliverability guide.

Touch 1 — reopen: "Hi Dana — back in March we sent over an estimate for $8,400 on the AC replacement. Did you ever get that project sorted? If the timing just wasn't right, happy to take another look."

Touch 2 — make saying yes cheap: "Following up once more — a few slots opened up over the next couple of weeks. Want me to hold one while you decide?"

Touch 3 — remove the obstacle, then stop: "Last note from me on this one. If the price was the sticking point, we can take another pass at the scope, or I can send over what financing would look like for a job this size. Either way, I'll leave it here unless I hear from you."

Notice what none of them do: no discount announced before anyone asked for one, no invented urgency, no monthly payment figure quoted before it's been calculated from your actual lender terms.

The reply is the whole game

Sends don't book jobs; the conversation after the reply does. When "we held off because of price" comes back at 8pm, the winning response arrives soon after with the original quote in hand and one concrete option — a trimmed scope, a real monthly number, a specific slot on the calendar. Route them to a contact form instead and the thread dies.

This is also the part that's hardest to sustain manually once the list is large, and it's what SignalBack is being built to carry: drafted replies with the original estimate attached, and pricing changes or complaints held for the owner's approval rather than answered automatically. Sending infrastructure is not live yet — the free CSV audit is what exists today.

Keep it legal

• Email: include accurate sender identification, a physical postal address, and a working opt-out, per the FTC's CAN-SPAM guidance
• Calls: telephone solicitations to residential subscribers are restricted to 8am–9pm in the called party's local time under 47 CFR 64.1200(c)(1), and do-not-call obligations apply independently of how the number was obtained
• SMS: requires A2P 10DLC carrier registration plus documented consent — the A2P guide covers registration, the consent checklist covers permission
• Honor every opt-out immediately, and across all channels rather than only the one it arrived on
• Suppress bounced and invalid contacts before the next send; repeated hard bounces damage the reputation the rest of the campaign depends on