The Estimate Went Quiet. Here's How to Follow Up Without Being a Pest.

You looked at the job. Wrote the estimate. Sent it over. The customer seemed interested, and now you haven't heard a thing.

Before you knock money off the price, find out whether they actually got the estimate.

I wouldn't build a follow-up process around guessing why somebody went quiet. They could be comparing options. The timing could have changed. They could have a question they haven't asked. You don't know yet.

Here's the estimate follow-up sequence we use with clients, followed by the action plan for running it. Each touch has a reason. The dates are checkpoints, and the customer's response decides what happens next.

Agree on the next step first

When you're wrapping up the visit, ask when they're hoping to decide and how they want to hear from you. Record the answer. If they only want the estimate and don't want follow-up, respect that.

Check delivery before treating silence as a sales objection. A sent status doesn't tell you whether the customer read the estimate or understood it. If they didn't receive it, confirm the destination and resend through the agreed channel.

The exact sequence we use with clients

Here are the exact messages, how I think about them, and a few alternatives. Use the version that fits the customer and the job.

24 hours later
"Hi [Name], it's [Your Name] with [Company]. Thanks for having us out yesterday. Did any questions come up once you had time to look over the estimate? Happy to walk you through anything."

3 days later
"Hey [Name], [Your Name] here. I was thinking about your [system/project]. If price or timing is what's holding things up, tell me straight. We usually have a few ways to make it work."

7 days later
"[Name], quick question. Did you end up going a different direction on the [project]? Totally fine if you did. I'd just like to know so I can close out your file."

30 days later
"Hi [Name], [Your Name] from [Company]. How's the [system] holding up? Your estimate is still on file. If you want to take another look, I'm happy to re-run the numbers so they're current."

90 days later
"Hey [Name], it's [Your Name]. We're starting to book [season] work and you came to mind. If the [project] is still on your list, I can save you a spot before the rush. No pressure either way."

Why these work
Each text has one job. The 24-hour text is about service. The 3-day text gives the customer permission to bring up the real objection. The 7-day text uses a soft takeaway, and that one tends to get the most replies. The 30-day text is a check-in on their system, and the 90-day text uses real seasonal timing. None of them chase the customer. They read like an owner who has plenty of work and actually cares, and that's the posture of a $100M operator.

Alternative approaches
1. Have the tech who ran the estimate send the 24-hour text instead of the owner. It feels even more personal.
2. Attach a photo from the visit to the 3-day text, for example "Here's that corroded coil I mentioned." Proof beats persuasion.
3. For big-ticket estimates over $10K, replace the 30-day text with a short phone call.

The exact action plan

1. Give the estimate an owner. Start the clock when the estimate is delivered, and record the visit date separately. Assign one person and a backup. Keep the job details, status, agreed contact channel, and follow-up permission in the same place.

2. At 24 hours, use the service-first message. Confirm the customer is eligible for the follow-up and the visit really was yesterday. If the estimate never arrived, fix that first. The tech who ran the visit can send it if they're responsible for the next step.

3. On day three, make room for the real objection. Check that the options you're implying actually exist. Don't promise an unapproved discount, financing, or date. If you include a photo, use an accurate photo from this customer's visit that you're allowed to share with them.

4. On day seven, ask where things stand. Pause the sequence for a person to handle any reply. If they chose another company, close it as lost. If they don't answer, mark it no response and finish the active chase. Silence doesn't tell you why they didn't proceed.

5. At day 30, review before reaching out. Confirm the later contact is permitted and still relevant. Check that the estimate is on file and review current scope, pricing, and availability. For estimates over $10K, a short personal call is an option when that contact method is appropriate and permitted.

6. At day 90, check the actual season and schedule. Send the seasonal message only if you're really booking that work and can genuinely offer a spot. Don't invent a rush. This is another staff review point, not an automatic restart for every silent estimate.

7. Keep the stop rules working. Pause on replies. Stop for opt-outs or booked, won, lost, or canceled jobs. If someone asks you to check back on a particular date, use that date. Cancel queued duplicates across your tools. Test the rules before activation and review the process regularly.

Check the setup before turning it on

Use these texts only where the customer has the right permission in place for that contact. Include required sender details and opt-out instructions. An estimate request isn't blanket permission for recurring promotional messages; check your provider's rules, including Twilio's messaging policy where applicable.

HighLevel's Stop on Response setting applies to replies to messages from that workflow. Test the other status changes and connected tools too. One setting doesn't cover every handoff.

What if they come back months later?

Have the conversation. Check whether the job is still the same, what the current costs are, and when you can do it.

Review the original terms and any existing agreement before changing anything. Don't invent an expiration date after the fact. If an update is appropriate, explain it and provide a revised estimate for review before scheduling or making a commitment.

Connect the inquiry to the next action

The handoff starts with the first conversation. If you're looking at an AI front desk, ask what information reaches your team and who owns the next step once the call ends.

We put the routine follow up on autopilot for you

At Ottomatic, we use HighLevel to put routine estimate follow-up on autopilot for you. We set up the approved messages and timing, the status checks, and the rules that pause the sequence when someone replies and stop it for an opt-out or a booked, won, lost, or canceled job. Replies go to a named person so your team can handle the actual conversation.

We agree the rules with you and test the setup before activation. The 30- and 90-day checkpoints retain the relevance, pricing, and real-availability reviews described above. We review the process regularly so the wording, handoffs, and timing stay useful. Your team still owns the customer's decision and any pricing or scheduling commitment.

That's part of what Otto's JobFlow™ connects: getting the inquiry, handling the conversation, and keeping the next step from being forgotten.

Start with the estimates already sitting in your list. Give each one a responsible person, a truthful next message, and a clear point where the sequence pauses or stops. Then make sure the system follows those decisions.