You send a proposal or a question, and the client goes quiet. You want to follow up without forgetting—or sending a reminder after they have already replied to a teammate. Set a reminder and a simple rule for checking the latest conversation before sending another message.
Chill&AutomateUpdated September 27, 2026
untangle → move on
✓
When this guide helps
Use this guide if any of these situations sound familiar:
Proposals remain unanswered, and nobody goes back to them.
You and a teammate both follow up on the same proposal.
You want to simplify follow-ups, but clients sometimes reply by phone or ask for more time.
Decide who will follow up and when to review the conversation. Use the editable message and learn what to do after a reply, rejection, or request to postpone. Start with a reminder for a person; automatic sending needs additional safeguards.
The approach
Start with a reminder for the person handling the conversation. Immediately before replying, they open the current thread, check for a response and then send. Three days passing is not, by itself, a reason to send automatically.
Check off steps as you finish them. Progress stays in this browser; reset it below when you start again.
A short proposal follow-up
Replace bracketed details and adapt the wording to the actual agreement. Use the button to select all text, then copy with your keyboard shortcut or browser menu.
Separate reminders from sending
Keep an owner, latest inbound and outbound message, next review date and stop reason against the inquiry. A reminder means check and decide, rather than send regardless. If the owner is away, assign a specific backup instead of giving two people the same sending task.
A reply, decline, request to stop contact or manual takeover ends the old plan. Set the next date around the new situation. Do not automatically reuse inquiry rules for marketing campaigns or invoice reminders; those serve different purposes and conditions.
A message that moves the decision forward
Bring back one unresolved question and make it easy to answer. For example: “Following up on the website scope: should we start with the catalog or the booking flow? Which matters more right now? If your timeline has shifted, just let me know.” Adapt this to the actual conversation without inventing urgency.
Automation must reread the current state
A scheduled step may hold stale data. Reread the conversation and stop state before sending, and keep one sending queue. If the response to a send request is lost, inspect sent messages first; blindly retrying can deliver the same message twice.
HubSpot documents reply-based sequence unenrollment, alongside exceptions and settings. Check your sequence against an email reply, an answer through another channel and reenrollment. A documented rule does not mean any combination of tools captures every stop signal.
Filled example
Fictional example to explain the process, not a real client record.
Example: a review is due Thursday at 10:00. At 9:58 the client replies asking for another week. The owner opens the thread, cancels the old reminder and records the new agreement. A colleague opening the reminder sees the stopped state and sends nothing.
Conversation and owner
JOB-01 thread; Alex replies, with Sam as backup only after a handoff.
Latest inbound / outbound message
Proposal sent Monday, September 28; client asks Thursday, October 1 at 9:58 a.m. to wait until Tuesday.
Review time, timezone and backup
Original review: Thursday 10:00 a.m., America/New_York. New review: Tuesday, October 6 at 10:00 a.m. Sam can see the change.
State: waiting / review / stopped / sent
Stopped — client replied. Tuesday’s review is a new task, not a scheduled automatic send.
Stop reason or sent-message reference
Reason: postponement requested in the current thread. No new follow-up was sent on Thursday.
Open question and message draft
Open question: does the proposed scope fit? Draft if no answer has arrived by Tuesday: “Hello, following up as agreed on the JOB-01 proposal. Does the scope work for you, or would you like any changes?” Recheck the thread before using it.
Take the worksheet with you
A follow-up rule, review record and editable reminder message.
Expand the blank template below, select the text, and paste it into your document. Replace the brackets with your own information, using the filled example above for guidance. Keep a separate copy for each job. You can also download the text. No sign-up required.
Start with a reminder for a person who reads the current conversation before sending. Use Tasks in Gmail or an activity in your existing CRM. You get a follow-up date without an automatic message continuing after a rejection or payment.
Prices and terms checked September 27, 2026, in the currency shown by the vendor. Quotes may vary by country; confirm your currency, tax and commitment before buying. Example budgets exclude any additional tax.
Budget for this job
Do not buy a CRM just for a reminder. Existing email plus a task adds no new subscription. A paid sequence is worth considering only for recurring volume with defined stopping rules; review time remains a cost.
Keep the latest conversation, the person following up, and the review date with the proposal. If the client asks for more time, record the new agreement there.
What can go wrong
The client may reply by phone or to another teammate. Check the project notes before following up; silence in one email thread does not necessarily mean there was no answer.
✓
How to check it works
When a follow-up is postponed, cancel the old reminder and make the new date visible to the backup handler. Anyone opening the old task should know not to send it.
Where to start today
Choose one proposal awaiting a reply and set a review date. Adapt the message template after reading the latest conversation.