Automated estimate follow-up sends reminders or creates staff tasks after a quote goes out. Done carefully, it gives the customer an easy way to ask a question and helps your team see which estimates still need attention.
The sequence starts after an estimate has actually been sent. Creating a draft quote is not the same event. First responses to new inquiries need a different workflow, covered in our speed-to-lead guide.
Plan the stopping point before the first message. Once someone accepts, declines or replies, the next step needs to reflect that. Nobody wants a reminder about a quote they have already discussed with your office.
Check the estimate before starting the sequence
Use a specific estimate reference and version, not just the customer's name. One customer can have multiple properties, alternative options or an older quote that has been replaced.
Before the first follow-up, check:
- It was sent through the intended channel and is still open.
- The customer has an appropriate, permitted contact method for this follow-up.
- A staff member owns the estimate and will receive replies.
- No existing conversation, opt-out or other stop rule prevents the next message.
- The link opens the current estimate, not an expired or superseded version.
If the estimate could not be sent, create a staff task to resolve the problem. Do not launch a “just checking you received it” sequence as a substitute for fixing a known delivery failure.
Give each message one useful purpose
Give each message a reason to exist. The sample below suits a planned home-service discussion, but its timing is a starting point to adjust, not a proven best schedule.
| Example timing | Purpose | Decision before sending |
|---|---|---|
| Two business days after the estimate was sent | Offer help with questions about the scope. | Is the same estimate open, and has anyone already replied? |
| About a week after sending | Ask whether the customer needs clarification or more time. | Has the assigned employee already agreed on a different next step? |
| At the business's agreed closing point | Explain that routine reminders will stop. | Is a closing message appropriate, or should the owner simply close the follow-up task? |
Match timing to the type of work, actual estimate validity and the customer's requested decision window. If they say “please contact me next month,” record that instruction rather than leaving them in this example sequence.
Do not invent urgency, claim a price is about to rise or say a slot is reserved unless that is true and authorized.
Example wording for email and text
Use these examples as a starting point. Replace the placeholders and check the details, then add the sender information and opt-out features your channel and location require.
An email that invites a question
Subject: A question about your estimate?
Hi [First name],
I'm following up on estimate [Reference] for [Short description of work]. If anything about the scope or options is unclear, reply here and [Assigned person/team] can help.
You can review the estimate here: [Current estimate link]. If you need more time or have decided not to go ahead, just let us know.
[Business name]
Use “I” only when the message genuinely comes from the named owner and replies reach that person or their designated team. Otherwise, use the business's voice rather than pretending an individual has personally reviewed the quote.
A shorter text, when that channel is permitted
Hi [First name], this is [Business name]. Any questions about estimate [Reference]? Reply here and our team can help. Reply STOP to opt out.
Before using the text, confirm that you have permission to send it and that STOP works with your provider. The wording alone does not cover those checks.
A final check-in without pressure
We'll leave estimate [Reference] with you and stop the reminders for now. If you'd like to pick it up later, contact [Business/team]. We'll confirm pricing and availability again then.
A final message is optional. If it adds nothing useful, an internal task closure may be enough.
Planning guide
Build the exit before the reminder.
Check the current estimate and customer conversation immediately before each send.
Continue only if…
The current estimate is open, contact is permitted and the next message still has a useful purpose.
Pause for a person
A reply, question or agreed change of timing needs the estimate owner’s attention.
Stop the old sequence
Acceptance, decline, replacement or opt-out changes what is allowed to happen next.
A delivery failure needs investigation, not endless retries or an unapproved switch to another channel.
Pause for replies and stop for decisions
Check the estimate again just before each message goes out. A customer may have accepted it or spoken to your team since the reminder was scheduled.
Use clear rules:
- Customer replies: Pause generic follow-up and assign the conversation to a person. A question should not sit unanswered while reminders continue.
- Estimate accepted: Stop the sales sequence and use the business's separate scheduling or onboarding process.
- Estimate declined: Stop. Record the outcome without automatically moving the customer into another campaign.
- Estimate revised or replaced: Stop the old version. The owner decides what follow-up is appropriate for the new one.
- Customer opts out: Stop the messages covered by that opt-out, including any already waiting to be sent.
- Delivery fails: Alert the owner, investigate and avoid unlimited retries or an unapproved switch of channel.
Give staff a manual pause as well. A phone conversation may change the next step even when no email or text reply reaches the system.
Our CRM and field-service integration guide explains why the estimate's status and communication restrictions need an agreed source of truth.
Check permission before sending
A phone number or email address in a customer record is not blanket permission for every follow-up. Decide the message's purpose, channel and applicable requirements before enabling the sequence.
For example, Twilio's messaging policy sets consent, sender-identification and opt-out requirements for messages using its services. Provider rules are one part of the review, not legal clearance.
Requirements also differ by jurisdiction and message type. The FTC's CAN-SPAM guide addresses US commercial email, while the CRTC's CASL guidance explains Canada's commercial electronic-message framework. Check the requirements for the messages you plan to send before turning them on.
Measure decisions and unanswered questions, not message volume
Keep these events separate:
- Sent: The messaging system reports its send stage. The exact meaning depends on the provider.
- Delivered: A delivery event was reported. It does not show that the customer read or understood the estimate.
- Reply: An incoming response arrived. Someone still needs to interpret and handle it.
- Decision: The estimate was accepted, declined or otherwise resolved in the system that owns it.
Twilio's message-status documentation distinguishes sent, delivered and incoming-message states. Do not label them all “customer contacted.”
Review open estimates without an owner, unanswered replies, messages sent after a stop event and the reasons estimates remain undecided. Use that review to fix unanswered questions and missed decisions, rather than adding another reminder to the sequence.
Make follow-up easier to manage
Start with one estimate type, a short sequence and a real reply owner. Test acceptance, a question, a decline, an opt-out and an estimate revision before launch.
If the reminders, records and replies currently live in different places, explore Goliath's automation and integration services. The goal is a useful next step for the customer and less chasing for your team.
