What to send after someone accepts your LinkedIn request
Skip the thank you message. Use the bridge technique and real templates to turn LinkedIn connection acceptances into sales conversations.
Get startedShort answer
The best message after a connection is accepted picks up exactly where your connection request left off. Instead of saying thanks for connecting, refer back to the specific reason you reached out so the prospect remembers why they said yes.
Stop using the thank you message
Most people send a message that says thanks for connecting or I am glad to have you in my network. These messages are filler. They don't provide value and they don't ask a question that is easy to answer.
When a prospect accepts your request, they've given you a small window of attention. If you use that window to say thank you, you've wasted the most valuable part of the interaction. You're essentially restarting the conversation from zero.
The goal of the first message is to move from a connection to a conversation. This requires a specific hook that reminds them why they liked your profile or your initial note enough to click accept.
Generic filler
- Thanks for connecting! I look forward to following your posts.
- Hi Sarah, thanks for adding me to your network. Hope you're having a great week!
- Great to be connected. Let me know if I can ever be of help.
Specific bridge
- I saw your comment on the post about B2B pricing, so I wanted to connect. Do you find that most of your clients push back on the implementation fee?
- You mentioned you're focusing on scaling the SDR team. Are you hiring internally or looking at agencies?
- I noticed your team is expanding the sales org. Are you changing your onboarding process to handle the new hires?
Write the connection request so the follow up is easy
The message after acceptance only works if the request note gave it something to work with. A blank request or a note that says would love to connect leaves you with nothing to reference.
Your note should name one specific thing: a post they wrote, a comment they left, a change in their team, or a problem you know their role runs into. Keep it short enough to read in the preview without scrolling.
Then the follow up can open with that same detail. The prospect reads it and remembers why they accepted. If you connected without a note, you can still use the bridge. Reference something from their profile: a recent job change, a post they published, or a line in their headline. It takes thirty seconds of reading and beats a thank you message every time.
Paste this job
Hi [First name], saw your comment on [Founder]'s post about [topic]. Curious how [company] handles [specific problem] right now. Happy to connect either way.
The bridge technique
The bridge technique is a way to transition from the connection request to a real business conversation without sounding like a bot. It relies on the fact that the prospect already saw your request note, so you don't need to introduce yourself again.
A bridge message references the hook, asks a low friction question, and avoids the pitch. If you try to sell in the first message after acceptance, you trigger a defensive response and the prospect will likely stop replying.
- 1
Reference the hook
Start by mentioning the specific reason you reached out. Use phrases like I noticed you mentioned or I saw your post about. This proves you aren't sending the same message to 500 people.
- 2
Ask one open ended question
Ask a question about their specific situation or a pain point related to your hook. Avoid yes or no questions. Ask how they handle a problem or what their current priority is.
- 3
Remove the sales pitch
Do not mention your product, your calendar, or your service. The only goal of this message is to get a reply. Once they reply, they've entered a conversation, which makes the eventual pitch feel natural.
Templates for different connection hooks
Your first message must match the energy and context of your connection request. If you connected because of a shared group, the follow up should be about that group. If you connected because they commented on a competitor's post, the follow up should be about that specific topic.
Use these templates as a starting point. Replace the bracketed text with the actual details from the prospect's profile or activity.
Competitor's post
- Connection hook
- I noticed you mentioned the struggle with [pain point] in the comments of [competitor name]'s post. Is that still a priority for you this quarter?
Shared interest
- Connection hook
- You mentioned you're focusing on [topic]. I'm curious if you've tried [alternative approach] to solve that yet?
Company growth
- Connection hook
- I saw your team is expanding the [department] org. Are you changing your onboarding process to handle the new hires?
Recent promotion
- Connection hook
- Congrats on the new role as [title]. Are you planning to change how you handle [process] now that you're leading the team?
Handling the first reply
When a prospect replies, they're giving you permission to dig deeper. The common mistake is jumping straight into a demo request the moment the prospect says yes to a question. This is too fast.
Instead, use a second bridge. Acknowledge their answer, validate it by mentioning other people in their position, and ask one more clarifying question. This builds trust and makes the prospect feel understood.
Example
- You
I noticed you mentioned the struggle with lead quality in the comments of Mark's post. Is that still a priority for you this quarter?
- Prospect
Yes, it is. We're getting plenty of leads but most of them are too small for us.
- You
That's common for teams at your stage. Are you filtering them manually or using a tool to score them?
- Prospect
Mostly manual and it's slow. My SDRs spend half their day on the wrong people.
- You
I have a way to automate that scoring. Would it be worth a 10 minute chat to see if it fits your workflow?
Wait for the prospect to admit a pain point before you offer the solution. If you offer the solution before they admit the pain, you're just another salesperson.
When they accept and then go quiet
Some people accept and never reply. That's normal. Acceptance is a click; replying takes thought. Don't treat silence as rejection.
Send one follow up after three to five business days. Change the angle instead of repeating the question. Reference something new from their activity, or share a short observation about their market.
After that, leave it. Two messages is enough. If they engage later on a post, you can reopen the conversation then.
- 1
Wait three to five business days
Long enough that the first message has settled, short enough that they still remember the context. Don't send the follow up the same day.
- 2
Change the angle
If the first message asked about their hiring plans, the follow up can mention a post they shared about onboarding. New detail, same relationship.
- 3
Stop after two
A third unanswered message reads as pressure. Move the lead back to your list and watch their activity for a natural opening later.
Doing this with Kinlead
Kinlead automates this sequence by connecting your lead research to your outreach. It finds people who match your customer profile and scores them from 0 to 100, so you only message high fit leads.
The platform uses AI to write connection notes under 200 characters that explain exactly why a person became a lead. After the request is accepted, the AI writes follow up messages based on your campaign goal and your own sales playbook.
You can choose how to handle the conversation. You can let the AI reply until a meeting is booked using your scheduling link, let it reply until there is real interest, or have it hand the conversation to you at the first reply. All messages are sent at a human pace, with at most one action every 5 minutes.
If you use the Steal Customers agent, Kinlead watches competitor pages and turns commenters into leads, keeping the post URL and the specific comment so the AI can use them as the bridge hook.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? What to send after someone accepts your LinkedIn request.md