Skip to content
OutreachGuy

Reaching out to old leads: who belongs on the list?

Choose old leads with a reason to hear from you. Use a selection worksheet, check the last conversation, and write a message that explains why you are back.

An orange bookmark selects a correspondence card from a charcoal archive folder.
In this article

Start with a reason to reopen the conversation. A buyer asked you to return when their project restarted. A property now matches an old enquiry. A feature they needed is available. “We have a large old list” is a description of your CRM, not a reason for someone to hear from you.

Before writing a message, separate the people you can reasonably contact from those who need review or should be excluded. The examples below are fictional.

Read the last answer before choosing the next action

A lead marked “lost” may have chosen a competitor, postponed the purchase, or asked never to be contacted again. Those are different situations. Keep the original response alongside the label.

Last known situation Suggested decision What to check
“Ask me again when the new office opens.” Consider including Has the office opened, and is the same person responsible?
Waiting for a feature you have now released Consider including Does the released feature actually meet the stated need?
“We signed a two-year contract elsewhere.” Hold for review Is there a relevant review date or a new enquiry?
Unresolved service complaint Route to the owner Is a sales message appropriate before the issue is resolved?
Asked you to stop contacting them Exclude Is the contact preference visible to everyone using the list?
No record of where the contact came from Exclude pending review Can you establish the relationship and contact preferences?

This is an operational selection method, not a substitute for the rules that apply to your business and market. Do not treat a historical email address as standing permission to run a new campaign.

Build a small, inspectable list

Download the old-lead selection worksheet. The sample rows are labeled fictional. Replace them with your own records and keep sensitive details in the appropriate system.

Record the last reply, its date, the reason to return, the source of that reason, contact preferences, and the next owner. Add a clear decision: include, exclude, or review. An empty cell should not silently count as approval.

Read a handful of included records before sending. If you cannot explain why each person belongs in the group, tighten the selection. A large list can wait while you establish that the first few records are usable.

Say why you are back

Suppose a buyer previously needed an export format you did not support. The feature has now shipped and someone has checked that it covers their specific request.

Subject: The export format you asked about

Hi Morgan,

When we spoke in June, you needed a separate row for each location in the monthly export. That option is now available. Is that still something your team needs, or have you settled on another approach?

Alex

The message gives Morgan context without pretending that the old opportunity is still active. Link to the relevant documentation if useful. Do not say “we built this for you” unless that is true.

If you do not have a concrete change, an agreed check-in may still be a reason to write. Use the actual agreement, as in following up next month.

Let a changed situation end the sequence

If Morgan says the project is cancelled, record that. If someone else owns the work, ask whether an introduction would be appropriate. If they want to revisit later, agree on a date rather than dropping them into an indefinite reminder cycle.

If there is no response, use the limit you set for this group. Do not interpret silence as permission to search for a personal number or try every channel you can find.

Review the selection as well as the message

After the first group, inspect wrong-person replies, outdated details, declines, and useful conversations. A polite email cannot fix a list whose premise is wrong.

Keep the selection rule and exclusions with the campaign so another colleague can understand them. The lead follow-up workflow shows the other context to prepare before giving OutreachGuy the job.

Put the example to work.

See the inputs and handoffs for this workflow.

Explore this use case