A second follow-up email is the third message in a cold thread, sent seven to nine days after the opener in the same thread, adding exactly one new piece of evidence, a result, a customer at the reader's stage or a short case, and repeating a small ask. It exists because the first follow-up restated and the reader still did not act; evidence is what changes that. Teams report the second follow-up contributes 15 to 25% of a sequence's positive replies on verified lists.
"{similar_company} cut bounces from 9% to 0.8% in the first month." Specific, checkable, at the reader's stage. The strongest form.
A logo works when it is in the reader's sector or city. It works less well when it is a global brand with nothing in common with them.
Situation, what changed, result. Three lines, no adjectives. Longer than that and the follow-up becomes a second opener.
A benchmark the reader can use regardless of whether they buy, such as a corpus rate for their list type. It earns goodwill and a reply even from people who are not buying yet.
The opener's job was relevance: why you, why now. The first follow-up's job was to get the opener read. By the second follow-up the reader has seen the pitch twice and not acted, which usually means they believe it is relevant but not that it works. Evidence answers that.
One piece, not three. A list of proof points reads as a brochure, and the reader does the same thing they did with the opener: triage and move on. One number, one customer or one three-line case, then the same small ask as before.
The ask stays small. If the opener asked for a call and the first follow-up offered a two-line summary, the second follow-up offers the summary again or something smaller, such as a yes or no to a question.
Subject: Re: {original_subject}
Hi {first_name},
One number instead of another nudge: {similar_company}, a {customer_descriptor}, went from {before} to {after} in {timeframe} with {sender_company}.
That is the kind of change I thought might matter for {company} given {trigger}. If it does, I can show the mechanics in 15 minutes; if not, a quick no saves us both the thread.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{customer_descriptor} Their stage or sector in three words{before} / {after} The metric before and after, same unit{trigger} The original reason for writingSubject: Re: {original_subject}
{first_name},
Short case, since words are cheap:
Situation: {situation}.
What changed: {change}.
Result: {result}.
Same shape as {company}? Yes or no is enough.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{situation} One line on where the customer started{change} One line on what you did{result} One numberSubject: Re: {original_subject}
Hi {first_name},
Whether or not we talk, this may be useful: {data_point}.
It comes from {data_source}, and it is the reason {outcome} tends to pay for itself at {customer_type}. If you want the full table, say "table" and I will send it with no pitch attached.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{data_point} One benchmark the reader can use{data_source} Where it comes from, in plain words| Rule or metric | Standard | Why |
|---|---|---|
| Thread | Same thread, Re: subject, opener quoted below | New threads look like new cold sends |
| Timing | Day 7 to 9 after the opener | Earlier crowds the first follow-up; later loses the thread |
| Links | One at most, to the case or table offered | Two links on the third touch is a filter pattern |
| Reply rate on this touch | 2 to 4% per 100 delivered (industry) | Evidence that does not match the reader's stage |
| Share of sequence replies | 15 to 25% | Lower means the evidence repeats the opener |
| Bounces | 0% on this touch | The list was verified and the sequencer stops on bounce |
Subject: Re: Verifying the Apollo export before the SDR team starts Hi Priya, One number instead of another nudge: Harbourline, a 40-person logistics SaaS, went from 8.4% bounces to 0.7% in the first month after verifying their Apollo exports, and their new SDRs booked 11 meetings in week two. That is the kind of change I thought might matter for Northgate given the hiring. If it does, I can show the mechanics in 15 minutes; if not, a quick no saves us both the thread. Dan If this is not relevant, reply "no" and I will not write again.
A list of proof reads as a brochure. One number, one customer or one three-line case.
An enterprise logo means nothing to a 40-person company. Match the comparable to the reader.
A PDF on the third touch trips filters. Three lines in the body; they will ask for the rest.
Keep Re: and the original subject so the opener stays quoted below.
Match the evidence to what the reader can check and relate to. A wrong-stage comparable is worse than none.
| Reader | Best evidence | Avoid |
|---|---|---|
| Founder or small-company lead | A number from a company the same size, with the timeframe | Enterprise logos; they read as a different world |
| Operator in a function (RevOps, demand gen) | A three-line case with the mechanism visible | Vague outcomes such as "improved efficiency" |
| Senior buyer who did not reply twice | A research data point they can use without buying | Anything that needs a meeting to understand |
| Someone who replied "later" to the opener | The same evidence, dated, with the later date honoured | A new pitch; they already said yes to the idea |
The full set
Day 3: restate and lower the ask
Day 15: change the angle or the person
Close the loop
Data points you may quote in Variant B
What each touch contributes
One new piece of evidence, a number from a comparable customer, a recognisable name or a three-line case, followed by the same small ask as before. Nothing else. The reader has seen the pitch twice; evidence is what they are missing.
Seven to nine days after the opener, in the same thread. The first follow-up went at day 3 or 4; the third goes around day 15; the break-up closes the sequence by day 21 to 28.
Put the case in three lines in the body instead. Attachments and extra links on a third touch trip filters and lower replies. If the reader wants the full case, they will ask, and that reply is the goal.
Teams report 2 to 4% positive replies on the touch itself and 15 to 25% of the sequence's total replies arriving here, on verified lists. Lower numbers usually mean the evidence did not match the reader's stage.
No. Keep Re: and the original subject so the thread stays intact and the opener sits quoted below. A changed subject breaks the thread and reads as a new cold email.
A sequence is only as deliverable as its list. Verify first, send to confirmed-valid addresses, and let the evidence do the work. 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
An after-event cold email template for conferences, webinars and trade shows
A first follow-up email template for when a cold email gets no response
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
A referral request email template for asking customers, partners and contacts for an introduction
Continue through related topics