The connection request that gets accepted

"Hi, I am X from Y, we help companies like yours with Z, do you have 30 minutes this week?" You already know how that one ends.

Why pitching first does not work

Imagine a stranger walking up and immediately asking you to sign a contract. That is what a sales pitch in a first connection request feels like.

The recipient does not know you, has no reason to trust you, and owes you no time. So the first step has exactly one goal: getting the request accepted.

What a good request looks like

Three properties, and they are all about restraint:

• Short, a couple of lines, not a paragraph.
• About them, a concrete reason you are reaching out to this person.
• No ask, no offer, no link, no calendar invitation.

What to say instead of selling

Give the reason that makes your outreach make sense: a shared field, something specific about their work, a clear explanation of why them and not someone else.

You are aiming for one reaction: "fair enough, that tracks." Not "another person selling something."

What acceptance rates to expect

There is no published figure worth planning against, so establish your own baseline and watch what moves it. The pattern we see is consistent even where the level is not: senior titles accept least readily, peers and mid-level managers most, and any warm context, a shared group, a mutual connection, a recent interaction, lifts the rate noticeably. If your acceptance rate sits well below the baseline you set for yourself, the problem is usually targeting or a thin profile rather than the message text.

Judge the number on a few hundred requests, not thirty. And remember what the metric is for: an accepted request is permission to start a conversation, nothing more. A high acceptance rate with no conversations afterwards means the requests are landing on the wrong people.

Three openings that get accepted

Patterns, not templates to paste. Each one gives the recipient a reason that survives two seconds of scrutiny.

• The shared context. "We are both in industrial staffing, and I follow a few of the same people. Thought it made sense to connect." True, specific, no ask.
• Their work. "Your comment on the driver shortage thread matched what we see in the Baltic market. Would like to keep your posts in my feed." This one requires having read the thing, and it shows.
• The trigger event. "Saw the new Kaunas site announcement. We work with operations teams in that region, so your updates are relevant for me." A dated, public reason beats a flattering one.

All three pass the same test: the recipient can accept without feeling they agreed to anything. Whether to send a request or an InMail is a separate decision with its own trade-offs, covered in InMail vs. connection request.

Common mistakes that kill acceptance

• Pitching in the request. Covered above, still the leading cause of death. Fix: the request earns the right to talk, nothing else.
• Fake familiarity. "Loved your recent post" sent to someone who has not posted since 2023. Fix: reference only what you have genuinely seen.
• Neglecting the profile. Every recipient checks who you are before accepting. A profile that reads like a CV wastes the click. Fix: rebuild it as a profile that sells for you before sending a single request.
• Blasting volume through automation. Mass-sent requests get ignored by recipients and flagged by LinkedIn, and restricted accounts are expensive to replace. The safe boundaries are covered in where the automation line is.
• Stopping after acceptance. An accepted request with no follow-up within a few days goes cold. Fix: have the next message drafted before you send the request.

The message after the request is accepted

Acceptance is the easy half. The next message decides whether this turns into a conversation or another dormant contact in your network.

A pattern that holds up: wait a day or two, then send four or five lines that refer back to the reason you connected and ask one question the person can answer from memory. No link, no attachment, no calendar. Something closer to "Thanks for connecting. You mentioned driver retention in that thread, are you seeing the same churn on long-haul, or is it mostly regional?" That question costs ten seconds to answer and opens a thread you did not have.

If nothing comes back, leave it. One unanswered question is normal. Three is a pattern the recipient remembers badly. The stopping logic matches email, covered in every sequence needs an ending.

A checklist before you send a batch of connection requests

1. Confirm the segment holds together. Everyone in the batch should share the trait that makes your reason true. If the reason fits half the list, split the list. Working from a defined ICP makes this step almost automatic.
2. Read the profile, not the title. Titles are unreliable across European markets, where one responsibility carries three labels in three countries. Thirty seconds tells you whether this person owns the problem you solve.
3. Check your own profile above the fold. Photo, headline, banner, first two lines of the About section. That is all a recipient sees before deciding.
4. Cap the daily number. A manageable batch reviewed by a person beats an automated blast on acceptance rate, and keeps the account safe.
5. Draft the second message first. If you cannot write a useful follow-up, the request is not worth sending.

Objections we hear about LinkedIn outreach

• "Nobody reads the note anyway." Some do not. The ones you want usually do, because they are selective about who they accept and want a reason. A note costs nothing and gives you something to test.
• "Personalising every request does not scale." It does not need to. One true reason that fits forty people in the same niche is honest and repeatable. Reserve individual research for the accounts that justify it.
• "Volume solves everything." Not here. LinkedIn limits requests, and a low acceptance rate can restrict the account. Email is where volume belongs, as cold email vs. LinkedIn outreach sets out.
• "LinkedIn does not produce pipeline." It does when it feeds a sequence rather than standing alone, which is the case for running both channels in one multichannel sequence.

Connection requests across European markets

The rules do not change much across borders, but the register does. In DACH, a request that opens with a first name and a claim of shared enthusiasm reads as presumptuous. Keep it formal, keep it factual, and give the professional reason in one sentence. German-language requests to German-speaking prospects lift acceptance noticeably, even when the recipient speaks fluent English.

In the Baltics and Poland the market is small enough that reputation travels. A request naming a real overlap, the same industry association, a shared client type, a mutual contact, carries more weight than anything you write about yourself. English is fine, and the mutual connection often matters more than the wording.

The ceiling is the same everywhere: LinkedIn is a slow, high-quality channel. It works on a defined shortlist built through Sales Navigator and worked patiently, not as a volume machine.

When the offer comes

Later, once there is a thread and some context, through a proper sequence. Rushing to the pitch the second a request is accepted is the single most common reason LinkedIn outreach stalls.

With a note or without

Sometimes an empty request performs better, particularly when your profile is strong and does the explaining for you. It is worth testing both against your own audience rather than trusting a rule of thumb, including ours.