AI SDR playbook for win-back campaigns
Use LinkedIn to win back former customers. Segment by why they left, write a memory trigger, and handle the 'we already have a tool' reply without pitching.
Get startedShort answer
Win-back campaigns on LinkedIn work when you remind a former customer of a specific result they got, then ask about the problem they have now. You do not need to explain the product from scratch. Segment by why they left, keep the first note short, and let the conversation earn the pitch.
Start with the reason they left
Win-back lists get messy because most teams only have a billing date and a cancellation note. That is not enough to write a useful message. Before you touch LinkedIn, pull the last year of closed-lost and churned accounts from your own records. Add the reason if anyone wrote it down. If nobody did, use the last support ticket and the person's title at the time.
Group former customers by the reason they stopped paying. A person who left because their company shut down needs a different note from someone who switched to a cheaper tool. A person who changed jobs needs a different note from someone who still has the same problem but a new budget owner.
Keep the first list small. Fifty to a hundred names is enough to test your message. A list of two thousand names with the same generic note will burn through your LinkedIn account and teach you nothing.
The migrator
- Segment
- Used your product at a previous company and now has a new role.
- What you know
- Ask how the new team handles the problem you solved for them before.
The churner
- Segment
- Left for a competitor or a cheaper plan.
- What you know
- Name the tradeoff they accepted and ask if it still holds.
The ghost
- Segment
- Stopped logging in years ago and never gave a reason.
- What you know
- Show one concrete change since they last used the product.
The champion
- Segment
- Liked the product but could not get budget.
- What you know
- Ask if the budget or the priority has changed.
Write a memory trigger, not a reunion
A memory trigger is one sentence that proves you remember the work, not the account record. Weak: 'I saw you used Acme Cloud at Northwind.' Better: 'You were running the weekly inventory report at Northwind when you used Acme Cloud.' The second version gives them a scene to recall. It also shows you are not scraping a database and blasting a template.
Use the person's old company or the workflow they ran. Do not mention the exact cancellation date. Dates feel like a collections call. If you only know the company and the product, say that. Do not invent a detail to sound personal.
Then connect the memory to their current job. If they were a manager and now run a department, the problem is bigger. If they moved to a smaller company, the problem may be simpler. The message should show you understand the change.
Weak memory trigger
- Hi Sarah, I noticed you used our tool at Northwind. We have changed a lot since then. Are you free for a call?
- Looks like you left Acme two years ago. Want to see the new version?
Strong memory trigger
- Sarah, you were running inventory reporting at Northwind when you used Acme. Now that you are at Lakeside, is that report still a weekly spreadsheet job?
- Sarah, you used Acme at Northwind before the 2022 rebuild. The import step you complained about is gone. Is that still the part that slows your team down?
Send the connection request without the pitch
The connection request is not the place for a demo ask. Use the note to remind them where you met, then stop. If they accept, the first message can carry the reason you are reaching out. If they do not accept, you have lost nothing and you have not pitched a stranger.
Keep the note to two sentences. Do not use it to list features. One shared detail and one light question is enough.
After they accept, send the first message within a day or two. Do not wait a week. The memory is fresher and the conversation feels natural.
- 1
Write the note from the shared history
Name the old company or the workflow they ran. Example: 'Sarah, you ran inventory reporting at Northwind when you used Acme. I'm curious how Lakeside handles it now.' Keep it short.
- 2
Ask one question in the first message
Do not attach a calendar link. Ask whether the old problem still exists. Example: 'Now that you are at Lakeside, is the weekly inventory report still a spreadsheet job, or did you replace it?'
- 3
Send one follow-up with a specific change
Wait four or five days. Share one product change that maps to their old complaint. Example: 'The import step you disliked is gone. It now reads the CSV directly. Want a two-minute look?'
- 4
Stop after two follow-ups
If they do not reply, withdraw the request or leave them alone. A former customer who is not ready now may be ready next quarter. Do not keep sending the same note.
If a former customer does not accept your connection request after two weeks, withdraw it. A pending request that sits for months makes your account look careless and reduces room for new invites.
Handle 'we already have a tool' without a feature fight
A former customer will often say they already use something else. That is not a rejection. It is a status update. Your job is to find out whether the problem that made them leave is still costing them time or money. If it is, you have a conversation. If it is not, you have a polite exit.
Do not run down the competitor. Ask about the workaround. People often stay on a tool because switching is annoying, not because the tool is good. A question about the workaround is harder to brush off than a claim about your product.
If they mention a bad experience with your support team, agree with them. Do not defend the old process. Say what changed and who owns it now. If nothing changed, say that too. Former customers can tell when you are reciting a script.
Example
- Prospect
We're on Northstar now. It's fine.
- You
That makes sense. Most teams that left us for Northstar wanted the lower monthly cost. Is the reporting still manual on your side, or did that get easier?
- Prospect
Reporting is still a pain. We export to a spreadsheet every Monday.
- You
That was the complaint we rebuilt around. The new version pulls the Monday numbers without the export. I can send a two-minute video, or we can skip it if the spreadsheet is not a real cost.
- Prospect
Send the video.
Write the follow-up before you need it
Win-back campaigns die because the first message gets a polite no and the seller stops. A former customer who says 'not now' is warmer than a cold lead who says nothing. Put them in a light follow-up sequence that runs for a few weeks, then stop.
Use three touches at most. The first is the memory trigger. The second is a specific change that maps to their old complaint. The third is a clean close: 'I'll stop here. If the reporting problem comes back, reply to this thread.' That close gets more replies than another feature list.
Do not send the same message on every channel. If you only have LinkedIn, keep it on LinkedIn. If you have their email from a past contract, use it once and then respect the answer. A win-back campaign is not a reason to spam every contact record you have.
Paste this job
Sarah, you were running the weekly inventory report at Northwind when you used Acme. Now that you are at Lakeside, is that report still a spreadsheet job? The import step you disliked is gone. It reads the CSV directly. If the report is still a real cost, I can send a two-minute video. If not, no follow-up.
Track the reason they left
Most teams track replies and meetings. For win-back, track the reason the person left. If every reply comes from the champion who lost budget, your message is working for that group and failing for the others. That is more useful than a single reply rate.
Keep a simple note on each lead: old company, old plan, reason they left, current role, and the one problem you asked about. When they reply, you will not have to search through old tickets while they wait.
Review the list every week. Remove people who asked you to stop. Remove people who left for a reason you cannot fix. Add people who changed jobs, because a new role often means a new budget and a new problem.
Doing this with Kinlead
If your win-back list lives in a spreadsheet, export the LinkedIn profile URLs and import them into a lead group in Kinlead. A campaign can point at that group, so you do not have to rebuild the list for every message. You can also export leads to CSV when you want to keep your own record.
Kinlead writes messages from the campaign goal, tone, and an optional sales playbook. For win-back, set the playbook to the memory trigger and the old complaint. Use hand-off mode so the AI stops at the first reply and you take over. Kinlead sends at most one action every 5 minutes inside the daily limits and send window you set. It does not warm up accounts, and it cannot guarantee LinkedIn will not restrict an account. See lead groups and scoring.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? AI SDR playbook for win-back campaigns.md