Free resourceEmail sequenceFollow up

Follow up on a plumbing estimate.

Three editable emails for a plumbing estimate that has gone quiet, with suggested timing and clear rules for when to stop.

How to use this in HighLevel
After an open estimate

Example timing: days 2, 5 and 10 after the estimate was sent. These are calendar days, not business days. Adjust to the customer’s expectations and your working hours; the page schedules nothing.

Stop reminders when they reply or book. See every stop rule.

Day 2 after the estimate

Check it reached them

SubjectA question about your [Service] estimate
Hi [First name],

I’m checking that the estimate from [Business name] for [Service] reached you.

Is there anything you would like me to explain about the work included or the proposed timing? You can reply here with a question.

If you have already spoken with us or arranged the work, let me know so I can update our notes.

Thanks,
[Your name]
[Business name]
Download email

Copy the subject and message into separate fields. Review names, sender details and the recipient before sending.

Day 5 after the estimate

Help with the decision

SubjectAnything to clarify about [Service]?
Hi [First name],

Before you decide on the [Service] estimate from [Business name], is there anything you would like us to clarify?

For example, you may want to check which parts and work are included, what access we need, or how we would arrange a suitable time. Reply with the question that matters to you.

If your plans have changed, that is useful to know too. We can update the estimate record without continuing to chase you.

Thanks,
[Your name]
[Business name]
Download email

Copy the subject and message into separate fields. Review names, sender details and the recipient before sending.

Day 10 after the estimate

Leave the door open

SubjectClosing the loop on [Service]
Hi [First name],

This is my last planned reminder about the [Service] estimate from [Business name]. I’ll leave the next step with you.

If you would like to revisit it, reply here. We can confirm that the scope, price and availability are still current before agreeing any work.

If you have decided not to proceed, no problem. There is no need to explain, and we will stop these estimate reminders.

Thanks,
[Your name]
[Business name]
Download email

Copy the subject and message into separate fields. Review names, sender details and the recipient before sending.

Keep the whole plan.

All three emails, timing, stop rules and the test checklist in one text file.

Download the pack

Copy-ready email content. No workflow, timer or automatic sending is installed. Account and inbox testing of this sequence has not been performed.

From template to useful

Put it to work.

Personalize the content, add it to your account, and test the complete experience before a customer sees it.

Read the setup guide
  1. 1

    Personalize the three emails. Use a recognizable project description, such as kitchen tap replacement. Copy each subject and message into separate email drafts or saved templates.

  2. 2

    For repeated use, replace the literal customer name with the appropriate HighLevel field. Keep the project description specific to that estimate. Configure your sender and required footer details; test a missing first name.

  3. 3

    Before each send, check the conversation, estimate status and booking record. Apply the stopping rules below. If a reminder is overdue, send at most the next useful message; never send the missed emails together.

  4. 4

    Use the test checklist before enabling any automation. This text pack does not install timers, enroll contacts, or stop messages in your account.

Start with the right estimate.

Start only after you have sent a non-emergency estimate to a customer who can be contacted by email. Confirm it is still open, has no reply or booking, and is not already in another follow-up sequence. Keep one active estimate per contact in this plan.

Know when to stop.

Check these before every email. Stop or hold the sequence when any of them applies.

They reply through any channel
Stop the remaining reminders and give the conversation to the person handling the estimate. Answer the question before deciding on any further follow-up.
They book or accept the estimate
Stop the sequence and use your normal job-confirmation process. A booking needs its own confirmation; none of these emails confirms one.
They decline, opt out, or the estimate closes
Stop the sequence. Record the decision or contact preference and do not restart it automatically.
The address is missing, fails, or contact is restricted
Hold the next email for review. Do not switch channels or bypass the contact’s preferences to keep the sequence running.
The event repeats or a second estimate appears
Keep one active plan for that contact. Have the owner choose the correct estimate; do not run overlapping reminders or restart completed ones.
No reply after the final email
End the reminders. Leave the estimate for owner review; do not mark it accepted or declined based on silence alone.
If you automate this in HighLevel

The emails are ready to adapt. Building and testing the account workflow is a separate step.

  1. Prepare a draft using the three messages and waits of 2 days, then 3 more days, then 5 more days. Recheck eligibility before each send. A permitted sending window may move the actual delivery time.
  2. Review Allow Re-entry and Allow multiple Opportunities; keep both off for this one-estimate-per-contact plan. Turn on Stop on Response, which covers responses to messages from that workflow. Handle replies from other channels separately.
  3. Map your reply, booking, accepted/declined, and opt-out events to removal from this specific sequence. HighLevel’s Remove from Workflow action can target it. An external calendar or conversation is not a verified exit until its event reaches your account.
  4. Keep the workflow in draft until the cases below pass in your own account. Shortened test waits do not verify the final production schedule. This pack contains no native workflow import or snapshot.

Read HighLevel’s workflow settings and workflow actions. Sources reviewed November 3, 2026; this sequence has not been exercised in an account.

Try the exceptions, too.

Use fictional records and your own test inbox. Record what actually happened for every case before enabling a live sequence.

One eligible, unanswered estimate
One message at each chosen interval, then no further reminder. Confirm the time zone and sending window.
Reply to the first email; separately, reply elsewhere
The next message does not send in either case, and a person takes ownership of the reply.
Book, accept, or decline while waiting
Each event independently removes the contact before another reminder. Test manual bookings too.
Opt out before entry or between messages
No later email sends. The contact’s preference remains recorded.
Repeat the entry event; add another estimate
No duplicate enrollment, second reminder series, or automatic restart.
Missing name, address, or project; failed delivery
Use a reviewed greeting for a missing name. Hold missing/invalid addresses or project context for review. A failed send does not count as a delivered reminder.
Booking integration unavailable; overdue reminders
Hold for manual review when eligibility cannot be confirmed. Restoring a connection does not release a burst of missed emails.
A clear starting point

Before you use this.

Copy three separate email drafts and use the setup checklist.

You’ll need

  • An open, non-emergency estimate, its sent date, and permission to contact the customer by email.
  • A configured sender, appropriate footer details, and a person responsible for replies and status changes.

Make it work for your business

  • The text pack does not install a workflow, send messages, or enforce timing and stopping rules.
  • Entered names and project details are literal text. Review account fields, missing values, and the recipient before reusing a draft.
  • Suggested timing is a starting point. Verify reply, booking, opt-out, duplicate, and missing-integration cases before enabling automation.
What has been checked?

The generated files for this version passed local content and personalization checks on . These checks cover the file output; they do not verify an import, a sent email, or a business result.

Full HighLevel account testing is incomplete. Inbox rendering is untested. Send to your own test address before using the email with customers.

How we check our resources

Original content, ready to adapt.

You may customize these free resources for your own business or client work. Do not resell the original files as a competing template library. Illustrations and copy are examples, not promises of results. Account behavior and email rendering still need testing.

How we create and check resources

One good next step.

You don’t need to fix everything at once. Let’s find a useful place to start.

What needs the most attention?