RoutineSmithQuote follow-up automation for a small business.
Give every open estimate one state, one owner and one deliberate next action—then stop when new evidence changes the route.
Check the next safe action before anyone follows up.
Use only statuses here. Do not enter a name, email, quote value, message or customer detail. This tool does not connect to your inbox or send anything.
Pre-send controls
Working control check only; human approval is still required.
QUOTE FOLLOW-UP — CONTROL CHECK Current state: Select a state A person approved and sent the current quote version: Not checked The canonical quote record exists in the approved system: Not checked One accountable owner is recorded externally: Not checked A next-action date is recorded externally: Not checked The latest inbound message was checked: Not checked The last outbound message was checked: Not checked Other approved queues and channels were checked: Not checked Another follow-up may already exist in any approved channel: Not checked A new customer reply or question is present: Not checked Scope, price, validity or decision context may have changed: Not checked Decline, opt-out, do-not-contact or other stop signal is present: Not checked Next controlled action: Select the current quote state Boundary: A person must approve any message, timing, channel and commercial statement.
Keep real owner, quote ID, customer and next-action details exclusively in your approved operating system.
Use the least automated option that keeps every quote visible.
Automation can mean a shared tracker, a reminder or autonomous sending. These are different risk levels, not interchangeable features.
| Level | Best fit | Who acts | Boundary |
|---|---|---|---|
| Manual tracker | Low volume or unclear process | A person reviews the queue, checks replies, drafts and sends | Best starting point while states and stop rules are being defined |
| Reminder-assisted | Stable states but human judgment still matters | The system surfaces due reviews; a person approves the action | Reduces forgotten work without giving software sending authority |
| Automatic sending | Only after controls work on representative cases | The system sends on schedule and stops on verified signals | Requires reliable reply detection, deduplication, consent controls and an audit trail |
Make the next action observable instead of leaving it in memory.
Use a small lifecycle model. Keep commercial outcome separate from urgency and never infer acceptance from silence.
| State | Meaning | Controlled action |
|---|---|---|
| SENT | Quote issued; receipt or response not yet confirmed | Record owner and a deliberate next-action point |
| WAITING | A response or agreed decision point is pending | Do not chase before the recorded review point |
| FOLLOW-UP DUE | The review point has arrived and no newer response is visible | Check every approved channel before drafting |
| REPLIED | The customer answered, questioned or changed context | Pause automation and route the response to a person |
| WON / LOST | A human-confirmed commercial outcome exists | Record the outcome and stop the follow-up sequence |
| STOPPED | Opt-out, do-not-contact, expiry or another stop rule applies | No further message; retain the reason appropriately |
Check for newer evidence before preparing a follow-up.
- Confirm a person approved and sent the current quote version, and that its canonical record exists.
- Confirm the quote ID, version, scope and validity period in the system of record.
- Check the latest inbound message, the last outbound message and every other approved queue or channel for replies or duplicate pursuit.
- Confirm one accountable owner; a shared mailbox or team name is not ownership.
- Record a next-action date or close the opportunity deliberately.
- Stop on decline, opt-out, do-not-contact, conflicting facts, expired terms or uncertain identity.
Automate preparation and reminders, not commercial judgment.
Summarize explicitly recorded context, identify a due review, flag missing controls and draft a message for review.
Whether to contact, which channel and timing to use, what commercial claims remain valid, how to answer objections and whether to change price, scope or terms.
Document roles, escalation and human oversight before connecting AI. The NIST AI Risk Management Framework provides a general risk-management reference; it does not approve a specific workflow.
Five quote follow-up email templates for the states that recur.
Replace every bracketed field, verify the current record and let the named owner approve the message. These examples are starting points—not permission to contact a customer or change commercial terms.
Delivery check
Subject: Did quote [REFERENCE] reach you?
Hi [NAME], I sent quote [REFERENCE] for [PROJECT] on [DATE] and wanted to confirm that it reached you. If it did not, I can resend the current version. If you have a question, reply here and [OWNER] will review it.
First useful check-in
Subject: Any questions about quote [REFERENCE]?
Hi [NAME], I am checking whether you have a question about quote [REFERENCE] for [PROJECT]. The current scope and price remain in the written quote. Would it help to review the scope, timing or next step with [OWNER]?
Revision acknowledged
Subject: We recorded your question about quote [REFERENCE]
Hi [NAME], we recorded your request concerning [NEUTRAL SUMMARY]. [OWNER] will review it against the current quote. The original scope, price and timing remain unchanged until a revised quote is issued.
Genuine expiry reminder
Subject: Quote [REFERENCE] review before [EXPIRY DATE]
Hi [NAME], quote [REFERENCE] shows an expiry date of [EXPIRY DATE]. If you want [OWNER] to review the current scope, price or availability before then, reply here. This message does not extend or change the written terms.
Close the loop
Subject: Should we close quote [REFERENCE] for now?
Hi [NAME], unless you would like us to keep reviewing quote [REFERENCE], we will close its follow-up for now. If the project becomes active later, contact [OWNED ROUTE] and [OWNER] can confirm current scope, pricing and availability.
Northstar Field Services reaches a follow-up date.
The queue marks quote Q-208 as FOLLOW-UP DUE. Maya remains the recorded owner.
The system finds a new customer question in the canonical thread and changes the route to REPLIED.
AI summarizes the question but does not send. Maya checks the current quote version and asks the estimator to review changed scope.
A qualified person approves a revised response. The original generic reminder is never sent.
Start with visible controls before buying more software.
Microsoft documents flags and reminders for tracking replies to sent messages, while Google documents snoozing and task creation. These features can support a low-volume pilot, but they do not create shared ownership, cross-channel deduplication or a reliable audit trail by themselves.
Test visibility and safety before testing persuasion.
Use synthetic or appropriately protected records. Compare a representative baseline and record exceptions rather than assuming a cadence will improve sales.
- GO: due work is more visible and stop signals are contained without unacceptable review burden.
- REVISE: ownership improves but states, sources or stop conditions remain ambiguous.
- STOP: duplicate contact, unsafe claims or missed replies cannot be reliably prevented.
Make the message useful, respectful and jurisdiction-aware.
Do not treat a transactional quote as unlimited permission for marketing. Make declining or asking for a change easy, honor stop signals and check the law that applies to the recipient, channel and business. This guide is operational information, not legal advice. The UK Information Commissioner’s Office guidance illustrates why electronic marketing rules depend on purpose, relationship and consent.
Practical questions before automating follow-up.
What is quote follow-up automation?
It is a workflow that records when a quote was sent, brings it back for review at a deliberate time and prepares or sends an appropriate next step. A safe first version reminds a named person to check replies, scope, consent and stop conditions before any message is sent.
When should a small team follow up on a quote?
At a deliberately recorded review point, after checking the canonical thread and any approved channels for a newer response. There is no universal timing rule: urgency, quote validity, customer expectation, sector and local law can change the appropriate action.
How many follow-ups should be automated?
This guide does not prescribe a universal number. Start with reminders and human-approved drafts, then stop on a reply, decline, opt-out, changed scope, expired quote, uncertainty or the end of the documented policy.
Can AI send the message automatically?
Not in this starter workflow. AI may assemble known context and draft a useful response, but a person checks recipient, channel, current thread, timing, claims and commercial terms before sending.
What should be measured?
Track quotes with an owner and next action, overdue reviews, responses, revisions, won/lost/stopped outcomes, duplicate contacts, corrections and human review effort. Message count alone is not a business outcome.
Put every open quote, owner and next review in one visible tracker.
Use the free browser-local template with fictional or appropriately protected data. RoutineSmith does not receive the quote details you type into it.
Open the free quote follow-up tracker