# How to message leads who ghosted after a demo
> Restart stalled LinkedIn conversations after a demo without check-in messages. Use specific scripts, a simple sequence and clear stop rules for good.
- HTML: https://getkinlead.com/linkedin-messages-for-stale-demo-leads
- Markdown: https://getkinlead.com/linkedin-messages-for-stale-demo-leads.md

**Short answer:** Stop asking for updates. Send one message that gives the prospect something useful or asks a specific question about the problem you discussed in the demo. Then follow a short sequence, make the next step easy to answer, and close the loop if they stay silent.

## Why your current follow-ups get ignored

Most follow-ups after a demo ask the prospect to do work. A message like 'Did you get a chance to review the proposal?' reminds them of an open task. They may want the product and still skip the reply because answering takes effort and gives them nothing new. The message also puts you in the same pile as every other salesperson who sent a reminder that week.

Silence after a demo usually means one of a few things: the project moved down the list, another person needs to weigh in, the budget changed, or they are busy and the message got buried. A check-in does not help you tell those apart. A specific message does. It gives the prospect a reason to reply beyond politeness.

A better reminder will not fix this. You need a different kind of message. You want the prospect to read it and think 'that is useful' or 'that is easy to answer.' If the message only asks for an update, it fails both tests.

**Messages that ask for an update**

- Just checking in on the proposal.
- Any update on the internal discussion?
- Did you get a chance to review what I sent?

**Messages that give a reason to reply**

- You mentioned the manual export was slowing down reporting. I found a setting that removes that step. Want the two-minute walkthrough?
- I wrote a short note on the integration question from our demo. Should I send it to you or to your ops lead?
- It sounds like the Q3 deadline may have moved. Is this still active for this quarter?

## Pick the reason for the silence before you write

Your next message should match the likely reason the person went quiet. If they were engaged in the demo and asked detailed questions, send something useful about that problem. If they went quiet after you sent pricing, ask a direct priority question. If you are unsure, use a short permission ask.

Keep the message easy to answer on a phone. Use one question, one link, or one choice. Do not attach a deck and ask for a call in the same message. The prospect should not need to open a laptop to reply.

The table below gives you four common reasons and a line for each. Pick one. Do not combine them into a long message that covers every possibility.

| | What likely happened | What to send | Example line |
| --- | --- | --- | --- |
| They got busy | A useful detail tied to the demo | You mentioned the reporting delay. I found a setting that skips the manual export. Want the clip? |
| The project paused | A permission ask | Usually silence means this moved down the list. Is that what happened? |
| Another person needs to approve | A question about the next step | Should I send the integration notes to you or to your ops lead? |
| They lost interest | A final message | I will stop here for now. If the reporting project comes back, reply and I will pick it up. |

## A four-message recovery sequence

Space the messages out. The point is to stay useful without filling their inbox. If you send three messages in two days, you look anxious. If you wait a month, the demo is a distant memory. A simple sequence keeps you in the conversation without making the prospect feel chased.

Use the sequence below as a default and adjust it to the deal. A warm prospect who asked good questions can get the useful message sooner. A prospect who went quiet after pricing needs the priority question first. The order matters less than the reason for each message.

1. **Send one useful message.** Wait 3 to 5 business days after the demo. Reference one problem they mentioned and give them something concrete: a setting, a short note, a timeline, or a question about the detail they cared about.
2. **Ask a priority question.** Wait about a week. Give them a graceful way to say the project is paused. 'Usually when I don't hear back, it means this moved down the list. Is that the case?' is enough.
3. **Offer a smaller next step.** If they reply but do not commit, lower the ask. Send the notes, answer one technical question, or offer to talk to the person who needs to approve the work.
4. **Close the loop.** After two weeks of silence, send one final message. Say you are closing the file for now and they can reply when the project is active again. Then stop.

> If you cannot think of anything useful to send, wait until you can. A reminder with no new information is easy to ignore.

## Scripts you can adapt today

Use the prospect's words from the demo. If they said 'the export takes forever,' do not write 'optimize your data workflow.' Write 'the export.' Specific language shows you were listening and makes the message feel like a continuation of the demo.

Keep the first line about them. Do not open with an apology or a line about your week. The message should be short enough to read in the preview. If the preview cuts off before the point, rewrite it.

The thread below is a realistic exchange. Notice that the first message offers a small piece of help and lets the prospect choose the next step.

- **you:** Hi Sarah, you mentioned the manual export was eating into reporting time. I found a setting that removes the export step. Want me to send a two-minute clip?
- **them:** Yes please. Sorry for the silence, it has been a busy week.
- **you:** No problem. Here is the clip. If it solves the export issue, I can send the setup steps.

```
Hi {{first_name}}, you mentioned {{specific_problem}} in our demo. I found {{specific_thing}} that may help with that. Want me to send it over?

If the project is paused, no problem. Just reply 'paused' and I'll check back later.
```

## What to say when you have no new information

Sometimes you have nothing new to send. The demo was fine, the proposal is out, and you have no insight, no update, and no useful link. In that case, do not invent a reason to message. Use a short priority check or wait until you have something real.

A priority check works because it names the silence without guilt. It gives the prospect a way to say 'paused' or 'not now' without writing a long explanation. That reply is useful even when it is not a yes.

**Weak priority check**

- Just following up again.
- Any news on this?
- I don't want to keep bothering you, but did you decide?

**Strong priority check**

- Usually when I don't hear back after a demo, it means the project moved down the list. Is that what happened?
- Should I close this for now, or is it still active for this quarter?
- Is the next step with you or with someone else on the team?

## When to stop and when to move to email

Stop after the close-the-loop message. If they reply later, pick the conversation up. If they do not, keep them out of your active follow-up list. Repeated messages after a clear close look like you are not listening.

Moving to email can help when the conversation needs a document, a calendar hold, or a longer explanation. Do not paste the same message into both places. Use LinkedIn for the short question and email for the detail. If you send the same note on both, it feels like a campaign.

Track the reason each lead went quiet. If five people from the same company go silent after pricing, the problem may be the price or the timing rather than your follow-up. If people reply to the useful message but not the call request, your next step is too big.

> Close the loop in writing. A lead who knows you will stop is more likely to reply later than one who expects endless reminders.

## Doing this with Kinlead

Kinlead can hold the ghosted leads in one place. Import a CSV of LinkedIn profile URLs into a [lead group](/features/lead-groups-and-scoring), then point a campaign at that group when you want to restart the conversation.

Set the campaign goal and tone, and add your own sales playbook so the AI writes from your wording. You can read and edit queued messages on the Actions page before they send. Use a [send window](/features/campaigns-and-send-windows) set to business hours in the lead's time zone, and choose hand-off mode so the first reply comes to you.

## Related

- [Follow-up cadence playbook](https://getkinlead.com/ai-sdr-follow-up-cadence-playbook.md)
- [Reply modes compared](https://getkinlead.com/ai-sdr-reply-modes-comparison.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**How long should I wait before the first follow-up after a demo?**

Wait 3 to 5 business days. That gives them time to talk to their team without making you look like you forgot the conversation. If they asked for something specific, send it sooner.

**Should I apologize for following up?**

No. Apologizing makes the message about your discomfort. Be direct and useful instead.

**What if they reply and say the project is paused?**

Ask when it makes sense to check back, then put a note in your calendar. Do not keep sending value messages every week while it is paused.

**Can I send the same restart message to every ghosted lead?**

No. Use the demo notes to pick one detail for each person. A message that could have been sent to anyone reads like a campaign.

**When should I move to email?**

Move to email when you need to send a document, a timeline, or a longer answer. Keep LinkedIn for the short question that gets the conversation moving again.

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