Email to Reconnect With a Past Client: 10 Templates

The short answer
Reference the specific project you did together and roughly how long it has been, then give a real reason for writing now — relevant news, new capacity, or a new capability — instead of a generic 'checking in.' Keep it under 100 words, skip the apology for the silence, and end with one low-effort question rather than a pitch.
10 copy-paste templates for an email to reconnect with a past client — by reason, timing, and tone, plus the version for a project that ended badly.
On this page
- 01When should you send a reconnection email to a past client?
- 02What does a good past-client reconnection email contain?
- 0310 templates for reconnecting with a past client
- 04Template 1: The no-agenda check-in
- 05Template 2: The relevant-news hook
- 06Template 3: The capacity-opened note
- 07Template 4: The new-capability note
- 08Template 5: The referral ask that doubles as reconnection
- 09Template 6: The milestone or anniversary nudge
- 10Template 7: The result-you'd-care-about share
- 11Template 8: The direct availability offer
- 12Template 9: The saw-you-mentioned follow-up
- 13Template 10: The short reconnect question
- 14The hard version: reconnecting after a project that ended badly
- 15What do you do if there's no reply to a reconnection email?
- 16Sending these consistently without starting from a blank page each time
An email to reconnect with a past client works when it does two things a generic check-in does not: it names the specific project you worked on together, and it gives a real reason you are writing this week rather than any other week. Without both, the email reads as a template — because it is one, and the client can tell.
The gap between 'reconnecting' and 'cold outreach to someone who already knows you' is smaller than it feels when you are staring at the blank compose window. You do not need to apologize for the silence, explain where the year went, or justify why you are writing now. You need a specific memory, a specific reason, and one question small enough to answer in a sentence.
Below are ten templates for different reasons to reach out — a no-agenda check-in, relevant news, newly opened capacity, a new capability, and a referral ask that doubles as reconnection — plus the harder version of this: a client whose project ended on a sour note.
When should you send a reconnection email to a past client?#
The best trigger is not a calendar reminder — it is a real event. Something changed that gives you an honest reason to write: you saw news about their company, a relevant project opened up on your end, you shipped a capability that would have solved a problem they had, or enough time has genuinely passed that a plain 'thinking of you' note is warranted on its own.
Three to twelve months of silence is the sweet spot for most freelance and agency relationships. Under three months and it can read as pushy follow-up on unfinished business. Past eighteen months without contact, acknowledge the gap plainly rather than writing as if no time has passed — the client will notice the omission either way.
- A relevant news item about their company — funding, a launch, a hire, an award
- Your own capacity opened up after finishing another project
- You built or added a capability that solves a problem they mentioned last time
- A mutual contact or referral gives you a natural reason to write
- Enough time has passed (6–18 months) that a plain, honest check-in stands on its own
What does a good past-client reconnection email contain?#
Four things, in order: the specific project or engagement you shared, roughly how long it has been, the real reason you are writing now, and one question small enough to answer without scheduling a call. Skip the apology for going quiet — most clients do not experience your silence as a wrong that needs righting, and opening with one manufactures a problem that was not there.
The reason you are writing matters more than the writing itself. 'Just checking in' gives the client nothing to respond to because it asks nothing and offers nothing. 'I built the thing you needed on [LAST PROJECT] and didn't have at the time' gives them something concrete to react to, even if the answer is 'not right now.'

Do not lead with an apology for the silence
10 templates for reconnecting with a past client#
Each template below fills a different reason for writing. Pick the one that matches something actually true about your situation — the wrong template with the right facts still beats the right template with invented ones.
| Template | Use when | Tone |
|---|---|---|
| 1. No-agenda check-in | Real time has passed and you want to reconnect without an ask | Warm, no pitch |
| 2. Relevant-news hook | You saw news about their company or role | Congratulatory, specific |
| 3. Capacity-opened note | A project of yours just wrapped and you have room again | Direct, low-pressure |
| 4. New-capability note | You added a skill or service that solves a past problem | Informative, one ask |
| 5. Referral-that-reconnects | You want a referral, and asking is itself a good reason to reach out | Light, mutual-value |
| 6. Milestone nudge | An anniversary of the project or a round-number gap has passed | Reflective, brief |
| 7. Result-you'd-care-about | You have a case study or result relevant to their old problem | Proof-led |
| 8. Direct availability offer | You have specific open dates or slots and want to say so plainly | Practical, concrete |
| 9. Saw-you-mentioned follow-up | Someone else brought them up in conversation | Casual, natural |
| 10. Short reconnect question | You want the lowest-friction possible opener | Minimal, one line |
Template 1: The no-agenda check-in#
Use this when nothing specific has happened — you simply want to reconnect and let the client decide if there is a reason to talk further. The honesty of having no ask is what makes it land; do not smuggle a pitch into the last line.
Template 2: The relevant-news hook#
Use when you saw something real about their company — a launch, a funding round, a hire, an award. Name the specific thing; a vague 'saw you've been busy' defeats the purpose of using news as the hook.
Template 3: The capacity-opened note#
Use when a project of yours just wrapped and you genuinely have room. This one can carry a light ask because the reason is real and stated plainly rather than implied.
Template 4: The new-capability note#
Use when you added a skill, tool, or service since you last worked together that solves something you know they cared about. This is the strongest template for converting a reconnection into real work, because it answers a specific gap rather than restating your general availability.
Template 5: The referral ask that doubles as reconnection#
Use this when the honest reason you are writing is that you would like a referral — the request itself is a legitimate reason to reconnect, as long as you frame it as mutual rather than one-sided.
Template 6: The milestone or anniversary nudge#
Use when a round-number gap has passed — a year, two years — and that fact alone is a reasonable trigger for writing. This one leans on the milestone rather than manufacturing a different reason.
Template 7: The result-you'd-care-about share#
Use when you have a case study, result, or piece of work relevant to the exact problem they had when you worked together. This template leads with proof rather than a general update, which is what makes it land as useful instead of self-promotional.
Template 8: The direct availability offer#
Use when you have specific open dates and want to say so plainly rather than hint at general availability. Concrete dates convert better than vague openness because they give the client something to respond to with a yes or no.
Template 9: The saw-you-mentioned follow-up#
Use when someone else brought the client up in conversation — a mutual contact, a comment at an event, a mention in a group. This one works because it is honest about the trigger rather than pretending the timing is a coincidence.
Template 10: The short reconnect question#
Use when you want the lowest-friction possible opener — a single question, easy to answer from a phone in ten seconds. This works best as a first touch when you are unsure whether reaching out at all is welcome.
The hard version: reconnecting after a project that ended badly#
Every template above assumes a project that simply ended — no conflict, no unresolved friction. Reconnecting with a client whose project ended on a bad note is a different job, and using a cheerful template there reads as either oblivious or dishonest, both of which cost more goodwill than staying quiet would have.
The difference is one sentence, placed first: a plain, specific acknowledgment of what went wrong, without relitigating whose fault it was. Not an apology tour, not a defense — one sentence that shows you remember it accurately, then the same structure as any other template: a real reason for writing now, and one small question.
Do not over-apologize. A long apology asks the client to manage your discomfort about the situation, which is the opposite of what a genuine reconnection is for. State it once, plainly, and move on to the actual reason you are writing.
One sentence of acknowledgment, then move forward
What do you do if there's no reply to a reconnection email?#
Silence on a reconnection email is not necessarily a no — most people simply do not respond to emails that ask nothing specific of them, including the no-agenda ones. One follow-up is reasonable. A second, unanswered follow-up is the point to stop, since past clients owe you nothing and a third message starts to read as pressure rather than genuine reconnection.
- 1
Wait 10–14 days before any follow-up
A reconnection email is not urgent by nature, so a fast follow-up undercuts the low-pressure tone the first message set.
- 2
Send one short follow-up that adds something new
Reference the first email in one line, then add a small new detail — a specific date, a new piece of relevant news — rather than repeating the same message.
- 3
Stop after one follow-up with no reply
Leave the relationship open for the client to reach out later rather than sending a third message. A past client who wanted to respond has had two honest chances to do so.
Sending these consistently without starting from a blank page each time#
The templates above solve the writing problem once. The harder problem is remembering to send them at all — which past clients you have not contacted in six, twelve, or eighteen months, and which specific project and detail to reference so the email does not read as generic.
We build AI Emaily, an AI-native email client that connects to Gmail, Outlook, or standard IMAP. Its Context brain and per-client profiles hold the specifics of past engagements you have had, so a drafted reconnection email references the real project and timeline rather than a placeholder you have to fill in from memory. Copilot mode holds every draft for your review before anything sends — nothing goes out on its own.
Frequently asked
See it in AI Emaily
Keep reading

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.