To automate quote follow-up, connect the proposal you send with its sales status, the email, and the team’s next task. The system should check what has happened since sending before preparing each reminder: there may be a reply, a revision of the document, or a decision already made.
The starting point is the specific quote and its current version. That way, you can remind someone about a pending proposal without writing about an old price or interrupting a conversation that is already being handled by someone. This flow is designed for proposals requested by the client, with their contact person and channel already agreed.
What data follow-up needs
Gather this data in the CRM or in a shared record connected to the business tools:
- Proposal reference and sent version.
- Link to the current document, send date and validity.
- Client, contact person and sales owner.
- Proposal status and date of the latest change.
- Latest relevant conversation and agreed next step.
- Follow-ups completed and reason for any pause.
If the quote software and the CRM are separate, decide which one is the source of truth for each piece of data. The amount and validity may come from the tool that creates the proposal; the next call, from the CRM.
Check how updates move between both systems. If an acceptance takes time to appear, a scheduled reminder could go out during that gap. The connection needs a rule to delay sending when it cannot verify the current status.
Define what happens in each status
A sent proposal can be waiting to be read, under review, or waiting for an internal decision. It is worth distinguishing these situations to prepare the next step:
| Registered situation | Action you can automate |
|---|---|
| Sent and waiting for a reply | Prepare a reminder or a task on the agreed date. |
| The client raises a question | Pause reminders and assign the reply to the salesperson. |
| Another version is being prepared | Stop follow-up on the previous document. |
| The client asks to pick it up later | Save the date and schedule a review for then. |
| Accepted or rejected | Close follow-up for that proposal and log the result. |
| Expired or with conflicting data | Leave a task for the owner to review it. |
The status needs proof: a client action, a tool update, or a team check. A comment like “seems interested” may work as context; to confirm an acceptance, you need the process your company has defined.
How to set up the automatic flow
You can start by creating internal tasks and drafts. Once the team has approved the messages and conditions, look at which ones can be sent automatically.
The flow would be:
- Confirm the proposal was sent. Save which version went out, to whom and from which account.
- Assign the next step. A review date, the owner and the channel.
- Check for updates when that date arrives. Replies, status, version and pauses.
- Prepare the right action. Reminder, call or proposal review.
- Log the result. Distinguish what is pending, what was sent and what failed.
Not every CRM function watches for the same signals. For example, Pipedrive documents reply conditions on a previously sent email within the automation, after a waiting step. Do not assume that check covers any message sent from outside the flow.
Pipedrive’s automatic email sending documentation also requires email sync to be set up and lets you choose the sender. Before activating it, check which account the message will be sent from, where replies will be received and which features your subscription includes.
The same review helps you decide whether the CRM features are enough or whether you need to connect the quote software through a custom integration.
Example: the client asks to change the proposal
A company sends a quote to renew a client’s website. They agree to review the proposal on Thursday. On Wednesday, the client replies that they want to add a catalogue.
This is an illustrative example to test the system, not a result from a Digency client. The expected behaviour would be:
- The reply pauses the reminder scheduled for Thursday.
- The owner receives a task with the request to expand the scope.
- The first version remains linked to the history and is marked as replaced when the new one is sent.
- The next follow-up uses the updated document and the new agreed date.
If the reply comes by phone, the salesperson should be able to log the pause from the proposal record. If only the PDF in a folder changes, the system needs to know which version replaces which. Renaming a file does not guarantee pending messages will be updated.
Before reactivating follow-up, check that the draft uses the current link and conditions. The new version must keep the conversation history.
When to stop reminders
Receiving a reply should lead to team review. You should also consider an acceptance, a rejection, a request to stop contact, or a manual pause.
In HubSpot sequences, exit rules for replies and meetings are configurable. The documentation also notes exceptions in detecting out-of-office automatic replies. It is worth testing the real setup with the inboxes you will use.
Two checks are especially useful:
Conversations on another channel. A call or a message to a colleague can change the situation without reaching the connected inbox. Give the team a control to pause and note the reason.
Several proposals for the same contact. A reply may only refer to one of them. Keep the reference and, if it is not clear, ask for review before continuing with the others.
Avoid restarting follow-up just because someone edits the record. Resuming should be an identifiable decision, with a date and a next step.
What message to prepare and where AI helps
The reminder should make the proposal easy to recognise and reply to. A draft could be:
Hi, Marta. I’m following up on the proposal to renew the website that we agreed to review this week. Is there any question about the scope or timing that we should solve before moving forward? You can reply to this same email.
Adapt the text to what was agreed. If there is a new version, check the link; if the client asked to wait, respect that date. Urgency, discounts and availability should come from real conditions approved by the team.
AI can help summarise a long conversation or prepare a draft using the available context. Keep the original message accessible and require review when there is any doubtful interpretation. To schedule a task by date or stop follow-up when a status changes, defined rules are enough.
What to test before scaling the automation
Run a test with controlled inboxes: proposal with no reply, reply before the reminder, version change, pause by call, rejection and connection failure. Also repeat receipt of the same send event: the result should keep a single follow-up for that proposal.
Review what the client sees and what remains on the record. When a send fails, the team should be able to tell a message that was not sent from one whose result is still unknown, before trying again.
To assess the pilot, count pending proposals with no next action, replies that require intervention, and time spent on follow-up, including review. If you compare sales, use comparable periods and proposal types; do not automatically attribute any change to automation.
If requests come first from your website, you can review how to connect a form to the CRM. At Digency, we build custom automations to connect these stages. Tell us where you prepare quotes and how you follow them up and we’ll define a first flow with your tools.
Cover: illustration generated with AI.
