bravabase
Start for free

7 LinkedIn follow-up message examples to copy and adapt

Good LinkedIn follow-up message examples all do the same thing: they pick up the conversation where it left off and move it one step forward. Find the situation below that matches your last exchange, copy the template and replace every bracket with the real details.

Want all seven in one place? Download them with their notes as a plain text file.

Pick the reason for your follow‑up

A promised resource, an open question and a proposal review each need a different message. Start from the reason you’re writing:

If none of these fits, write down why you’re getting in touch before you pick any wording. If you can’t, you may not need to send anything yet.

1. Deliver a resource you promised

They asked for a checklist, example or other resource, and you said you’d share it.

Hi [name] — here’s the [resource] we discussed: [link]. The section on [specific issue] relates to your question about [context]. Let me know if anything needs explaining.

Make it work: name the resource, check the link opens for them, and point to the section that answers their question.

Avoid: turning a resource into a sales call. They asked for a checklist, not a pitch.

2. Answer an open question

They asked something you needed time to answer.

You asked whether [requirement] is included. [Direct answer.] The part we would still need to confirm is [unknown]. Would it help if I outlined the two options?

Make it work: put your real answer where the brackets are. If nothing is left to confirm, cut that sentence. If you already know the two options, spell them out instead of offering to.

Avoid: using their question as a reason to restart the whole pitch.

3. Follow up after a proposal review

You sent a proposal they asked for, and they told you when they’d review it.

Hi [name] — you mentioned reviewing the proposal after [agreed event]. Has the scope raised any questions? I can clarify [relevant section] if useful.

Make it work: use the review point they gave you, and name the part most likely to raise questions: scope, responsibilities or what happens first.

Avoid: inventing a deadline, guessing at a price objection or offering a discount before you know what the question is.

4. Return at the agreed time

They asked you to come back later because it wasn’t a priority yet.

When we last spoke, you suggested revisiting [problem] around [time]. Is that still a priority, or would a later check-in be more useful?

Make it work: reread the last few messages first, in case something changed. Describe the problem and the timing the way they did.

Avoid: treating an agreed check-in as a sign they’re ready to buy. If they push it back again, change the date and move on.

5. Confirm a next step after a call

A call ended with something you agreed to do, and LinkedIn is where you’ve been talking.

Thanks for the conversation, [name]. My next step is to [agreed action] by [agreed date]. I’ll include [specific item] so you can review [decision]. Have I captured that correctly?

Make it work: include only the actions and dates you actually agreed. If the timing is still open, ask about that one thing.

Avoid: stretching a small next step into a bigger commitment. A recap should be easy for them to correct.

6. Follow up when there’s no response

You’ve talked before, your last question went unanswered and no later date was agreed.

Hi [name] — I’m returning to your question about [specific issue]. I can share [one useful, available item] if it would help. Is that still something you are working on?

Make it work: offer something you already have ready. If you’ve sent it before or asked this exact question, bring something new or let the conversation rest.

Avoid: sending it to someone you’ve never spoken to. It only works when there’s a real earlier exchange.

7. Close a conversation without pressure

A conversation has stalled and you want to leave the door open without chasing.

I’ll leave this here for now. If [specific problem] becomes a priority, you’re welcome to pick up the conversation. Thanks for taking a look.

Make it work: mean it. Mark the conversation as paused so you don’t reopen it next week.

Avoid: sending it to someone who asked you to stop. Then the right message is no message.

When to send a LinkedIn follow‑up message

Use the timing you agreed. “I’ll send it today” and “let’s revisit next month” need very different follow-ups, so write down the actual agreement instead of giving every conversation the same gap.

With no agreement, ask two questions before you write. Has the person had a fair chance to reply? Do you have something new to add? If either answer is no, wait.

Stay in the channel you’ve been using. Switching to email or a phone call because someone went quiet feels like chasing. Switch when you’ve agreed to.

Haven’t spoken yet? You need an opener, not a follow-up. Start with these personalized LinkedIn outreach messages.

Worked example: from reminder to delivery

Morgan asked a consultant for a project-handoff checklist, and the consultant said they’d send it (example). The lazy follow-up is “Just following up — any thoughts?” It skips the one thing Morgan is waiting for.

Hi Morgan — here’s the handoff checklist we discussed: [working link]. The owner and acceptance-criteria sections relate to your question about tasks coming back unfinished. Let me know if either section needs explaining.

This is template 1 with the brackets filled in. It delivers what was promised and points Morgan to the part that answers the original question. That is what makes a follow-up worth opening.

Track the follow‑up, not just the draft

A written draft is not a finished follow-up. Until the checklist is sent, the task is still open. To keep it from slipping, paste this note into the free follow-up planner and choose Create plan:

Person: Morgan (example)
Conversation: Morgan asked for a project-handoff checklist. I agreed to share it. The message is drafted but has not been sent. No delivery date was agreed.
Next step: Check the resource link, then send the promised checklist.

The planner picks up the Person: and Next step: lines and leaves the due date empty, because none was agreed. Its No due date view shows open actions like this one.

  1. Before sending: make sure the checklist exists and the link opens for Morgan.
  2. After sending: mark the action done.
  3. When Morgan replies: read the new message, then set the next action. Add a date only if you agree one.

Check every follow‑up message before you send it

  1. Is the premise real? Only mention requests, events and agreements that actually happened.
  2. Are the brackets gone? Check names, dates, resource titles and links.
  3. Is there one ask? Answer or deliver first. Cut the extra meeting link and the service blurb.
  4. Is it still current? A newer reply, a postponement or a request to stop changes what you send.
  5. Did you record it? Mark the action done once it’s sent, and note what happens next.

LinkedIn follow‑up message FAQs

What should a LinkedIn follow‑up say after no response?

Refer to the real question or task you were discussing and offer one concrete next step, as in the no-response template. If you have nothing new to add, let the conversation rest.

Does accepting a connection request mean someone wants a pitch?

No. Accepting a request is not a stated need. These templates assume you’ve already had a real conversation. For a first message, start with a reason to talk.

How many follow‑ups should I send?

As many as the conversation earns. Follow the person’s timing, send another message only when you have something to add, and stop as soon as they ask you to.

Can I use AI to personalise these templates?

Yes. Give it the real conversation, then read the draft for invented facts or promises before you send. In bravabase, Brava drafts replies in your LinkedIn inbox and you review and send each one. Plans start at $99 a month with a 7-day free trial.

Does the copy button send anything?

No. It copies the template, brackets included, to your clipboard. You paste it, edit it and send it yourself.