# How to write connection notes that avoid spam reports
> Stop using generic LinkedIn templates that trigger spam reports. Learn how to write specific, low-pressure connection notes that buyers actually accept.
- HTML: https://getkinlead.com/avoid-spam-reports-with-notes
- Markdown: https://getkinlead.com/avoid-spam-reports-with-notes.md

**Short answer:** To avoid spam reports, stop using generic phrases like 'I'd like to add you to my professional network' or 'I see we have mutual connections.' These trigger a mental filter in buyers that leads to 'I don't know this person' reports. Start your note with the specific reason they are a lead, such as a comment they left on a post or a specific role they hold at a company you follow.

## Why generic notes get you reported

When a buyer sees a request that says 'I'd like to add you to my professional network,' they don't see a person. They see a pattern. This phrase is the default for thousands of automated bots, and buyers have learned to expect a pitch right after they hit accept.

A low acceptance rate is one problem. The bigger risk is the report. When someone clicks 'I don't know this person' after declining your request, LinkedIn treats it as a spam signal. A cluster of those signals in a short window can put your account under review or limit your invites.

Buyers also check your profile before they decide. They look at your headline, your recent activity, and the reason you gave. If the note says you are excited to connect but your profile is a wall of product posts, the mismatch confirms the pattern. They report the request and move on.

The fix is to make the note feel like it could only have been written for that one person. You do that with a specific reason, a real detail, and no ask beyond the connection itself.

**Generic (high report risk)**

- I'd like to add you to my professional network.
- I see we are both in the same industry and thought it would be great to connect.
- I've been following your profile for a while and would love to keep in touch.

**Specific (low report risk)**

- Saw your comment on the post about B2B pricing. Your point about tiered seats was spot on.
- Noticed you're scaling the SDR team at Acme Corp. I'm curious how you're handling the hiring surge.
- Read your thoughts on the recent industry shift in the thread by Sarah Jenkins. Let's connect.

## The 200 character framework

LinkedIn gives you a short note box, and 200 characters fills faster than you think. You have very little space to prove you are a person with a reason to reach out. The connection note has one job: give the person a clear reason you are in their notifications. Selling comes later, if it comes at all.

The most effective notes follow a simple structure that points at the other person's activity. Keep every line tied to something you can see on their profile or in their recent posts. If you cannot name the thing you read, you are not ready to send the note.

1. **The trigger.** Start with exactly why you are reaching out today. Use a specific event, such as a post they wrote, a comment they left, a job change, or a shared thread. Avoid 'I came across your profile' because it describes your search. The note should point at their work.
2. **The connection.** Mention a specific detail that proves you read the content. Avoid vague praise like 'great post' and mention the point they made. For example: 'Your note about tiered pricing made me rethink how we package seats.'
3. **The low-pressure ask.** Ask to connect without mentioning a meeting, a demo, or your product. The only goal here is the connection. If they accept, you can continue the conversation in messages.

> Keep the note under 200 characters and read it out loud. If it sounds like a template, it is one. If it sounds like something you would say to a person at a conference, you are close.

## Templates for different lead sources

Your note should change based on where you found the lead. A person who commented on a competitor's post needs a different opening than someone you found through a keyword search. Using the same script for everyone is a fast way to get flagged.

Use these examples as starting points. Swap the bracketed text for real details from their profile or activity. If you cannot fill in the bracket, you do not have a reason to send the note yet.

| | Lead source | Example note | Why it works |
| --- | --- | --- | --- |
| Competitor post | Saw your comment on Northwind's post about lead scoring. Your point on data decay was interesting. Let's connect. | It names the company, the topic, and the exact comment. The person can verify you read the thread. |
| Industry leader | Read your thoughts on B2B growth in the thread by Sarah Jenkins. I'm working on a similar project. Would love to follow your updates. | It points to a public thread and a specific idea. The ask stays inside the connection. |
| Role-based | Noticed you're leading the sales team at Acme Corp. I've been following your growth in the Midwest market. Mind if we connect? | It uses a real role and a real market. It does not pretend to know more than the profile shows. |
| Event or job change | Saw you started as VP of Sales at Acme last month. Congrats. I'm curious how you're structuring the team. Let's connect. | It uses a recent change that is easy to verify. The question is light and leaves the meeting for later. |
| Content creator | Your post on outbound follow-ups was useful. The part about writing the second line first stuck with me. Let's connect. | It references a specific post and a specific line. It works even when you have no mutual connection. |

## Common mistakes that trigger restrictions

Even a specific note can fail if it carries sales markers. Buyers are quick to spot language that suggests a sequence. If the note reads like the first line of a pitch, they will report it.

Avoid over-flattery. Telling a stranger you are a 'huge fan of their work' after reading one post feels dishonest and sets off the spam alarm. Mention the one thing you actually read.

Keep the note free of links, calendar asks, and product names. Those elements turn a connection request into an ad. The person has not agreed to a sales conversation yet.

- The note asks for 15 minutes on Tuesday.
- The note includes a calendar link.
- The note opens with 'I help companies like yours.'
- The note uses the same text for every lead in a list.

- **draft:** Hi Mark, saw your post on AI. I have a tool that can help you save 10 hours a week. Do you have 15 minutes on Tuesday to chat?
- **them:** (Clicks 'Ignore' and then 'I don't know this person')

> Never pitch your product or ask for a meeting in the connection request. That is the fastest way to get an 'I don't know this person' report.

## How to test a note before you send it

Before you send a note, read it as the recipient. Would you know why this person is in your notifications? If you cannot find the reason, rewrite the first line.

Run a few checks. Can you point to the exact post, comment, or role that made you reach out? Does the note ask for anything beyond a connection? Could you send the same note to fifty people without changing a word? If the last answer is yes, it is too generic.

Keep a small set of notes you have tested. When someone accepts a note and replies, save the opening line. When someone ignores a note, look at the first sentence. The problem is usually there.

Test one change at a time. If you switch the lead source, the opening line, and the ask in the same week, you will not know what caused the change. Pick one variable and run it across a small group.

- The first line names a real post, comment, or role.
- The note stays under 200 characters.
- There is no link, calendar ask, or product pitch.
- The note sounds like something you would say out loud.

## Doing this with Kinlead

Kinlead writes connection notes under 200 characters that open with the specific reason a person became a lead. That reason comes from the lead source, such as a comment on a competitor's post or a match against the customer profile you described.

The Steal Customers agent watches competitor company pages and optional founder or employee profiles. It reads the 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, so the note can use the real context.

Kinlead sends at a human pace. Each LinkedIn account sends at most one action every 5 minutes, inside the daily invite and message limits you set and inside a send window in the lead's time zone. If LinkedIn pushes back on an account, Kinlead pauses invites on that account and emails you.

You can read and edit queued campaign messages on the Actions page before they send, and any campaign can be paused.

## Related

- [Connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)
- [Steal customers agent](https://getkinlead.com/features/steal-customers.md)

## Common questions

**Should I send a note with every request?**

If you have a specific reason for reaching out, yes. If you are sending a massive volume of requests to a broad list, sometimes a blank request is safer than a bad template.

**What happens if I get too many 'I don't know this person' reports?**

LinkedIn may temporarily restrict your ability to send connection requests or put your account under a manual review process.

**How many connection requests can I send per day?**

LinkedIn does not publish exact limits. You should monitor your pending invitation pool and stop sending if you see a high number of unanswered requests.

**What should I do if someone ignores my note?**

Leave it alone. Do not send a follow-up message or a second request. Move on to the next lead and use the ignored note as a signal to check your opening line.

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