# How to ask a LinkedIn connection for a referral
> Get warm intros without burning the relationship. Write a connection request they accept, ask with an exit clause, and hand over a blurb they can forward.
- HTML: https://getkinlead.com/connection-requests-for-referral-asks
- Markdown: https://getkinlead.com/connection-requests-for-referral-asks.md

**Short answer:** Send a short connection request that gives a real reason to accept, and only ask for the introduction in a second message after they accept. In that message, name the target, say plainly that a no is fine, and include a short blurb they can forward unchanged.

## Why the ask has to come second

A second degree connection is a stranger who happens to share a contact with you. That shared contact is the reason they might open your message at all, and it stops being a reason the moment you ask for something in the same breath.

The people who get introductions reliably do it in two moves. The first message earns the connection. The second one, sent after they accept, asks for the intro and makes it easy to say yes or no.

There's a mechanical reason too. A connection note on LinkedIn caps out at 200 characters, which is room for one sentence about why you're reaching out and not much else. Trying to fit a referral request into that space is what produces the messages people screenshot.

Warm introductions work because the referrer lends you their credibility. That loan only makes sense if they know what they're vouching for, and a stranger reading a two line note doesn't.

**Transactional**

- Hi Sarah, I see you know John at Acme. Can you introduce us? Thanks!
- Hi Mark, I'm looking for a contact at Northwind. I see you're connected to their VP. Would you mind introducing me?

**Relationship first**

- Hi Sarah, we're both connected to John Miller. I build payments tooling for mid-size logistics teams and wanted to connect with people doing similar work.
- Hi Mark, your post on warehouse scheduling was the clearest thing I've read on that problem this quarter. I work on the software side of it and would like to follow what you write.

> The weak versions name the target and skip the reason. The strong ones give the person a reason to accept that stands on its own.

## Write a connection request they will accept

Lead with the mutual contact when that contact is genuinely relevant. 'We're both connected to John Miller' explains how you found them and gives them someone to check with before they reply.

When there's no mutual contact worth naming, use something they wrote. Pick one specific claim, result or complaint from a recent post and respond to it. The test is whether your first sentence still makes sense with their name removed. If it would work on anyone, it isn't a reason.

Skip the compliment sandwich. 'I loved your profile' and 'your content is amazing' give the reader nothing to reply to, and they read as the opening line of a pitch, because usually they are.

They will look at your profile before accepting. Two things matter there: a headline that says what you do in plain words, and some recent activity that shows you're a person who actually uses the platform. A profile with an empty feed and a vague headline is where most requests die.

- **you:** Hi Sarah, we're both connected to John Miller. I work on onboarding tooling for logistics teams and I've been following your posts on warehouse scheduling.
- **them:** Hi, yes, John and I worked together a few years ago. Happy to connect.
- **you:** Thanks. Your point about handoffs being the real bottleneck matched what we keep hearing from ops managers.

> One sentence about who you are, one about why them. If your note needs three clauses to make sense, it's too long.

## Wait a day, then ask with an exit clause

Send the ask the day after they accept. Same minute asks confirm the suspicion that the connection was only a step toward the favor.

The ask is two or three sentences. Name the target, say why you want to talk to them, and say plainly that a no is fine. That last part does more work than it looks like. People agree to introductions when refusing is easy, and they stall when the ask feels like a debt.

Then remove the work. If they have to figure out how to describe you to their contact, they'll mean to do it and won't.

1. **Name the target and one reason.** 'I'd like to talk to Priya at Northwind about how they run onboarding for enterprise accounts' beats 'I'd love an intro.' The reason is what the referrer repeats when they forward you.
2. **Say that a no is fine.** Put it in the message, not just in your head. 'If you don't know her well enough, no problem at all, I'd rather ask than assume.' Then drop it if the answer is no.
3. **Send the blurb in the same message.** Don't wait for a yes and then send what they need. That turns one reply into two and gives them a chance to lose momentum.
4. **Offer to write the first message yourself.** Some people would rather paste than compose. Give them both options: a paragraph they can forward, or a note from you that they can react to by replying in the thread.

```
Hi Sarah, thanks for connecting. One ask, and a no is fine. I'd like to talk to Priya at Northwind about how they handle onboarding for enterprise accounts. I'm comparing notes with a few teams before we build the next version, so it's a conversation rather than a pitch. If you'd rather not make the intro, no problem at all. If you're up for it, there's a paragraph below you can forward so you don't have to write anything.
```

## Write the blurb so they can forward it unchanged

The blurb is a message in the referrer's voice that they can paste into a chat with the target. Third person, short, and about the target rather than about you.

Keep it under about 60 words. Longer and they'll either trim it themselves, badly, or decide to write their own version later and never get to it.

Two things have to be in it: what you do, in one clause, and a specific reason the target would want the conversation. A result for a similar company works. A question you want to ask them works better, because it gives the target something to answer.

> If the blurb sounds like your website, rewrite it. It should sound like the person forwarding it talking to someone they like.

```
[Target], I know [your name], who works on [problem] for [type of company]. They had a question about [the specific thing the target's team does] and I thought of you. It's not a pitch, they're comparing notes with people who have already solved it. Want me to connect you two?
```

## What happens after you ask

Most of what looks like rejection here isn't. It's people who meant to help and got busy, plus people who didn't feel able to say no and went quiet instead.

Your job is to make each outcome cheap for them and clear for you.

| | Their reply | What to do | What to avoid |
| --- | --- | --- | --- |
| They say yes | Send the blurb in the same reply, thank them once, and tell them afterward how the call went. | Don't ask them to chase the target on your behalf. |
| They ask for more detail | Send two or three lines: what you do, the one question you want answered, and the blurb again. | Don't send a deck or a booking link. It turns a favor into a sales process. |
| They say no | Reply with one line and leave it. Stay connected and keep engaging with what they post. | Don't ask why, and don't offer to make it easier. Both push for a second answer. |
| They go quiet | One follow-up after about a week, and make it about them rather than the intro. | Don't message the target saying a colleague suggested you reach out when they didn't. |

## Keep a list of who you asked

One row per person: their name, company, the mutual contact, the date you asked, whether you sent the blurb, and what happened. Five columns is enough.

The point isn't admin. It's so you don't ask the same person twice eight months later, and so that when an intro lands you can go back and tell the referrer how it went. That thank you message is what makes the next introduction possible.

At any volume, run it weekly. Ten new requests, then work the older rows: anything past five days with no answer gets one follow-up, and anything past two weeks gets closed out.

The same list tells you which mutual contacts actually produce introductions. After a month you'll know two or three people in your network who are worth going back to, and the rest of the list stops being guesswork.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line aren't kept, so the requests you write by hand go to people who already look like buyers.

The Steal Customers agent 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 they commented, which gives you something specific to open with.

Connection notes are written by AI under 200 characters and open with why that person became a lead. Replies land in one inbox, and if you'd rather make the referral ask yourself, hand-off mode passes the conversation to you at the first reply.

## Related

- [Personalizing connection requests](https://getkinlead.com/ai-connection-request-personalization-tips.md)
- [Writing a sales playbook for outreach](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Finding buyers in competitor comments](https://getkinlead.com/features/steal-customers.md)

## Common questions

**What if they never accept the connection request?**

Leave it. An unanswered request is a no, and chasing it through another channel usually costs you the mutual contact as well.

**Should I name the target in the first message?**

No. Naming the target before they've accepted makes the request read as a transaction and hands them a reason to decline. Save the name for the second message.

**How long should I wait between the connection and the referral ask?**

A day is normal. Same minute asks look automated, and a week later reads as an afterthought.

**What if they offer to introduce me and then never do it?**

Send one short message after about a week, include the blurb again, and give them an easy line out. If it still doesn't happen, let it go and keep the relationship.

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