How to reply when a prospect says contact me in a month

Stop losing leads to vague follow-up requests. Learn how to confirm a date and the reason behind it so your next LinkedIn message lands with context.

Get started

Short answer

When a prospect asks you to follow up in a month, don't just say 'will do'. Name the exact date you'll reach out and ask what event or milestone they're waiting for. That turns a generic brush-off into a scheduled commitment you can actually plan around.

Why 'I'll check back then' fails

Most people answer a timing objection by agreeing to the delay. They type 'No problem, I'll reach out in 30 days' and close the tab. The conversation is now open-ended, and you have given away the one thing that made your message different from everything else in that inbox: a reason to be there.

Thirty days later the prospect has forgotten the conversation. They don't remember your name, the problem you described, or why they agreed to a follow-up at all. Your message arrives looking like another cold pitch, and it gets read like one.

There is a second cost. A vague agreement tells you nothing about whether the person is genuinely busy or being polite. You spend the next month counting a lead that was never real and planning pipeline around it.

The fix is to trade the vague agreement for a specific appointment: a date you both know, and the event that makes the date matter. That takes one extra message and about forty seconds.

The vague reply

  • Sounds good, I'll reach out in a month.
  • No problem, I'll check back in 30 days.
  • I'll follow up with you then.

The specific reply

  • I'll put a note for October 12. Is that when the new budget gets approved?
  • Understood. I'll mark November 1. Does that line up with the project wrap-up?
  • I can do that. I'll write on the 20th. What needs to happen between now and then?

The three-step reply framework

Change the shape of the reply. Instead of asking permission to come back, propose a plan and let them correct it. People find it much easier to fix a wrong date than to invent a right one.

You get two things out of this. A date keeps you organised. A reason gives your next message a hook, so it reads as a continuation of a conversation rather than a restart.

  1. 1

    Acknowledge the timeline

    Accept the delay in as few words as possible. 'Understood' or 'Makes sense' does the job. Anything longer sounds like you're negotiating with it.

  2. 2

    Propose a specific date

    Name a day, not a period. 'October 15' beats 'mid-October', and 'mid-October' beats 'in a month'. A day is something they can disagree with, which is what makes it real.

  3. 3

    Ask for the trigger

    Ask what happens between now and then. A budget cycle, a product launch, a hire, a holiday. Whatever they name becomes the first line of your follow-up.

Paste this job

Understood, {first name}. I'll put {specific date} in my calendar. Is that when {likely trigger} happens, or should I aim for a different week?

Templates for different scenarios

The question you ask for the trigger should match the person's job. A finance lead is usually waiting on a budget cycle. A project manager is usually waiting on a deadline. A founder is usually waiting on a hire or a funding round.

Keep the ask short. A long message reads like a pitch, and a pitch is what they were trying to postpone.

Example

  1. Prospect

    I'm interested but snowed under right now. Reach out in a month.

  2. You

    Understood. I'll put October 15 in my calendar. Is that when the migration wraps up?

  3. Prospect

    Roughly, yes. We're moving off the old platform that week.

  4. You

    Good to know. I'll leave you to it and write on the 15th.

  5. Prospect

    Works.

Paste this job

Hi {first name}, you asked me to come back after {event}. Is {event} still the thing standing between you and {outcome}? If it is, I'll come back in {timeframe}. If it isn't, tell me what changed and I'll adjust.

Handling the response

Not every prospect gives you a clean answer. Some confirm the date and the reason. Some say yes and ignore the question. A few realise mid-conversation that they can talk sooner than they thought.

Your next move depends on which one you get. In every case, stop the back and forth once the date is set. The point of the exchange was to get out of their inbox, not to keep it busy.

Confirms the date and the reason

Prospect response
Set the reminder and stop messaging.
Your action
Reference the milestone they named.

Says yes but skips the reason

Prospect response
Follow up on the date you proposed anyway.
Your action
Say you're writing as agreed on that date.

Says let's talk sooner

Prospect response
Send your scheduling link the same day.
Your action
Go straight to the discovery call.

Goes quiet entirely

Prospect response
Send one message on the date, then stop.
Your action
Ask whether the timing has changed.

What to send on the day you said you would

This is where most of these commitments die. People open with 'Just checking in' or 'Circling back as promised', which is filler and gives the prospect nothing to reply to.

Open with the trigger they gave you. Restate the problem in one line. Ask something that can be answered in a sentence.

  • Lead with the event, not the calendar. 'You said the migration wraps on the 15th, so I'm guessing the team is past the worst of it.'
  • Remind them what you do in one line. They have had thirty days of other conversations since yours.
  • Ask something small. 'Worth a 15 minute call this week, or should I come back after the quarter closes?'
  • Don't apologise for following up. You said you would, and you did.

When the delay is real and when it isn't

A real delay has a name. Budget approval, a hiring freeze, a system migration, parental leave, a funding round that closes in six weeks. If the prospect can name it without hesitating, the date is probably real and your follow-up should reference it directly.

If they can't name anything, the delay is usually a soft no. That doesn't mean you should argue with it. It means you stop spending calendar space on it and let the follow-up be a cheap check rather than a planned pitch.

One follow-up after the agreed date is enough. If that one gets no reply, move on and leave the door open in your last line. Chasing a second and third time after a date you both agreed to makes you the person they were avoiding.

A date without a reason is a polite no with a delay attached. Ask for the reason once, then plan accordingly.

Doing this with Kinlead

Kinlead keeps leads in lead groups, so you can put everyone who asked for a later date into a group of their own and point a campaign at that group when the dates come around. Any campaign can use any group.

When you do reach out, the campaign's AI writes from your goal, tone and an optional sales playbook, which is your own script. Queued messages can be read and edited on the Actions page before they send, so you can add the trigger the prospect gave you.

Kinlead doesn't record why someone asked for a delay, so keep that reason in the playbook or in the lead group you built for them. Each campaign also chooses how replies are handled, from handing the conversation to you at the first reply to letting the AI book a meeting with your scheduling link. You can start a trial or book a demo to see it on your own leads.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to reply when a prospect says contact me in a month.md