Guide · LinkedIn connection request templatesLinkedIn connection notes people actually accept.

How to use these templates

Words in double curly braces, like {{first_name}} or {{company}}, are variables. Fill them by hand, or map them from a CSV, your CRM or Clay columns if you send through an outreach tool. Before sending, read the note with the variables filled in. If it would sound odd said out loud, rewrite it.

Shared context

The easiest acceptances. Lead with the thing you genuinely have in common.

1. Same event. Hi {{first_name}}, saw you were at {{event}} too. I caught the session on {{topic}} and would like to stay in touch with people working on the same problems. Happy to connect.
2. Same group or community. Hi {{first_name}}, we’re both in {{community}}. Your post about {{topic}} was useful. Would be good to connect.
3. Mutual connection. Hi {{first_name}}, {{mutual_name}} and I worked together at {{company}} and your name came up when we talked about {{topic}}. Would like to connect.
4. Same alma mater. Hi {{first_name}}, fellow {{school}} grad here. I see you’re leading {{team}} at {{company}}. Always good to know alumni in the space. Let’s connect.

Engaged with their content

Specific beats flattering. Mention one concrete idea, not “great post”.

1. Recent post. Hi {{first_name}}, your point about {{post_topic}} matched what we’ve seen with {{similar_companies}}. Would like to follow your posts and connect.
2. Article or podcast. Hi {{first_name}}, listened to you on {{podcast}}. The part on {{topic}} changed how I think about it. Would love to connect.
3. Comment you both made. Hi {{first_name}}, we were both in the comments on {{author}}’s post about {{topic}}. You made the better point. Let’s connect.

Trigger events

Something changed at their company. Acknowledge it without pitching.

1. New role. Congrats on the new role at {{company}}, {{first_name}}. The first 90 days in {{role}} are a lot. Would be good to connect.
2. Funding round. Hi {{first_name}}, congrats on the {{round}}. I work with a few {{industry}} teams at the same stage and would like to connect.
3. Hiring. Hi {{first_name}}, noticed {{company}} is hiring {{roles}}. I talk to a lot of teams scaling {{function}} and would be glad to connect.
4. Product launch. Hi {{first_name}}, saw the {{launch}} launch. Nice work. Curious how it lands with {{audience}}. Let’s connect.

Peer and relevance

No shared history? Make the reason to connect obvious in one line.

1. Same role. Hi {{first_name}}, I’m also in {{role}} and always trying to learn how other teams handle {{challenge}}. Would like to connect.
2. Same niche. Hi {{first_name}}, I spend most of my time with {{industry}} {{role_plural}}, and your work at {{company}} keeps coming up. Happy to connect.
3. Local. Hi {{first_name}}, fellow {{city}} {{industry}} person here. Always good to know people nearby. Let’s connect.

Reconnecting and following up

For people you’ve already met or contacted elsewhere.

1. After a call or meeting. Hi {{first_name}}, good speaking with you {{when}} about {{topic}}. Connecting here so we stay in touch.
2. After an email. Hi {{first_name}}, I emailed you about {{topic}} last week. Easier to connect here, no pressure to reply there.
3. Old colleague or customer. Hi {{first_name}}, it’s been a while since {{shared_place}}. Saw you’re now at {{company}}. Would be great to reconnect.
4. No note at all. Sometimes the best note is none. For peers with an obvious overlap, a blank request often performs as well as a written one, and it saves your note allowance.

What makes a connection note work

1. One reason, stated plainly. “We’re both in {{community}}” beats three compliments.
2. Short. Most good notes are 150 to 250 characters. On mobile, anything longer gets cut off.
3. About them, not you. Skip your title, your company and what you sell.
4. No ask. Don’t request a call in the invite. Earn the conversation in the first follow-up.
5. Variables that are always filled. A blank {{company}} is worse than no variable. Clean your data or use a fallback.
6. Tested on one audience at a time. Compare acceptance rates for two notes on the same list before changing anything else.

Character limits and note allowances

LinkedIn changes these limits without notice, and they vary by account and plan. Treat them as guidance, not guarantees.

What to send after they accept

The connection note opens the door; the first message does the work. Wait a day or two after acceptance, then send a short message that follows on from your note: a question about the trigger you mentioned, or one useful resource. If there’s no reply, one or two spaced follow-ups are plenty. Our guide on how to automate LinkedIn outreach covers full sequence design.

Using these templates in SalesMix

In SalesMix, paste a template into a Connection Request step and the variables fill from each lead’s data, including custom fields from Clay, HubSpot or the API. A Condition step can then send a follow-up message only to people who connected. If you’re on a new account, ramp up slowly with our LinkedIn account warm-up schedule first.