How to Handle Not Now Replies in Cold Email (2026)
Summarize this page withChatGPTClaudePerplexity
On this page
Why trust this playbook?
This playbook is written by the Master Inbox team and reviewed by our founder, Abdul Mukati. We build a reply inbox for outbound teams and agencies, so we see how "not now" replies are labeled, scheduled and brought back across many mailboxes and clients. Master Inbox is one of the tools mentioned, and we say where it fits in its own section. We do not quote conversion statistics, because "not now" outcomes vary by market, offer and timing. Where we suggest a gap between touches, it is a recommendation to adapt, not a benchmark.
What a "not now" reply is, and why it needs its own playbook
A "not now" reply says the prospect might be interested, but the timing is wrong. Typical wording: "Not a priority this quarter", "Reach out in the new year", "We just signed with someone, check back later", "Busy right now". In a reply labeling setup it usually gets its own label, such as Not Now or Not Right Now.
It needs its own playbook because it is the reply type most often lost. A positive reply gets attention. A clear no gets closed. A "not now" gets a polite acknowledgment and then drifts, because nobody owns the date. Three months later the prospect has forgotten you, and the opportunity has to be rebuilt from scratch.
It also differs from an out-of-office message. An away message is automatic and carries a return date; see out-of-office replies in cold email. A "not now" is a person making a decision about timing.
The three kinds of "not now"
| Kind | Example wording | What you know | Follow-up rule |
|---|---|---|---|
| Dated | "Come back in January." | A date | Schedule a touch a few days before the date they named |
| Event-based | "After we finish the migration." | A trigger, not a date | Ask roughly when it ends, then schedule around that and watch for the event |
| Vague | "Maybe later." "Not right now." | Nothing specific | Ask one gentle question to get a date, or pick a default gap and tell them |
How to handle a not now reply in 5 steps
1. Label it and stop the sequence
Label the reply so it leaves the active queue and shows up in the right report. Pause the remaining steps of the sequence for that prospect, on email and on LinkedIn, so a scheduled touch does not arrive the next morning. If your sequencer keeps sending, the prospect will feel ignored. In Master Inbox a workflow can stop the sequence the moment the Not Right Now label is applied.
2. Thank them and keep the reply short
Acknowledge the answer in one line. Do not argue and do not try to convert a "not now" into a call with a long pitch. If you push, you turn a soft delay into a firm no. If the sender is warm, one short line about why you would reach back is enough.
3. Capture the date and the reason
Write two things on the record: when you will come back, and why they said not now (budget, timing, a project, a recent purchase). The reason tells you what to say later. The date tells your system when. A dated reply is easy. For an event-based or vague one, ask:
- "When does that usually wrap up, roughly?"
- "Would it be more useful if I checked back next quarter?"
One question is enough. If they do not answer, use your default gap and say so in your reply, so the follow-up is expected and not a surprise.
4. Schedule the follow-up before you close the thread
This is the step that decides whether the playbook works. Set a reminder, snooze the thread to the date, or move the lead into a time-based nurture list. The follow-up should exist as a dated item that a person or a workflow will see, not as a good intention. Add the reason and date to the CRM record so it survives a change of owner. This is called CRM sync, and it is what lets a RevOps lead see the future pipeline.
5. Re-open with something new
When the date arrives, write a fresh message. Mention what they said ("You mentioned January"), then give one reason to talk now: a new result, a relevant change in their market, a short idea, or a simple check on whether the timing has changed. Keep it short and give an easy way to answer. If they reply with interest, switch to the interested reply playbook.
Example replies
Example 1: a dated "not now"
Illustrative example, not a real customer message.
Prospect: Thanks, but budgets are locked until the new year. Reach out in January.
Your reply: Understood, and thanks for telling me. I will get back to you in the first half of January. If it helps, I can send a short summary now so you have it for planning. No reply needed.
Why it works: it confirms the date, makes no demand and offers a useful extra.
Example 2: an event-based "not now"
Illustrative example, not a real customer message.
Prospect: We are in the middle of a platform change. Maybe after that.
Your reply: That makes sense. Roughly when do you expect the change to wrap up? I will check back a couple of weeks after, so it does not land in the middle of it.
Why it works: one question gets a date, and it shows respect for their workload.
Example 3: a vague "not now" and the re-open message
Illustrative example, not a real customer message.
Prospect: Not right now, maybe later.
Your reply: No problem. I will check back in about three months in case things change. If a different time suits you better, tell me and I will use that.
Re-open, three months later: Hi [name], you said it was not the right time back in [month]. A quick check: has anything changed on your side? Since then we have [one relevant new thing]. If it is still not a priority, I will leave you be.
Why it works: a default gap is stated and easy to change, and the re-open message references the earlier answer.
Decision rules
| If the reply says | Then |
|---|---|
| Names a month or date | Schedule a touch shortly before it. Log the date on the record. |
| Names an event or project | Ask for a rough end date. Schedule after it and add a note about the event. |
| Says "maybe later" and nothing else | Reply once with a default gap. Do not ask more than one question. |
| Says "not now" but asks a question | Answer the question. It may be an interested reply in disguise. |
| Says "not now" and names a reason such as price or a competitor | Treat the reason with the objection playbook, then schedule the follow-up. |
| Says "not now" and says who handles it | Follow the wrong person playbook for the referral. |
| Says "remove me" or "stop emailing" | Treat it as an unsubscribe. See how to handle unsubscribe replies. |
Common mistakes
- No date on the record. A "not now" without a follow-up date is a quiet "no".
- Replying with a long pitch. The prospect told you the timing is wrong. Respect that.
- Letting the sequence continue. A scheduled step the next day undoes your polite reply.
- Treating all "not now" replies the same. Dated, event-based and vague replies need different follow-ups.
- Re-sending the first email. When you come back, bring something new.
- Using a "not now" as a reason to keep emailing someone who asked to stop. If they ask to be removed, suppress them and keep the record of that request. The ICO's guidance on business marketing suggests keeping objectors on a suppression list so they are screened out of future lists.
- Keeping the date in a rep's head. It leaves with the rep. Put it in the system.
How to do this in Master Inbox
Master Inbox is the reply management platform for outbound teams and agencies. It works alongside your sequencer, CRM and support desk, so you can keep Smartlead or Instantly for sending and use Master Inbox as the reply layer.
- Label. AI labeling tags each email and LinkedIn reply by intent as it lands. Not Right Now is one of the thirteen default labels, and you can use your own taxonomy on your own OpenAI, Anthropic or OpenRouter key. If a thread changes direction, the next reply re-runs the labeler, so an Interested thread that turns into Not Right Now updates itself.
- Workflows. Workflows run inside the inbox and trigger by label. Use one to stop the sequence, post a Slack card, update HubSpot or send a webhook when a reply is labeled Not Right Now.
- Snooze and follow-ups. Snooze a thread until the date you agreed, and set a follow-up, so the conversation returns to your queue when it is due.
- Needs Reply view. When a snoozed thread comes back or the prospect writes again, it appears in the Needs Reply view, with SLA tracking on every reply. See reporting.
- CRM sync. Labels and replies pass to HubSpot, Pipedrive, Attio and other CRMs, so the date and reason are on the record.
- Everything in one place. The Unibox threads email and LinkedIn replies from the same prospect, so the "not now" you got on LinkedIn sits next to the email thread.
Agencies can keep a different follow-up rule for each client with client workspaces. Pricing is based on connected mailboxes and client workspaces, with unlimited users on every plan. Every plan starts with a free 7-day POC. See pricing or take the product tour.
Frequently asked questions
How long should I wait before following up on a not now reply?
Use the date the prospect gave you. If they gave none, ask once, and otherwise pick a gap that fits your sales cycle and tell them what it is. Treat the gap as a setting to adjust from your own results.
Is a not now reply a positive reply?
It is a warm reply with a delay. Report it separately from interested replies and from clear rejections, so that your positive reply numbers stay clean and your future pipeline stays visible.
Should I keep sending my sequence after a not now?
No. Pause the sequence for that prospect and replace it with one dated follow-up. Further automatic touches in the meantime often turn a delay into a refusal.
What if the prospect never answers my re-open message?
Send one short nudge a few days later. If there is still no answer, move the lead to a longer nurture list and note it on the record. Do not keep pushing.
Can AI handle not now replies?
AI labeling can spot them and workflows can schedule the follow-up. A person should usually read the reason and write the re-open message, and Reply Agents in Master Inbox can draft it for approval first.
Sources
Links checked on 29 October 2026.
- ICO: Business to business marketing (objections, suppression lists and screening before sending).
- Google: Email sender guidelines (spam rate guidance and one-click unsubscribe for bulk senders).
This is general information, not legal advice. Check the rules for the countries you email.
Do not let a not now go quiet
Pick a label, a default gap and an owner, and make sure every "not now" leaves your inbox with a date. If you want the labeling, snoozing and syncing handled in one place, Start your free 7-day POC and we will onboard you with your own mailboxes. Smartlead, Instantly, HubSpot, Pipedrive, Attio and Slack are trademarks of their owners. Master Inbox is an independent product and is not affiliated with them.