Write a LinkedIn Connection Request That Gets Accepted

Most connection requests die for one of three reasons. The note could have been sent to anyone, there's no reason given for connecting, or it's a sales pitch dressed up as networking. The answer to how to write a LinkedIn connection request that gets accepted is a short note in three parts: one specific detail about the person, one honest reason you want to connect, and no ask. Two or three sentences. Then stop.

Everything below is about getting those three parts right, why the pitch does more damage than people think, and five before/after rewrites you can adapt today.

Why the note matters more than the volume

At 25 requests a day per account, you don't have requests to waste. Each one either becomes a connection, gets declined, or sits in limbo as a pending invitation.

That last outcome is the expensive one. LinkedIn watches how people respond to your invites. A stack of unanswered requests, plus the occasional "I don't know this person" from a recipient, reads as spam behaviour. That's how accounts end up restricted or forced to enter email addresses before inviting anyone. A weak note doesn't just cost you one connection. It quietly degrades the account you need for the next thousand.

So the note is a safety tool as much as a conversion tool. Better notes mean more accepts, fewer stale pending invites, and a healthier account. Your profile has to hold up its end too: the first thing a curious recipient does is click through, which is why optimizing your profile for outbound belongs before any campaign, not after.

How to write a LinkedIn connection request that gets accepted: the hook

The hook is the first line, and it has one job: prove this note was written for them. Not "I came across your profile." Everyone came across their profile. That's how invitations work.

Good hooks come from things the person did, said, or changed recently. Weak hooks come from things that are true of thousands of people. Here's how common sources stack up:

Notice the pattern. Strong hooks require you to have read something. That's the point. It's also why list quality matters more than copy: if your search pulls people who never post, never speak, and never change roles, you have nothing to hook on. The Sales Navigator search tricks that filter for recent activity fix this upstream.

The reason: why them, why you

A hook alone feels like a compliment with no follow-through. The second sentence answers the question every recipient is silently asking: why do you want to be connected to me?

The reason should be true and should make sense from their side. "I work on the same problem" works. "I'm building in this space and follow people who write honestly about it" works. "I'd love to pick your brain" does not, because it's a request for free time wrapped in flattery.

It's fine to say what you do. "I run a churn analytics tool" is context, not a pitch, as long as it doesn't come with an ask attached. The line between the two is simple: context explains who you are, a pitch asks them to do something. Keep the first, cut the second.

No pitch, and why it costs more than a decline

Accepting a connection is a cheap decision. Accepting a connection plus a meeting request is an expensive one, and people default to "no" on expensive decisions from strangers.

There's a second-order cost. Someone who accepts a pitchy request often accepts out of politeness and then ignores everything that follows. You won the connection and lost the conversation. Someone who feels pitched before accepting is more likely to click the option saying they don't know you, which is the signal you least want on your account.

The pitch belongs later in the sequence, after they've accepted and you've opened with something useful. How you space those follow-ups is its own discipline; designing an outreach cadence that gets replies covers the timing, and booking meetings from LinkedIn covers the ask itself.

Rewrites 1-3: generic, pitchy, and flattering

1. The default template

Before: "Hi Rohan, I'd like to add you to my professional network on LinkedIn."

After: "Rohan, your post on why you stopped cold-calling CFOs was refreshingly specific. I sell into finance teams too and I'm rethinking the same thing. Would be good to stay connected."

The before is LinkedIn's own placeholder text. Sending it tells the reader you didn't bother. The after has a hook (the post), a reason (same audience, same problem), and no ask.

2. The pitch in disguise

Before: "Hi Priya, we help SaaS companies reduce churn by up to half with our AI platform. Open to a quick 15-min call this week?"

After: "Priya, your thread on annual-plan churn in mid-market accounts was the most honest take I've read on it. I work on retention tooling, so this is my whole day. Glad to connect."

The before has an unverifiable claim and a calendar ask before you've said hello. The after mentions what you do but asks for nothing.

3. The vague compliment

Before: "Hi Karan! I'm so impressed by your amazing career journey and would love to connect with inspiring leaders like you!"

After: "Karan, going from support lead to VP Customer Success at the same company is a path I don't see often. I'm curious how support teams get a voice in product, and you seem to have done it. Happy to connect."

Generic praise reads as automated even when it isn't. Naming the actual career move proves you looked.

Rewrites 4-5: fake common ground and the essay

4. Common ground that isn't

Before: "Hi Neha, I noticed we're both in the tech industry. Let's connect!"

After: "Neha, I saw you're speaking at the Bengaluru product meetup next month. I'll be in the room and would like to be connected before then."

"Both in tech" covers a large share of LinkedIn. Real common ground is something narrow enough that it couldn't apply to everyone you're sending to that day.

5. The essay

Before: "Hi Vikram, hope you're doing well! My name is Sam and I'm the founder of a B2B startup that helps sales teams automate their workflows. We've been working on this for two years and I'd love to share what we're building, get your feedback, and maybe explore whether there's a fit for your team. Let me know if you have time for a chat!"

After: "Vikram, your breakdown of how you structure SDR territories was useful. I'm a founder working on sales workflows and trying to learn from people who've built teams. Would be glad to connect."

The note field is short for a reason. Three asks (share, feedback, fit) in one invite is three reasons to say no. The rewrite keeps one hook and one reason. Recruiters fall into the same trap with job pitches in the invite; the hiring outreach playbook applies the same rule to candidates.

Should you ever send a blank request?

Our position: rarely. A blank invite from someone with no visible link to the recipient is a coin flip they have no reason to call in your favour. The common argument for blank requests is that a note signals "sales incoming." That's true of bad notes. A specific, ask-free note signals the opposite.

The exception is when the context already exists: they commented on your post yesterday, you met them in person, or they've been engaging with your content for weeks. Then the relationship is the hook, and a note adds little. This is where combining content and outbound pays off, since people who already know your name accept without needing persuasion.

If you find yourself sending blank requests because you can't think of a hook, that's a targeting problem. Tighten the list.

Sending notes like these without burning the account

Personalised notes and automation aren't opposites. Pull a list from LinkedIn search or Sales Navigator, write two or three note variants built around the hook types in the table above, and use first-name and company variables only where they read naturally. Then personalise the hook line for the accounts that matter most.

Ampliflow handles the sending side. Connection requests run at 25 a day on every paid plan, with randomised timing jitter and only during the working hours you set, so the pattern looks like a person, not a script. A/B testing lets you run two note variants against each other, and funnel analytics shows which one gets accepted and replied to more often. When someone replies, the sequence pauses automatically so you never send a canned follow-up into a live conversation. Campaigns run in the cloud through the Unipile API, so you can close the laptop. Real-time account safety scoring flags anomalies before they turn into a restriction.

To be fair about it: if you send ten hand-written requests a week, you don't need any tool. If you want a cheap desktop option and are comfortable with it running on your machine, Linked Helper starts at $15/mo, which is less than our Standard plan. Ampliflow's case is cloud execution and safety controls, not being the cheapest. Standard is $19/mo for founding members, Pro is $39/mo, and every plan starts with a 7-day free trial. Details are on the pricing page.

Whatever you use, the note is still yours to write. Hook, reason, no pitch.