Refer to the actual conversation, offer one useful next step and make it easy to pause or decline. Keep the contact plan tied to the customer’s situation.
Review the decision before writing the message
Open the proposal and the last conversation together. What did the customer need to decide? Who was expected to review it? Was a next contact date actually agreed, or did you assume one? Write those details down before choosing a template.
Salesforce’s introductory sales-process guidance treats a proposal as part of a broader process and discusses summarizing conversations and next steps. It is vendor guidance, not evidence of a universal follow-up schedule or of results for this site. Read the original lesson.
The workflow here is an editorial recommendation for a small service business. It does not promise replies or closed deals. Its purpose is to make each contact relevant and to distinguish a real decision from a growing list of unanswered reminders.
Choose a reason that helps the customer
| Known situation | Useful purpose | Avoid assuming |
|---|---|---|
| A review date was agreed | Ask about the unresolved decision and offer the agreed next step. | That no reply means rejection or acceptance. |
| An input is missing | Name the input and explain which part of the proposal depends on it. | That the customer knows your internal dependency. |
| Scope is unclear | Clarify a choice or offer a short review of specific questions. | That a discount solves a scope mismatch. |
| The customer has paused the project | Record the pause and any future contact they request. | That you should keep the same reminder sequence running. |
One message should usually have one main decision. If you need to change the scope, availability and price, explain that a revised proposal is needed instead of burying three changes inside a friendly reminder.
Three original messages to adapt
Fictional examples: the following drafts describe an existing proposal conversation. Replace the details with facts; the names, project and dates are not customer records.
1. Return to an agreed review
Subject: Next step for the product-page project
Hi Alex,
You planned to review the proposal with your colleague this week.
Is the remaining question the monthly scope or the handover process?
I can clarify either in writing, or we can arrange a short review.
If the timing has changed, let me know and I will update the plan.2. Explain a missing dependency
Hi Alex,
The proposed schedule depends on receiving the product information.
Would a checklist of the required fields help your team prepare it?
Once we know when that information is available, I can confirm
whether the proposed delivery window still works.3. Offer a clear pause
Hi Alex,
I have not heard whether the project is still a priority.
Would you prefer to continue reviewing it, revisit it later,
or close this conversation for now?
If it is paused, I will stop the reminders. We can discuss a new
scope and schedule if you decide to return to it.These drafts do not create a real deadline or reserve capacity. Mention a proposal expiry or limited availability only when it is accurate and consistent with what you offered. Do not add a false “final chance” to make the message sound urgent.
Let the conversation determine the contact plan
Start with an agreed review date when there is one. If none exists, choose a reasonable next contact based on the decision process you know, explain your purpose and ask what timing would help. This guide does not prescribe a universal number of days or messages.
Record the response as a distinct state: clarification needed, decision pending, paused, declined or accepted. A reply asking about a detail is not an acceptance. If the customer asks you to stop, respect that request and update the contact plan.
When a person returns after the original proposal is no longer current, recheck scope, dependencies and availability. The old document is context, not automatic confirmation that you can still offer the same conditions. Keeping those states clear also helps a small team avoid conflicting messages.
Use repeated questions to improve the proposal
If several conversations stall around the same issue, inspect the document. Does it explain what is included, what the customer must supply, who approves the work and how a change is handled? A better follow-up cannot substitute for missing scope.
Our brand-positioning framework can help clarify the intended customer and promise. The guide to trust and conversions explains why an observed contact and a business outcome need separate evidence. Neither a message sent nor a proposal viewed proves a sale.
Use the Content Brief Builder to plan an explanation for one recurring customer question. It can structure your answer, sources and unknowns; it is not an email sender or a sales automation tool. If the question belongs on your website, link the published explanation in a relevant conversation rather than pasting an unrelated tool list.
Keep a small follow-up log
Download the follow-up worksheet
Record the proposal version, unresolved decision, last agreed step, next contact reason and current state. Keep customer details in your own appropriate workspace, not in a public copy of an example. The blank worksheet contains no client information.
At the next review, ask whether each contact had a useful purpose and whether the document answered the customer’s actual question. Our customer-question content guide shows how those recurring questions can improve your public explanations. The goal is a clearer conversation, including a clear no when the offer does not fit.
Follow the evidence.
References checked Oct 16, 2026. Examples and workflow recommendations are editorial illustrations, not measured results. Provider guidance may change. Our editorial standards.
