Automate quote follow-up: cadence, copy, and the build
A 24h/3d/7d/14d quote follow-up cadence with copy-paste message templates, stop-on-reply logic, and an n8n or Make build outline you can ship this week.
What you get from this guide
- A four-touch cadence at 24 hours, 3 days, 7 days, and 14 days with the reasoning behind each gap
- Copy-paste message templates for every touch, in email and SMS lengths
- Stop-on-reply logic that covers email, SMS, and quote status changes
- A build outline that works in n8n or Make, using a scheduled sweep instead of fragile multi-day waits
- Guards for quiet hours, high-value quotes, and human handoff
Why quotes die in the follow-up gap
Nearly every small business that quotes work has the same leak. The estimate goes out the same day, the customer means to reply, life happens, and the quote sits in a folder until it is stale. Nobody decided not to hire you. The follow-up just never happened, because the person who would have made it was on a job.
The general pattern in sales research and in practitioner reporting is consistent: a substantial share of deals close only after several follow-up attempts, and quotes that are never followed up mostly go quiet for good. Treat the widely-quoted precise percentages with suspicion, because most of them trace back to vendor marketing rather than to a published study. The directional claim is safe to build on, and your own before-and-after numbers over a hundred quotes will be more persuasive than any statistic you could cite.
The good news is that this is close to an ideal automation candidate: the trigger is clean (a quote was sent), the timing is fixed, the copy is repeatable, and the only judgment involved is what to do when someone replies, which stays with a human. That combination is exactly what scores highest on the automation audit template.
The 24h / 3d / 7d / 14d cadence
Four touches over two weeks, then a clean stop. The spacing widens deliberately: early messages ride the momentum of the site visit, later ones respect that the customer is deciding on their own schedule.
| Touch | Timing | Job of the message |
|---|---|---|
| 1 | 24 hours after sending | Confirm it arrived and invite questions. Low pressure, high open rate. |
| 2 | Day 3 | Add something useful: scope clarification, availability, a relevant note about the job. |
| 3 | Day 7 | Ask the direct question. Are we going ahead, and what would help you decide? |
| 4 | Day 14 | Clean close-out. Say you will stop chasing, keep the door open, note if pricing expires. |
Touch four does more work than people expect. A message that explicitly stops the chasing often gets a reply from customers who felt awkward about the silence, and it protects the relationship for the next job. Do not extend past it into a fifth and sixth nudge on ordinary residential work; that is where follow-up becomes pestering.
Long-cycle work is the exception. Commercial jobs, insurance work, and anything waiting on a third party justify a slower tail: a check-in at day 30 and again at day 90, framed as a genuine status question rather than a sales push.
Copy-paste follow-up templates
Fill the braces from the quote record. Keep the amount and the job description as literal fields so nothing is ever paraphrased into something you did not quote.
Touch 1 - 24 hours (email)
Subject: Your {job_type} quote from {business}
Hi {first_name},
Sending a quick note to make sure the quote for
{job_description} landed with you - it came to {amount}.
If anything in there is unclear or you want it broken
down differently, just reply and I will sort it out.
{sender_name}
{business} - {phone}Touch 1 - 24 hours (SMS)
Hi {first_name}, {sender_name} from {business}. Just
checking the quote for {job_description} ({amount})
reached you okay. Any questions, reply here.Touch 2 - day 3 (email)
Subject: Re: Your {job_type} quote
Hi {first_name},
One thing worth knowing while you are deciding: we
currently have availability {availability_window}, and
that tends to fill up a couple of weeks out.
Happy to walk through the quote on a quick call if it
is easier than reading it. Either way, no rush.
{sender_name}Touch 3 - day 7 (email or SMS)
Hi {first_name},
Checking in on the {job_description} quote ({amount}).
Are you looking to go ahead, or has something changed?
If it is the price, the scope, or the timing, tell me
which and I will see what I can do. A no is completely
fine too - it just helps me plan the schedule.
{sender_name}Touch 4 - day 14 (email)
Subject: Closing this one out
Hi {first_name},
I will stop chasing you on the {job_description} quote -
I know it is not the only thing on your plate.
The quote of {amount} holds until {expiry_date}. If you
want to pick it up after that, message me and I will
re-check the numbers.
Thanks for thinking of us.
{sender_name}
{business} - {phone}Copy rules that matter more than the wording
Stop-on-reply logic (get this right first)
One badly-timed message undoes the whole system: a customer who replied "yes, book us in" and then receives "checking whether you are going ahead" concludes, correctly, that nobody read their message. Build the stop logic before you build the sending logic.
Treat all of these as a stop signal:
- An inbound email reply on the thread, matched by thread id or by the sender address against the quote contact.
- An inbound SMS from the customer's number, including a bare STOP.
- The quote status changing to accepted, declined, or expired in your CRM or quoting tool.
- An invoice, deposit, or job being created for that customer.
- A manual stop, because the estimator spoke to them on the phone. Give the team a one-click way to do this or they will not do it.
Two implementation details keep it honest. Check status immediately before each send, not only when a reply arrives, because a reply that lands two minutes before the scheduled send otherwise loses the race. And record which signal stopped the sequence, so your reporting can distinguish a win from a decline from a silent expiry.
The build in n8n or Make
The shape is identical in n8n and Make, and the only real design decision is state. Do not implement multi-day gaps with wait nodes; an instance restart, a redeploy, or a plan limit can strand or duplicate them. Keep the state in a table and sweep it on a schedule.
Define the quote-sent trigger
Pick one source of truth: your quoting tool's webhook, a CRM stage change, a Google Sheet row, or a label applied to the sent email. Capture quote id, first name, email, mobile, job description, amount, and quote expiry. If the amount and description are not in the trigger payload, the templates cannot be filled and the sequence will read generic.
Create the follow-up record
Write a row to a Google Sheet, Airtable, Baserow, or a Postgres table with the quote fields plus status = open, step = 0, and next_touch set 24 hours ahead. This record is the sequence. Anything you cannot see in that table is state you cannot debug at eight in the morning.
Build the stop listeners
An IMAP or Gmail trigger for inbound email, a Twilio or provider webhook for inbound SMS, and a CRM webhook for status changes. Each one finds the matching record and sets status = stopped with a reason and timestamp. Test all three with real messages before enabling any sends.
Run the hourly sweep
A Schedule trigger every hour reads all records where status = open and next_touch is in the past. For each one, re-read the status, check the quiet-hours guard, then route by step to the right template. An hourly sweep is precise enough for a cadence measured in days and is trivially resumable.
Send and advance
Send through your email node or SMS node, then update the record: increment step, set next_touch to the next gap (3 days, then 4, then 7), and log the send. After step four set status = closed_no_response. Never let a record loop back to step one.
Guard the edges
Hold sends to working hours in the customer's timezone, skip weekends unless your trade works them, and branch high-value quotes above your threshold into a task for a human instead of an automated message. Add an error workflow so a failed send alerts someone rather than silently ending the sequence.
Route replies to a person
When a stop listener fires on a reply, alert the estimator immediately with the quote id, amount, and message text. Speed of response after a reply matters far more than the elegance of the sequence that produced it.
Measure and tune one thing at a time
Report reply rate and win rate by touch number across a decent sample of quotes. Then change one variable, usually the day-seven message or the timing of touch one, and compare cohorts. Adding a fifth touch is almost never the change that helps.
Email, SMS, or both
Use the channel the customer used to contact you, and where you have both, split the work: the quote document and any detail by email, short nudges by text. Both channels must share one state record, so a text reply cancels the queued email and vice versa. Two independent sequences running on the same customer is worse than no automation at all.
If you add SMS in the US, the carrier registration rules apply here just as they do for missed call text-back: automated texts from a 10-digit number need A2P 10DLC brand and campaign registration, and the campaign description has to match what you actually send. The missed call text-back guide covers that registration in detail. Keep opt-out handling working on every automated text.
Where these sequences go wrong
- Sending touch one before the quote has actually been delivered, so the customer is asked about something they have not seen.
- Using multi-day wait nodes instead of a state table, then losing or duplicating sequences on a restart.
- Checking the stop condition only on reply, not immediately before each send.
- Running email and SMS as two sequences with separate state.
- Sending at 9pm or on a Sunday because the guard uses server time.
- Six or seven touches on a small residential quote.
- Generic copy with no job description or amount, which reads as a mailshot.
- Automating the follow-up on a five-figure job that deserved a phone call from the estimator.
FAQ
- How many times should I follow up on a quote?
- Four touches over about two weeks covers most residential and small commercial work without becoming a nuisance: a next-day check, a value-add on day three, a direct ask on day seven, and a clean close-out around day fourteen. Longer, higher-consideration jobs justify a slower fifth or sixth touch spaced over months, and anything shorter than four touches usually leaves winnable work on the table.
- Does following up on quotes actually win more work?
- The pattern is consistent enough across sales research and practitioner reporting to plan around: a meaningful share of deals close after several follow-up attempts rather than on first contact, and most quotes that are never followed up go quiet permanently. Be careful with the very precise percentages that circulate, since most trace back to vendor marketing rather than published research. Measure your own before-and-after win rate on a hundred quotes and you will have a number you can trust.
- Should follow-ups go by email or text?
- Match the channel the customer used to reach you, and for trades work text usually gets the fastest response while email carries the quote document. A practical split is quote and detail by email, short nudges by text, with the same stop-on-reply state shared across both so a text reply cancels the queued email.
- How do I stop the sequence when someone replies?
- Hold a status field on the follow-up record and set it to stopped on any inbound signal: an email reply, an inbound text, a quote marked accepted or declined, or an invoice raised. Check that status immediately before every send rather than only when the reply arrives, because the race between an incoming reply and a queued message is exactly where embarrassing sends happen.
- Can I use AI to write the follow-ups?
- Use it to personalise one line, not to write the message. A fixed template with the job description and amount slotted in reads more professional than a generated paragraph, and it never invents a discount, a timeline, or a detail of the job. If you do generate copy, keep the amount and scope as literal fields from the quote record.
- What about quotes over a certain value?
- Flag high-value quotes and have the automation prompt a human touch instead of sending. On a large job the follow-up should be a phone call from the person who walked the site, with the automation only handling the reminder to make that call. Automate the long tail and protect the top end.
Done for you
Want the follow-up sequence built and connected to your quoting tool?
We wire quote follow-up into the system you already use, including the stop-on-reply logic, the state table, and the reporting that tells you whether it is winning work. The audit comes first, and it is free.
The consult is free, and you keep whatever we build.
Keep building
The rest of the cluster
Jobber Quote Follow-Up Automation Past 2 Reminders
The documented two-reminder limit, and the four-touch sequence you build on top of Jobber's API.
Read the guideJobber + n8n Integration: The Full Build
OAuth against Jobber's GraphQL API from the HTTP Request node, webhook verification, and one complete workflow.
Read the guideMissed Call Text-Back with n8n (Free Build Guide)
Twilio trigger, business-hours guard, AI qualification, calendar booking, and the A2P 10DLC registration step.
Read the guideFree AI Automation Audit Template
Score every recurring task and rank the top three worth automating before you build anything.
