
When an estimate goes quiet, automate the reminders, not the relationship. Send a short, timed series of follow-ups after the estimate, stop it the moment the customer replies or books, and alert a real person whenever the customer asks a question or the job is big enough to deserve a call.
An estimate that goes quiet is not always lost. Often the homeowner got busy, is comparing two bids, or is waiting on a spouse. A polite nudge at the right time is often all it takes. The problem is that nobody in a busy office remembers to send it. That is the part a system should handle.
Know what you are automating
Automation here means three simple jobs:
- Sending a planned message at a planned time after the estimate goes out.
- Stopping that series as soon as something changes, like a reply or a booking.
- Alerting a person when a human should step in.
It does not mean a robot that argues about price, makes discounts, or answers technical questions. Those stay with you.
The estimate follow-up map
Think of every estimate as being in one state at a time. Each state has a trigger that moves it into the next one. Here is a simple map you can copy into your CRM, scheduling app, or even a spreadsheet with reminders.
State 1: Estimate sent
- Trigger in: the estimate is emailed or texted.
- What happens: a short confirmation goes out the same day. "Here is your estimate for the roof repair at [address]. Reply here with any questions."
- Owner: the estimator who wrote it.
State 2: Waiting
- Trigger in: no reply and no booking after the first message.
- What happens: follow-up 1 after about 2 days, asking if they had a chance to look. Follow-up 2 after about 5 to 7 days, offering to walk through it by phone. Follow-up 3 after about 14 days, a polite last check.
- Owner: the system sends, the estimator gets a copy.
The exact days are a starting point. Emergency repairs need tighter timing. Large remodels can wait longer between messages.
State 3: Customer replied
- Trigger in: any reply by text, email, or call.
- What happens: all automatic messages stop right away. The estimator gets an alert with the reply.
- Owner: a person, every time.
This is the most important rule in the whole map. Nothing annoys a customer faster than a "just checking in" text an hour after they already said yes.
State 4: Booked or signed
- Trigger in: a job date is set or the estimate is accepted.
- What happens: follow-ups stop. A booking confirmation goes out instead.
- Owner: the office.
State 5: Lost or closed
- Trigger in: the customer says no, chose someone else, or the last follow-up got no answer.
- What happens: follow-ups stop. Mark the reason if you know it. You can add them to a seasonal check-in list later if they agreed to hear from you.
- Owner: the estimator marks the reason.
State 6: Opted out
- Trigger in: the customer replies STOP, "no more texts," "unsubscribe," or anything like it.
- What happens: every automated message to that customer stops, on every channel, and stays stopped.
- Owner: the system, with a note on the customer record.
Write the stop rules first
Before you write a single message, write the rules that end the series. A good set of stop rules:
- Any reply from the customer, even "thanks"
- A booking, signed estimate, or payment
- An opt-out word or request, in any wording
- A wrong number or a bounced email
- The estimator manually pausing it, for example after a phone call
Test each rule before you go live. Send yourself an estimate, reply "thanks," and make sure nothing else arrives.
Decide when a person steps in
Some moments are too important for a template. Set alerts so a person is told, and the system waits, when:
- The customer asks a question, mentions price, or asks for changes
- The estimate is above a dollar amount you choose
- The customer opens the estimate several times but does not reply, if your software shows that
- A message fails to send
Example numbers. Say an HVAC company sends 30 estimates a month. Their rule: anything over $8,000 gets a personal call from the owner on day 3 instead of follow-up 2. Smaller estimates follow the automatic series. The owner makes a handful of calls a month instead of chasing all 30.
Keep texting and email legal
Follow-up texts and emails come with rules. Here are the basics, but confirm the details with your texting provider or an attorney.
- Texts. FCC rules require a caller to get consent before sending autodialed texts to a wireless number, and people can opt out of robotexts at any time in any reasonable way. FCC: Stop Unwanted Robocalls and Texts Ask on your estimate form whether the customer agrees to texts about their estimate, and keep that record.
- Emails. The FTC's CAN-SPAM guide says you must honor an opt-out request within 10 business days. FTC: CAN-SPAM Act Compliance Guide Make unsubscribing easy and real.
- Carrier rules. Business texting providers often require you to register your business before sending. Check your provider's current rules, as of November 2026, before launch.
Where automation breaks
Plan for the failures, because they will happen:
- Two systems, one customer. The CRM sends follow-ups while the estimator also texts from a personal phone. The customer gets both. Pick one channel of record.
- Replies the system cannot see. A customer calls the office instead of replying to the text. The series keeps going. Make "mark as replied" one tap for whoever answers the phone.
- Old estimates in the queue. Turning on automation for estimates from months ago can send a wave of strange messages. Start with new estimates only.
- Templates that sound like templates. Use the customer's name, the job, and the address. Keep messages short and in your normal voice.
- No one owns the alerts. If alerts go to an inbox nobody checks, the system helps no one. Name a person for each alert.
What a good follow-up sounds like
Short, specific, easy to answer:
- "Hi Dana, it's Mike from [your company]. Any questions on the water heater estimate? Happy to walk through it."
- "Hi Dana, just checking if the timing still works for you. Reply here or call us at the office number."
- "Hi Dana, we will close out this estimate for now. If you want to move ahead later, just reply and we will pick it up."
No pressure, no fake deadlines, no "last chance" discounts you did not plan.
If you want help setting up the states, stop rules, and alerts in the tools you already use, our AI automation work starts with this kind of map. For the email side, see email marketing. And if calls are slipping through before an estimate is even written, missed-call text-back covers that earlier gap.
Common questions
How many follow-ups should I send after an estimate?
Two or three is a reasonable start for most jobs. Track how many estimates turn into jobs after each follow-up, then adjust.
Should I use text or email?
Use what the customer agreed to and actually answers. A common setup is text for short nudges and email for the estimate itself, but only text people who have given consent.
Will automated follow-ups annoy customers?
They can if they keep going after a reply or sound like a robot. Strong stop rules and short, personal messages prevent most of that.
Can AI write the follow-up messages?
It can help draft templates, but a person should approve them before they go live. Keep anything about price, changes, or scheduling in human hands.
What software do I need?
Many CRMs and scheduling apps already include follow-up reminders. Start with what you have, write the map and stop rules, and only add tools if your current ones cannot handle them.
Next step
Want a free plan for estimate follow-up that stops at the right time? We will map your states, stop rules, and alerts with you. Get my free plan



