# How to write LinkedIn connection requests that get accepted
> Learn how to write LinkedIn connection requests that get accepted, with a simple three-part formula, real templates, and examples for B2B outreach.
- HTML: https://getkinlead.com/perfect-connection-request-guide
- Markdown: https://getkinlead.com/perfect-connection-request-guide.md

**Short answer:** A good connection request gives the person one specific reason you noticed them, a short reason you're connecting, and an easy way to accept. Skip the pitch and the meeting ask. The note should read like something you'd say at a conference.

## What a connection request is actually for

Most invites fail because the sender treats the note like a landing page. They squeeze in a value prop, a company description, and a request for fifteen minutes. The recipient sees a stranger asking for time before any trust exists.

The job of the note is to give someone enough context to click Accept. You are not booking a demo in the invite. You are not proving your expertise. You are giving a reason that makes sense to the person receiving it.

Treat the connection request like a handshake. The strongest notes mention one detail that could only come from looking at that profile or reading that post. A specific detail does more work than any clever phrasing. It tells the reader you wrote this note for them.

If you can't name that detail, send a blank request. A blank request is neutral. A generic note is a signal that you didn't look.

The note is a filter. It helps the right people accept and the wrong people ignore. That's useful. You don't want a connection who has no idea why you're there.

The note is not the place to explain your product. If they accept, you'll have a chance to do that. The invite is a filter, not a brochure.

## A three-part note you can write in two minutes

You don't need a novel. You need a pattern you can repeat without sounding like a robot. The pattern has three parts: the detail you noticed, why you're connecting, and a low-pressure close.

Use nouns the person recognizes. 'Your post about churn' beats 'your content'. 'The fintech compliance angle' beats 'your industry'. Specific nouns prove you looked.

Two minutes is realistic if you keep the detail short. You don't need to read every post. One comment or one line from a recent post is enough.

Keep the note under 200 characters. That's short enough to read in the notification preview. If you need more space, you're explaining too much. The conversation can carry the rest.

Write the note in the same voice you use in comments. If you're formal in comments, be formal. If you're casual, be casual. A sudden shift in tone reads like a template.

1. **Open with the detail.** Name the post, comment, promotion, or project. Start with 'I saw' or 'I noticed' only if it's true. Example: 'I saw your comment on Priya's post about tiered pricing.'
2. **Add your reason.** Connect the detail to why you're reaching out now. 'I'm working on packaging for a similar product and your point about annual plans stuck with me.' Keep it to one sentence.
3. **Close with a simple ask.** Ask to connect, not to meet. 'Would be glad to connect' or 'Wanted to say hello' works. Leave the meeting ask for after they accept.

```
I saw your [comment/post] on [Name]'s post about [topic]. Your point about [specific detail] stuck with me. I'm working on [your context] and wanted to connect.
```

## Templates for the situations you'll actually hit

Your note should change with how you found the person. A daily poster expects a different message than a quiet operator who updates their profile twice a year. Use these as starting points, then replace the brackets with a real detail.

If you're using a tool that pulls comment context, paste the comment into the first line. Don't paraphrase it into something generic. The reader should recognize their own words.

Don't use a template if the bracket text is fake. 'I loved your post about leadership' when they posted about hiring is worse than no note. The template is a scaffold, not a script.

If you sell to a technical buyer, use a technical detail. If you sell to a founder, use a business detail. The detail should match the person's world.

For a quiet executive, use a detail from their company page or a recent press release. Don't pretend you read a post they didn't write.

| | Situation | What to write |
| --- | --- | --- |
| They commented on a post | Saw your comment on [Name]'s post about [topic]. Your point about [specific detail] made me stop scrolling. Would be glad to connect. |
| They wrote a post | Your post on [topic] changed how I think about [specific detail]. I'm following your work now and wanted to connect. |
| You share an industry | I'm also working in [industry], mostly on [niche]. Your profile came up while I was researching [specific thing] and I wanted to say hello. |
| You share an alma mater | I saw we both went to [school]. I'm building in [industry] now and wanted to connect with other alumni. |
| They were promoted | Congrats on the move to [role]. I've been following [company]'s work on [topic] and wanted to connect. |

## What to cut before you hit send

Even a specific note fails when it sounds like a sales email. Certain phrases flip the reader's spam switch. They see 'synergy', 'quick call', or 'pick your brain' and they assume the note is a template with a name swapped in.

Read your note out loud. If you wouldn't say it to someone at a conference, delete it. The goal is a normal sentence from a normal person.

The fastest edit is to delete the first sentence. Most notes start with throat-clearing. 'I hope this message finds you well' adds nothing.

Cut adjectives. 'Amazing', 'incredible', and 'game-changing' make the note sound like an ad. Replace them with the specific thing you noticed.

Don't ask for a referral in the invite. 'Can you introduce me to your head of sales?' is a second ask before the first yes.

Don't use 'I' more than once. The note should be about them. 'I saw', 'I noticed', 'I wanted' can pile up and make the note feel like a diary entry.

**Sounds like a pitch**

- I have a solution that can increase your ROI by 20%.
- I'd love to jump on a quick 15-minute call to introduce myself.
- I'm looking for a few more partners in the SaaS space.

**Sounds like a person**

- I'm curious whether you've seen the same trend with [topic].
- I'm following your updates on [topic].
- I wanted to reach out after seeing your work on [project].

> Never write 'I'd love to pick your brain'. It signals a free consulting request. Also skip 'Dear Sir/Madam' and 'It would be a privilege'. Write the way you talk.

## What to do after they accept

Acceptance opens the conversation. It doesn't close it. Send a short thank-you within a day. Reference the same detail from your invite so the thread feels continuous.

Don't pitch in the first message. Ask one question about their work. If they reply, keep the exchange going until there's a real reason to suggest a call.

If they don't reply, don't send a follow-up pitch. A connection request that gets accepted and ignored is still a weak signal. Move on.

When you do suggest a call, tie it to their problem. 'You mentioned the upgrade path is messy. I have a short walkthrough that might help. Want me to send it?' That's a smaller ask than a meeting.

If they ask what you do, answer in one sentence and ask about their work again. The conversation should stay balanced.

If they reply with a question, answer it in one or two sentences. Then ask a follow-up. The goal is a back-and-forth, not a monologue.

- **you:** Thanks for connecting, [Name]. Your comment on Priya's pricing post stuck with me. Are you seeing annual plans hold up better than monthly right now?
- **them:** Yeah, annual is holding, but the upgrade path is messy. We're reworking it.
- **draft:** That matches what I'm hearing from other teams. The messy part is usually the handoff between sales and onboarding. Happy to share what worked for us if it's useful.

## Doing this with Kinlead

Writing every note by hand gets slow once you're sending more than a handful a day. Kinlead finds people who match the customer you describe, scores each lead from 0 to 100, and keeps the ones above your fit line.

The [Steal Customers](/features/steal-customers) agent watches competitor company pages and optional founder profiles, reads comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about, and what they commented. That gives you the detail for the first line.

Kinlead writes connection notes under 200 characters that open with why that person became a lead. You can read and edit queued messages on the Actions page before they send, and pause any campaign. Sending runs from your own LinkedIn account through Unipile at one action every five minutes, inside limits and a send window you set.

No tool can guarantee a LinkedIn account won't be restricted. Kinlead keeps sending inside the limits you set. The note still has to be specific to work.

1. **Find the leads.** Use Steal Customers or describe your customer to Kinlead. Kinlead scores each lead and keeps the ones above your fit line in lead groups.
2. **Write the note.** Campaigns use the lead's source context to open the note. The AI keeps it under 200 characters and opens with why they became a lead.
3. **Check the queue.** Open the Actions page to read and edit queued messages before they send. Pause the campaign if something looks off.
4. **Set the pace.** Choose daily invite limits and a send window in the lead's time zone. Kinlead sends at most one action every five minutes per account.

## Related

- [Connection notes for founders](https://getkinlead.com/connection-notes-for-founders-and-ceos.md)
- [LinkedIn lead generation guide](https://getkinlead.com/linkedin-lead-generation-guide.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I send a connection request without a note?**

Yes, when you have no specific detail to reference. A blank request often works better than a generic note that reads like a template.

**How long should a connection request be?**

Keep it under 200 characters. The recipient should be able to read the whole note in the notification preview.

**What if they accept but don't reply?**

Wait a day or two, then send a short message thanking them for connecting. Ask one question about their work before you mention a call.

**Can I use the same note for everyone?**

No. The detail is the part that earns the accept. Swap the detail for each person or send a blank request.

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