A useful quote follow-up workflow reminds the right person at the right time and stops when the situation changes. It shouldn't keep chasing a customer who has replied, accepted a newer quote or asked you to stop.
Start with internal follow-up tasks if your team doesn't yet keep quote statuses current. Automatic emails depend on information that the business must first be able to trust.
Follow the quote, not just the contact
A customer might have several quotes open at once. They may accept one, decline another and ask a question about a third. A contact-level “followed up” flag can't describe that properly.
Give each quote its own reference, version, owner, sent date and current status. Define which version remains open when a price or scope changes. A reminder for a superseded quote can cause confusion even if it reaches the correct customer.
Use statuses that change what happens next, such as waiting for a reply, question received, accepted, declined, expired and paused. Staff need a quick way to update them after a phone call as well as an email.
Put the stop conditions before the message
Write the rules in ordinary language before setting delays:
- don't follow up a draft or a quote that was never sent successfully.
- stop when the quote is accepted, declined or replaced.
- pause when a question needs a person's answer.
- stop the automated route when the recipient asks you to stop.
- send an overdue item to its owner after the agreed final reminder.
Don't assume that a workflow automatically removes records whose circumstances have changed. For example, HubSpot documents configurable unenrolment triggers. The rules and behaviour need checking for the particular workflow and subscription.
Whatever platform you use, recheck eligibility immediately before sending. A record can change while it waits in a delay. Also decide how a cancellation affects messages already handed to an email service. Stopping the workflow can't reliably recall a message that's already been sent.
A fictional follow-up sequence
Imagine a maintenance business sends a quote for a repair. This example illustrates a process, not a recommended number of emails for every business.
The first step creates a task for the quote owner after the agreed review interval. The task shows the quote reference, current status, last conversation and any promised response date. The owner can contact the customer, postpone the task with a reason or close the quote.
Once that works consistently, the business might allow a short reminder for eligible quotes. Its purpose is to ask whether the customer needs clarification. It uses the agreed quote details and doesn't add a new discount, change the expiry date or pretend a person has individually written it.
If the customer replies that they're waiting for a landlord, the owner pauses the routine and records the next agreed contact date. The system shouldn't send another “have you seen our quote?” message the following morning.
Keep a quote conversation separate from a marketing campaign
Following up a specific request and adding someone to ongoing promotions are different decisions. Don't use the quote workflow to enrol people into unrelated sales messages or work around an unsubscribe request.
Decide what communications are appropriate for your circumstances and check the applicable marketing and privacy requirements separately. This process guide doesn't establish permission to send a particular message.
Give staff a visible hold control. A complicated exception should be handled by the owner, rather than forced through the nearest available template.
Test the moment just before a reminder
Use test recipients you control and a separate test workflow. Try accepting, replacing and pausing a quote while it is waiting. Add a reply through the channel your business actually uses and check whether the stop condition is detected or needs a staff update.
Repeat the original “quote sent” event. It shouldn't start a second follow-up routine for the same quote version. Check what happens when the owner is away and when the email service rejects a message.
Measure unanswered quotes with no next action, duplicated reminders and replies that arrived after an unnecessary chase. Review a sample of closed cases before increasing automation. A smaller sequence that respects the current conversation is more useful than an elaborate sequence built on stale statuses.