How to write LinkedIn connection requests that get accepted

Most advice about LinkedIn connection requests treats acceptance as a nice-to-have. It isn’t. Your acceptance rate is the single number that decides whether your outreach keeps working or slowly poisons your account. Requests that get accepted build your network and your standing. Requests that get ignored, withdrawn, or marked “I don’t know this person” do the opposite — they drag down your ratio and inch you toward a restriction. So writing a good request isn’t about being polished. It’s about staying in the game.

Here’s how to write one people accept.

Start with who, not what

The best-written request in the world fails if it’s sent to the wrong person. Before you write anything, be honest about whether this person has a real reason to connect with you. A tight, relevant list is what makes everything downstream easier. If you find yourself needing a clever line to justify the request, that’s usually a sign the targeting is off, not the wording.

The structure that works

A connection note is short — you’ve got around 300 characters — so every part has to earn its place. A reliable shape:

1. A specific reason you’re reaching out to them. Something drawn from their profile, their company, a post they wrote, a shared group. This is the part that proves you’re not sending the same note to a thousand people.
2. A one-line hint of relevance. Why this connection might be worth something to them — not a pitch, just a reason.
3. A low-pressure close. No hard ask in a connection request. You’re opening a door, not walking through it.

Notice what’s missing: your product, your pitch, and your calendar link. A connection request that tries to sell gets declined. The sale, if there is one, comes later.

Two examples

Weak, generic:

Hi Sarah, I’d love to add you to my professional network.

There’s nothing here for Sarah. It could go to anyone, so it reads like it did.

Better, specific:

Hi Sarah — I read your post on cutting onboarding time for RevOps teams and the point about default dashboards really landed. I work with B2B teams on the same problem and would like to follow your writing. No pitch, just think we’re in the same orbit.

The second one references something real, gives a reason, and asks for nothing. That’s what gets accepted.

Personalization is the safety mechanism, not just a nicety

It’s easy to read all this as etiquette. It’s actually risk management. When your notes are specific and relevant, acceptance goes up and “I don’t know this person” reports go to zero — which is exactly what keeps your account healthy. When your notes are generic and blasted at volume, the reverse happens, and that’s the pattern that gets accounts flagged. This is why automating your outreach backfires: the automation strips out the personalization that was keeping you safe in the first place.

The problem with personalizing at scale

There’s an obvious tension. Personalization works, but reading every prospect’s profile and crafting a genuine, specific note for each one is slow. That’s why most people give up and fall back on templates — and templates are what get ignored. The bottleneck isn’t willingness. It’s time.

This is exactly the gap a tool should close — not by sending for you, but by doing the reading and drafting so the specific note takes a minute instead of ten. Ombaia reads a prospect’s profile alongside your own company context and drafts a connection note written for that one person, in your tone. You review it, adjust anything you want, and send it yourself. You get the acceptance rate of a hand-written note at a pace you can actually sustain — and because you’re the one sending, nothing about it puts your account at risk.

Write for the one person in front of you, keep the sending human, and your acceptance rate — the number that matters — takes care of itself.

If you want help writing requests that get accepted, try Ombaia free.