# InMail or connection request: which to use for cold outreach
> Learn when to use LinkedIn connection requests versus InMails for B2B sales. Compare costs, reply behavior, and a decision rule for high-value leads.
- HTML: https://getkinlead.com/inmail-vs-connection-request
- Markdown: https://getkinlead.com/inmail-vs-connection-request.md

**Short answer:** Use connection requests to build your network and start conversations without paying for a message. Use InMails for high-value targets or time-sensitive offers where you cannot wait for a connection request to be accepted.

## The difference between the two

A connection request is an invitation to join your network. It asks for a relationship. If the person accepts, you can message them, and they can see your posts. The request itself can carry a short note, but the main event is the accept. That accept is permission to keep talking.

An InMail is a paid direct message LinkedIn offers for reaching people outside your network. It arrives without a connection, and availability depends on the account and the recipient's settings. You are paying to skip the accept step. The message still has to earn a reply.

The feel is different. A request reads as networking, especially when the note mentions a shared group, a comment or a real reason to connect. An InMail reads as a direct pitch because it lands in the inbox without permission. InMail is a different tool with a different job.

**InMail with a generic pitch**

- Subject: Partnership opportunity. Hi Sarah, I saw you are VP of Sales at Acme. We help teams like yours book more meetings. Do you have 15 minutes next Tuesday?

**Connection request with a real reason**

- Hi Sarah, your comment on the post about sales handoffs was the clearest take I read this week. I work on the same problem at a small agency and would like to connect.

## Comparing cost and reach

For a small team, the trade-off is volume versus precision. Connection requests cost no direct money, but you are limited by how many invites LinkedIn lets your account send and by how many people accept. InMails cost money, but they put a message in front of someone who has not agreed to connect.

InMails are useful when the account or the moment is worth the spend. A connection request is better when you need to reach many similar people and build a network you can talk to again. The cost of an InMail is easy to see. The cost of a weak connection request is a lower acceptance rate and a pending invite pool that fills up with people who ignore you.

Recipients judge the sender too. A request from someone with mutual connections or a real reason to connect gets a look. An InMail from a stranger has to earn attention in the first line, because the recipient did not ask for it. If your first line is about you, the rest of the message is already in trouble.

There is also a timing cost. A connection request can sit pending for days or weeks. An InMail arrives now. If the lead just announced a funding round, a hire or a problem you solve, timing matters. If the lead is simply a good fit, a request is usually enough.

| | Feature | Connection request | InMail |
| --- | --- | --- | --- |
| Cost | No direct message cost | Paid option |
| Reach | People you can find and invite | People outside your network, subject to settings |
| Psychology | Networking | Direct pitch |
| Best use | Broad persona and network over time | High value or time sensitive target |

## When to use a connection request

Use connection requests for most of your outbound work. They are the default because you are building a list of people who can see your posts, reply to your messages and introduce you to others. That network keeps working after the first message.

This works best when you are targeting a broad persona. If you need to reach many marketing managers, founders or agency owners, paying for InMails on every touch is hard to justify. A request with a short note can start the same conversation for less.

Requests are also better for nurture over time. Once someone accepts, your posts can appear in their feed. You do not have to send another cold message to stay visible. The relationship has a place to live.

The note should give the person a reason to accept. A pitch gives them a reason to ignore. If you cannot write that reason in one sentence, you probably do not have one yet.

1. **Pick a persona you can describe in one sentence.** Example: heads of sales at 20 to 100 person B2B software companies. If you cannot name the role, company size and problem, fix that before you send.
2. **Look for a real reason to connect.** A shared group, a mutual connection, a comment they left or a post they wrote. The reason goes in the note. It should be true.
3. **Send a short note, then wait.** Do not pitch in the request. If they accept, send a normal message that asks one clear question. If they do not accept, leave it alone until you have a new reason to reach out.

```
Hi {{first_name}}, your comment on {{post_topic}} was the clearest take I read this week. I work on {{problem}} with {{persona}} and would like to connect.
```

## When an InMail is worth it

Save InMails for high value plays. If the lead is a decision maker at a company that would change your quarter, the cost of one paid message is small compared with the deal. The mistake is using InMail for every lead because you are impatient.

Timing is another reason. If a prospect just posted that they are hiring a sales team or struggling with a problem you solve, you may not want to wait for an accept. An InMail can get your note in front of them while the pain is fresh. The message still has to be specific. A generic pitch sent faster is still a generic pitch.

Use InMail as a second attempt with a new angle. If you sent a request two weeks ago and got nothing, a short InMail that references something new can sometimes break through. Do not repeat the same message. That just proves you are sending the same thing to everyone.

Write the InMail like a short email. Name the reason you are reaching out, say what you do in one line and ask for a small next step. Do not attach a deck. Do not ask for 30 minutes in the first line. The goal is a reply, not a calendar hold.

> Only spend an InMail when you can name the reason this person needs the message today. If the reason is 'I want more pipeline', use a connection request instead.

## The decision rule for cold outreach

To decide what to send today, work down a short list. Start with the lowest friction and highest reward option. That is usually a connection request with a real reason.

If you have a mutual connection, use it. A request that mentions the mutual contact has a better chance of being accepted than a cold InMail from a stranger. If you do not have a mutual, engage with the person's content first. Like a post or leave a comment that adds something. Then send the request a day or two later. The request feels like a follow-up to a real interaction, not a cold pull.

If the lead is high value and time sensitive, send the InMail. If the lead is high value but not time sensitive, send the request and wait. If the lead is low value, do not spend an InMail. Put them in a broader connection request campaign and move on.

After no reply, do not send the same message again. Change the channel or change the reason. A second touch can be a comment on a new post, a short InMail with a new angle or a request if you have not sent one yet. If none of those fit, drop the lead and work the next one.

- **you:** Hi Mark, your post about the shift to product led growth was useful. I work with founders on the same handoff problem and would like to connect.
- **them:** Thanks. Happy to connect.
- **you:** Appreciate it. You mentioned churn in that post. I work on a small tool for 40 person agencies that fixes the follow-up gap after a trial. Open to a quick look next week?

## Doing this with Kinlead

Kinlead runs connection request and message campaigns from your own LinkedIn account. It finds people 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.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. It sends at a human pace, with 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. Replies from every campaign land in one inbox, classified by intent, with interested replies first.

If you want to see how that works for your list, [book a demo](/demo).

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [LinkedIn connection request templates](https://getkinlead.com/linkedin-connection-request-message-templates.md)
- [Avoid LinkedIn restrictions](https://getkinlead.com/avoid-linkedin-restrictions-during-outreach.md)

## Common questions

**Do InMails have higher reply rates than connection requests?**

They do not always get higher reply rates. InMail puts the message in the inbox without an accept, but people can still ignore it. A connection request builds a relationship first, and the conversation after an accept is often warmer.

**Can I send a connection request after an InMail?**

Yes, but the order matters. If you spent an InMail and got no response, a connection request can be a gentle second touch. Do not mention the InMail in a way that sounds like a complaint.

**What happens to my InMail if the person does not reply?**

Treat it as spent once you send it. If you need a free touch, use a connection request instead. Check the current terms in your LinkedIn account before you rely on a refund.

**Should I use InMail for high value leads?**

Yes, when the deal size or timing justifies the cost and you have a specific reason to reach out. If the reason is vague, a connection request is the better first move.

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