# How to message old leads about a new feature
> How to restart conversations with cold LinkedIn leads using a product update, with templates for each objection and a way to keep the message short.
- HTML: https://getkinlead.com/linkedin-messages-for-reengaging-old-leads-new-feature
- Markdown: https://getkinlead.com/linkedin-messages-for-reengaging-old-leads-new-feature.md

**Short answer:** Stop sending 'just checking in' messages to old leads. Lead with the specific update that fixes the problem they described, and explain why you thought of them. A lead needs a reason it's worth replying now, not a reminder that you exist.

## Why checking-in messages fail

Most attempts to revive a cold lead open with 'just checking in'. That message asks the lead to do all the work: remember who you are, remember what you discussed, and work out whether anything has changed since. Nothing has, so they don't answer.

A product update changes that. Something in the product is different, which means the reason they said no last time might not apply anymore. You aren't asking them to reopen the whole decision, only the part that moved.

The test is whether the update touches a problem they described in their own words. If it doesn't, no amount of good writing will fix the message, because there's nothing behind it.

**Checking in**

- Hi Sarah, just checking in to see if you're still interested in our software.
- Hi Mark, any updates on your end about the proposal from November?
- Hi Jane, wanted to see if this is still on your radar for Q1.

**Leading with what changed**

- Hi Sarah, we shipped the one-click Shopify export last week. You mentioned manual data entry was eating your Fridays, so most of that should be gone now. Want the 30 second version?
- Hi Mark, the Salesforce sync you asked about in July is live. It took us longer than I said it would. Do you still want to see it against your setup?
- Hi Jane, onboarding is two steps now instead of ten. That was the part you got stuck on in the trial.

## Decide whether the update is worth a message

Not every release earns a message. A new settings screen doesn't. A change to the thing the lead complained about does.

Ask one question before you write anything: if this lead saw the update, would their old objection still hold? If yes, leave them out. Sending anyway spends the one reason you have to get in touch, and the next update won't land either.

1. **Find the last real thing they said.** Open the thread and read the last two messages from them, not from you. The objection is usually sitting right there: budget, a missing integration, a rollout that stalled, or a champion who left.
2. **Connect the update to it in one sentence.** Write the sentence that links the update to that objection. If you have to stretch to make it fit, the update is not relevant to this lead and you should not send it.
3. **Sort the list before writing anything.** Group leads by objection, one group per message. Ten leads who stalled on setup get one message written for that problem, not ten variations of a generic one.
4. **Leave the rest untouched.** Leads whose objection the update doesn't touch stay in the list. Messaging them now means you have nothing to say when a real reason arrives.

> If the update doesn't answer the reason they stopped replying, the message is a check-in with a product name in it.

## Match the update to why the lead went cold

The angle changes with the objection. Send a feature announcement to someone who left over price and they'll read it as a broadcast, because that's what it is. Match the update to the thing that blocked them and the same message reads like a note from someone who was listening.

Some leads never gave a reason. They replied twice and vanished. For those, ask a real question about the silence instead of inventing an objection for them.

| | Why they went quiet | The angle | Example opener |
| --- | --- | --- | --- |
| Price | Cheaper path | We added a smaller plan that covers what you actually used in the trial. Same product, lower ceiling. Still worth a look? |
| Missing integration | The thing they asked for | The Tool sync you asked about in July is live. I said I'd tell you when it shipped. |
| Too complicated | Less setup | Setup is two steps now, down from ten. The part you got stuck on is gone. |
| Wrong timing | A different problem | When we spoke you were hiring for X. We now handle Y, which is what the hiring was for. Is that still the plan? |
| Champion left | New owner | I saw Name moved on. Who has picked up the project now? |
| No reason given | Honest question | You went quiet after the pricing call, which usually means something in it was wrong. Was it the price or the scope? |

## Write the message so it reads like a person

Three things belong in the message: what shipped, why you thought of them, and one question they can answer in a line. Everything else gets cut.

Describe the change the way you'd describe it to a colleague. 'The Shopify export is live' beats a sentence about being thrilled to announce anything, and it costs the reader less attention.

Make the ask small. After eight months of silence, 'worth a look?' is easier to answer than a request for thirty minutes on Thursday.

- **you:** Hi David, we added the automated reporting you said was missing back in September. You were spending most Friday afternoons on spreadsheets, so this should take most of that off your plate. Worth a quick look?
- **them:** Oh, actually yes. Is it a paid add-on or included now?
- **you:** Included in the standard plan since last week. I can send a two minute clip against your reporting setup if that's easier than a call.

```
Hi {first name}, {what shipped, in one line}. You mentioned {their exact problem} when we spoke in {month}, so this should {what it removes for them}.

{One question they can answer in a sentence}.
```

## What to do when they reply

A reply after months is usually a question, not a yes. They want to know whether the thing they cared about is fixed, or whether the price moved. Answer that first and leave the catching up for later.

If they reply with a new objection, treat it as a fresh lead rather than a revived one. Write the next message to the new objection and forget the old thread.

- Not a priority this quarter: ask which month to come back in, and write that date where you'll see it.
- Moved to another tool: ask what they picked and why. That answer helps your next hundred messages more than the lost lead does.
- No reply at all: don't send a second message about the same update. Wait for the next real reason.

1. **Answer the question they actually asked.** If they ask whether it costs extra, say yes or no in the first line. Detail comes after the answer, never before it.
2. **Skip the apology tour.** One line about the gap is plenty. A long apology makes the reply about you and gives them another reason to stop reading.
3. **Offer one specific next step.** 'Thursday or Friday for 15 minutes?' beats 'let me know when you're free'. A named choice is easier to accept than an open calendar.

## Doing this with Kinlead

If the old leads live in a spreadsheet, import them as a CSV of LinkedIn profile URLs into a [lead group](/features/lead-groups-and-scoring). One group per objection keeps the right message away from the wrong person.

Point a [campaign](/features/campaigns-and-send-windows) at the group and write the goal as the update itself, not 'reactivate old leads'. Kinlead drafts messages from that goal, the tone and an optional playbook, which is your own sales script. Paste in the objection language you collected above.

Set the campaign to hand off at the first reply. Reactivation conversations turn on details an AI doesn't have, like what went wrong in the original trial. Replies from every campaign land in one [inbox](/features/unified-inbox), with interested ones first.

1. **Group the leads by objection.** Import each list into its own lead group. Kinlead scores every lead from 0 to 100 against the customer you describe and drops the ones below the fit line, so the group stays clean.
2. **Write the goal as the update.** A goal like 'tell leads who stalled on setup that onboarding now takes two steps' gives the AI something concrete to work with. 'Reactivate old leads' gives it nothing.
3. **Read the queue before it sends.** Queued messages sit on the Actions page. Edit any draft where the reference to the old conversation is wrong, then let the rest send.
4. **Hand off at the first reply.** Set the reply mode to hand the conversation to you at the first reply. For a short list, pause the campaign and write the follow-ups yourself once they answer.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [See pricing](https://getkinlead.com/pricing.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Start a free trial](https://getkinlead.com/signup.md)

## Common questions

**How long should I wait before messaging an old lead?**

Wait until you have something specific to say. A message every month without a new reason reads as spam, and the lead stops opening your notes. If nothing has changed in the product, there's no message to send.

**Should I send a new connection request if we're not connected?**

Yes, and keep the note short. Say what shipped and which problem of theirs it fixes, then let them decide whether to accept.

**What if they don't reply to the feature update?**

Leave it. A specific answer to a problem they described is the strongest reason you'll have, and if that doesn't get a response they're either out of the market or already using something else.

**Can I send the same update to my whole old lead list?**

Only if the update solves the same problem for all of them. Usually it doesn't. Split the list by objection and send the version that fits each group.

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