# LinkedIn connection request templates based on lead intent
> Write LinkedIn connection requests for cold search leads and warm competitor leads using templates that avoid generic praise and focus on intent.
- HTML: https://getkinlead.com/connection-request-templates-for-different-intent-levels
- Markdown: https://getkinlead.com/connection-request-templates-for-different-intent-levels.md

**Short answer:** The best connection requests state exactly why you are reaching out based on how you found the person. Cold leads need a reason based on their role or industry. Warm leads from competitor posts need a reference to the specific comment they left.

## How cold and warm leads change the note

The first line of a connection request depends on how you found the person. A lead from a search filter has no shared context with you. A lead from a competitor's comment thread has a specific conversation you can point to. Treat them as two different jobs.

For cold search leads, use their role, company or industry as the reason. You are telling them why they are on your list. 'I saw you run sales at Acme' works because it is a fact. 'I admire your profile' does not.

For warm competitor leads, use the comment. Say what post they commented on and what point they made. That gives them a reason to accept that is tied to their own words.

The mistake is using one note for both groups. A cold lead cannot confirm a comment you never saw. A warm lead will wonder why you ignored the conversation that put them on your list.

**Generic approach**

- I'd love to join your network and explore synergies.
- I see you're a leader in the industry and wanted to connect.
- I'm an expert in X and think we could help each other.

**Intent-based approach**

- I saw you manage the sales team at Acme. I'm connecting with people handling X.
- I saw your comment on Northwind's post about X. Your point on Y was interesting.
- I'm building a network of VPs in logistics to discuss how X is affecting shipping.

## Templates for cold search leads

Cold notes fail when they try to cover the whole pitch. The note has one job: give the person a reason to accept. Save the product story for the message after they accept.

Use a template with three parts: how you found them, the problem you work on, and a low-pressure close. Keep each part to one sentence. If the note needs a scroll on mobile, it is too long.

Pick the template that matches your search filter. Role-based works when you searched by title. Industry-based works when you searched by company or keyword. Commonality works when you share a group, event or follower.

When you have no shared context, a short note can still work. Name the role and the problem. Skip the compliment. The reader can check whether the problem is relevant in one second.

| | Lead type | Template | Why it works |
| --- | --- | --- | --- |
| Role-based | Hi {first}, I saw you lead {team} at {company}. I'm connecting with {role}s working on {problem}. Open to connecting? | The role and company show you searched with intent. |
| Industry-based | Hi {first}, I'm building a network of {role}s in {industry} to compare notes on {trend}. Your work at {company} caught my eye. | The industry and trend give context without praise. |
| Commonality-based | Hi {first}, I saw we both follow {name} and work in {field}. I'd like to connect and keep up with your posts. | The shared reference is easy to check and feels human. |

```
Hi {first}, I saw you lead {team} at {company}. I'm connecting with {role}s working on {problem}. Open to connecting?

Hi {first}, I saw your comment on {competitor}'s post about {topic}. Your point about {specific point} matched what I see at {company type}. I'd like to connect.
```

## Templates for warm competitor leads

A comment on a competitor's post is a signal. The person cared enough to write something in public. Your note should show you read it. Quote the point they made. Leave their profile out of it.

Use a three-part bridge: observation, agreement, connection request. Observation names the post and topic. Agreement states the specific point you found useful. The request asks to connect. Do not ask for a call in the same note.

If the comment is short, use the post topic. If the comment is detailed, use their phrase. Avoid saying you saw their activity. Say you saw their comment on a specific post.

If the comment is negative about the competitor, do not pile on. Say the issue is familiar and ask how their team is handling it. That keeps the note useful and avoids sounding like a hit piece.

- **draft:** Hi Sarah, I saw your comment on Northwind's post about API latency. Your point about checkout conversion stuck with me. I work on the same problem for ecommerce teams and would like to connect.
- **them:** Thanks. The latency issue has been a headache for months. Happy to connect.

## Writing your own notes

Most notes fail because they sound like a pitch. The invite asks for a connection. Save the demo request for later. If you ask for a meeting now, the person has to decide whether you are worth 15 minutes before they know who you are.

Use plain words. Avoid adjectives that do not add a fact, such as innovative or disruptive. A note that says 'I work on checkout latency for ecommerce teams' is easier to trust than one that says 'I am a leader in innovative solutions'.

Use the person's own words when you have them. A phrase from their comment or profile is easier to answer than a description of your product. Keep the phrase short and put it in the first line.

1. **Write the reason first.** Start with the fact that put the person on your list. Example: I saw your comment on X or I saw you lead Y at Z.
2. **Add one line of context.** Say what you work on or what you want to compare notes on. Keep it specific to their role or comment.
3. **Remove praise and adjectives.** Delete words like visionary, innovative or best-in-class. Replace them with a fact about their work or the problem.
4. **Close with a simple question.** End with 'Open to connecting?' or 'Would you be open to a connection?' Do not ask for a call.

> If the note could be sent to 100 people without changing a word, it is too generic. Change at least the first sentence for each lead.

## What to send after they accept

The first message after acceptance is where most people rush. Do not open with a calendar link. Open with the reason you connected and one useful observation. Ask a question that is easy to answer.

For cold leads, use the role or industry reason. For warm leads, return to the comment. You can say you tried the fix they mentioned or ask how the issue is going. Keep the message short.

If they reply with interest, then ask for a call. If they reply with a question, answer it before you pitch. The goal of the first message is a reply, and the booking comes later.

If they accept and stay quiet, wait a few days. Send one message with a specific fact or question. Do not send a follow-up that only says 'bumping this'.

- **you:** Thanks for connecting, Sarah. You mentioned checkout conversion on Northwind's post. We saw the same pattern when API calls slow down during peak traffic. Is that still an issue for your team?
- **them:** It is. We are testing a fix now but the data is noisy.
- **draft:** That makes sense. If it helps, I can send the checklist we use to separate latency from checkout bugs. No call needed.

## Common mistakes that lower acceptance

Most low acceptance notes have the same problems. They praise without a fact, ask for time too early, or sound like a template you copied. Fix these before you test new openers.

Test one change at a time. If you change the opener, the length and the close in the same week, you will not know what caused the difference. Run the new note on a small group and compare replies.

- Praising the profile: 'I admire your impressive background' gives the reader nothing to respond to. Replace it with a fact from their role or comment.
- Asking for a call in the note: the person has not agreed to a conversation yet. Ask for the connection first.
- Using the same note for every lead: the first line stops matching the person, and the note reads like a template.
- Writing a paragraph: long notes get skimmed. Keep the note to two or three short sentences.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe or your website and scores each lead from 0 to 100 against that profile. Kinlead does not keep leads below the fit line. You can keep leads in groups and point any campaign at any group.

The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads comments on recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead.

Outreach runs from your own LinkedIn account through Unipile. Kinlead sends at a human pace, at most one action every 5 minutes, inside the daily limits and send window you set. You can read and edit queued messages on the Actions page before they send. Start with the [Steal Customers agent](/features/steal-customers).

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**Should I send a connection request without a note?**

For cold leads, a short note usually helps because it gives the person a reason to accept. For senior people who get many requests, a blank request can feel lighter. Test both with small groups.

**How do I handle people who accept but don't reply?**

Wait a few days, then send a message that adds a specific fact or asks a question about the reason you connected. Keep the first message short and skip the pitch.

**What happens if I send too many requests in one day?**

LinkedIn does not publish exact invite limits. Sending too many can lead to restrictions. Set a daily cap you can keep and use a tool that stops when LinkedIn pushes back.

**How do I reference a comment without sounding creepy?**

Quote the point they made and say why it caught your attention. Leave their profile out of it. Avoid mentioning that you scraped their activity.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
