A specific reference to a real comment, event or shared contact can explain why you are reaching out. Use it only when it is true and relevant to the person. The examples below are illustrative writing patterns, not evidence of measured acceptance or customer results; assess your own invitations rather than expecting a universal rate.
Four useful parts of an invitation note
- Specific signal in line 1 (where they came from, why now)
- Light value or curiosity in line 2 (what's interesting to you about them)
- Soft CTA in line 3 ("Open to connecting?")
- Concise enough for your account's invitation-note allowance
Seven connection-request examples
These are illustrative examples. Replace every placeholder and use only facts you have checked. Mention attendance or plans to attend only when true; registration alone does not prove attendance. A mutual connection is not an endorsement. Praise a specific takeaway only if you heard or read it, and claim shared group membership only if it is accurate. Use research or advice wording only when that is your real purpose. Mention a problem only if the person has described it; otherwise use the actual topic.
1. Post commenter
Hi {firstName}, saw your comment on {Author}'s post about {topic}. Curious how you're approaching {pain} at {company}. Open to connecting?
2. Event registration
Hi {firstName}, saw you're registered for {event}. Will be there too. What are you hoping to take away?
3. Mutual connection
Hi {firstName}, we're both connected to {mutualName}. Would be great to be in your network.
4. Job change
Hi {firstName}, congrats on the new role at {company}. Always like to connect with new {role}s in our space.
5. Conference speaker
Hi {firstName}, saw you spoke at {event} on {topic}. Brilliant point about {specific takeaway}. Would love to connect.
6. Asking for advice
Hi {firstName}, building a tool for {role} like yourself. Would love your perspective on what's broken in {workflow} today. No pitch, just curious.
7. Group member
Hi {firstName}, fellow {group} member. Your recent post in the group about {topic} stood out. Would love to connect.
What to review before sending
- A sales pitch that does not fit the actual relationship or reason for connecting
- Generic praise ("Love your work")
- Industry buzzwords stuffed in
- A note that exceeds the allowance shown in your account
- No clear, truthful reason for connecting
Frequently asked questions
What should a connection request reference?
Use a specific detail you have verified and can explain, such as a relevant comment, event or shared contact. It should support your real reason for connecting. Shared engagement or a mutual connection does not by itself establish buying intent or endorsement.
Should a connection request include a sales pitch?
A brief reason to connect is a useful starting point for an initial introduction. Whether a commercial point belongs depends on the actual relationship and purpose. Acceptance alone does not establish interest in a sale.
How long should a connection request note be?
Keep it concise and check the character limit and personalized-invitation allowance shown in your LinkedIn account. Include enough verified context to explain the connection; this guide does not establish a length that guarantees higher acceptance.
Do these examples guarantee acceptance or sales?
No. They are illustrative writing patterns, not measured benchmarks. For your own records, define a cohort and observation window, count invitations sent and accepted, and record replies, relevant conversations and purchases separately. An accepted connection does not establish buying intent.
Find relevant people, then manage the conversation.
If you need to find relevant people and manage outreach, conversations and follow-up, explore Leadsforlinked. Starter is advertised with multi-step campaigns, an inbox and a pipeline; choose the plan for your actual workflow and check current terms. For a profile sample, check the signup allowance available after email verification and the batch timing shown in your account.
Create an account