Automating quote tracking and follow-ups in a small business
Sending a quote does not finish the task. You need to know who is waiting for a reply, when to follow up and what should stop a reminder. This guide organises that work before choosing the tool that will handle it.
06 chapters
Trace a quote from the first message to the decision
Reconstruct a few recent cases
- Choose a few recent cases: an accepted quote, a rejected one and one that received no reply.
- Reconstruct the actual journey using messages, version changes and phone calls.
- You will see which information supports a decision and which disappears when someone is away.
Example: an installation business
Consider a fictional example: an installation business receives an enquiry through its website. Someone clarifies the need, prepares a quote and waits for a decision.
The follow-up date currently sits in their inbox; a colleague cannot tell whether the client has already called. The first need is to share that status before sending more messages.
Define the workflow’s boundaries
Record the start, end and exceptions of the workflow. The guide to turning a process into a tool explains this observation. An automatic rule cannot repair a status whose meaning nobody understands.
Give each quote a status and a next action
Separate status from next action
Separate “in preparation”, “sent”, “reply to process”, “accepted” and “closed”. A status should describe what is true now. The last contact date and next action describe what needs to happen. Mixing these two kinds of information makes lists harder to use.
Keep an owner and the right version
Each quote has an owner. A colleague can take over temporarily without becoming responsible for every case. Also keep the version sent: an acceptance must be matched to the right document, amount and scope.
Check your existing tools
First look for these features in the tools you already use. An existing or custom CRM may fit. The CRM, ERP and business tools comparison helps decide where the authoritative information should live.
- A stable identifier and the version of the quote sent.
- An owner visible to the relevant team.
- A dated last contact and next action.
- Separate statuses for waiting, replies, acceptance and closure.
Define a reminder and the conditions that stop it
Define the trigger and delay
A workable rule specifies its trigger, chosen delay, recipient and the conditions that prevent sending. For example: prepare a reminder for a sent quote with no recorded reply once its follow-up date is reached. That delay depends on your sales cycle; no universal recipe can determine it.
Start with an approved draft
Start by preparing a task or draft for the owner to approve. Automatic sending can follow later for stable cases. A phone conversation, rejection, new version or request to pause must interrupt the sequence.
Recheck the case before sending
Before each send, the system must recheck the case status. A reminder scheduled yesterday is no longer appropriate if the quote was accepted this morning. Set a limited number of reminders and a manual review for cases without a decision.
- Define the trigger, delay and recipient.
- A reply, rejection or acceptance stops the sequence.
- A new version replaces follow-up for the previous one.
- An owner can pause a reminder.
Plan for cases that need someone to take over
Match replies to the right case
A client may reply from another address, call instead of writing or send two identical messages. The team must be able to attach this information to the case and take control. If no reliable match is possible, create a task to check rather than another outgoing message.
Resume after a failure
An email service outage must not erase pending work. Keep the action, its outcome and the reason it failed. When resuming, distinguish a message that was never sent from one already handed to the sending service to limit duplicates.
Limit the records you retain
Logs support checks; they are not a reason to retain every conversation indefinitely. Define the information needed, who may consult it and its retention period. Avoid copying sensitive attachments into every technical log.
Each action should be explainable
The CNIL recommends proportionate logging. A log lets you examine an operation without unnecessarily opening all the underlying data.
- Action
What did the system do?
Keep the operation and the case it affected.
- Actor
Who triggered it?
Distinguish a person from an automatic process.
- Time
When did it happen?
Make it possible to correlate events during diagnosis.
Use AI only for a task that requires interpretation
Automate known rules
Creating a due date or stopping a reminder after acceptance does not require AI. A known rule is easier to test. The chatbot, automation and AI agent guide explains these different roles.
Check AI suggestions
A model can help draft a summary of an exchange or suggest a request category. The result must remain verifiable against the original message. Uncertainty about a client’s agreement must not turn a quote into an order on its own.
Separate drafting from permission to send
Drafting a message and sending it are separate permissions. Creating an invoice, applying a discount or changing a contract are others. Define these boundaries before connecting an AI tool to email and the CRM.
Test known cases before expanding the workflow
Replay difficult cases
- Replay the rule on test cases: a reply just before the reminder, a replaced quote, a rejection received by phone, an invalid address and a duplicate trigger.
- Compare the result with what the owner would do.
- The test must also check messages that are not sent.
Observe a full sales cycle
Start with part of the workflow and keep a way to pause the rule. After a complete sales cycle, look at quotes without a next action, time spent on follow-up and manual corrections. An email open rate alone does not prove that follow-up has improved.
Prepare a colleague to take over
Document how it works for another person: where to change a delay, how to close a case and who handles an alert. If the team still has to ask its creator every morning what the system did, the dependency has merely moved.
- Test both expected sends and prohibited sends.
- Check behaviour after a failure and recovery.
- Keep an accessible pause control.
- Train the colleague who will take over cases.
The remaining decisions
Do I need a different CRM to automate follow-ups?
Not necessarily. Check the statuses, tasks and connections available in your current tool. A change is justified when a specific gap prevents the workflow, not simply because another tool has more features.
How many days should I wait before following up?
The delay depends on the quote, its validity and the client’s decision cycle. Set a rule the team understands and adjust it after observation; there is no optimal delay for every small business.
Can I automate work without sending messages automatically?
Yes. Preparing a due date, task or shared draft can already reduce missed actions while leaving the person to decide whether to send it.
Can creating an invoice follow quote acceptance?
It can be part of the workflow if acceptance and invoicing rules are clearly defined. Preparation, approval and transmission of the invoice need separate handling, particularly where electronic invoicing applies.
Put the guide against a real project.
A few lines are enough: context, the main constraint, and the expected result.