Choose the message from the current estimate, not its age alone
Read the latest conversation before deciding what to send. A three-day-old quote with a recorded question needs an answer. A 60-day-old estimate may need a scope review. A quote accepted yesterday needs the next job or scheduling step. Sending all three homeowners the same reminder ignores what they already told you.
A useful review order is current work or acceptance, contact exclusions, open conversation, customer-requested timing, estimate validity, then unanswered status. Resolve the earliest applicable condition before enrolling the record. If the conversation is missing or contradictory, assign a review task instead of letting AI fill in the history.
| Current evidence | Use | Check before sending |
|---|---|---|
| Estimate delivered; no reply or newer action | Template 1 or 2 | Real estimate, permitted channel and reply owner. |
| An unresolved question is recorded | Template 3 | An approved answer tied to that scope. |
| Customer gave a later time | Template 4 at the agreed review point | Requested date and any newer conversation. |
| Older estimate needs updating | Template 5 | Current project interest before re-quoting. |
| Accepted, booked, lost, excluded or actively handled by staff | An operational action or no sales reminder | Route the known next step; resolve any conflicting queued contact. |
1. Email after sending a new estimate
Use this when the estimate was actually delivered and there is no newer reply. Reference the real project rather than starting another sales pitch. The estimator or salesperson who can explain the scope should own the response.
Pick a follow-up interval with your team. If an existing CRM reminder already does this well, configure its content and recipient settings first. Do not add a second system that sends the same reminder.
Subject: A question about your [project] estimate
Hi [first name], I sent estimate [estimate reference] for [specific project] on [date]. Did it reach you, and is there anything in the scope you would like me to walk through? You can reply here with your question. [Owner name] will help with the next step. [Your name] [Company]
Filled HVAC example: the homeowner is comparing scope
Fictional estimate E-241 covers an upstairs cooling project. It was emailed September 10; there is no recorded response yet. Priya is the estimator and owns questions about the listed equipment and installation scope. The message refers to that project rather than promising lower bills or pushing an unsupported discount.
The customer can reply with the point they are comparing. That gives Priya a specific conversation to handle. A shorter message is useful here because the estimate already contains the sales presentation; the follow-up’s job is to discover the unresolved decision.
Subject: A question about your upstairs cooling estimate
Hi Jamie, I emailed estimate E-241 for your upstairs cooling project on September 10. What part of the equipment or installation scope would you like Priya to walk through? Reply here with the item you are comparing and we’ll review it with you. Casey Example HVAC Company
2. Text when a short reply would help
Use a permitted text conversation when the customer can answer one short question. Identify the company and the project. The message should connect to the same estimate record as any email or call.
A reply such as “call after 4” should pause pending generic reminders and create a callback for the owner. A delivered message is not a customer response. Use the sender’s required opt-out wording and handling for the channel.
Hi [first name], it’s [name] with [company]. Do you have a question about estimate [reference] for [project], or would a quick call help? Reply here and I’ll arrange the next step with [owner]. [Required opt-out wording]
Filled plumbing example: one question in a permitted text thread
Fictional estimate E-317 is for a water-heater replacement. Morgan has an eligible text conversation with the business, and Sam can explain the replacement scope. This example includes a hypothetical sender’s configured stop footer; use the wording and handling of your own approved channel.
Keep this as an alternative to the email follow-up when a short reply fits. It is not a second message to send immediately after every email. If Morgan asks for a call after 4, the office records that callback and checks the pending sequence before another reminder is sent.
Hi Morgan, it’s Sam with Example Plumbing. Would you like me to walk through what’s included in water-heater estimate E-317? Reply here and I’ll help with the next step. Reply STOP to opt out.
3. Follow up on the question that held the estimate
Use this only when the earlier conversation records a real unresolved question. For example, a siding customer wanted to confirm the color package; a plumbing customer wanted to understand what the replacement included.
The approved answer must come from a person or an authoritative business record. AI can help turn that answer into concise wording. It should not create a warranty, financing offer, technical finding or discount that your team has not approved.
Subject: Your question about [specific scope item]
Hi [first name], You asked about [recorded question] when we reviewed estimate [reference]. [Approved answer in one or two sentences.] Does that resolve the question, or would you like [owner] to go through the options with you? [Your name] [Company]
Filled siding example: answer the recorded color question
The fictional customer asked whether another color could be selected. Alex has reviewed the estimate and approved the answer below. It identifies what the current estimate contains and who will confirm a change. It does not invent supplier availability or authorize an order.
Attach the approved answer to the estimate’s history. If the customer has already resolved the selection with production, update the next action instead of repeating the sales question. An answer that was correct for a previous package may be wrong after a revision.
Subject: Your color question on siding estimate E-482
Hi Taylor, You asked about choosing another color for siding estimate E-482. The estimate includes the color listed on page 2. If you prefer another option, Alex will confirm the revised scope and supplier availability before an order is placed. Would you like Alex to review a different color with you? Jordan Example Siding Company
4. Reconnect when the customer’s timing changes
Use the customer’s stated timing when it is still relevant. “Later this fall” is context you can verify; an AI guess about a homeowner’s finances is not. Ask whether the plan changed without inventing urgency.
If the customer asks for a later date, record that date or a staff review task. Do not put the person back into an unchanged daily sequence. If they are no longer pursuing the project, stop the applicable follow-up.
Subject: Is [project] still on your list for [stated timing]?
Hi [first name], When we last spoke, you were considering [project] around [timing the customer gave]. Is that still the plan, or has the timing changed? If you would like to revisit it, [owner] can review what needs updating before we discuss the next step. [Your name] [Company]
Filled landscaping example: draft for the customer’s requested week
Fictional customer Avery asked the office to reconnect during the week of October 12 about a planting project. This is a draft for that review point, not an instruction to send it today. The customer’s date takes precedence over a generic “seven days after quote” sequence.
If the customer says “spring instead,” record the new review point or assign a staff task to establish it. Do not classify that as immediate interest and return the estimate to the original sequence. The next action should reflect the answer, not just the fact that a reply arrived.
Subject: Is the planting project still on your October list?
Hi Avery, You asked us to reconnect during the week of October 12 about the planting project in estimate E-204. Is that still a useful time to review it? If so, Robin can check the current scope and availability with you before we arrange the next step. Lee Example Landscaping Company
5. Revisit an old or expired estimate
Use this for a suitable older opportunity after checking its current status. An expired quote needs a review of scope, price and availability. The message should not imply that an old price or installation window still stands.
The useful outcome is a current answer: still interested, later, needs a revised estimate or no longer interested. Keep those responses separate from sold jobs. Our lead reactivation walkthrough shows the eligibility and handoff process in more detail.
Subject: Do you still want help with [project]?
Hi [first name], We prepared estimate [reference] for [project] in [month/year]. Are you still considering the work? If so, [owner] can review the current scope, pricing and availability with you. The earlier estimate may need updating. If the project is no longer on your list, let us know and we’ll close the follow-up. [Your name] [Company]
Filled painting example: reopen the project before re-quoting
Fictional estimate E-118 was prepared in June for interior painting and needs review before the office can stand behind its old scope or price. The useful first answer is whether the customer still wants the work. A fresh scheduling promise would get ahead of that decision.
If the customer says yes, the estimator checks any changed rooms, preparation requirements and current pricing. Keep that as a review or re-quote action until the customer accepts the updated scope. A positive reply does not by itself establish a sold project.
Subject: Is the interior painting project still planned?
Hi Riley, We prepared estimate E-118 for your interior painting project in June. Are you still considering the work? If so, Devon can review any changes to the rooms, preparation and current pricing. The earlier estimate may need updating. If you have moved on, let us know and we’ll close this follow-up. Sky Example Painting Company
Use a short proposed cadence, then let the customer’s answer change it
The following cadence is an illustrative office policy, not a measured best-performing sequence. It assumes a delivered estimate, an eligible channel, no active conversation and no other owner already following up. Discuss the interval and attempt limit with the team that will handle the replies.
Choose email or text for the first follow-up based on the actual conversation and approved setup. Do not add both just to increase the attempt count. For an expensive or complex scope, the next action may be an owned call rather than another automated message.
A requested callback, scope question, acceptance, staff takeover or opt-out changes the sequence immediately under your agreed process. Check the current record at send time; a list exported last week cannot establish that nobody has answered since.
| Review point | Action if still eligible | What changes it |
|---|---|---|
| Day 0 | Send the actual estimate; record channel, recipient, delivery and owner. | Failed delivery is an address/channel repair, not a new sales attempt. |
| Day 2 | One follow-up using template 1 or 2. | Existing reply or requested date routes to a person or later review. |
| Day 7 | One second message only if still unanswered and appropriate. | Known scope question uses template 3; expired scope needs review. |
| Day 10 | Office reviews the unresolved item and chooses close, hold or an owned next action. | No automatic restart merely because the customer stayed quiet. |
What the office should do with each reply
Assign an owner and an expected response window before starting. A reply should pause the applicable pending sequence while a person handles the conversation. Check the customer’s current status again immediately before any scheduled contact.
Use this table as a proposed operating rule. Test it on representative records in your own accounts before enabling customer contact. AI classification can propose a category; ambiguous replies need a person.
Make the promised response window match the office’s actual coverage. If the sender says a named estimator will help, somebody must monitor that reply path and assign the question to that estimator. An unattended inbox makes even accurate copy ineffective.
| Customer response | Next action | Record to keep |
|---|---|---|
| “I have a question.” | Pause reminders; assign the estimator or salesperson. | Question, owner and agreed response time. |
| “Call next Tuesday.” | Record a callback under the agreed schedule. | Customer’s requested date and assigned caller. |
| “I want to go ahead.” | Route acceptance through the business’s approval process. | Accepted scope and the verified next booking or job step. |
| “Yes.” | Inspect the question being answered; ask a person to resolve ambiguous intent. | Original question, reply and the verified next action. |
| “Maybe later.” | Ask the owner to establish a useful review date; pause generic contact. | Customer’s words and an owned timing decision. |
| “We hired someone else.” | Close the opportunity and stop this sales follow-up. | Lost reason from the customer’s answer. |
| “Stop contacting me.” | Apply the opt-out and stop the applicable contact. | Opt-out event and the suppression state. |
| No reply | Keep within the agreed cadence and attempt limit. | Last attempt, outcome and next action or closure. |
Follow one estimate through the message, reply and job handoff
This fictional history continues HVAC estimate E-241. The first follow-up produces a scope question and a callback request. The useful automation result is a paused sequence with an owned conversation; the estimator still supplies the approved scope answer.
Keep the customer’s exact words available to the owner. An AI summary of “interested” would discard the requested call time and the removal question. The next step can be correct only if those details survive the handoff.
| Event | Record to keep | Next action |
|---|---|---|
| September 10 · estimate emailed | E-241, recipient/channel, delivery outcome, estimator Priya | Wait under the agreed cadence. |
| September 12, 9:00 a.m. · first follow-up sent | Attempt reference, actual wording and send result | Await reply; the second attempt remains conditional. |
| 9:08 a.m. · “Does it include removing the old system? Call after 4.” | Original reply, scope question and callback request | Pause generic reminders; assign Priya the call. |
| 4:15 p.m. · estimator handles the question | Approved answer, call outcome and next customer decision | Keep the unresolved decision visible. |
| September 13 · “We want to go ahead.” | Interest/acceptance signal and current scope reference | Route through the business’s actual acceptance process. |
| September 14 · job exists, first visit not yet confirmed | Verified job reference and unscheduled state | Dispatcher owns scheduling; do not count a booked visit yet. |
The minimum follow-up record
Keep estimate reference, current status, last inbound timestamp, channel eligibility, last attempt/result, requested callback or review date, next action, owner and suppression state together. If another app owns an attempt, preserve its reference so the office can investigate an uncertain send.
Record a job or confirmed visit only after it exists in the operating system. The Jobber integration guide shows why approval, job creation and scheduling require separate evidence. Recovered revenue needs its own outcome and attribution record; a positive reply is insufficient.
Use AI to draft and classify from a bounded record
AI can select a draft for the actual state and propose reply categories. Give it the current estimate reference, approved scope facts, latest customer words, requested timing, chosen owner and channel. Leave unnecessary personal data out. If a required fact is missing, the draft should request review rather than invent an answer.
A useful drafting instruction is: “Choose one of the five situations from the supplied record. Write one concise follow-up with one customer decision. Use only the approved scope facts. Preserve the estimate reference and requested timing. Return the chosen situation, draft, facts used and anything requiring staff review.”
For the E-241 reply, a classification should preserve both “scope question” and “callback after 4.” A single category such as “positive lead” is too coarse. Keep opt-outs, scheduling changes, technical answers, price revisions and ambiguous acceptance in the appropriate verified process.
- Have the owner approve the templates and which record states can use them.
- Review representative drafts against the exact records and customer wording.
- Apply eligibility and stop checks outside the drafting step, using current state.
- Route uncertain classifications and missing approved answers to staff.
- Inspect the actual attempt, reply and destination handoff before marking a record complete.
Use native CRM reminders where they fit
Jobber documents up to two customer quote follow-ups for awaiting-response quotes on Connect and higher plans. These use the original delivery method and recipient communication settings. They differ from staff schedule reminders, which do not contact the customer. Follow the Jobber setup walkthrough for the actual editor steps.
For a broader process, write down the missing behavior: a shared owner across channels, a callback on a specific date, a response that stops another queue, or a reliable record of the next step. Confirm the exact reads, writes and plan access before commissioning a connection.
The Jobber guide, JobNimbus guide and Housecall Pro guide explain different native and integration boundaries. Use the estimate follow-up cost calculator to model your usage rather than assume a recovered-sales figure.
Jobber also says custom automation rules do not apply to past items retroactively. Treat older estimates as a reviewed backlog, then configure future rules. In JobNimbus, a time-based salesperson review task can be a native starting point before another sender is added.
Measure outcomes without counting every reply as recovered work
Separate eligible estimates reviewed, distinct estimates contacted, delivered attempts, replies, scope questions, callbacks, accepted work and confirmed visits. Several messages to one homeowner are several attempts on one estimate; they are not several opportunities.
Choose a cohort and record the next action for every unresolved item. A simple weekly office review asks how many appropriate records received a first attempt, which replies still need an owner, and whether promised callbacks happened. That is more actionable than a message-volume total.
If testing wording, keep the eligible record types and cadence comparable and change one meaningful choice at a time. Small samples can help find confusing copy or routing failures; they do not establish a reliable conversion lift. Keep actual job and revenue outcomes separate from a customer’s expression of interest.
Review five estimates before automating the backlog
Choose five examples that represent different situations: a new unanswered estimate, an unresolved scope question, a delayed project, an expired quote and one that should be excluded. Use anonymized details for a first conversation; keep customer records in your own account.
For each one, note the estimate reference, current status, last customer reply, suitable channel, next action and owner. If one of those is unknown, put the estimate in a review queue before contact. You can download the message pack and review checklist without entering an email address.
GoodHandoff’s free 20-minute five-estimate check ends with a short follow-up plan: which examples need review, what the CRM can already handle, and the first workflow worth scoping. A process that needs deeper investigation starts with the $500 assessment, credited toward the build if you go ahead within 30 days. The estimate follow-up build covers setup, approved messages, response handling, testing and handover.
- A reply arrives before the next reminder: pending contact pauses and the owner sees it.
- The estimate is accepted or a visit is booked: the generic sales sequence stops under your rules.
- The customer opts out: the applicable future contact stays suppressed.
- The same event arrives twice: it does not create a second attempt.
- A message may have sent but the response times out: reconcile delivery before retrying.
- The CRM update fails: a named person sees the repair without another message being sent.
Supporting documentation
Official documents were checked for the latest update to this guide. Examples and operating recommendations are GoodHandoff’s analysis; they are not claims of live customer results or vendor certification. We have not tested these integrations in your account. Access, pricing and API behavior can change.
- Jobber: Automations and Quote Follow-UpsNative quote reminder availability, count, delivery method and recipient settings. Message wording and operating rules above are GoodHandoff’s proposed examples.
- Jobber: Staff Quote RemindersStaff schedule reminders differ from customer follow-up messages.
- Jobber: Custom Automation BuilderNew rules do not apply retroactively to past items. Cadence and AI operating rules above are proposed examples.
GoodHandoff sells custom workflow services. We recommend built-in configuration when it meets the requirement. No ranking payment or vendor partnership is implied by inclusion.