Write the rule before the message
Define who enters
Require an identified, sent quote, the correct recipient, an assigned owner and an open status. Exclude unrelated contacts, stop requests and other workflows already sending the same reminder.
Agree the timing
Use the date agreed with the customer where one exists. Otherwise, have the team approve the interval, sending window, time zone and maximum attempts. There is no universal schedule that suits every quote.
Check again before each send
Recheck quote status, latest reply, any linked order and holds. If the system cannot verify those details, create a task for the owner rather than sending without them.
Record the step
Link the reminder to the quote reference and version. Record the outcome and prevent the same step from running twice.
Two short messages to adapt and approve
These are illustrative drafts for an existing sales conversation. Before activation, the owner approves the wording, recipient and schedule. Do not add discounts, availability or deadlines that have not been confirmed.
First reminder
Subject: Quote [reference] — anything we can clarify?
Hello [name], I’m following up on quote [reference], sent on [date]. Is there anything we can clarify to help you assess it? Thank you, [signature]
Ending the automatic reminders
Subject: Quote [reference] — how would you like to proceed?
Hello [name], is quote [reference] still of interest? If a later conversation would suit you better, let us know when. We’ll stop the automatic reminders for now; you can reply here whenever you’d like to pick this up. [signature]
The second message requires the workflow to stop. Ending reminders does not automatically mean the quote is lost.
Stopping rules and handoff to the owner
| Event | Expected action |
|---|---|
| Customer reply | Stop reminders and assign the conversation to its owner. |
| Order, acceptance or rejection recorded | Stop the workflow and record the actual outcome. |
| No-contact request or invalid address | Stop and update the exclusion or contact details. |
| Quote amended, expired or withdrawn | Pause. The owner decides whether a new proposal is needed. |
| Automated or out-of-office reply | Do not assume a commercial response. Apply a verified rule or request review. |
| Status unavailable or sending outcome uncertain | Pause and investigate. Check for a possible previous send before retrying. |
| Reminder limit reached | Stop the sequence and leave the next decision to the owner. |
Test what should prevent a message
Measure useful replies, correctly stopped cases and work handed back to the team. Email volume alone does not show that the process is working.
- A customer replies just before the reminder: the message does not send.
- An order arrives through another channel: its linked quote leaves the workflow.
- An out-of-office reply does not become quote acceptance.
- The CRM is unavailable: the case remains visible to its owner.
- A step runs again: it does not send an identical second message.
- The customer uses another language or time zone: wording and timing follow agreed preferences.
Check how your software stops a sequence
HubSpot, for example, documents unenrollment conditions involving replies, meetings, unsubscribes and bounces, along with exceptions for automated replies. Test the actual settings: a feature named “sequence” or “follow-up” is not enough.
References: HubSpot — Unenroll contacts from a sequence
Practical questions
How many days should we wait?
Start with the agreed date and the normal decision time for that proposal. Where no rule exists, agree one with the people who handle customers and review the results. This guide does not prescribe an interval for every industry.
Can we automate only the internal reminder?
Yes. Where statuses are unreliable or a conversation needs care, the workflow can prepare a task and draft for its owner, leaving the send decision to them.