How to follow up when a prospect says "not now"

Save what the prospect actually said before choosing a follow-up date. “Try me in November,” “not a priority” and “we decided against it” do not belong in the same campaign.

A reply gives you more information than silence. It does not necessarily give you permission to keep sending. The useful next step may be a later conversation, an internal review, or closing the record without another message.

What sellers are trying to keep track of

In a June 2025 sales discussion, a B2B SaaS seller said a prospect wanted to evaluate in a few months, but not now. Comments split between putting a reminder in the calendar and sending useful material in the meantime. One commenter specifically said to establish whether the prospect wanted drip content before the pause.

That disagreement is the problem: wanting to evaluate later does not establish a preference for messages in between. The discussion supplies opinions, not a tested follow-up interval or evidence that frequent contact wins.

A different small-business discussion in August 2026 asks how to preserve lead history, dates and next steps when someone is interested but not ready. A CRM can store those details, but so can a small worksheet. Neither should turn a missing date into a contact schedule.

Separate four kinds of reply

Agreed later timing. “Try me in November” is a request about timing. Keep November as the stated window, not an invented November 1 appointment. If an exact date matters, settle it in the conversation rather than silently choosing one. Do not fill the waiting period with a monthly sequence unless the prospect separately asked for it.

Vague “not now.” “This isn’t a priority” gives you no return date. Acknowledge it and wait. Do not label it “follow up in 30 days” because your tracking system requires a date. You can set a date to review your own notes without scheduling a message.

Silence. No reply is not an agreement to talk later. It also does not tell you whether the person read the message. That is a separate decision, covered in our no-response follow-up guide, not a reason to put someone into this workflow.

A decision against the offer or a request to stop. Record it and stop pursuing that offer. An explicit do-not-contact request needs a durable stop marker so an old queue or a new campaign does not revive the contact. Do not reinterpret “no” as a timing objection.

If the reply instead asks for information, answer that request. “Send the price, but we’re not looking this quarter” asks for the price and sets a timing limit. It does not ask for a meeting.

Copy this into the record

Use the original thread as the source, not a memory of the conversation. Separate the prospect’s words from your interpretation.

Person and original thread/source:
Exact reply and date received:
Reason for waiting, in their words (unknown if absent):
Agreed timing or window (none if absent):
Contact preference and any stop request:
What must be rechecked before contact:
Next internal review (not a scheduled message):
Decision: CONTACT / WAIT / STOP
Reason and permitted next action:

A review can end with “keep waiting.” A blank contact date is more accurate than a made-up agreement. If software requires a task, call it “review record,” not “send follow-up.”

A manual check of four fictional records

These people, replies and situations are invented teaching examples. We filled and checked the records manually against the words below. No messages were sent and no sales results were measured.

1. A month, not an appointment

Person/source: Lina; fictional original conversation A
Exact reply: "Try me in November, after our budget review."
Reason: budget review
Agreed timing: November; no day or time agreed
Contact preference: later contact requested; no interim updates requested
Recheck: latest thread, budget-review status if known, role and company
Next internal review: before preparing a November follow-up;
                      this is not an outbound appointment
Decision: WAIT now; review before contact in the requested window

The check: November is supported. November 1, a booked call and weekly updates are not. When the window arrives, read the thread again before preparing anything.

2. No priority and no date

Person/source: Theo; fictional original conversation B
Exact reply: "Not a priority for us right now."
Reason: not a current priority; underlying cause unknown
Agreed timing: none
Contact preference: no future contact or content schedule requested
Recheck: original reply and any later incoming message
Next internal review: optional housekeeping review; no contact scheduled
Decision: WAIT; acknowledge the reply, then leave it there

The check: the record does not invent a budget freeze or a monthly campaign. A relevant public announcement later would still need review against this conversation; it would not automatically authorize a message.

3. A clear stop

Person/source: Amira; fictional original conversation C
Exact reply: "We decided against this. Please don't contact me again."
Reason: decided against the offer; no further explanation supplied
Agreed timing: none
Contact preference: do not contact
Recheck: stop marker is retained wherever outbound work is prepared
Next internal review: record hygiene only, not sales reactivation
Decision: STOP; cancel pending outreach and retain the stop instruction

The check: no “try another channel” or “ask again next quarter.” A new case study does not erase the request.

4. The old contact changed jobs

Person/source: Ben; fictional original conversation D
Exact reply: "Try me after the rollout."
Reason: rollout; completion date not supplied
Agreed timing: after that event, not a calendar date
Contact preference: later contact about the original work
Recheck: latest thread and whether Ben still owns that work
New fact: Ben has moved to a different company
Next internal review: resolve stale ownership before preparing contact
Decision: WAIT; do not reuse the old pitch at the new employer

The check: an old timing request does not prove the same need exists at a new company. Nor does it supply an introduction to Ben’s replacement.

Rebuild context before a later message

A May 2026 discussion about re-engaging after six months raises a narrower issue: the recipient may not remember the original exchange, and their priorities may have changed. It does not establish a six-month cadence.

Before writing, recover the original topic and timing request, check for newer replies, and verify that the person and work still match. If contact is still appropriate, give enough context that they do not have to reconstruct the thread. Do not say their budget is approved, the rollout is finished or the problem persists unless you know it.

Dollar Outreach queues LinkedIn steps and prefills drafts; you still click send. A queued step is not a reason to contact someone. Leave it unsent when the record says wait, and remove it when the record says stop.

Checked October 15, 2026: three separate Reddit discussions, the linked Dollar Outreach guides and the product page. The discussions are self-reported situations and advice, not controlled evidence of response rates. The four record checks are manual analysis of fictional inputs, not customer outcomes or a tested sending schedule.