Agents in the Trades
Sales

The quiet estimate that gets worked for 30 days — and stops itself when it books

It is 4:50 p.m. in a residential HVAC office and the comfort advisor is staring at a board of open estimates — eleven sent this week, three answered, the rest gone quiet while the phones keep ringing.

Source: Hatch, "Journey Builder" — https://www.usehatchapp.com/product/journey-builder — the vendor describes real-time enrollment from live CRM status, multi-day sequences across voice, text, and email, personalization from the CRM record, and removal rules that pull a contact out the moment a booking or status change lands in the CRM. Adapted here for a small shop; not a report of one shop’s results, and no vendor performance figures are used.

The problem

An unsold estimate rarely dies in one conversation. It dies in the week after — the homeowner is comparing two other quotes, waiting on a spouse, or just busy — while the advisor who wrote it is already on the next sales call. Follow-up becomes whoever remembers, whenever they remember.

The manual version fails in both directions. Work it too little and good quotes go cold for no reason. Work it by spreadsheet and someone eventually gets a cheerful nudge the day after they already booked — or after they told the office they went with another shop. Both cost trust.

Get one workflow like this, every day.

The free Agents in the Trades newsletter — each workflow broken down: what it does, what it costs, and where it breaks.

How the agent workflow works

  1. Enrollment happens when the estimate is sent. The moment an estimate lands in the CRM with an open status, the customer enters the follow-up journey automatically — no weekly list upload, no one exporting a spreadsheet on Friday.
  2. The cadence runs across channels, on a schedule the shop sets. A short text on day one, an email a few days later, a voice touch after that — sequenced over roughly 30 days, with spacing and stop date owned by the shop, not improvised per advisor.
  3. Every touch is personalized from the actual quote. The messages pull the real system, scope, and price from the estimate record, so the follow-up talks about that homeowner’s job — not a generic “just checking in on your project.”
  4. Replies stay in one conversation. When the homeowner answers on any channel, the agent picks the thread up there, answers routine questions from the job record, and hands anything pricing- or judgment-shaped to the advisor with the full history attached.
  5. It removes people the instant the status changes. Booked, sold elsewhere, or marked closed in the CRM — the removal rule fires and the sequence stops. The same live sync that enrolled them is what protects them from one touch too many.

What you need to set it up

Where it breaks

It is only as current as the CRM. A booking taken by phone and never entered is a booking the agent cannot see — the customer gets followed up anyway, and that one message undoes the polish of the previous six. Status discipline is the workflow.

Persistent is not the same as welcome. Thirty days of touches across three channels can tip from diligent to irritating, especially on a small quote. Caps, quiet hours, and an instant opt-out are not optional settings; they are the reputation line.

Personalization exposes bad data. Pull the wrong system size or an old price into an otherwise warm message and the homeowner learns the follow-up is automated — and that the record is sloppy.

It cannot close. Financing worries, a competitor’s lower number, a spouse who was never in the room — those are advisor conversations. The agent keeps the quote alive; a person still has to win it.

The bottom line

Run it on one estimate type first, with statuses cleaned weekly and the removal rules proven on test records. The win is unglamorous: every open quote gets the same patient 30 days of follow-up, and not one customer gets chased after they have already said yes — or no.

Related use cases

← All use cases

One working agent workflow, every day.

Real AI agent use cases from solar, construction, and field operations — what they do, what they cost, and where they break. No hype, no theory.