# How to write AI connection notes that get accepted
> Generic praise gets ignored. Write LinkedIn connection notes that name a specific post, role or trigger, plus templates you can copy and edit today.
- HTML: https://getkinlead.com/ai-connection-request-personalization-tips
- Markdown: https://getkinlead.com/ai-connection-request-personalization-tips.md

**Short answer:** Effective connection notes open with a specific reason for writing. Name a post they commented on, a problem their role owns, or a change in their job, then ask to connect and nothing more. Keep the note under 200 characters so it reads like a person typed it.

## Why generic notes fail

Most people write connection requests like cover letters. They open with lines like I would love to join your network or I am impressed by your professional background. Anyone who gets a handful of these a week reads them as one thing: a campaign.

When someone suspects a template, they stop judging the offer and start judging the risk. A note that could have been sent to anyone gives them nothing to work with, so the safe move is to ignore it.

The note has one job: show you know who you're writing to and why now. If you can't finish the sentence I'm reaching out because with a fact about them, you don't have a reason yet. Go find one before you send anything.

This is also why bought lists perform badly. A name, a title and a company give you nothing to reference, so the note collapses into praise. The trigger is the work. The sentence is just the delivery.

**Generic, gets ignored**

- I'm impressed by your background and would love to connect.
- I see we are both in the marketing space and thought it would be great to network.
- I've been following your company for a while and want to stay in touch.

**Specific, gets accepted**

- Saw your comment on the post about B2B pricing models and wanted to connect.
- I'm connecting with VPs of Sales who are rebuilding their SDR team this quarter. Thought it made sense to connect.
- Your post about the shift to product led growth was useful. I'd like to follow your updates here.

## The framework for a note that gets accepted

A working note has two parts and sometimes a third. The trigger is the evidence: something the person did or said that you can point at. The bridge is the clause that connects that evidence to why you're writing. The ask is the request itself, which should be nothing more than the connection.

You're working inside a character budget, so the trigger goes first. Don't introduce yourself before it. Nobody has agreed to meet you yet, and your job title is not a reason for them to care.

The bridge is where most notes go wrong. People over explain, add their company name, and slip in what they sell. Keep it to one clause. Thought it made sense to connect carries the whole note when the trigger is strong.

1. **Find the trigger.** Look at what the person actually did in the last few weeks: a post, a comment on a competitor's page, a new role, a talk they gave. Pick the one thing you could describe to a colleague without checking your notes.
2. **Write the trigger sentence.** Name the thing in plain words. Saw your comment on Northwind's post about renewal pricing. No adjectives, no flattery, no summary of their career.
3. **Add the bridge.** One clause that says why that makes you want to connect. I'm comparing notes with people who run renewal pricing right now. That's it.
4. **Cut everything else.** Remove your title, your company, your calendar link and any sentence about what you do. Read it out loud. If it sounds like a brochure, rewrite it.

> Never mention a product, a call or a meeting in the request. The only thing you're asking for is the connection, and anything else reads as a pitch before permission.

## Templates for different lead sources

The trigger changes with where the lead came from, so keep a small set of notes rather than one master template. Four sources cover most outbound.

For people who comment on a competitor's post, quote the topic. Naming the competitor works when the comment was substantive, but the topic alone is usually enough and it keeps the note short.

For role based targeting there's no post to reference, so use the shared problem. Say what people in that seat are usually dealing with and let them correct you if you're wrong.

| | Lead source | What to reference | Template |
| --- | --- | --- | --- |
| Comment on a competitor post | The topic they commented on | Saw your comment on Acme's post about renewal pricing. I'm comparing notes with people who run renewals right now. |
| Job title only | The problem the role owns | I'm connecting with heads of support who are trying to keep response times down without adding headcount. |
| Content creator | A specific point from a recent post | Your point about onboarding emails being too long was useful. I'd like to follow what you write here. |
| New role | The move itself | Saw you took over sales at Northwind. I'm connecting with new sales leaders in the same spot. |
| Event or group | The shared room, not the person | We were both in the pricing session at SaaStr. Curious how you're applying it at Northwind. |

## Phrases to cut before you send

Some phrases do damage on their own. Pick your brain frames the conversation as a favour where they give and you take. I have a solution that can help you is a pitch before hello. Several mutual connections means nothing when those connections are random people in the same industry.

Compliments about someone's trajectory or impressive background are filler. They cost characters and tell the reader something they already know about themselves.

The fix is usually deletion. Take the sentence out and see if the note still stands. If it does, the sentence was never carrying weight.

**Cut these**

- I'd love to pick your brain about your process.
- I have a solution that can help you increase revenue.
- I see we have several mutual connections in common.

**Use these instead**

- I'm curious how you're handling the pricing pushback from smaller accounts.
- I'm connecting with others who are rebuilding their support team this quarter.
- I saw you're connected to Dana, who I worked with at Acme.

## What to send after they accept

The connection is not the win. The first message after acceptance decides whether this becomes a conversation or sits in a list forever.

Don't open with a calendar link. Ask one question about the thing you referenced in the note, and make it a question they can answer in a sentence.

If they reply, keep the thread short and let them set the pace. If they don't reply, one follow up a week later is enough. Two is a pattern.

- **you:** Thanks for connecting. Your comment about renewal pricing stuck with me. Are you seeing the same pushback on annual increases that everyone else seems to be getting?
- **them:** Yes, mostly from smaller accounts. They want month to month now.
- **you:** That matches what I'm hearing. Is it the commitment or the cash flow that's the sticking point?
- **them:** Cash flow, mostly. The commitment they'd sign.
- **you:** Makes sense. Worth a short call to compare what other teams are doing on this? Happy to send times.

## Check the note before it goes out

Before a note goes into a campaign, run it against four checks. Does it name something specific, is it under 200 characters, does it avoid pitching, and would it still make sense if you swapped in a different person's name?

That last check catches most templates. If the note works for anyone with the same job title, it isn't specific, it's a segment.

- Specific: it names a post, a comment, a role change or a problem tied to their seat
- Short: it fits in a phone notification without truncating
- Clean: no product, no call, no calendar link
- Swappable test: changing the name should break the note

```
Saw your comment on [company]'s post about [topic]. I'm connecting with [role] who are working on [problem] right now. Thought it made sense to connect.
```

## Doing this with Kinlead

Kinlead writes the note for you. Connection requests can carry an AI written note under 200 characters that opens with why that person became a lead, so the trigger is already in the first line.

The [Steal Customers](/features/steal-customers) agent watches competitor company pages and optional founder or employee profiles, reads the comments on their 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, which is exactly the material the note needs.

Queued campaign messages can be read and edited on the Actions page before they send, so you can rewrite the weak ones and leave the rest. Outreach runs from your own LinkedIn account through Unipile, one action every 5 minutes, inside the daily limits and send windows you set.

If you'd rather see it running on your own account first, book a call through the [demo page](/demo).

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [Connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [Avoid spam reports with notes](https://getkinlead.com/avoid-spam-reports-with-notes.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

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

Sometimes. If your profile makes the reason obvious, a blank request can look less like outreach. For cold outbound where nobody knows you, a specific note gives the person something to accept.

**How long should a connection note be?**

Short enough to read on a phone without scrolling. Staying under 200 characters forces you to keep the trigger and drop the rest.

**What if I can't find anything specific about the person?**

Then you have a name, not a lead. Check their recent comments, their posts, or a change in their role. If nothing turns up, skip them and open the next profile.

**Do I need a paid search seat to find these triggers?**

No. Public posts, comments and profile updates cover most notes. A paid search tool helps with filtering, but the trigger itself comes from reading what the person wrote.

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