A follow-up email after no response is the second message in a cold thread, sent three to four days after the first with no reply, in the same thread, restating the reason for writing in one line and lowering the ask. It is where most cold replies come from: teams report that 40 to 55% of all positive replies arrive on the first or second follow-up, not the opener. Its deliverability depends on the opener having reached a mailbox, which is why the thread starts with a verified list.
The opener arrives in a full inbox and gets triaged, not read. The follow-up arrives in a thread the mail client now shows with two messages, which is a signal of persistence without being a nuisance yet. The reader opens it, scrolls up, reads the opener properly, and replies to whichever message is easier.
That is why the follow-up should not add new arguments. Its job is to make the opener get read and to make replying cheap. One line that restates the reason, one ask that is smaller than the first, and nothing else.
Timing is three to four working days. Sooner reads as pressure. Later than five, and the thread has fallen off the first screen of the inbox.
Subject: Re: {original_subject}
Hi {first_name},
Floating this back up. The short version: {sender_company} helps {customer_type} {outcome_one_line}, and I thought it might apply to {company} because of {trigger}.
If a call is too much, a one-word reply tells me whether to send a two-line summary or leave it.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{original_subject} The opener's subject, so the thread stays intact{trigger} The reason you wrote in the first place, in a few words{outcome_one_line} What you deliver, in one lineSubject: Re: {original_subject}
{first_name}, any thoughts on the note below?
If the timing is wrong, "later" is a fine answer and I will come back in {months} months.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{months} Three or sixSubject: Re: {original_subject}
Hi {first_name},
One thing I should have led with: {single_fact}.
That is usually the part that makes {outcome} worth 15 minutes for {customer_type}. If it does not land for {company}, no harm done; say so and I will close the thread.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{single_fact} One number or result, no adjectivesA new thread looks like a new cold email to the mailbox provider and to the reader. Reply to your own message so the subject carries "Re:" and the opener is quoted below.
A follow-up to a bounced address is a second bounce on a dead mailbox. Sequencers often keep sending after a soft bounce. Start the sequence from a list verified with bulk verification and stop the thread on any bounce.
The follow-up is text only. Adding a link or a PDF on the second touch is a spam-filter pattern and a reader irritant.
Day 3, day 8, day 15, break-up by day 21 to 28. Beyond that, replies fall and complaints rise; keep complaints under 0.3%.
| Metric | Healthy range (industry) | If missed |
|---|---|---|
| Share of positive replies from follow-up 1 | 20 to 30% of all positive replies | Sent too early or with new arguments; cut it to the one-line version |
| Reply rate on this touch | 2 to 5% per 100 delivered | The opener's ask was already small; try Variant B |
| Unsubscribe or "stop" replies | Under 1% | Normal; honour within a day, remove from all sequences |
| Bounces on this touch | 0% | The sequencer is sending after a bounce; fix the stop rule |
Subject: Re: Verifying the Apollo export before the SDR team starts Hi Priya, Floating this back up. The short version: we verify database exports before they reach a sequencer, so a new SDR team starts on confirmed addresses, and I thought of Northgate because of the three roles you are filling. If a call is too much, a one-word reply tells me whether to send a two-line summary or leave it. Dan If this is not relevant, reply "no" and I will not write again.
The follow-up's job is to get the opener read. New arguments make it a second opener.
A fresh thread is a second cold email. Reply to your own message.
Three to four working days. Sooner reads as pressure.
Sequencers retry soft bounces. Start from a verified list and stop the thread on any bounce.
Pick by what the opener lacked. Each variant repairs one specific gap; none of them adds a second pitch.
| Variant | Use when | Length | What it repairs |
|---|---|---|---|
| Main | The opener was fine and simply went unread | About 55 words | Restates the reason and lowers the ask to a one-word reply |
| A: shorter still | The opener was already short and clear | Under 30 words | Makes the thread visible again with zero cost to reply |
| B: with one new fact | The opener had no number in it | About 60 words | Adds the single proof point the opener should have carried |
| Any variant | The opener bounced | Do not send | A follow-up to a dead mailbox is a second bounce; fix the list |
The full set
Day 8: add one piece of evidence
Day 15: a different angle or a different person
Close the loop and earn the last reply
Sequence design beyond the templates
Measuring replies per delivered
Three to four working days. Sooner reads as pressure; later than five and the thread has left the first screen of the inbox. Follow-ups two and three go at roughly day 8 and day 15, the break-up by day 21 to 28.
The same thread. A new email is a second cold send to the mailbox provider and a second interruption to the reader. Replying to your own message keeps the opener quoted below and the subject prefixed with Re.
One line restating why you wrote and one ask smaller than the first. No new arguments; the follow-up's job is to get the opener read. Variant B adds a single fact if the opener lacked one.
More than three plus a break-up. Replies fall after the third touch and complaints rise. If the thread earns nothing by the break-up, the next contact is a re-engagement email months later in a new thread with a new reason.
Many tools treat a soft bounce as deliverable and retry. Fix the stop rule, and start every sequence from a verified list so bounces are rare: confirmed-valid addresses only, catch-all and unknown routed elsewhere.
No follow-up to a dead mailbox, no second bounce. Confirmed valid, catch-all, unknown and invalid per address. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
A competitor user cold email template
An after-event cold email template for conferences, webinars and trade shows
A second follow-up email template for cold sequences
A third follow-up email template for cold sequences
A break-up email template for cold sequences
A re-engagement email template for leads who went quiet after a cold sequence
Continue through related topics