revsetHVAC estimate follow-up automation tracks an approved, sent estimate and schedules useful next steps while that estimate remains open. It should pause on a customer reply, stop on acceptance, decline or opt-out, and recheck the latest quote before every send. Start with one estimate type and clear owner responsibility, then measure decisions and completed work rather than message volume.
Which estimates should enter the workflow?
Separate an urgent repair quote from a planned system replacement, a maintenance agreement and a commercial proposal. These customers have different decision timelines and questions. One sequence that treats every quote as an overdue purchase will feel inappropriate and produce misleading results.
Begin with a narrow group such as approved residential replacement estimates that have actually been sent. Record estimate identifier, current version, amount, scope, expiration if applicable, recipient, approved contact channel and responsible estimator. A draft, an unsent quote or a request for pricing should not silently enter the same sequence.
Use the quote as the unit of work. One household might have a repair quote and a replacement alternative. Decide whether those are options within one decision or separate opportunities. Without that rule, the system may send two competing reminders or close the wrong record when a customer responds.
Fix these gaps before automating
| Check | Why it matters |
|---|---|
| Clear scope and options | The customer needs to understand what the estimate includes before a reminder can help. |
| Known delivery state | A bounced estimate needs a delivery repair, not another reminder to read it. |
| One current version | A revision must not leave an old price or acceptance link in circulation. |
| Named estimator | Technical, financing and scope questions need an accountable person. |
| Visible customer responses | Messages from supported channels must reach the same decision record. |
| Defined decision states | Accepted, declined, revised, expired and on hold need distinct actions. |
Ask the estimator what customers most often need clarified: equipment options, installation scope, scheduling, included work or financing application steps. Prepare approved answers and document which questions require the estimator. Do not allow the automation to invent efficiency savings, warranties, rebates, credit approval or installation availability.
An example sequence for a replacement estimate
The following cadence is a starting design for a fictional planned replacement, not an industry benchmark. Prefer a customer’s agreed follow-up date over a generic schedule. Use an eligible communication channel and the customer’s local time. A person asking to discuss the estimate next week should not receive an automated reminder tomorrow.
| Timing | Purpose | Required condition |
|---|---|---|
| When the approved estimate is sent | Provide the correct version, scope link and contact person. | Estimate is approved and delivery is attempted through the chosen channel. |
| Two business days later | Check access and invite one useful question. | Still open; no reply, delivery problem or owner pause. |
| Five business days later | Offer a conversation about the decision. | Prior checks still pass; no agreed later follow-up date. |
| At the agreed decision date | Ask whether to proceed, revisit later or close. | Date is appropriate and current estimate is still valid. |
| After the final permitted follow-up | Create a review task or move to a defined dormant state. | No silent transition to “lost sale” solely because a message went unanswered. |
Do not set an automatic discount simply because the customer has not replied. A lower price is a business decision with margin and scope implications. Equally, an arbitrary deadline should not create false urgency. Use the quote’s genuine validity period and the estimator’s approved wording.
Messages that give the customer a useful next step
Confirm the estimate is accessible
“Hi [Name], this is [Estimator] at [Business]. Were you able to open replacement estimate [reference]? If there is a part of the scope you would like explained, reply here and I can help.”
Offer a decision conversation
“Would a short call help you compare the options in estimate [reference]? Tell me a convenient time, or use [verified consultation link] to choose an available call.”
Respond to a timing concern
“Thanks for letting us know you are planning for later. What month would you like us to revisit this? We will confirm whether the current scope and pricing still apply before you make a decision.”
Close the loop politely
“Would you like to continue with estimate [reference], revisit it later, or close the request for now? Any of those is fine; it helps us keep the next step accurate.”
These are editorial examples. Identify the sender and apply the required opt-out language and permission controls for your channel. Twilio’s policy distinguishes conversational, informational and promotional messaging; follow-up is not exempt merely because it is sent by CRM software. Review the messaging policy ↗
The stop rules matter more than the cadence
| Event | Required workflow behavior |
|---|---|
| Any customer reply | Pause the generic sequence; attach the message and route to the estimator. |
| Customer accepts | Stop sales reminders; start only the separately approved next-stage process. |
| Customer declines | Stop the sequence and record the decision without pressuring the customer. |
| Customer opts out | Suppress the relevant messaging and cancel queued sends that would violate the preference. |
| Estimator revises the quote | Cancel old-version messages; require the current approved estimate and send date. |
| Estimate expires | Do not invite acceptance of an invalid quote; ask the owner to review it. |
| Delivery fails | Create an exception; do not count the estimate as read. |
| Owner pauses or agrees a later date | Respect that state until an authorized person resumes the appropriate follow-up. |
Check those conditions immediately before a send, not only when scheduling it. A reply can arrive one minute before tomorrow’s reminder. Store a unique identifier for each quote-version and sequence step so a retried job does not produce a duplicate message. If the current state cannot be fetched, pause and surface the problem instead of sending from stale data.
A reply should change what happens next
“Does this include the electrical work?”
A fictional customer receives replacement estimate Q-104, version 2, on Monday. On Wednesday morning they reply, “Does this include the electrical work?” A generic reminder is due later that day.
The reply pauses the scheduled reminder and creates an estimator task linked to Q-104 version 2. The system preserves the exact question instead of treating it as acceptance or rejection. The estimator checks the actual scope, responds, and decides whether a revision is required.
If version 3 is issued, queued version-2 messages remain cancelled. Any new follow-up starts only from the newly approved state and the owner’s chosen timing. If the customer accepts, the implementation records the acceptance and follows the agreed deposit or scheduling policy. It does not mark an invoice paid because an estimate was accepted.
This distinction matters operationally: estimate accepted, deposit requested, deposit received and installation confirmed are separate events. The HVAC journey demonstration illustrates those handoffs with fictional data.
Use native tools first, then close the gaps
Inspect the capabilities already included in your quoting software. Jobber documents scheduled quote follow-ups for quotes awaiting a response, with channel behavior tied to how the original quote was sent. Availability depends on the account plan. Review the current controls in your own account. Jobber automation documentation ↗
Do not infer that a native reminder catches every reply from every connected channel. Test a customer response by email, SMS and phone where those channels are in scope. Check whether the estimator must update a status manually and whether the next send respects that update. The goal is dependable behavior, regardless of whether it comes from a built-in tool or an integration.
If you add a custom workflow, decide which system owns the quote status and which owns sending. Disable overlapping reminder sequences. A CRM connector should preserve quote IDs, versions, timestamps, amounts and currencies; it should not create another “source of truth” that drifts from the quoting system. Ask how delayed or repeated events are reconciled.
What should implementation and operation cost include?
Request separate line items for process review, data cleanup, workflow configuration, integrations, acceptance tests, training and ongoing support. The number of quote types, channels and systems is usually more informative than the number of reminder messages. A simple native sequence has different delivery work from a cross-platform system with revisions and payment handoffs.
For ongoing operation, include platform and messaging charges, monitoring, exception handling and estimator time. Confirm who fixes a broken connector, who updates templates when offers change and whether that work is included. RevSet scopes implementation and support after reviewing your tools and process; the example below is not a quoted price.
A transparent break-even calculation
Assume an incremental monthly cost of $800 and a contribution of $400 per genuinely additional completed job after variable delivery costs. The arithmetic break-even is two additional jobs. If contribution is only $200, it becomes four. Setup recovery, capacity constraints and later cancellations can change the decision.
Do not apply a guessed conversion improvement to the entire value of your open pipeline. Some quotes will close without automation, and some cannot be delivered at a profitable margin. Measure the incremental change with the strongest comparison your records support.
Run a limited pilot before expanding
- Choose one cohort. Use one estimate type and defined sent-date window. Exclude quotes already accepted, expired, in dispute or paused.
- Clean the records. Match duplicates, link revisions and identify the responsible estimator. Keep unknown decisions visibly unknown.
- Approve the sequence. Review message purpose, timing, channel permission, stop conditions and customer commitments.
- Test the interruption paths. Simulate a reply just before sending, a revised quote, an opt-out, a failed delivery and a duplicated event.
- Inspect actual outcomes. Check the message log and destination record, not only the workflow’s success badge.
- Review before widening scope. Fix unresolved questions and operator workload, then consider another quote type.
Define rollback as stopping future automated sends while retaining the records and a human task list. Make sure a paused automation cannot be restarted accidentally by importing the same contact list again. Use the reproducible stop-rule simulation to understand the logic, then test your actual tools separately.
Which numbers show whether it helps?
Use a cohort of distinct, sent estimates and record how many remain open, receive a reply, are accepted, are declined, expire or are revised. Record completed work and collected payment separately. Define a consistent treatment for quote alternatives and versions so one project does not inflate the denominator.
Useful operational metrics include time to first useful response, unanswered customer questions, reminder sends after a stop event, estimator workload and decisions with documented reasons. Sending more messages is not an outcome. A reduction in inappropriate reminders can be valuable even before a revenue effect is established.
How often should HVAC estimates be followed up?
Use the customer’s timing and the estimate type. The sample cadence here is a starting point to review, not a universal optimum. Stop or pause as soon as the state changes.
Can AI answer the objections?
It can help classify a question or draft an answer from approved information. Have the estimator own changes to price, equipment, warranties, financing or scope. Do not allow a confident generated answer to change the commercial agreement.
What happens when a quote is accepted?
Close the sales reminder sequence and follow the business’s approved acceptance, deposit and scheduling process. Confirm each action independently; acceptance alone is not payment or a confirmed installation slot.
MAKE IT PRACTICAL
Turn the guide into a project brief.
See the implementation scope and interactive preview ↗
Use the worksheet to record your current tools, decisions, costs and pass/fail checks. Bring a redacted example and the workflow you want to improve.
Download the implementation worksheet ↗
RevSet reviews the process, scopes the build, configures the agreed connections, tests the handoffs and documents ownership. Implementation fees and ongoing support are agreed separately after the review.
Book an HVAC systems consultation ↗What the 30-minute review covers · Evaluate our implementation evidence
Sources and editorial approach
Product documentation checked October 5, 2026. Product availability, interface labels and prices can change. The workflows and buying criteria are RevSet’s editorial recommendations, supported by illustrative examples.