LinkedIn Connection Request Message Templates That Get Accepted

A LinkedIn connection request message should give one honest reason to connect, prove that the sender chose this person deliberately, and stop before the sales pitch. The best note is usually one or two short sentences based on a shared event, a specific post, a relevant introduction, or a genuine professional overlap. No template can promise acceptance. Your profile, targeting, timing, and the recipient's preferences still shape the decision.

Build a LinkedIn connection request message around one reason

Start with the reason the recipient would recognize. That might be a conference session you both attended, a point from a post they wrote, an introduction they authorized, or work in the same narrow market. Use only details you can verify from the person's profile, their public work, or a source you trust.

Then make the request proportionate to the relationship. An invitation asks someone to add you to their professional network. It is a poor place for a product summary, discovery call request, or disguised proposal.

Use the recipient's name only when it reads naturally. Remove generic praise such as "impressive background" because it proves no research.

Six connection request templates by scenario

These are LeadHaste editorial starting points, not LinkedIn recommendations or acceptance guarantees. Replace every bracket with accurate information, and delete any line you cannot support.

After a shared event

Hi [Name], your point about [specific topic] during [event or session] stayed with me. I work on [closely related area] and would be glad to stay connected.

Use this when both people attended the same event and you can name the relevant session or discussion. "We were both at the conference" is weaker because it does not explain why this person stood out.

In response to a specific post

Hi [Name], I appreciated your point about [specific idea] in your post on [topic]. It connects with work I am doing around [relevant area], and I would be glad to follow your thinking.

Reference the idea rather than praising the post as "great content." A precise disagreement can also work when expressed respectfully, but an invitation is not the place to start a debate for attention.

With an authorized introduction

Hi [Name], [Mutual contact] suggested I connect with you because we both work on [specific area]. I would be glad to compare notes when useful.

Use a person's name only when they actually made or approved the introduction. A shared connection displayed by LinkedIn is not permission to imply a referral.

For a peer in the same market

Hi [Name], I work with [specific buyer or market] on [specific problem], and your role at [Company] puts you close to the same issue. I would be glad to connect and exchange practical notes.

Keep the overlap narrow enough to be credible. "We are both in business" is not context. Naming a real market, operating problem, or professional discipline gives the recipient a reason to understand the request.

After a role change or company announcement

Hi [Name], congratulations on the move to [Company]. I follow [relevant market or function] and would be glad to connect as you settle into the new role.

Confirm the change through the person's profile or an official company announcement. Do not infer a budget, urgent pain, or buying project from a new job. The public event supports the introduction, not a sales claim.

For a customer, partner, or community relationship

Hi [Name], we are both involved with [customer, partner, association, or community] through [truthful context]. I would be glad to connect and keep in touch around [shared topic].

Name the relationship accurately. Attending the same large community does not make someone a close peer, and working with the same company does not prove that the recipient knows your contact.

Match the note to LinkedIn's current limits

LinkedIn's invitation limit guidance says all members, including Basic and Premium members, are subject to invitation limits. If a member reaches the limit, LinkedIn says the sending restriction typically lasts one week. Withdrawing pending invitations does not remove that restriction, and LinkedIn says the wait period cannot be bought, removed, or shortened.

The same help page says Basic and free members can add a personalized message to five connection requests per month. Premium members can send unlimited personalized messages with their connection requests. "Unlimited personalized messages" does not remove the invitation limit, and it does not make every request relevant.

For a Basic or free account, our practice is to reserve the five personalized notes for situations where the context genuinely needs explaining. A clearly recognizable colleague, customer, or event contact may not need a note. A less familiar peer with a specific shared context often does.

LinkedIn's User Agreement also prohibits bots or other unauthorized automated methods used to add or download contacts or send or redirect messages. It separately prohibits bypassing access controls or service use limits. A template library can support manual drafting and review, but it does not authorize automated sending.

Avoid notes that create work or suspicion

A weak request usually asks the recipient to process too much before they know the sender. Remove these patterns:

• A product pitch followed by a request for 15 minutes.
• A calendar link, website link, attachment, or several calls to action.
• Generic praise that could describe any profile.
• False familiarity, an invented referral, or an unsupported claim about the person's priorities.
• A question that requires a detailed answer before the connection exists.
• Urgency created by a made-up deadline or limited offer.
• Personalization tokens left visible, misspelled names, or the wrong company.
• A copied note sent through unauthorized automation.

Do not replace a long pitch with a compressed pitch. "We help companies like yours grow, open to connecting?" is shorter, but it still makes the sender's offer the only reason for the request.

Run the six-part message review test

At LeadHaste, we recommend a pass-or-rewrite test before a connection request enters an outbound workflow. The note should pass all six checks:

1. Truth: Can you verify every name, event, post, role, company, and relationship in the note?
2. Specificity: Does the note contain one detail that belongs to this recipient or this shared context?
3. Reason: Can the recipient understand why this sender wants to connect?
4. Ask size: Is the only request to connect, without a meeting, link, demo, or proposal attached?
5. Voice: Would the sender say the note aloud without sounding like a mail merge?
6. Policy: Will a person send it through an authorized LinkedIn workflow without bypassing limits?

Rewrite the note if any answer is no. After it passes, check the sender's profile from the recipient's perspective. The role, company, photo, and recent activity should support the context in the note rather than create a new credibility question.

A team can record the scenario, source detail, sender, send date, acceptance, and any reply in its CRM. Keep acceptance and reply as separate outcomes. An accepted request shows that the person agreed to connect; it does not prove interest in a product or permission for an immediate sales sequence.

Our outbound service treats the message as one controlled step inside a broader system of targeting, research, channel selection, reply ownership, and suppression. For more practical guidance on those decisions, browse the LeadHaste blog.

Ready to improve your LinkedIn outreach?

We can review your ICP, connection-request scenarios, and channel mix during a free campaign-fit discovery call. Book your free discovery call →