A re-engagement email for cold leads is a fresh first-contact message to someone who received a cold sequence 60 to 120 days earlier and did not buy, sent in a new thread with a reason that did not exist the first time, such as a change at their company, a change in your product, or new evidence. Because B2B addresses decay at roughly a decay rate at which only 19.2% of addresses remain valid after 90 days (BounceZero decay study), the first step is re-verifying the address; a quarter of a six-month-old list has moved, and a re-engagement that bounces damages the domain twice.
The old thread failed on the old reason. The re-engagement needs one of the following, or it is the same email with a later date.
| New reason | Where it comes from | Strength |
|---|---|---|
| Something changed at their company | Funding, hiring, new leader, new tool: the trigger pages in this set | Strongest; it is a trigger email to a known name |
| Something changed in your product | A feature, a price, an integration they lacked | Strong if it addresses an objection they raised or implied |
| New evidence | A new customer in their sector, a new benchmark | Medium; works with Variant B |
| Their "later" date arrived | A "B, come back in six months" reply to the break-up | Strong; you have permission |
| Nothing changed | You just want to try again | Weak; expect low replies and higher complaints |
Sixty days is the minimum gap. Shorter, and the reader remembers the old thread as unfinished nagging. One hundred and twenty days is about the maximum before the original context is gone and the email becomes an ordinary cold send.
Inside that gap the address has aged. At roughly 22% annual decay, three to four months means 6 to 8% of the list has moved, and the movers are concentrated in exactly the senior roles you targeted. Re-verify the segment before the re-engagement send: a bounce on a re-engagement is a second strike on the same domain.
The movers are not lost. A business address that went from valid to invalid is a job-change trigger; find the new company, and the new role template is the better send.
Subject: {company} and {change}
Hi {first_name},
We spoke briefly by email in {month}; the timing was not right then. Writing again because {change} at {company} changes the picture: it usually brings {problem} forward.
{sender_company} handles that for {customer_type}. Since we last wrote, {similar_company} did it in {timeframe} after a similar change.
Worth a 15-minute look now? If the answer is still later, tell me when and I will hold to it.
{sender_name}
{sender_title}, {sender_company}
If this is not relevant, reply "no" and I will not write again.
{month} When the first sequence ran{change} The trigger: raise, hire, new leader, new tool{problem} The problem that change brings forwardSubject: The thing that was missing
{first_name},
When we were in touch in {month}, {objection} was the gap. It is closed now: {what_changed}.
If that was the only thing in the way, the rest of the conversation is short. If there were others, I would rather hear them than guess.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{objection} The objection they raised or implied{what_changed} The feature, price or integration, in one lineSubject: You said {month}
Hi {first_name},
In {earlier_month} you said to come back around now, so here I am, no earlier.
The offer is the same: {outcome} for {company}, shown in 15 minutes or sent as a two-line summary. Has the timing moved from "later" to "now", or further out?
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{earlier_month} When they said later{month} The month they namedRun the segment through bulk verification again. Movers become invalid and come out; catch-all and unknown stay out of cold volume. The second sequence must not bounce where the first did not.
Replying to a four-month-old thread drags the failed sequence back into view. Start clean, reference the earlier contact in one clause.
Opener, one follow-up, one break-up over two weeks. The reader has already seen a full sequence; a second full one is pressure.
Anyone who said no, unsubscribed or complained the first time is never re-engaged. Keep the stop list across tools and across quarters.
| Metric | Healthy range (industry) | If missed |
|---|---|---|
| Positive replies | 4 to 9% per 100 delivered with a real new reason | The reason was not new; see the table above |
| Bounce rate | Under 1% after re-verification | The segment was not re-verified |
| Movers found | 6 to 8% of the segment at 3 to 4 months | Treat as new role triggers, not losses |
| Complaints | Under 0.3% | Gap under 60 days, or a stop-list contact slipped through |
Subject: Northgate and the new RevOps hire
Hi Priya,
We spoke briefly by email in June; the timing was not right then. Writing again because the RevOps lead Northgate just hired changes the picture: a RevOps hire usually brings the CRM data clean-up forward.
We handle that for sales teams. Since we last wrote, Kestrel Freight did it in three weeks after a similar hire.
Worth a 15-minute look now? If the answer is still later, tell me when and I will hold to it.
{your_name}
{your_company}
If this is not relevant, reply "no" and I will not write again.
The old email with a later date earns the old result. Find a change at their company, in your product, or in the evidence.
It drags the failed sequence back into view. New thread, one clause of context.
Six to eight percent of a four-month-old segment has moved. A bounce here is a second strike.
Anyone who declined, unsubscribed or complained stays closed, across tools and quarters.
The full set
The message that ends the first sequence
For the contacts who moved in the gap
Monthly loss rates behind the 22% figure
The maintenance loop that re-verifies on a schedule
A new reason, when the company raised
Sixty to 120 days after the break-up. Shorter reads as nagging; longer loses the original context. If they gave a date in reply to the break-up, use that date and say so.
A reason that did not exist the first time: a change at their company, a change in your product that closes an objection, new evidence, or the arrival of the date they named. Without a new reason it is the old email with a later timestamp.
No. A new thread with one clause referencing the earlier contact. Replying to the old thread brings the failed sequence back into view and reads as a fifth follow-up.
Addresses decay fast, with only 19.2% of addresses still valid 90 days after verification in the BounceZero decay study, so 6 to 8% of a three-to-four-month-old segment has moved, concentrated in senior roles. A bounce on a re-engagement is a second strike on the domain. Verify, remove invalid, and treat the movers as new role triggers.
Three at most: opener, one follow-up, one break-up over about two weeks. The reader has already received a full sequence. Anyone who declined, unsubscribed or complained the first time is never re-engaged.
Movers out, confirmed-valid addresses in, and the new reason reaches a mailbox. 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 third follow-up email template for cold sequences
A break-up email template for cold sequences
A referral request email template for asking customers, partners and contacts for an introduction
A partnership outreach email template for integration, co-marketing and referral partnerships
An agency pitch email template that beats the hundred identical pitches a prospect gets each week
A recruiter outreach email template for contacting candidates cold
Continue through related topics