# How to connect with LinkedIn users who don't post
> Find a hook in the About section and job history of LinkedIn users who never post, then write connection requests they actually want to accept.
- HTML: https://getkinlead.com/connection-requests-for-inactive-profiles
- Markdown: https://getkinlead.com/connection-requests-for-inactive-profiles.md

**Short answer:** People who never post still leave plenty to work with: their About section, their job history and the way they describe their own work. Read those first, then open the connection note with one specific detail from them. Skip the recent-post hook entirely, because there isn't one.

## Identify the lurker profile

Most outreach templates assume the person posts. You check their activity, quote a line from something recent, and the reply lands. That breaks the moment you hit someone whose last post went up two years ago. Send a post-based opener to that person and you've told them you're working from a template.

Before you write anything, open their profile and scroll to Activity. Two minutes there tells you which approach you're using. If the recent post is about the problem you solve, use it. If the feed is empty, full of reposts, or last touched years ago, stop looking at posts and read the profile instead.

A lurker still reads their feed and still checks the requests sitting in their inbox. They just don't leave public opinions behind to quote. The hook has to come from static profile data: the About section, the job history, the skills they list, the companies they came from. It's a smaller pile of material, and it's enough.

**Built on a post they never wrote**

- Check Recent Activity for a post from the last 30 days
- Quote a specific sentence from that post
- Ask their opinion on the topic they wrote about

**Built on the profile they did write**

- Open Activity and confirm there's nothing recent
- Scan the About section for a stated goal or a named process
- Pick one job change or one past company to ask about

## What the about section gives you

The About section is the closest thing to a self-description you'll get. People who never post still write one, because recruiters read it. It's short and put together on purpose, usually in the words the person thinks are accurate for their own work.

Read for two things: the problem they say they solve, and the vocabulary they use for it. If someone writes 'I help logistics teams cut empty miles', then empty miles is the phrase to echo back, not supply chain optimization. Their words get you read. Yours get you filtered.

Don't compliment the summary. 'Your background is impressive' carries no information. Point at a specific line inside it and ask something real about that line.

1. **Read the first two lines.** That's where the stated mission usually sits. Write down the exact phrase, not your paraphrase of it.
2. **Copy their vocabulary.** If they say handoff instead of integration, use handoff. Matching their word for a process shows you read the summary rather than a scraped job title.
3. **Look for what's missing.** A summary that names a problem but no scale, no team size and no system is leaving a gap. That gap is your question.
4. **Check featured when about is empty.** Featured items often hold a deck, a talk or a written piece. One line from a talk they gave beats anything you'd invent.

## Use the job history when about is thin

When the About section is empty, generic, or clearly written by a ghostwriter, the job history carries more signal anyway. Where someone worked, how long they stayed and what they moved between tells you what their week probably looks like.

Three transitions are worth a question: a company change, a title change at the same company, and an industry change. Each one changes what the person is measured on, and people answer work questions about that far more readily than they answer 'tell me about yourself'.

Keep the question about the work. 'How has the jump from fintech to healthtech been?' is a fine question on a call and an odd one from a stranger. 'Do you still run the same reporting setup you had at Northwind?' is a work question with an easy answer, and it opens a real conversation.

| | Scenario | The hook | Why it works |
| --- | --- | --- | --- |
| Past company | I saw you spent three years at Northwind. Are you still running the reporting process you had there? | It shows you read the history and named an operational detail, not the logo. |
| Promotion | You moved from manager to director about a year ago. That usually comes with budget sign-off on top of the old workload. | It acknowledges the change and points at the part of the job that probably got harder. |
| Industry pivot | You went from fintech to healthtech. Did the compliance side of your role change much? | It treats the move as a work question with a concrete answer instead of flattery. |

## Write the note like a person, not a pitch

The only job of the connection note is to get the accept. If you pitch, the reader files you under vendor and moves on.

One sentence on why you're writing to them specifically, one on what you're working on, then stop. No calendar link, no 'quick question', no asking for fifteen minutes before they've agreed to know you.

Short notes get read on a phone between meetings. If it takes more than a glance to work out what you want, it gets skipped, so keep the whole thing to two sentences.

**Template with one variable filled in**

- Hi {first_name}, I came across your impressive profile and would love to connect and explore how we might work together.
- I help companies like yours grow revenue. Open to a quick chat this week?

**Read the profile first**

- You've been at Halden about a year now, after three at Northwind. I'd guess the warehouse handoff process came with you.
- I work on that exact handoff problem and would like to connect, mostly to hear how Halden runs it.

- **you:** You've been at Halden about a year now, after three at Northwind. I'd guess the warehouse handoff process came with you. I work on that exact handoff problem and would like to connect.
- **them:** Sure, happy to connect. What does your thing actually do?
- **draft:** It puts order and carrier data in one view so nobody rebuilds the same handoff sheet each morning. Want me to send a two minute clip, or would a quick call be easier?

> If the hook could be pasted into someone else's request without changing a word, it isn't a hook.

## What to send after they accept

Accepting a request costs nothing. Replying costs attention, and most accepted connections go quiet because the first message asks for time before it gives anything.

Send the first message the same day if you can, while your name is still on their screen. Continue the thought from the note, add one piece of information they don't already have, and end with a question they can answer in a sentence.

Hold the booking link until they've replied twice. Before that it reads as the real reason you knocked.

```
Hi [first name], thanks for connecting.

You mentioned [exact phrase from their About or role]. I've been talking to [type of team] about the same thing, and the pattern I keep hearing is [one observation from real conversations].

How does [company] handle that today? Happy to share what the others said either way.
```

## Mistakes that get the request ignored

Most ignored requests fail on a small number of things, and none of them are about your product.

- Quoting a job description back at them. 'Responsible for driving operational excellence' is the line their employer wrote, not theirs.
- Asking something the About section already answers. It shows you skimmed for keywords instead of reading.
- Opening every note with 'I noticed'. It's the tell of a template with one variable filled in.
- Saving the point for the last line. Put the reason you're writing in sentence one.
- Following up with 'just bumping this' after a week of silence. Say something new or wait.

> Read the profile for thirty seconds before you type. That's the whole difference between a request that lands and one that sits pending until it expires.

## Doing this with Kinlead

Kinlead finds people who match the customer you describe, or your website, and scores each one from 0 to 100 against that profile. Leads under the fit line aren't kept. None of that depends on the person posting, because the score comes from who they are, not from their activity feed.

Connection notes are written under 200 characters and open with the reason that person became a lead, which is the same hook you'd pull out by hand from their About section or job history. Queued notes can be read and edited on the Actions page before they send, and a campaign can be set to hand the conversation to you at the first reply.

If you want ready-made wording to compare against, see [connection request templates](/ai-linkedin-connection-request-templates).

## Related

- [AI LinkedIn connection templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [AI sales playbook guide](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Lead scoring setup](https://getkinlead.com/ai-lead-scoring-fit-line-setup.md)

## Common questions

**Should I mention that I noticed they don't post often?**

No. Pointing out that someone is a lurker comes across as odd and slightly intrusive. Use the profile data you have and leave the observation unsaid.

**Is a blank request better than a personalized one for people who don't post?**

Personalized, almost always. A blank request asks them to judge you by a photo and a headline. A note with one specific detail gives them something to react to.

**How long should I wait before following up?**

Give it a week. People who don't post also tend to check LinkedIn in bursts, so a request sent Monday may sit unread until the weekend.

**What if their profile has nothing specific at all?**

Then you have no hook. Find a different route in, such as a colleague on the same team who does post, or skip them. A request with nothing specific behind it is a blank request with extra words.

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