# Blank invites vs. notes on LinkedIn
> Learn when to send blank LinkedIn connection requests and when to use a note, with examples for commenters, executives and broad prospect lists.
- HTML: https://getkinlead.com/comparing-linkedin-automation-connection-methods
- Markdown: https://getkinlead.com/comparing-linkedin-automation-connection-methods.md

**Short answer:** Send a blank request when your profile explains your work and the list is broad. Use a note when you have a specific reason, like a comment on a competitor's post, because the note gives that person a reason to accept.

## What a blank request is good for

A blank request is a connection request with no note. The person sees your name, photo and headline. If those three things make sense for their world, they click accept. If they don't, they ignore it. That is the whole test.

Blank requests work best when you target a wide group with the same job title or industry. You are not trying to start a conversation in the request. You are trying to get into their network so you can see their posts and message them later.

Your profile has to do the selling. A headline like 'I help logistics teams cut empty miles' gives a VP of Operations a reason to accept. A headline like 'Founder at Acme' gives them nothing to work with.

**The pitch in the request**

- Hi Sarah, I see you're in sales. I have a tool that can help you get more leads. Would love to connect and show you.
- Hello Mark, I've been following your work. I offer a service that speeds up your workflow. Let's connect to discuss.

**The blank request**

- (No text). The recipient sees a clear headline, a real photo and a shared industry, then accepts or moves on.
- (No text). The recipient checks your profile because a mutual connection or group is visible, not because you asked for their time.

## When a note is worth the extra step

A note is worth it when the person has a specific reason to know who you are. The reason has to exist before you write the note. If you have to invent it, send a blank request instead.

The clearest trigger is a comment. If someone commented on a competitor's post about pricing, you can mention that comment. A blank request looks like a coincidence. A note that names the post and the point they made shows you were paying attention.

Notes also help when you reach people who get a lot of requests, or when your profile is new and does not yet explain your work. In those cases the note carries the context that your profile cannot.

| | Situation | Better choice | Why |
| --- | --- | --- | --- |
| Broad list of one job title | Blank request | The profile does the work and the request stays low pressure |
| Commenter on a competitor's post | Specific note | The comment gives you a real reason to reach out |
| Executive at a mid-sized company | Specific note | A blank request gives them nothing to react to |
| New profile or new niche | Contextual note | The note explains why you are relevant |
| Former customer or warm contact | Blank request or short note | They already know you, so keep it simple |

## How to write a note that gets read

The note has one job: give the person a reason to click accept. It does not need to explain your product, ask for a call or prove you are clever. Those things can happen after they accept.

Open with the trigger. Name the post, the comment, the event or the introduction. Then stop. A note that says 'Saw your comment on Northwind's post about pricing models' is enough. The person knows why you are there.

Keep it under 200 characters. That is the limit for a connection note, and it is also about the length people will read on a phone. If you run past it, cut the second sentence before you cut the trigger.

1. **Find the trigger.** Look for a comment, a post, a shared group or a real introduction. If you cannot find one, use a blank request.
2. **Write the first sentence.** Name the trigger in plain words. Example: 'Saw your comment on Northwind's post about pricing models.'
3. **Add one line of context.** Say why it mattered to you or what you are working on. Example: 'I'm working through the same question with a few agency owners.'
4. **Remove the ask.** Delete any request for a call, a demo or a reply. The only ask is the connection.
5. **Check the character count.** If it is over 200 characters, cut adjectives and company description first.

```
Hi [First name], saw your comment on [Company]'s post about [topic]. I'm working on [related thing] and your point about [specific detail] stuck with me. Would like to connect.
```

## How to choose between the two

Use the size and source of your list to decide. If you have a list of 800 people with the same title and no specific trigger, send blank requests. You will move faster and your profile will do the work.

If you have 40 people who commented on a competitor's post this month, write notes. The list is small enough to handle and the trigger is strong enough to mention. The same goes for people who attended a small event or replied to a newsletter.

You can also split a list. Send blank requests to the cold half and notes to the half with a trigger. Then watch which group replies after they accept. Do not judge the request by acceptance alone. A blank request that gets accepted but never replies is not better than a note that starts a real conversation.

- **you:** Hi James, saw your comment on the Northwind post about pricing models. I've been thinking about the same shift in my agency. Would like to connect.
- **them:** Thanks for reaching out. I'm glad someone else noticed that. Accepted.
- **you:** Appreciate it. Did the shift affect churn for you, or mostly the initial onboarding?
- **them:** Mostly onboarding. We had to rewrite the first two weeks.

## Mistakes that make either approach fail

The first mistake is using a generic note. 'I'd like to join your professional network' has no specific reason in it. It reads like a template, so it gets treated like one.

The second mistake is pitching in the request. A note that mentions a demo or a quick call gives the person a reason to say no before they know who you are. Save the pitch for the message after they accept.

The third mistake is sending a blank request to someone who has no reason to know you. If your profile is thin and the person is a senior executive, a blank request is a coin flip. Use a note with a real trigger or skip the request.

> If you cannot name the reason in one sentence, you do not have a reason yet. Send a blank request or wait for a better trigger.

## Doing this with Kinlead

Kinlead writes connection notes under 200 characters that open with why the person became a lead. That removes the blank page problem. You still decide the campaign goal and tone, and you can edit queued messages on the Actions page before they send.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles. It 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, so the note can reference the real trigger.

Outreach runs from your own LinkedIn account, connected through Unipile. Kinlead never stores your LinkedIn password. 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.

Pro starts with a 7-day free trial. A card is needed to start the trial, nothing is charged that day, and you can cancel any time in Settings. You can [start the trial](/signup) or [book a demo](/demo).

## Related

- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)
- [Handling LinkedIn pushback on invites](https://getkinlead.com/handling-linkedin-pushback-on-invites.md)
- [AI SDR reply modes comparison](https://getkinlead.com/ai-sdr-reply-modes-comparison.md)

## Common questions

**Does a note lower my acceptance rate?**

It can, if the note is generic. A note tied to a real trigger gives them a reason to accept.

**Should I follow up right after they accept a blank request?**

Wait a few hours or a day. A message the second they accept can make the request feel like a sequence.

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

LinkedIn does not publish exact limits. Sending a lot of requests quickly can lead to a temporary restriction, so set conservative daily limits and keep a consistent send window.

**Can I use a note for every request?**

You can, but it slows you down and many notes will be generic. Use notes where you have a real trigger and blank requests where your profile can carry the request.

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