# How to message former customers to win them back
> Reach out to former clients on LinkedIn with a low-pressure sequence that names why they left and what changed since, then asks for a short call.
- HTML: https://getkinlead.com/linkedin-outreach-for-former-customers
- Markdown: https://getkinlead.com/linkedin-outreach-for-former-customers.md

**Short answer:** To win back former customers on LinkedIn, find out why they left before you write anything. Then point at the change on your side that answers that reason, in a short message that names the gap in time. Keep the first ask small, like ten minutes of feedback on the new version.

## Audit why they left

A generic message lands badly on someone who left for a specific reason. If they cancelled because your software had no reporting module, a new pricing plan means nothing to them. Match what you have now to what pushed them out then.

Start with whatever record you kept. Old support tickets, the cancellation email, the notes your account manager wrote before the renewal call. The reason is usually in there, written in the customer's own words, and that wording is what your message should answer.

If nothing was written down, look at their LinkedIn profile. Their title, company size and remit may have moved. Someone who outgrew you two years ago might now sit at a company that fits your current product exactly, and that's a different conversation from the one you'd have had back then.

| | Reason they left | What the message should point at |
| --- | --- | --- |
| Price | A cheaper entry tier, or the fact that you dropped the onboarding fee. |
| Missing feature | The specific thing you shipped, named the way they'd name it. |
| Bad service | The person or process that changed, said plainly. |
| Outgrew you | The scale you handle now, with one example. |
| Budget cut | Their new budget cycle, timed to when they plan. |

## Decide who to contact first

Not every former customer deserves the same effort. Rank the list by two things: what they were worth to you and how well your current product fits what they do now.

Start with the ones who left over something you've since fixed. They have a concrete reason to look again. People who left over budget are worth a message, but the timing sits with them, so put them lower down.

- Left over a missing feature you shipped: write this week.
- Left over price: write when you have a tier or offer that fits.
- Left because they outgrew you: check their current headcount first.
- Left over a service failure: write only after the process has actually changed.

> If you can't name the reason someone left, you're not ready to write to them.

## Write the first message so it reads like a person

The first message has one job: get a reply. Leave the pitch, the deck and the calendar link out of it. People who left you are not cold prospects, and a cold script insults the history you have.

Open with the gap in time, then add something true about their business right now. That second part is the proof you looked at their profile before you typed. Keep the whole thing under about 80 words. Long messages read like memos.

If they don't answer, the second message can carry the specific change. Wait several days first. Two messages in the same week reads like a sequence, and they'll spot it as one.

- **you:** Hi Sarah, it's been a while since the Q3 project at Northwind. I saw your post about the UK expansion, that's a bigger operation than the one we worked on together. How's it going?
- **them:** Hi, good to hear from you. The UK move has been a lot. How are things with you?
- **you:** Busy in a good way. We rebuilt the reporting side last year, mostly because of the export problem you flagged back then. If you're still stitching those numbers together by hand, I can show you what it looks like now in about ten minutes.

> Never send the second message in the same week as the first. A gap of several days is what separates a person catching up from a sequence running.

## What to say once they reply

A reply gives you permission to talk about the old problem. Ask whether it's still there before you describe anything you've built. People's problems move, and a fix for an old issue can land as a non-answer today.

Be honest about the past. If the product was buggy or the handover was slow, say so in one sentence. Admitting the fault is what makes the claim that things changed believable. Skipping past it makes the whole message sound like marketing.

Then make the ask small. A former client will agree to ten minutes about their current setup far more readily than a formal demo with three people on the line.

If they say the problem is solved elsewhere, ask what they're using and why it works. That answer is worth more than the win-back, and it keeps the door open for the next time the contract comes up.

1. **Name the gap.** Say how long it's been since the contract or project ended. One clause is enough.
2. **Name the change.** Be specific: 'We rebuilt the export pipeline you complained about in March.'
3. **Show it working.** Point to one client in a similar position and what changed for them. Keep it to a sentence.
4. **Ask for ten minutes.** Frame it as feedback on the new version. That's a much easier yes than a sales call.

## Common mistakes to avoid

Most failed win-backs use a cold script on a warm name. The person remembers the contract, the kickoff call and the reason they left. A message that ignores all of that reads as a mail merge.

The other common failure is over-apologising. Two sentences of apology and the reader starts wondering why you're writing at all. One acknowledgement, then move to the reason for the message.

One more: don't send the same win-back message to everyone on the list. A person who left over a missing integration and a person who left because their budget got cut need different sentences. If the only difference between two messages is the first name, neither is ready to send.

**Weak message**

- Just checking in to see if you need our services again.
- So sorry I've been quiet for two years, things have been hectic.
- Attached is our new 20-page capabilities deck.

**Strong message**

- You're running operations at Acme now, which is a different shape of team than when we worked together.
- It's been about 18 months. I'm writing because we fixed the thing you left over.
- Here's a 60 second video of the feature you asked for in 2023.

## How to time the sequence

Win-back sequences run slower than cold outreach. The relationship buys you attention, and rushing it spends that attention fast.

Three touches is usually enough: the catch-up, the specific change, and one short close that gives them an easy way to say no. If none of them land, stop and come back when something material changes on your side.

Track what happened to each person. If someone replies and says the timing is wrong, put a date in the notes and honour it. Coming back a week after they asked you to wait is the fastest way to lose the contact for good.

| | Touch | When | What it carries |
| --- | --- | --- | --- |
| First | Day one | The catch-up and one true detail about their business |
| Second | Several days later | The specific change that answers why they left |
| Third | A week after that | A short close with an easy way to say no |

## Doing this with Kinlead

If the list of former clients is long, Kinlead keeps the personal parts intact while the sending runs itself. Import the LinkedIn profile URLs of your old customers from a CSV into a lead group, then build one campaign per reason they left.

Kinlead sends from your own LinkedIn account at a human pace, one action every five minutes inside the daily limits and send window you set. Connection notes can be AI-written under 200 characters and open with why that person became a lead.

Set the campaign to hand the conversation to you at the first reply. Win-backs need your memory of the account, and hand-off mode puts every reply in one inbox with interested ones first. Queued messages can be read and edited on the Actions page before they send.

1. **Import the list.** Bring former customer LinkedIn URLs in as a CSV and keep them in their own [lead group](/features/lead-groups-and-scoring).
2. **Split by reason.** One group per churn reason so each campaign points at the right change.
3. **Load your script.** Add your own win-back wording as the [sales playbook](/ai-sales-playbook-for-linkedin-outreach) so the tone matches a returning client.
4. **Choose hand-off.** Set replies to come to you at the first message, then edit queued drafts on the Actions page before they send.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Hand-off workflow](https://getkinlead.com/ai-sdr-hand-off-workflow.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**Should I apologise for not staying in touch?**

Don't over-apologise. One sentence acknowledging the gap is enough, then get to why you're writing now. A long apology makes the message about you.

**Do I offer a discount in the first message?**

No. Lead with the change that answers their old problem. A discount in the first line tells them the only thing that's different is the price.

**What if they left because of a bad experience with someone on my team?**

Say what changed, in plain terms. If that person has moved on or the process was rebuilt, name it. Vague reassurance about improvements won't land.

**How many times should I try before giving up?**

Three touches, then stop. Come back when something real changes, like a new feature, a new price or a new person in their role.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
