They reply, then nothing: saving the conversation
Getting a reply is the hard part. Losing it afterwards is the common one, and it turns on the next message, almost always written too fast.
Someone replied. That is the hard part, the one everybody writes about, and you just cleared it. Two messages later, the conversation is dead.
It is the least documented moment in outreach, and by far the most expensive: you spent the attention, you got it, and you lose it on a message written in thirty seconds.
A first reply is not agreement. It is permission to go one step further, and it is withdrawn as easily as it was given.
What kills the conversation
Almost always the same thing: asking for the meeting straight away. The person wrote three words to say they saw what you meant, and you answer with a booking link.
From their side the jump is brutal. They granted thirty seconds, you are asking for thirty minutes. Nothing in the exchange justifies that yet, and the polite refusal that follows is not a refusal of your offer, it is a refusal of the jump.
| What they wrote | What it means |
|---|---|
| Yes, that speaks to us | The problem is recognised, nothing more. Whether it is a priority is still open |
| How does it work? | A credibility question, which a meeting does not answer |
| Not right now | The subject exists, the timing does not. The worst moment to push |
| Send me some material | Often a polite exit. Sometimes a real request, what follows will tell |
All four look like a green light and call for four different continuations. Treating them alike, with the same booking link, is the most common way to lose all four.
The message that moves things forward
A good next message does two things, and only one at a time: it sends back a question answerable in one line, and it gives something without asking for anything.
- A closed question about their situation, not about your offer. Do you handle it in-house today, or is it outsourced?
- One concrete element answering what was just asked, in two lines, not a twelve-page document.
- No slot request in that message. The meeting comes when the person has a reason to want it.
- The same length as their reply. Answering three words with ten lines unbalances the exchange.
The last point sounds trivial and is not. The length of a message says who it serves. A long message after a short reply announces that you are in more of a hurry than the person opposite.
Two continuations, same first reply
The continuation that closes
- A booking link on the first reply
- A document sent without being asked for
- A restatement of your offer
- A question that cannot be answered quickly
- A follow-up the next day
The continuation that advances
- A closed question about how they work
- Two lines answering exactly what was asked
- An example close to their situation
- A slot proposed only once there is a reason
- Time to answer
When to propose the meeting
The right moment has a simple tell: the person asks something a message can no longer answer. What would that look like here? How would you handle it with our stack? At that point proposing a slot does not cut the conversation, it continues it.
And propose it with its reason. Twenty minutes to look at your case specifically beats a bare link, because a bare link asks the person to guess what they are agreeing to.
If the moment never comes, the conversation is not lost. Someone who replied once is far more reachable in three months than someone who never did. Note what they said, and come back when their situation has moved.
Where Meidly helps
The objections you get in messages are the same as the ones in your calls, phrased shorter. We surface them from your customer conversations, along with what worked in reply, and suggest what comes next by objective and by channel. You read it back, you correct it, and you are the one who sends.
See how messages and sequences work→In short
Do not answer a first reply with a booking link. Send back a short question about their situation, give one concrete element without asking for anything, and match their length. The meeting is proposed when a question outgrows what a message can carry, and it is proposed with its reason.
Frequently asked questions
What should you reply when a prospect says it speaks to them?
Not a booking link. A closed question about how they work today, answerable in one line. That answer tells you whether the problem is merely recognised or actually a priority, and that difference decides what comes next.
When should you propose a meeting after a reply?
When the person asks something a message can no longer handle, along the lines of what would that look like here. At that point a slot continues the conversation instead of interrupting it. And propose it with its reason, not as a bare link.
What do you do when someone says not right now?
Nothing immediately, it is the worst moment to push. The subject exists, the calendar does not follow. Note what was said and come back when the situation has moved: someone who replied once stays far more reachable than a cold contact.
Should you send material when asked for it?
Send two lines answering exactly the question asked, not a twelve-page document. A request for documentation is often a polite exit; a short precise answer lets you find out which of the two it was.