Blog

    LinkedIn Connection Request Message Examples That Get Accepted

    FollowArc7 min read
    LinkedIn outreachconnection requestsmessage examples

    Quick answer: A good LinkedIn connection request note is short, specific, and gives the other person a reason to accept that is about them, not you. Notes are optional and capped at 300 characters, so write one or two plain sentences. A blank request is a reasonable choice when your profile already makes it obvious why you are reaching out.

    The two rules that matter before the examples

    The note is optional. You can send a connection request with no message at all. LinkedIn also limits how long a note can be: 300 characters, which is roughly two short sentences. Check the limit on your own account type, because LinkedIn can change it.

    The note is not the pitch. The only job of a connection request is to get accepted. Everything you want to say about your product, your offer, or a meeting belongs in the message after they accept. A note that sells in 300 characters usually reads as a sales message, and people treat it like one.

    When a blank request is fine

    Skip the note when:

    • Your headline and profile already say something relevant to the person (same industry, same role, same topic).
    • You share a lot of mutual connections or a visible group or event.
    • You are sending at volume and the note would be a generic line that adds nothing.

    Write a note when the reason to connect is not visible from your profile: a specific post of theirs, a shared event, an introduction, or a niche interest. A generic note ("I'd love to connect and share ideas") is often worse than no note, because it signals a template.

    You do not have to guess. Run a blank version and a noted version against similar lists and compare acceptance rates (more on that at the end).

    What a good note contains

    Most notes that work follow the same three parts:

    1. A real hook. Something true and checkable: a post, a shared event, a mutual contact, a role change.
    2. A reason it matters to them or to both of you. Why this connection makes sense.
    3. No ask. No call, no demo, no "quick question".

    Keep it under 300 characters, and read it aloud. If it sounds like something you would not say to a stranger at an event, rewrite it.

    14 example notes by situation

    Replace anything in brackets. Do not send these word for word; the point is the shape.

    Shared context

    1. Same event or conference "Hi [Name], I saw you were at [Event] this year. I was there too and your panel comment on [topic] stuck with me. Would be good to stay in touch."

    2. Same LinkedIn group or community "Hi [Name], we are both in the [Group] community and I keep seeing your answers on [topic]. Thought it made sense to connect here."

    3. Mutual connection "Hi [Name], [Mutual] and I worked together on [thing] and mentioned you do similar work at [Company]. Happy to connect if you are open to it."

    4. Alumni "Hi [Name], fellow [School] alum here. Noticed you moved into [field] after graduating. I'd enjoy following your path."

    5. Same city or region "Hi [Name], another [City]-based person in [industry]. Not many of us working on [niche], so I thought I'd say hello."

    Triggered by something they did

    6. A post they wrote "Hi [Name], your post on [topic], especially the point about [specific detail], matched what I have seen on my side. Would like to follow your writing."

    7. A podcast, talk, or article "Hi [Name], I listened to your episode on [show] and took away [one specific thing]. Wanted to connect and keep up with your work."

    8. A recent job change "Hi [Name], congratulations on the move to [Company]. I follow what the team there is doing in [area] and thought I'd connect."

    9. Company news "Hi [Name], saw the news about [Company] launching [thing]. Interested in how your team is approaching [related topic]. Glad to connect."

    Peer and role-based

    10. Same role, different company "Hi [Name], I run [function] at a [type of company], and I'm trying to meet others doing the same job. Your take on [topic] caught my eye."

    11. Adjacent industry "Hi [Name], I work in [your industry] and spend a lot of time around [their industry]. Always looking to learn from people closer to it."

    12. Shared interest from their profile "Hi [Name], noticed we both volunteer with [cause] / follow [niche topic]. Nice to see someone else in [industry] into it."

    Cold, with a light business reason

    13. Relevant to what you do, no pitch "Hi [Name], I work with [type of team] on [problem]. Your role at [Company] suggests you think about the same thing, so I'd like to connect. No pitch intended."

    14. After a previous touch elsewhere "Hi [Name], you opened my email last week about [topic]. Rather than clutter your inbox, I'll connect here in case it is easier to reach out later."

    Mistakes that cost acceptances

    • Pitching in the note. "I help companies like yours grow revenue 3x" is a sales message wearing a connection request.
    • Flattery with nothing behind it. "Impressed by your profile" tells them nothing.
    • Vague, reusable lines. If it could go to anyone, they can tell.
    • Using their name wrong. Merge fields that break ("Hi {{firstName}}") are the fastest way to get ignored. Spot-check before anything sends.
    • A profile that does not back you up. People often open your profile before they accept. A clear photo, an honest headline, and a sensible About section do more than any line in the note.

    Test it instead of trusting a template

    The best note for your audience is an empirical question. A simple way to test:

    VariableVersion AVersion B
    NoteBlankShort specific note
    LengthOne sentenceTwo sentences
    HookShared contextTheir recent post

    Change one thing at a time, send each version to a similar group of people over the same period, and compare acceptance rate (accepted divided by sent). For example, if you send 100 invites with a note and 30 accept, that is 30%; compare it to the same math on the blank version. Small samples bounce around a lot, so do not call a winner on a handful of sends. Our guide to the metrics that matter covers how to read these numbers, and how many connection requests you can safely send per day covers volume.

    Where FollowArc fits

    FollowArc runs LinkedIn and email outreach as a coordinated sequence, with Sophia personalizing the first touch from what is known about each contact, and sending safeguards that check pacing before each request. Safeguards reduce account risk but cannot remove it, and you stay in control of what goes out. If you want to see how that works with your own list, start the 7-day free trial or read about LinkedIn outreach automation.

    Keep reading

    Follow FollowArc on LinkedInPractical outreach tips, no fluff.
    Share this:LinkedInXEmail

    Get new guides and tools by email

    When we publish a new outreach guide, template or free tool, we will send it to you. No spam, and you can unsubscribe any time.

    We will email you about new guides and tools. Unsubscribe any time.

    See FollowArc run your outreach

    An autonomous AI sales agent for LinkedIn + email — you stay in control.

    Start your 7-day free trial

    7-day free trial. Add a card to start, $0 today, cancel before day 7 and pay nothing.