Quick answer: After someone accepts your LinkedIn connection request, send a short first message within a day or two that thanks them and starts a low-pressure conversation. If they do not reply, send one or two more touches spaced several days apart, each adding something new, and then stop. The goal is a real conversation, not a pitch.
Why the first message matters most
An accepted request means the person is mildly open to you. That goodwill is thin. The most common way to waste it is to send a long product pitch the moment the request is accepted. The second most common is to say nothing for weeks and let the connection go cold.
A good follow-up sequence respects three things: timing (soon after acceptance, then spaced out), relevance (each message has a reason to exist), and an exit (the sequence ends, politely).
A simple cadence
These timings are suggestions, not rules. Adjust them for your audience and test them.
| Touch | When | Purpose |
|---|---|---|
| First message | Within a day or two of acceptance | Thank them, start a conversation |
| Second touch | A few days after the first | Add something useful or a clearer question |
| Last touch | About a week after the second | Close the loop, make it easy to say no |
Keep the whole sequence to three or four messages. Anything beyond that is more likely to annoy than to convert. If you are sending the same sequence on email too, space the channels so the person is not hit on both on the same day.
First message templates
Template A: Ask about their work "Thanks for connecting, [Name]. I saw you lead [function] at [Company]. How are you thinking about [topic] this year? I'm curious what's actually working for teams like yours."
Template B: Reference the reason you connected "Thanks for accepting, [Name]. I reached out after your post on [topic]. Your point about [detail] stayed with me. Did that come from something you tried at [Company]?"
Template C: Light relevance, no pitch "Thanks for connecting, [Name]. I work with [type of team] on [problem]. If it is not a priority for you right now, no worries. If it is, happy to share what we have seen."
Template D: Resource first "Thanks for connecting, [Name]. I wrote up [short resource] on [topic] after talking to a few [role] folks. Want me to send it over?"
A good first message ends with one question or one offer. Not both.
Second touch templates
The second message should add something. "Just checking in" adds nothing.
Template E: A relevant observation "Hi [Name], I noticed [Company] recently [event/news]. Teams in that position often run into [specific problem]. Is that on your radar, or is it handled?"
Template F: A short example "Hi [Name], one example of what we do: [one sentence about a type of result you can actually back up]. If something like that would be useful, I can send details. If not, no problem."
Template G: Make the ask smaller "Hi [Name], I might have come on too strong earlier. Would it be useful if I just sent a two-line summary of how we help with [problem]? You can decide from there."
Last touch templates
The last touch should be generous. It is the one people remember.
Template H: Close the loop "Hi [Name], I will stop filling your inbox. If [topic] becomes a priority later, feel free to message me here. Either way, glad to be connected."
Template I: Offer a referral "Hi [Name], I haven't heard back, which is fine. If [topic] is not your area, is there someone at [Company] who owns it? I'd appreciate a pointer."
Template J: Leave something useful "Hi [Name], last note from me. Here is [short resource] in case it helps whenever [topic] comes up. Take care."
Templates for the no-reply case
Plenty of accepted connections never reply. That is normal and does not mean your message was bad. A few things help:
- Vary the angle, not the volume. If message one was about their work, message two can be about a result, and message three can be a referral request. Three versions of "did you see my message?" is just repetition.
- Use a different format. If you wrote a paragraph, try one line. If you asked a question, try offering a resource.
- Know when to stop. After the last touch, leave them alone. They remain a connection, and you can still engage with their posts naturally.
Template K: The nudge "Hi [Name], bumping this in case it got buried. If [topic] isn't relevant, just say so and I will leave it."
Template L: The pivot to a different person "Hi [Name], I may be talking to the wrong person. Who at [Company] handles [function]?"
What to avoid
- Pitching in message one. It turns an accepted request into a rejected conversation.
- Walls of text. If it does not fit on a phone screen without scrolling, cut it.
- Fake familiarity. "Hope you're having a great week!" followed by a pitch is a pattern people recognize.
- Broken merge fields. Check names, company names, and any inserted text before it sends.
- Ignoring replies. A reply of "not now" or "send info" deserves a human-quality response. Move quickly on genuine interest; honor a clear no.
Measure what works
Track the reply rate of each touch separately: replies divided by the number of people who received that message. For example, if 60 people received your first message and 9 replied, that is 15%. Compare versions of the first message against each other, not against messages from different audiences. See the metrics that matter for how to build a baseline, and how to write cold LinkedIn messages that get replies for principles behind the templates.
Where FollowArc fits
FollowArc sequences the follow-ups for you across LinkedIn and email, ranks the replies by intent so the interested ones surface first, and drafts responses in your voice for you to approve. Sending safeguards (pacing, send windows, a one-tap killswitch, and a short undo window) reduce risk but cannot remove it, and you stay in control of what sends. To see it run your own sequence, try FollowArc free for 7 days.