A cold email reply once sat in a shared inbox for nineteen hours before anyone saw it. It said, more or less, "interesting timing, we're looking at this now — can you send some detail?" By the time we answered, they had booked a call with a competitor. Not because the competitor's product was better. Because the competitor answered.
That is the part of outbound nobody optimises, and knowing what to do after a cold email reply is worth more than another round of subject-line testing. Enormous effort goes into list quality, subject lines and sequence design — all of which exist to produce exactly one event, a human replying — and then the process handling that event is "someone checks the inbox eventually".
The reply is the scarce thing. Everything before it is manufacturing; everything after it is where the deal is actually won or lost.
Quick answer: what should you do when a prospect replies?
Answer fast — inside minutes, not hours — and use the reply to book a meeting rather than to qualify. Confirm you are talking to the right person, acknowledge the specific thing they said, and give an assumptive call to action with a calendar link ("here's my calendar, 15 minutes this week") rather than asking whether they would like to talk. Deep qualification belongs in the meeting, not in the email thread before it. Positive replies decay quickly, so speed matters more than polish; a good answer now beats a perfect answer this afternoon.
Speed is the whole game, and it is measurable
Speed-to-lead research has been consistent for years: the odds of a productive conversation drop sharply within the first hour, and the steepest part of that decline is in the first few minutes. The exact multiples vary by study and are usually quoted by companies selling response automation, so treat the specific numbers with suspicion — but the shape is not controversial, and it matches what anyone who has run outbound has felt.
The mechanism is not mysterious. A prospect who replies is, at that moment, thinking about the problem. Twenty minutes later they are in a standup. Tomorrow they are back to their actual job, and your email is competing with everything that arrived since — including replies from whoever else they contacted.
Two practical consequences:
- A reply is an interrupt, not a queue item. If replies land in a folder someone reviews twice a day, you have designed a system that loses the fast ones.
- Response time is a metric worth tracking, and almost nobody tracks it. Median time-from-reply-to-answer will tell you more about your pipeline than open rate ever will — and unlike open rate, it is not contaminated by privacy prefetching, a problem I went into in what a good average email open rate actually tells you.
Not all replies mean what they appear to
The second failure is treating every reply as the same object. They are not, and the correct response differs sharply.
| Reply type | What it usually means | Correct response | What kills it |
|---|---|---|---|
| "Tell me more" | Genuine interest, low effort | Short answer + calendar link, same hour | Sending a deck instead of booking |
| "What does it cost?" | Evaluating seriously, may be benchmarking | Give a real range, then book | Refusing to answer until a call |
| "Not right now" | Timing, not rejection | Ask when, then set a reminder and leave | Arguing, or pretending it was a yes |
| "Not me — talk to X" | A referral, the most underrated reply | Thank them, ask permission to use their name | Emailing X without the referral context |
| "Unsubscribe" / annoyance | You mis-targeted | Remove immediately, apologise briefly | Any attempt to save it |
| Out-of-office | Nothing, but it is data | Note the return date, re-touch after | Continuing the sequence blindly |
| A question about detail | High intent, testing competence | Answer precisely; brevity signals confidence | A vague answer, or deferring everything to a call |
Two of those deserve more attention.
"Not me — talk to X" is the highest-value reply you get and most people waste it. You now have an internal referral, which is a completely different opening than a cold approach. The move is to reply to the original person, ask whether you can mention they pointed you over, and only then contact X — leading with the referral. Skipping that step converts a warm introduction back into a cold email.
"What does it cost?" should get an actual answer. Deflecting to "it depends, let's book a call" reads as evasive and is the most common reason a promising thread goes silent. Give a range, name what moves it, and then book. If your pricing genuinely cannot be summarised, that is a product problem showing up in your sales process.
The over-qualification trap
Here is the mistake I see most in teams that have read a lot of sales advice: someone replies with interest, and the response is three qualifying questions.
Budget, timeline, authority — all reasonable things to know, and all wrong to ask in the first reply. You have just converted a warm human moment into a form. The prospect expressed interest in fifteen seconds of effort; you have answered by requesting several minutes of theirs before offering anything.
Qualify enough to not waste the meeting, and no more:
- Is this plausibly the right person? You should mostly know this from your list. If you built it from signals rather than a purchased database — the approach I set out in finding B2B leads without buying a list — you already have a reason to believe they are.
- Is there any obvious disqualifier? Wrong company size, a competitor's employee, a student doing research.
That is it. Everything else — budget, procurement, who else needs to be in the room — is what the meeting is for. A fifteen-minute call filters better than any email exchange, and it costs the prospect less than answering your questionnaire.
Ask for the meeting the way people actually say yes
The phrasing of the ask changes the outcome more than the length of the reply.
"Would you be open to a quick call sometime?" invites a decision about whether to have a call at all. "Here's my calendar — 15 minutes Thursday or Friday?" invites a decision about when. The second is not a trick; it is simply the next step stated plainly, and it removes the work of proposing times.
A few rules that hold up:
- Name the duration and keep it short. Fifteen minutes is easy to grant. "A quick chat" is unbounded and therefore expensive.
- Send the calendar link only after interest. In a cold first touch it presumes too much; after a reply it is a convenience.
- Offer two concrete windows as well as the link. Some people will never click a scheduler but will happily answer "Thursday 3pm works".
- Do not attach a deck. A deck is a way of postponing the meeting while appearing helpful.
The operational problem: replies do not arrive in one place
All of the above assumes you see the reply. On a single-channel email sequence that is a solved problem. Run the multi-channel sequences that actually get replies — the spacing rules for which I laid out in multi-channel outreach sequences — and it stops being solved, because a prospect answers wherever it suits them. LinkedIn DM, a WhatsApp reply to the number in your signature, a reply from a colleague's address.
Now the five-minute window has to be met across half a dozen inboxes, most of which nobody is watching, and the sequence engine has to stop sending on all of them the moment any one of them gets a response. That second part is the failure I have seen do real damage: a prospect answers on LinkedIn, the day-10 call task fires anyway, and you have told them their reply did not register.
MisarReach is built around that specific gap — conversations from every channel land in one pipeline rather than scattered across apps, a reply anywhere stops the sequence everywhere, and it suggests the next step on each open thread so the ones with no obvious action do not silently rot. Its AI agent can go further and answer or book on its own, which is either the appealing part or the alarming part depending on how comfortable you are with an autonomous system speaking for you. I would turn that on last, if at all, and only after watching what it drafts for a few weeks.
The unglamorous version, if you are running this by hand: forward every channel into one inbox, and make "check for replies" a scheduled thing a named person owns rather than a habit you hope survives a busy Thursday.
The metric that actually matters
Most outbound dashboards stop at reply rate. The number that predicts revenue is reply-to-meeting conversion — of everyone who answered, how many ended up on a call.
Tracking it separates two very different problems that reply rate alone conflates:
- Low reply rate, high reply-to-meeting means your targeting and messaging are fine and you simply need more volume.
- High reply rate, low reply-to-meeting means you are generating interest and mishandling it. Almost always this is slow response, over-qualification, or a weak ask — all fixable this week, and all invisible if you only watch replies.
The second pattern is far more common than people expect, and far cheaper to fix than building a bigger list.
What I would change first
If you do nothing else:
- Measure your median reply-to-response time this week. Most teams are shocked. If it is over an hour, that is your bottleneck, not your copy.
- Route every channel's replies into one place, even if that place is a forwarded inbox.
- Delete the qualifying questions from your first response. Replace them with a calendar link and one specific sentence about what they said.
- Make "not me, talk to X" a scripted play rather than an improvised one. It is the highest-leverage reply you receive.
- Start tracking reply-to-meeting conversion alongside reply rate.
The reply is the expensive thing your entire outbound machine exists to produce. It is worth more care than the fifteenth iteration of a subject line.
FAQ
How fast should you respond to a cold email reply?
Within minutes if you can, and certainly the same hour. Interest decays quickly — the prospect is thinking about the problem when they hit send and is back to their own work shortly after. A fast, imperfect answer consistently beats a polished one sent tomorrow, so do not sit on a reply while you draft the ideal response.
Should you qualify a prospect before booking the meeting?
Only enough to confirm they are plausibly the right person and there is no obvious disqualifier. Budget, timeline and decision-making authority are what the meeting is for. Asking them by email converts a moment of interest into a questionnaire, and it is one of the most common reasons warm threads go quiet.
Should you send a calendar link in the first reply?
Yes, once they have shown interest — that is exactly when a scheduler is a convenience rather than a presumption. Pair it with two concrete time windows, since plenty of people will answer "Thursday 3pm" who would never click through to a booking page. Avoid calendar links in the initial cold touch, where they read as entitled.
What if they reply "not right now"?
Treat it as timing information, not rejection, and resist the urge to argue. Ask one question — when would be worth revisiting — then set a reminder and genuinely leave them alone until then. Prospects who said "not now" and were treated well are a meaningfully warmer list than any cold segment when that date arrives.
