The short answer
Follow up to help the customer make a decision, not simply to ask whether they are ready. Confirm the estimate arrived, invite scope questions, check the project timeline, and close the loop when the answer is no or not yet.
Before the estimate is sent
Set the expectation during the site visit. Tell the customer how the estimate will arrive, when they should expect it, what it includes, and the easiest way to ask a question. That small step makes the first follow-up feel like part of the process rather than a surprise sales message.
Make sure the customer record has the correct name, project, mobile number, email, and decision timeline before starting any reminders.
The first check-in: confirm delivery
Send a short note after the estimate has had a reasonable chance to arrive. Mention the project and ask whether the document came through. Invite questions about scope, preparation, options, or timing.
Example structure: “Hi [Name], I wanted to make sure the estimate for your [driveway/patio/project] came through. If anything in the scope needs clarification, reply here and I’ll walk through it with you.”
The second check-in: ask about the decision
If there is no response, the next message can ask whether the project is still active and whether the customer’s timing has changed. Do not manufacture urgency. If scheduling availability is genuinely relevant, explain it accurately.
Example structure: “I’m checking in on the [project] estimate. Is this still something you’re planning, or has the timing changed? Either answer is helpful so I can keep our schedule and your request accurate.”
The final check-in: close the loop
A final message should make it easy to say not now. This protects the customer relationship and keeps the pipeline honest. If they are postponing, ask whether there is a useful month to reconnect. If they chose another contractor, thank them and record the reason when they are willing to share it.
Example structure: “I don’t want to keep filling your inbox. Should I close the estimate for now, or would a later check-in be useful?”
Rules that keep follow-up from becoming spam
Use the communication permissions and expectations established with the customer. Keep the sequence short, stop when they reply or opt out, and let a person handle questions. The system should remind the team and support the conversation, not pretend that persistence is the same as service.
- Use the customer’s real name and project type.
- Do not send the same message through several channels at once.
- Do not keep sending after a reply, decision, or opt-out.
- Keep notes so the next person understands the conversation.