# How to message someone on LinkedIn without connecting
> How to start a LinkedIn conversation without a connection request: shared group messages, public comments, and a first message template you can copy.
- HTML: https://getkinlead.com/linkedin-messages-for-cold-outreach-without-connection
- Markdown: https://getkinlead.com/linkedin-messages-for-cold-outreach-without-connection.md

**Short answer:** You can message someone on LinkedIn without connecting when you share a group with them, because LinkedIn shows a Message button on the profiles of fellow group members. If you don't share a group, comment on their public posts first, then send a connection request that mentions the thread.

## What your options are

A connection request is not a message. The note you attach has a tight character cap, plenty of people ignore requests from strangers, and once it's sent you can't add anything until they accept.

That leaves two routes you can use today without paying LinkedIn anything: a group you both belong to, and a post they wrote that you can comment on. LinkedIn's paid messaging credits exist for some accounts, and I'm not covering them here because you don't need them for either route.

Open the profile of the person you want to reach and look for a Message button first. Some accounts accept messages from people outside their network. If the button is there, use it and skip the workarounds.

## The group message route

LinkedIn lets members of the same group message each other. It's the only free way to send a full message, with no character cap, to someone you've never met. The message lands in their normal inbox with the group name attached, which answers the question they'd otherwise ask: who is this and why are they writing to me.

Finding a shared group takes about a minute. Open their profile, scroll to Interests, click Groups. You'll see what they've joined, or nothing if they keep it private. If the list is empty, go to the comment route instead.

1. **Check their groups.** Open the profile, scroll to Interests, click Groups. Write down one or two that match your world, not the biggest ones you can find.
2. **Join and read before you write.** Join the group and spend ten minutes on recent posts. You want to know what the group argues about before you message anyone inside it.
3. **Find them in the member list.** Open the group page, click Members, search the name. A Message button sits next to each member.
4. **Send a short, specific message.** Reference a thread in the group, ask one question, and keep it to about five lines. Long first messages read like a pitch no matter how friendly they are.

> The group is your reason for writing, so name it in the first line. Saying you saw them in the RevOps group does more work than any compliment about their career.

## Comment first, then message

A public comment is the lowest-friction way to become a name they recognize. They post, you reply with something useful, they reply back, and a message from you is no longer from a stranger.

The mistake is treating comments as a numbers game. Great post, on ten threads, does nothing. One reply that adds a detail, disagrees with a specific point, or asks a question they'd enjoy answering beats fifty reactions.

- **them:** We moved our whole onboarding flow into the product last quarter. Support tickets dropped, but I'm not convinced new accounts finish setup any faster.
- **you:** Which step still drops off? For us the killer was the invite step, where people stalled waiting on a teammate to accept.
- **them:** Same. We're testing a skip option this week.
- **you:** Would like to hear how that lands. Sending a request now, no rush on it.

> Wait a day after the thread goes quiet before you send the request. A request that arrives mid-conversation feels like a trap.

## Which route fits which person

Pick based on how much context you already have. A group message works when you share a group and can point at something concrete inside it. A comment works when they post regularly and you have something to add. A request with a note is fine when you have an event or a mutual contact to mention.

If you're reaching out because of a comment they left on someone else's post, say so. That's the strongest opening of the lot, because it shows you read the same thing they did.

| | Route | What it needs from you | Where it fails |
| --- | --- | --- | --- |
| Group message | A shared group and one specific thread to mention | Groups so large that nobody reads the feed |
| Public comment | A post you can genuinely add something to | Generic praise repeated across ten threads |
| Comment on someone else's post | The person commenting somewhere you can reply | Threads where they never come back to answer |
| Request with a note | A shared event, group or mutual contact | A pitch squeezed into the note |

## What to write in the first message

The first line decides whether the rest gets read. It names the thing you have in common or the thing they said, in plain words. Then one question. Then stop.

Leave out the paragraph about your company, the line about hoping this finds them well, and the calendar link. All three belong in a later message, if they belong anywhere.

**Reads like a template**

- Hi [Name], I came across your profile and was impressed by your background. I help companies like yours improve their pipeline.
- Hey! Quick question, do you have 15 minutes this week to talk about your goals?
- Great post! By the way, we just launched something you might like.

**Reads like a person**

- You mentioned your team moved onboarding into the product. Did the invite step ever get fixed, or is that still where people stall?
- Saw your comment in the RevOps group about forecast accuracy. We're arguing about the same thing internally. What did you land on?
- Your post on pricing pages made me rewrite ours on Tuesday. The part about showing the annual number first was the bit I'd missed.

> One question per message. Two questions gives them a reason to answer neither.

```
Hi [Name], I'm in the [Group] group too and your post about [topic] stuck with me. We hit the same wall with [specific problem] last year and ended up [what you did]. Are you still running into it, or did [their approach] fix it?

Either way, good luck with [the thing they mentioned].
```

## How much you can send before LinkedIn pushes back

LinkedIn doesn't publish its limits, so anyone quoting a number is guessing. What matters is that a new account, or one that's been dormant, has less room than an account that's been active for years. Treat the first weeks as a test: send a few, watch for anything unusual, and back off at the first warning.

Variety matters more than volume control. Twenty identical messages look automated however slowly you send them. Change the opening line for each person, name the actual group or post, and don't send the same link to everyone in a row.

Clean up pending invitations before you send more. A stack of requests nobody accepted is the first thing to fix, and it's easier to spot than a limit you can't see.

> If LinkedIn shows a warning, stop for the day. Pushing through costs more than the messages you'd lose.

## Doing this with Kinlead

Finding the group and the right comment thread is manual work, and it's the part people quit on. The [Steal Customers agent](/features/steal-customers) 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 the person commented, which is the context a first message needs.

Those leads sit in lead groups, and any campaign can point at a group. Connection notes can be AI-written under 200 characters and open with why that person became a lead. Outreach runs from your own LinkedIn account through Unipile, one action every 5 minutes inside the limits you set and a send window in the lead's time zone. There's more on [account safety](/features/linkedin-account-safety) if that's what's holding you back.

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Account safety tips](https://getkinlead.com/features/linkedin-account-safety.md)

## Common questions

**Can I message a group member without being connected?**

Yes, if LinkedIn shows a Message button on their profile or in the group member list. Group membership is what unlocks it. If the button isn't there, comment on their posts and send a request that mentions the thread.

**Does the other person know which group we share?**

The message thread shows the group you have in common, so they'll work out how you found them. Mention the group yourself in the first line rather than leaving them to guess.

**Is commenting on posts enough on its own?**

Rarely. A comment gets you recognized, and the message or request is what starts the actual conversation. Plan for both steps.

**What if they never reply to the group message?**

Send one follow-up after a few days that adds something new, then leave it. Two unanswered messages is the point to stop.

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