How to spot spam triggers in connection notes
Learn why LinkedIn connection requests get reported as spam and how to write short, specific notes that lower the risk of account restrictions.
Get startedShort answer
LinkedIn flags accounts when people click 'I don't know this person' after receiving a request. That happens when a note feels like a template, pitches a product, or gives the recipient no clear reason for the request. Enough reports lead to invite limits or account restrictions.
Why people report your requests
LinkedIn doesn't run a keyword spam filter like email. The strongest signal is what recipients do. When a stranger sends a request that looks like a mass marketing blast, the recipient often clicks the button that says I don't know this person. The report button is easy to click.
That button is the main trigger for account flags. If people report a high percentage of your invites, LinkedIn treats it as a sign that you're using automation to spam users. The platform may then limit your invites or restrict your account.
Most reports happen because the note shows you didn't do any research. If a recipient feels like a row in a database rather than a peer, they'll report the request to protect their inbox. One report is usually not enough to cause a problem. A pattern of reports is.
High report risk
- I'd love to connect and learn more about your business and see how we can collaborate.
- I've been following your work and think my solution could really help you grow your revenue this quarter.
- Hi, I'm a founder in the AI space and I'm looking to connect with other leaders like you.
Low report risk
- Saw your comment on Sarah's post about remote hiring. I agree that culture is harder to scale than tech.
- Your post on hiring ops matched a problem I've been stuck on. Thanks for writing it.
- Read your article on B2B sales. The point about discovery calls was a new perspective for me.
The biggest spam triggers
Certain writing patterns are red flags. They tell the recipient you've sent this exact message to a hundred other people. That makes them feel undervalued and more likely to report you.
The first trigger is sales language. Brochure words make you look like a vendor before you've built a relationship. Second is vague flattery, which feels dishonest without specific evidence. Third is the hard pivot, where you give a small compliment and immediately ask for time. A fourth is the link drop, where the note asks the recipient to book time before they've agreed to connect.
There is also the empty compliment. A note that says 'great profile' could go to anyone. The recipient knows it, and the report button is right there.
The note doesn't have to be long to be bad. A short line that asks for a call can trigger the same reaction as a paragraph. The ask matters more than the word count.
Sales language
- Trigger type
- solution, optimize, guarantee, help you grow
- Red flag phrases
- Sounds like a cold pitch
Vague flattery
- Trigger type
- impressed by your profile, great experience
- Red flag phrases
- Feels like a template
The hard pivot
- Trigger type
- do you have 15 minutes, can we hop on a call
- Red flag phrases
- Too much friction too early
Link drop
- Trigger type
- here's my calendar, book a time
- Red flag phrases
- Moves to a transaction before a conversation
How to write a low-friction note
The goal of a connection note is to get the person to click accept. Selling comes later. You do this by reducing the risk of connecting with you. A low-friction note proves you're a real person with a legitimate reason for reaching out.
Keep notes short. On mobile, long notes get truncated or look like a wall of text, which triggers a negative reaction. If you can't explain why you're connecting in two sentences, you're trying to do too much in the first interaction. If the note needs a scroll on mobile, the recipient may skip it.
The note has to be true. Clever writing does not help if the detail is fake. Mention a specific post, a shared group, or a comment they made. If you can't find a real reason, skip the note and connect without one.
- 1
State the specific trigger
Mention exactly where you found them, such as a specific post, a shared group, or a comment they made. Use a detail that only applies to them.
- 2
Keep it short
Aim for two sentences. Short notes feel like a quick thought rather than a prepared sales script.
- 3
Remove the call to action
Delete any mention of meetings, calls, or demos. Save the ask for after they accept.
- 4
End with a soft close
Use a simple statement or a question about their opinion on a specific industry topic. Don't ask for a reply unless the question is easy to answer.
Testing your outreach for safety
Don't rely on a feeling. Watch your acceptance rate and the number of pending invites. If you have hundreds of sent requests that are never accepted, you're in the danger zone for a restriction. A simple spreadsheet is enough.
Run a small split test. Send a few requests using your old style and a few using the low-friction approach. If the personalized notes are accepted and the generic ones are ignored, you know what to change.
Check your pending invites once a week. Withdraw requests that have sat for weeks without an answer. A large pending pool makes your account look less like a person and more like a queue.
Example
- You
Hi Mark, saw your comment on the post about B2B pricing. Your point about value-based tiers was interesting. Would love to connect.
- Prospect
Thanks for reaching out! I've been thinking about those tiers for a while. Happy to connect.
- You
Glad it resonated. I'm actually curious if you've tried implementing that with a specific tool or just manually?
If you notice a sudden drop in acceptance rates, stop sending invites immediately. Continuing to send requests that get ignored or reported is the fastest way to get your account flagged.
What to do when a request gets reported
A report is not the end of your account. The problem is what you do next. If you keep sending the same note, you turn a warning into a pattern. The goal is to break the pattern. Arguing with the warning does not help.
Slow down and look at the last batch of notes you sent. Find the phrase that repeats. Look for the sentence you copied from your template. That phrase is the one to remove.
- 1
Pause new invites for a few days
Stop sending requests and let the pending pool clear. Keep using LinkedIn for normal activity like reading, commenting, and replying to messages.
- 2
Review your recent notes
Open the last twenty or thirty notes you sent. Look for repeated openings, generic compliments, and any sentence that asks for a call.
- 3
Withdraw stale requests
Remove requests that have been pending for weeks. A smaller pending pool is easier to manage and looks more natural.
- 4
Follow any warning instructions
If LinkedIn shows a warning, read it and follow the steps. Don't open new tabs and keep sending. That is how temporary limits become longer ones.
Doing this with Kinlead
Kinlead writes AI notes under 200 characters that open by explaining why that person became a lead. That gives the recipient a reason for the request instead of a generic compliment.
Kinlead sends outreach at a human pace, with at most one action every 5 minutes. You set your own daily invite and message limits and define a send window in the lead's time zone. Kinlead never stores the LinkedIn password.
Stale pending invitations are withdrawn automatically to keep the pending-invite pool healthy. If you use Kinlead for demos, you can read the minimum booking guarantee terms.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to spot spam triggers in connection notes.md