Email Template for Reconnecting With Old Clients

The right email template for reconnecting with old clients starts before the drafting. First, answer one question: should you write to this person at all?

That sounds obvious, but most reconnection advice skips straight to templates and leaves you with a beautifully worded email going to someone who filed a complaint two years ago, or whose project you are not actually sure went well. The template is the easy part. The hard part is the list.

This guide gives you four copyable templates for different reconnection situations, then walks through a realistic three-contact triage — one person who is fine to approach, one who needs a phone call first, and one who should never receive an outreach email — so you can see how the decisions get made before the drafting even starts.

Your turn · A one-minute experiment

Which action do you take for each contact?

Fictional one-minute exercise. All contacts, CRM records, and project details below are invented for practice.

The situation

FICTIONAL RECONNECTION SCENARIO Agency: Hartwell Studio (fictional) CRM: fictional platform called ClientBase Decision rules (from this article): — ELIGIBLE FOR EMAIL: Documented closed project, no open disputes, no opt-out on record, genuine specific reason to reconnect. — PHONE CALL FIRST: Complaint or unresolved issue logged in CRM; do not send templated email until issue is resolved and documented. — EXCLUDE: Opt-out recorded at any time. No email, no call for outreach purposes. Three contacts from ClientBase: Contact 1 — Simone Adler, Adler & Marsh CRM: Final invoice paid, project closed 18 months ago, no complaints, no opt-out. You have since added a service she asked about during the original engagement. Contact 2 — Carl Brentwood, Brentwood Ops CRM: Complaint logged in the final project month, resolution field reads "pending." No opt-out on file. You would like to re-engage the account. Contact 3 — Yuki Tanaka, Tanaka Retail CRM: Opt-out recorded 9 months ago. Project closed cleanly before that. You believe she might welcome news about a new service.

Choose what you would do, then open it to see the reasoning. You can explore every option.

A · Send Simone an email, call Carl first, exclude Yuki.

This is correct. Simone meets every eligibility criterion: closed project, no dispute, no opt-out, and a specific service that connects to her documented interest — exactly the Contact A profile the article describes as appropriate to email. Carl has an unresolved complaint in his CRM record; the article is explicit that 'an email sequence — even a thoughtfully written one — is the wrong tool here' and requires a phone call led by someone with authority to acknowledge the issue. Yuki opted out nine months ago. The article states that a documented opt-out must simply be respected regardless of how relevant the reason to reconnect might feel.

B · Send all three an email using the honest-pitch template.

This violates two rules simultaneously. Carl has an unresolved complaint that disqualifies him from any templated outreach until the issue is resolved and documented. Yuki has an opt-out on record; the article cites CAN-SPAM's requirement to honor opt-out requests and states plainly there is no amount of relevant reason that changes this. Sending to all three would risk a complaint response from Carl and a compliance problem with Yuki.

C · Exclude all three until CRM records are manually re-verified.

Simone's record is already clean and fully documented. The article's eligibility check requires a source record, an honest reason, and no opt-out — all three conditions are met for Simone. Withholding her email while re-verifying what is already confirmed adds delay without a supporting rule. The triage framework exists precisely so that clean contacts like Simone can move forward while Carl and Yuki are correctly handled differently.

D · Call Carl, email Simone, and email Yuki with an unsubscribe link included.

Adding an unsubscribe link does not override a prior opt-out. The article states that Yuki's documented opt-out must be respected and that no amount of relevant reason changes this. The CAN-SPAM requirement cited in the article is about honoring removal, not about giving someone another chance to opt out again. Yuki must be excluded from outreach entirely, not contacted with a workaround mechanism.

A clean CRM record unlocks an email. An unresolved complaint routes to a phone call first. An opt-out excludes the contact permanently — no template, no workaround, no exceptions.

Step Zero: Sort Your Past Clients Before You Draft Anything

Pull your past client list. For each contact, you need three things before deciding to reach out:

The interaction source — an actual record (a CRM entry, a signed proposal, a closed invoice) confirming the relationship existed and how it ended.
An honest reason to reconnect — something real, not "I wanted to check in." If the real reason is that you want more business from them, that is fine; say so plainly. Disguising a sales email as a friendly catch-up is the fastest way to lose trust.
Opt-out status — anyone who has previously asked to stop receiving email from you must not receive this email, full stop.

Once you have those three things, you can sort each contact into one of three groups.

The Three-Contact Triage (Illustrative Example)

The following three contacts are fictional. They are designed to show the decision logic — nothing here is a real client or a real project outcome.

Contact A — Maya Osei, Osei Interiors ✅ Suitable to contact

Source: Closed project record in CRM; final invoice paid; no open tickets.
Reason to reconnect: You have started offering 3D rendering walkthroughs, which she specifically asked about during the original engagement and you could not deliver at the time.
Decision: Appropriate. The past project is documented and unambiguous. The reconnection reason connects directly to something she expressed interest in. One email, one follow-up if no reply, then stop.

Contact B — Derek Paulsen, Paulsen & Co. ⚠️ Unresolved complaint — personal attention required

Source: CRM shows a complaint logged in the final month of the project; the resolution field reads "pending."
Reason to reconnect: The account is large enough that you'd like to re-engage.
Decision: Do not send an automated or templated email. Contact Derek by phone first, led by a person with authority to acknowledge and resolve the original issue. An email sequence — even a thoughtfully written one — is the wrong tool here. Remove this contact from any outreach list until the complaint is resolved and documented.

Contact C — Rachel Tao, Tao Creative 🚫 Do-not-contact

Source: CRM shows an opt-out recorded fourteen months ago.
Reason to reconnect: You would like to, but she asked to stop receiving email.
Decision: Excluded. No amount of relevant reason or good writing changes this. The CAN-SPAM Act requires that you honor opt-out requests within 10 business days and that removal remains effective for at least 30 days after the email was sent — a documented opt-out must simply be respected.

Only Contact A gets an email. The templates below are built for contacts like her.

Four Templates You Can Copy Today

Each template is short. That is intentional. A reconnection email is not a newsletter or a proposal; it is an opening to a conversation. If you find yourself writing three paragraphs of preamble, that is usually a sign you are not sure why you are reaching out.

Use the one that honestly fits your situation.

Template 1 — The Check-In (Warm Prior Relationship)

Subject: Quick check-in — [first name]

Hi [first name],

It's been a while since we wrapped up [brief honest description of the project — e.g., "the brand refresh last spring"]. I wanted to see how things have been going.

Is there anything on your plate right now where a conversation might be useful? No agenda; if the timing's wrong just say so.

[Your name]

When to use it: You have a solid record of a completed project and a genuine reason to believe the person would welcome contact. The subject line is low-key because you are not trying to manufacture urgency.

When not to use it: When you actually do have a business agenda. Use Template 2 instead.

Template 2 — The New Relevant Service (Honest Pitch)

Subject: Something new that might be relevant — [first name]

Hi [first name],

I hope things are well. We worked together on [project description], and I've been thinking about it lately because we've since added [specific service] — which is something you asked about at the time.

I don't know whether the timing is right for you, but I didn't want to assume it wasn't. Would a short call make sense?

[Your name]

When to use it: You have a documented past project and the new service connects directly to something the client expressed interest in. The business intent is transparent.

The key difference from Template 1: The subject line signals there is something new. Do not use a low-key check-in subject when you are pitching; it feels deceptive when they open it.

Template 3 — The Useful Resource

Subject: [Topic] — thought of you

Hi [first name],

I came across [specific real resource — e.g., "the updated accessibility guidelines for commercial interiors"] and thought it might be relevant given the work you're doing on [their known focus area].

No ask attached. If it's useful, great; if not, feel free to ignore it.

[Your name]

When to use it: You have a resource that is genuinely useful to this person based on documented knowledge of their work — not just a pretext to get back in their inbox.

A hard rule: The resource must be real and specific. A link to a blog post you wrote about a topic they might vaguely care about is not a useful resource; it is a thinly disguised marketing email. If that is what you are sending, use Template 2 and be honest about it.

Template 4 — The Honest Feedback Request

Subject: A quick question about our work together

Hi [first name],

I've been reflecting on [project description] and wanted to ask, honestly: was there anything we could have done better? We have since changed [specific thing you changed], and I'm curious whether that would have made a difference.

If you'd rather not, completely understood.

[Your name]

When to use it: You want genuine input and you are prepared to hear critical feedback. This is not a tactic for getting a positive testimonial; if that is the goal, ask for a testimonial directly.

What a Sample Email to Reconnect With Old Clients Actually Needs to Do

A sample email to reconnect with old clients tends to be shown in isolation, as if the words alone do the work. They do not. What actually determines whether the email lands well is:

The eligibility check that happened before it was drafted
The honest reason stated in the email itself
The one clear optional next step (not three, not a calendar link and a phone number and a reply request)
Who is going to handle the reply if the person says yes

That last point is easy to skip in the template phase and expensive to skip in reality. Before you send any reconnection email, identify the person who will respond when a reply comes in that sounds like interest. That person needs to know the history of the relationship well enough to pick up the conversation without making the client repeat themselves.

Bounded Follow-Ups and When to Stop

A reconnection sequence is not a drip campaign. The outer limit for a past-client reconnection is:

Email 1: The reconnection email itself.
Email 2: One follow-up, sent roughly five to seven business days later if no reply, referencing the first email briefly.
Email 3: A short final note, one more week out, making it clear this is the last message.

Then stop. If someone has not replied after three thoughtful emails, they are not interested right now, and continuing to send is the kind of behavior that gets you marked as spam. Gmail's sender guidelines make this operationally concrete: keeping spam complaint rates below 0.30% is a deliverability requirement, not a courtesy — and one person marking your email as spam is one too many in a small-volume reconnection campaign.

Hard stop conditions:

Any reply that says "please don't email me" — remove immediately and document it.
Any bounce indicating the address is no longer valid — do not retry.
Third wave sent with no reply — the sequence is over for this contact.

Deliverability: The Infrastructure Problem Nobody Wants to Think About

Even a perfectly written reconnection email fails if it lands in the spam folder. Before you send anything, confirm:

SPF, DKIM, and DMARC are configured for the domain you are sending from. Google's email guidelines require these for bulk senders and strongly recommend them for all senders. Sending reconnection emails from an unauthenticated domain is asking for delivery problems regardless of what the emails say.
Your domain is warmed. A domain that has not sent email recently and suddenly starts sending outreach looks suspicious to filtering systems. If this is a new sending domain, warm it gradually before running reconnection campaigns.
Addresses are verified before sending. An email address in your CRM from two years ago may no longer be valid. A bounce rate that spikes on a small campaign causes disproportionate reputation damage. Verify before you send.
One-click unsubscribe is in place. Gmail's guidance explicitly requires that marketing and subscribed messages support one-click unsubscribe and include a visible unsubscribe link in the body.

A Note on Legal Requirements

Reconnection emails exist in a legally meaningful category. The CAN-SPAM Act covers email whose primary purpose is advertising or promoting a commercial product or service. If you are reaching out to tell a past client about a new service, that is a commercial email under the Act — meaning you must include a physical mailing address, a clear opt-out mechanism, and an honest subject line, among other requirements.

A pure, relationship-maintenance check-in may qualify as a transactional or relationship message, which has fewer requirements — but the distinction depends on the actual content and primary purpose of the email, not on what you call it.

If your clients are based in the EU or Canada, GDPR and CASL apply additional consent requirements that are separate from and more stringent than CAN-SPAM in many cases. The right move before running any campaign to international contacts is to verify your specific situation with legal counsel familiar with business email law.

This article is a practical guide to drafting good reconnection emails. It is not legal advice.

The Approval Step That Gets Skipped

Here is a step that most guides leave out: before the first email goes to any client, a person who knows the relationship history should review and approve the draft.

This is not bureaucratic overhead. It is how you catch the case where the CRM record shows a closed project but someone on your team remembers a detail that is not written down — a late delivery, a pricing disagreement that was smoothed over verbally, a client who expressed satisfaction at the time but who has since had a change of circumstance. A template passes through spell-check; a human reviewer catches context.

The AI email reply guide on this site works through exactly this decision framework: when to send a draft as-is, when to edit it, and when to hand it to a person with authority. The same principle applies here. Good wording does not substitute for a verified fact or a person with authority to make a promise.

Running This at Scale: Where Beep Beep Fits

If you have a modest list of eligible past clients and a comfortable amount of time, the manual approach above works fine. If you have a Salesforce CRM with hundreds of past clients, verifying eligibility manually before each campaign is a recurring time sink.

That is the gap Beep Beep, Splice Work's automated email follow-up agent, is designed for. According to the published product description, Beep Beep pulls contacts from Salesforce first, researches each company's current website to write a personalized sentence that is specific to that recipient, verifies every address through NeverBounce before sending, executes three follow-up waves timed to 8 a.m. in each recipient's own timezone, and then stops. It does not send wave four. Anyone who asks to come off the list is removed immediately, without a separate step from you.

The part that matters for reconnection campaigns specifically: nothing happens until you approve it. The campaign card in Slack shows the targeting, contact count, and any data credit ceiling before a single email is drafted or sent. If a reply comes in that sounds like genuine interest, Beep Beep flags it in Slack and hands the conversation to a human — it does not try to negotiate, price, or book a meeting on your behalf.

That last point is worth stating plainly: an automated follow-up sequence is useful for getting a reply; a person is required for everything that comes after.

One limitation to be honest about: Beep Beep is built around Salesforce as the CRM source. If your past client records live in a different system, you would need to discuss what a setup looks like for your stack. And as the agent page itself notes, inbox placement cannot be known without a seed test — the system reports what it can actually count.

If your reconnection outreach is mostly manual and ad hoc, the templates above are enough to start today. If you are working from a CRM with enough contacts that scheduling and sequencing becomes its own job, it is worth looking at what Beep Beep actually does before building the manual infrastructure yourself.

Try It Now

Pick one past client from your list. Find a CRM record, closed invoice, or signed document that confirms the relationship ended cleanly. Write down the actual reason you want to reconnect — the real one, including the business reason if there is one. Then choose the template above that honestly fits that reason and draft it with the specific project name filled in.

Before you send it, hand it to one other person in your business and ask: "Does anything in this email claim something we can't verify?" If the answer is no, it is ready to review for send. If the answer is yes, revise before approving.

That is the whole process. The template is the easy part.