How to Warm Up an Aged Lead List and Earn Permission That's Yours
The short version
Warming up an aged list is a sequence, not a send. Clean the file and check it against your suppression list and the Reassigned Number Database first. Then re-open the conversation with plain-text email that assumes nothing, ask for permission once the reader has engaged rather than in the first message, and retire the non-responders quietly instead of mailing them harder. Done over a few weeks, this converts a list you bought into a list you own — and the people who confirm are the ones worth calling.
Before the first send
Three passes over the file, in this order. Each one removes people who would cost you more than they could return.
**Your own suppression list.** Prior opt-outs, complaints, current customers, anyone excluded by policy. This is separate from the national Do Not Call registry and it is yours to maintain. Scrub every batch, not once at import.
**The Reassigned Number Database, if you plan to call.** Numbers change hands over the months a record sits, and a reassigned number reaches a stranger who never consented. Checking first provides a safe harbor and takes minutes.
**Obvious dead weight.** Malformed addresses, duplicates across vendors, records with no usable contact method. A smaller file that reaches people beats a larger one that bounces, because bounce rate is what mailbox providers use to decide whether your future mail arrives at all.
Why the first email does not ask for anything
The instinct is to open with the offer, because that is what you want. It reliably underperforms on an aged list.
The reader does not remember you. They filled in a form months ago, possibly on a site whose name they never registered, and the mailbox they used has since absorbed a lot of mail. An email that opens by asking for a decision is asking someone with no context to spend attention they have no reason to spend.
So the first message earns the right to send the second. It is short, it is plain text, it is useful on its own, and it makes replying easy. Everything after it is easier because of it.
Pacing, and why it decides whether this works
Send the whole list at once and two things happen. Mailbox providers see an unfamiliar sender producing a volume spike and start deferring, which shows up as soft bounces. And any problem in your copy or your data hits every contact before you can see it.
Spread the first pass across days rather than hours. Watch the bounce rate: under 3% of attempted is healthy, and above that mailbox providers begin throttling. Hard bounces matter more than soft ones — a soft bounce is a mailbox deferring, a hard bounce is an address that does not exist and should be suppressed immediately.
If you are sending from a domain that is new or has been quiet, start smaller than feels necessary and increase over a couple of weeks. Reputation is easy to build slowly and slow to repair.
What to do with the people who never respond
Most of the list will not reply, and that is the expected result rather than a failure. What you do next is what separates an appreciating list from a decaying one.
Retire them from active sending and move them to a low-frequency track — a monthly or quarterly newsletter with a standing confirmation link. Someone who never opens anything over several months has told you something, and continuing to mail them harms the deliverability of everything you send to everyone else.
This is the quiet part of the permission pass. The list gets smaller and the mail gets better.
The sequence
Five emails over about three weeks. The permission ask sits at day 9, after two messages have already earned attention — asking in the first email converts worse and costs you the contact.
- Day 0 — send today
Subject
the thing most people get wrong about aged leads
Hi {{first_name}} — a while back you looked into {{vertical}}. I have no idea whether that is still live for you, and this is not a pitch either way.
One thing worth knowing if it is: the people who do well with this rarely have a better list than everyone else. They have a better second and third contact. Most of the value in any list sits behind the first attempt, and most people stop there.
If that is useful, I write about it. If not, the unsubscribe link below works immediately and I will not be offended.
Why this works
- ✓Names the gap in memory instead of pretending a relationship exists
- ✓Gives something usable in the email itself, so opening it was worth it
- ✓Offers the exit early, which raises trust and lowers complaints
- ✓Plain text, one idea, no images — it reads like a person wrote it
- Day 4
Subject
the second and third contact
Hi {{first_name}} — following on from last week.
Here is the pattern, concretely. Attempt one reaches the people who were already ready. Attempts two through five reach the much larger group who were busy, distracted, or not in the right week. The gap between operations that work and operations that do not is almost entirely in that second group.
What that looks like in practice: a short call, a voicemail that gives a reason to call back, and an email that assumes nothing. Spread over two weeks, not two days.
That is the whole method. It is unglamorous and it is why it works.
Why this works
- ✓Pays off the specific promise made in the first email
- ✓Teaches something the reader can use whether or not they ever buy from you
- ✓Builds the case for follow-up without asking for anything yet
- Day 9This is the permission ask
Subject
worth keeping in touch?
Hi {{first_name}} — short one.
I have been sending these because you looked into {{vertical}} at some point. That is a thin reason to keep showing up in your inbox, so I would rather ask.
If this is useful, confirm here and I will keep sending: {{confirm_link}}
If you confirm, I can also reach out directly when something genuinely relevant comes up, rather than only by email.
If you would rather not, do nothing at all. I will stop.
Why this works
- ✓Asks only after two messages have earned attention, which is why it converts
- ✓Confirming is one click and the alternative is genuinely doing nothing
- ✓Captures permission that names your company, with a timestamp — the whole point of the sequence
- ✓States plainly what confirming allows, so the consent is informed
- Day 14
Subject
one number worth checking
Hi {{first_name}} — for anyone still working {{vertical}}, this is the number I would look at first.
Work out what you can afford to pay for a contact: your average deal value, times your close rate, times the share of that you are willing to spend to acquire it. Most people have never calculated it, and it changes what they buy.
The calculators on the site will do it in about two minutes if you would rather not do the arithmetic.
Why this works
- ✓Returns to being useful immediately after the ask, so the sequence does not read as a funnel
- ✓Sends engaged readers to a tool, which is a low-commitment next step
- ✓Works for people who confirmed and people who did not
- Day 21
Subject
last one from this sequence
Hi {{first_name}} — this is the last of these.
If you confirmed, you will hear from me when there is something worth your time, and not otherwise.
If you did not, this is where I stop and let you get on with your week. You are welcome back any time.
Either way, the short version of everything above: the money is in the second contact, and almost nobody makes it.
Why this works
- ✓Ending on schedule is what makes the next sequence welcome
- ✓Restates the single most useful idea so the last email still gives something
- ✓Closes the loop cleanly for non-responders instead of trailing off
What to use
Any of these will run the sequence above. The differences that matter are what happens to your consent record and your suppression list, not the template editor.
Transactional and sequence sending
Developer-first, clean deliverability defaults, and per-message webhooks that let you keep delivery, bounce and complaint data in your own database rather than only in a vendor dashboard.
Limit: There is no drag-and-drop journey builder. You are writing code or wiring it to something that does.
Sequenced outreach
Built for exactly this shape of work — multi-step email with reply detection, so a prospect who answers drops out of the sequence automatically instead of receiving the next scheduled message.
Limit: Oriented toward one-to-one sales outreach rather than large recurring broadcasts, and it is not where you would run an ongoing newsletter.
All-in-one CRM and marketing
Keeps the pipeline, the calling, the calendar and the email in one place, which suits a small operation that does not want to integrate four tools.
Limit: Broad rather than deep, and the breadth invites automation you may not have consent for. Turn the SMS features off until permission is yours.
| Tool | Use it for | Where it stops |
|---|---|---|
| ResendTransactional and sequence sending | Developer-first, clean deliverability defaults, and per-message webhooks that let you keep delivery, bounce and complaint data in your own database rather than only in a vendor dashboard. | There is no drag-and-drop journey builder. You are writing code or wiring it to something that does. |
| MailshakeSequenced outreach | Built for exactly this shape of work — multi-step email with reply detection, so a prospect who answers drops out of the sequence automatically instead of receiving the next scheduled message. | Oriented toward one-to-one sales outreach rather than large recurring broadcasts, and it is not where you would run an ongoing newsletter. |
| GoHighLevelAll-in-one CRM and marketing | Keeps the pipeline, the calling, the calendar and the email in one place, which suits a small operation that does not want to integrate four tools. | Broad rather than deep, and the breadth invites automation you may not have consent for. Turn the SMS features off until permission is yours. |
No vendor on this list pays us. Our only paid relationship is disclosed site-wide on our affiliate disclosure.
Common questions
How long should warming up an aged list take?
Plan three weeks for the sequence itself and several months for the list as a whole. The five emails above do the concentrated work, and the standing confirmation link in your ongoing newsletter keeps converting quietly long after. Anything promising a re-consented list in a single campaign is describing a blast rather than a warm-up.
Should the first email ask people to confirm?
No, and this is the most common mistake. A reader who does not remember you has no reason to grant anything in the first message, so an early ask converts poorly and burns the contact. Two useful emails first, then the ask at around day nine, when opening your mail has already been worth their time.
What bounce rate should worry me?
Above three percent of attempted sends is where mailbox providers begin throttling. Distinguish the two kinds: soft bounces are mailboxes deferring and often resolve on their own, while hard bounces are addresses that do not exist and should be suppressed the moment they appear. A rising hard-bounce rate is the signal that matters.
What do I do with people who never open anything?
Retire them from active sending and move them to a low-frequency track carrying a standing confirmation link. Continuing to mail people who never engage lowers the deliverability of everything you send to everyone else, so the unresponsive part of a list is not free to keep. Smaller and reaching inboxes beats larger and filtered.
Can I run this sequence from a brand-new sending domain?
You can, but start smaller than feels necessary and build over a couple of weeks. A new or long-quiet domain has no reputation, and a sudden volume spike from an unfamiliar sender is exactly the pattern that triggers deferrals. Reputation is straightforward to build slowly and slow to repair once damaged.