HVAC Estimate Follow-Up: A Workflow for Unsold Replacement Quotes

An HVAC estimate follow-up workflow should give every sent replacement quote an owner, a dated next action, and a documented outcome. It should also stop when the customer approves, declines, chooses another provider, asks for later contact, or opts out.

That sounds basic, but many estimate queues cannot show it.

A comfort advisor sends a replacement estimate after a long appointment. The record moves to "awaiting response." A reminder may fire later. The customer replies with a financing question, asks to include a spouse, or says the timing changed. That answer lands in a text thread or inbox. The estimate still looks open, and nobody can tell whether another touch would help or annoy the customer.

A longer sales script will not solve this. The company needs one operating owner that can watch the queue, use approved facts, handle routine coordination, and keep each estimate moving until the record tells the truth.

Start with the tracker below. You can use it before buying or connecting anything new.

Copy this HVAC estimate follow-up tracker

Put these seven fields in a shared note or spreadsheet:

Pre-fill the queue with lines like these:

EST-1042 | Awaiting response | Email; SMS allowed in source record | Customer said another decision-maker must review | Ask for a joint callback window by Tuesday 2 p.m. | Comfort advisor | Callback booked or dated customer response saved
EST-1043 | Approved | Email; SMS allowed | Customer approved through portal | Stop follow-up; create booking handoff | Sales coordinator | Approval and booking record linked
EST-1044 | Closed | Email only; SMS opted out | Customer selected another provider | Stop estimate outreach; save loss reason | Sales manager | Customer email and closed status linked
EST-1045 | Decision needed | Email; SMS allowed | Customer asked whether the quoted equipment qualifies for a rebate | Route the exact question with estimate link to estimator | Estimator | Approved answer sent and logged
EST-1046 | Awaiting response | Email only | No response after the company-approved cadence | Close as unreachable or set a later review date under policy | Sales manager | Terminal status and reason code saved

These are fictional operating examples, not client results. Replace the IDs, dates, and roles with your own records.

The tracker is intentionally small. You need to see the current state, the next action, who owns it, and what will prove completion. Add fields such as estimate value, salesperson, expiration date, message template, delivery result, or loss detail only when they change a decision.

Why replacement estimates disappear after they are sent

Most estimate systems are good at preserving the quote. The breakdown happens between records.

The estimate has scope and price. The CRM has customer history. Text and email hold the conversation. The calendar has a promised callback. A financing portal may have another status. The comfort advisor remembers a concern that never made it into any of them.

An "awaiting response" label cannot tell you:

whether the customer received the estimate;
whether the last message asked a question;
whether a second decision-maker needs to join;
whether the customer wants to wait until a certain month;
whether a technical or pricing answer is pending;
whether the customer selected another company;
whether the allowed contact channel changed;
whether someone promised a call today.

Jobber's documentation for its quote list and key metrics shows how field-service software can filter quotes by status, date, and salesperson. It also documents states such as Awaiting Response, Changes Requested, Approved, Converted, and Archived. Housecall Pro describes an Estimates Board and Pipeline for centralizing open estimates and automating tasks.

Those tools can supply the queue. They cannot repair unclear ownership by themselves. Someone still has to interpret replies, set the next action, resolve routine coordination, and close the loop.

ServiceTitan makes the ownership question explicit in its article on following up on estimates: decide who will do the work and review the customer history before making contact. That is the operational decision to make before choosing message timing.

Define a finished estimate before you automate follow-up

A sent estimate should not stay open forever. Give the workflow a small set of terminal outcomes.

Approved and handed to booking or project coordination.
Declined by the customer.
Another provider selected.
Postponed with a customer-requested review date.
Closed as unreachable after the company's approved cadence.
Invalid or superseded estimate archived with a reason.
Contact stopped because of an opt-out or channel restriction.

"Followed up" is not an outcome. It is an activity.

The record is finished when the status, reason, evidence, and downstream action agree. If the customer approves, the estimate should not remain in a reminder sequence while somebody manually creates the job. If the customer declines, the system should not send another "just checking in" message three days later.

Jobber's quote basics describes Awaiting Response and Archived quote states and a quote history that records related activity. Use the equivalent fields in your system. The names matter less than the rule: every open record needs a next action, and every closed record needs evidence.

The job an AI employee can own

An AI employee can own routine estimate follow-up from the sent event to a documented outcome.

The trigger is a real status change: the approved estimate was delivered and moved from draft to sent or awaiting response. The employee then checks the customer record, allowed channels, last interaction, responsible salesperson, expiration data when present, and any open task.

From there, it can:

create the follow-up record and next-action date;
send an approved message populated from verified estimate fields;
ask routine scheduling and decision-process questions;
read replies and classify the customer's stated intent;
update permitted CRM fields;
book an authorized callback or appointment window;
stop messages when a terminal outcome appears;
keep an audit trail of the channel, template, delivery result, response, and action;
send one decision-ready brief when a true exception appears;
carry out the decision and finish the affected work afterward.

The employee should communicate directly on routine paths. It should not dump every reply into the office inbox with a note that says "please review." That would add another queue for the team to manage.

It also should not invent an answer. A replacement estimate can contain equipment, scope, warranties, rebates, financing, and technical details. Those facts must come from approved source records or an authorized person.

NIST's Generative AI Profile defines confabulation as confidently presented false or erroneous content. In this workflow, the practical control is simple: the AI employee may retrieve an approved fact, but it may not manufacture a commercial or technical one from model memory.

Build the workflow in seven steps

1. Use the sent event as the trigger

Do not start the clock when someone remembers to open a report.

The workflow should begin only after the system confirms that the customer-facing estimate was sent. A draft, internal option, or superseded version should never enter the follow-up queue.

Required trigger data:

estimate ID and link;
customer record ID;
sent timestamp;
responsible salesperson or team;
current estimate status;
approved scope label;
channel eligibility and suppression fields;
expiration date if the company stores one.

If the estimate changes later, the workflow should know which version is current. Do not let an old reminder point to a superseded quote.

2. Set the owner and next action immediately

Every sent estimate gets a responsible person and a next-action date, even when automation will perform the routine touch.

The responsible person is accountable for the commercial relationship. The AI employee owns the operating work: watching the clock, sending approved communications, collecting the response, updating the record, and routing only decisions that exceed its authority.

If the queue cannot show both owner and next action, it is still a storage list rather than a working system.

3. Check the record before every contact

Before sending anything, re-read the live status and recent activity.

The customer may have approved through a portal, replied to another employee, booked by phone, asked to stop, or received a revised estimate. A sequence that ignores those events will create duplicate or contradictory contact.

The pre-send check should ask:

Is this the current estimate?
Is it still awaiting a customer outcome?
Did the customer or team add a newer message?
Is this channel still allowed under the company's current record and policy?
Does a promised callback or review date already exist?
Would this message conflict with another active process?

Housecall Pro documents estimate sent, first follow-up, and second follow-up communication states. Treat those as events, not a universal recommendation to send exactly two messages. Your cadence should follow customer preference, estimate context, company policy, and applicable requirements.

4. Make the message earn the reply

A weak follow-up says, "Just checking in on the estimate."

A useful follow-up identifies the estimate, reflects the last known state, and asks one question that can move the record.

Example after estimate delivery:

"Hi Jordan, this is Northside Heating following up on estimate EST-1042 sent Thursday for the replacement options we discussed. Did the estimate open correctly, and is there a specific question the comfort advisor should address?"

Example when another decision-maker is involved:

"You mentioned that you and your spouse want to review the estimate together. I can arrange a callback with the comfort advisor. Which is better, Tuesday between 2 and 4 or Wednesday between 9 and 11?"

Example after a requested pause:

"You asked us to reconnect in October about estimate EST-1042. Is the project still something you want to discuss, or should we close the estimate for now?"

Use only facts in the record. Do not claim a price will expire, equipment is scarce, a system is likely to fail, or a rebate applies unless an approved source and company policy support that statement.

5. Turn each reply into a next state

A reply should change the record. Otherwise, the conversation becomes another inbox archive.

Use a short response map:

Ready to proceed: stop sales follow-up and start the approved booking or project handoff.
Needs a callback: offer authorized times and book the call.
Another decision-maker involved: coordinate a shared callback or record the agreed review date.
Timing changed: save the customer's stated timing and pause until that date.
Pricing, scope, equipment, warranty, rebate, or financing question: preserve the exact question and route it to the authorized person.
Selected another provider: stop outreach, record the stated reason when offered, and close the estimate.
Declined: close with the customer's stated reason when available.
Opt-out: suppress that channel immediately and stop any conflicting automation.
No response: move to the next action in the company-approved cadence or close with the proper reason.

The AI employee should never convert silence into a guessed objection. "No response" is a valid state.

6. Escalate a decision, not raw work

A useful exception brief is short enough to decide.

For example:

Decision needed: Customer on EST-1045 asked whether the quoted equipment qualifies for the listed utility rebate. The estimate and current customer message are linked. No approved rebate field is present. Confirm the approved answer or assign the estimator to call by 3 p.m.

The employee pauses only that answer. It can still preserve the message, keep the customer informed that the question is being checked, update the task, and watch the deadline.

After the estimator decides, the employee sends or records the authorized response, updates the estimate, sets the next action, and closes the exception. Escalation should not end ownership.

7. Stop on proof, not assumptions

Each terminal outcome needs visible evidence.

Examples:

portal approval and booked appointment link;
customer decline message and closed status;
customer request for an October review and dated future task;
opt-out event and suppressed channel;
approved closure reason after the cadence ends;
archived superseded estimate linked to its replacement.

This prevents "probably lost" estimates from staying open and prevents closed estimates from receiving another message.

Put contact rules inside the workflow

Channel policy should not live in a separate document that the sequence never checks.

Housecall Pro's guide to SMS consent and opt-outs describes storing consent status and blocking later texts after replies such as STOP, Cancel, or Unsubscribe until the customer opts back in. Your system may behave differently, so test the exact suppression path before launch.

For commercial email, the Federal Trade Commission's CAN-SPAM compliance guide covers accurate headers and subject lines, sender identification, postal address, a clear opt-out, and honoring opt-outs within 10 business days. The FTC also says a company cannot transfer its legal responsibility to the vendor sending on its behalf.

Federal communication rules can also depend on the technology, purpose, consent, and destination. 47 CFR § 64.1200 contains restrictions for covered automated or artificial/prerecorded telemarketing calls and treats certain text messages as calls.

Do not turn those links into a homemade legal opinion. Have qualified counsel define the policy that applies to your channels, message types, jurisdictions, and tools. Then make the AI employee enforce the approved fields and stop rules every time.

Measure whether the workflow is under control

Do not begin with an invented industry close-rate target. Establish a clean operating baseline first.

Track:

sent estimates with a responsible owner;
sent estimates with a current next action and due time;
overdue next actions;
replies waiting on a promised response;
open technical or commercial exceptions;
estimates closed with a terminal reason and evidence;
messages blocked by suppression or missing channel permission;
time from customer reply to completed next action;
approved, declined, postponed, competitor-selected, and unreachable outcomes.

Separate process quality from sales results. A clean follow-up operation can tell you what happened. It cannot make every customer buy, and it should not hide a loss by leaving the estimate open.

For the first week, inspect five records each day. Compare the estimate status, message thread, next action, and terminal evidence. Any mismatch becomes a workflow correction.

Common mistakes

Automating before cleaning the queue

Old, duplicated, approved, expired, or superseded estimates should not enter a new sequence blindly. Define the eligible state and review the first batch.

Using one generic reminder for every situation

A customer who needs another decision-maker is not in the same state as someone who asked a financing question or chose another company. The next message should follow the recorded signal.

Letting the model explain technical or commercial details

The employee should retrieve approved content or route the question. It should not improvise price, scope, equipment performance, warranties, rebates, or financing terms.

Counting attempts instead of outcomes

Five reminders do not prove five useful actions. Measure whether the record reached a truthful next state.

Treating the opt-out as an inbox note

Suppression must change the channel eligibility used by every later step. Otherwise, another automation can keep sending.

Ending ownership at the escalation

A raw forwarded message is unfinished work. The employee should package the decision, watch the deadline, receive the answer, communicate it, update the record, and continue.

Map the first estimate lane

Start with one estimate type, one source system, one responsible team, and one approved message path. Do not connect every branch on day one.

A good first test proves that the workflow can detect a sent estimate, assign the next action, check channel status, send an approved message, process a routine reply, create a decision brief when needed, stop on a terminal outcome, and preserve an audit trail.

ComfortGrowth AI builds AI employee workflows for HVAC companies around the systems and policies the business already uses. You can also see how ownership starts earlier in the pipeline in our HVAC lead response workflow, or review the distinction between an operator and a basic tool in what an AI employee is.

If replacement estimates still sit in "awaiting response" while the real conversation lives elsewhere, request a free business audit. We will map one estimate lane from sent quote to documented outcome, including the records, authority, message paths, exception brief, and completion proof an AI employee would need to own it.

HVAC Estimate Follow-Up: A Workflow for Unsold Replacement Quotes