# Connecting on LinkedIn after a mutual introduction
> Learn how to transition from a three-way email or chat introduction to a direct LinkedIn connection using templates that maintain referral trust.
- HTML: https://getkinlead.com/connection-requests-after-mutual-connection-intro
- Markdown: https://getkinlead.com/connection-requests-after-mutual-connection-intro.md

**Short answer:** When someone introduces you via email or chat, don't send a blank LinkedIn request. Use the connection note to name the person who introduced you and the reason for the reach out. This moves the trust from the mutual contact to your direct relationship.

## The mistake of the blank request

Someone introduces you over email. You reply, thank them, and then the thread goes quiet. A week later you remember to send a connection request, and you send it blank because the introduction already happened. That gap is where most referrals die.

The person you want to meet gets a lot of notifications. A request with no note is a name and a photo. Even if they half remember the intro, they can't place you, so they leave it pending and forget about it. The referrer's goodwill doesn't transfer on its own.

The request is the handoff. You're moving trust from the person who vouched for you to yourself, and the note is where that happens. One sentence naming the referrer does more work than any pitch you could fit in the same space.

**Request with no note**

- You send a blank request three days after the intro email.
- They see a name they can't place and leave it pending.
- The intro thread goes cold and you never hear back.

**Request that names the referrer**

- You send the request the same day: 'Hi Sarah, Mark at Acme suggested we connect about the pricing rebuild.'
- They read Mark's name, remember the thread, and accept.
- You message the same day while the intro is still fresh in their head.

## Writing the transition note

A connection note is short, around 200 characters. That's two sentences, maybe three if they're tight. There's no room for a pitch, and a pitch is the wrong thing to put there anyway.

Put the referrer's name first. It's the only part of the note that tells the reader this isn't cold outreach, and it should land before they decide whether to keep reading. Then the topic from the intro, then a low-pressure close.

Name the topic specifically. 'Your growth plans' means nothing. 'The API migration your team is running' tells them you were listening in the intro thread, and it gives them something concrete to reply to.

- **you:** Hi Jane, David at Northwind suggested we connect after your team's API migration came up. Happy to pick it up here.
- **them:** Hi, yes, David mentioned you. Thanks for reaching out.
- **you:** Good to hear from you. He said you're moving the billing service off the old endpoints this quarter. Is that still the plan?

## Templates for different intro styles

Match the tone to how the introduction actually happened. A friend's casual 'you two should talk' doesn't need formal language, and a colleague's structured intro email reads oddly if you come back with something too chummy.

The loose case is the one people get wrong. If the referrer only said 'you should talk to Priya' and never opened a thread, Priya has no email from you to connect to. Your note has to carry the whole context, or it looks like cold outreach with a name dropped in.

Keep the note free of asks. No 'would love 15 minutes' inside the request itself. The request is for the connection, and the ask comes after they accept.

| | Intro type | What to write |
| --- | --- | --- |
| Warm intro from a friend | Hi [Name], [Referrer] said we should meet. I work on [thing] and they thought it overlapped with [your project]. Would be good to connect here. |
| Formal intro from a colleague | Hi [Name], [Referrer] introduced us over email last week. Following up here so the conversation is easier to keep track of. |
| Loose suggestion, no thread | Hi [Name], [Referrer] mentioned you're working on [project] and suggested I reach out. I've been doing [related thing] for [type of company]. |
| Intro made in a group chat | Hi [Name], we were both in [Referrer]'s thread about [topic] last week. Sending a request so we're connected directly. |

## Moving from connection to conversation

Acceptance is not a meeting. The moment they accept is when the referrer's name is doing the most work, and that fades fast. Message the same day if you can, and within a couple of days at worst.

Don't open with a calendar link. The intro was a conversation between three people, so your first direct message should continue it rather than jump straight to scheduling. Ask about the specific thing the referrer raised, or send something useful about it.

1. **Watch for the acceptance.** Check notifications once in the morning and once in the afternoon. A message sent the same day reads very differently from one sent a week later.
2. **Open with the thread, not with yourself.** Reference the intro topic in the first line. 'David mentioned your API migration' beats 'thanks for connecting' every time.
3. **Ask one question.** One specific question about the thing the referrer raised. Two questions in a first message reads like a form.
4. **Offer a time only after they answer.** Once they reply with substance, suggest a short call and give two specific windows instead of a booking link.

## When the intro happened in a group chat or on a call

Introductions made in a group chat, on a call, or at an event leave no thread to reply to. The prospect may have seen your name once, in passing, and that's the whole of their memory of you.

In those cases the note has to do more work. It needs the referrer's name, where the two of you crossed paths, and the topic. That's a lot to fit into two sentences, so cut everything else.

If the group was large, quote the referrer. 'Priya said you're rebuilding the onboarding flow' is harder to ignore than a general mention, because it shows you were paying attention to a specific message rather than mining a contact list.

```
Hi [Name], [Referrer] put us in the same thread about [topic] last week and said we should talk. I work on [specific thing] for [type of company]. Sending a request so we're connected directly.
```

## When they don't accept, or accept and go quiet

Some requests sit pending. That's normal and it usually means the note didn't land, not that they said no. They may have read it on a phone, meant to reply later, and lost it in the queue.

Don't send a second request. You can't, and chasing through the referrer is worse. What you can do is go back to the intro thread and reply there with something useful, which puts you in front of them again without firing another notification.

If the referrer is close to the prospect, one short update to the referrer is fine: 'Sent Priya a request, no rush, just wanted you to know I followed up.' Then stop. Asking them to nudge the prospect spends their credibility on your behalf, and they'll hesitate before introducing you to anyone else.

> Never ask the referrer to chase the prospect for you. The introduction was the favour. A follow-up request turns it into a debt.

## Doing this with Kinlead

If a partner sends you a list of names after an event, or you collect referrals in a spreadsheet, you can import them as a CSV of LinkedIn profile URLs into a lead group. Any campaign can then point at that group.

Connection notes are AI-written, under 200 characters, and open with why that person became a lead, so the referral reason is the first thing the reader sees. Queued messages can be read and edited on the Actions page before they send, which is where you check the tone on a batch you didn't write by hand.

Sending runs from your own LinkedIn account at a human pace, at most one action every 5 minutes, inside a send window you set in the lead's time zone. How that's enforced is covered on [LinkedIn account safety](/features/linkedin-account-safety).

## Related

- [AI connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [AI sales playbook for LinkedIn](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)

## Common questions

**Should I reply on email or send the LinkedIn request first?**

Reply on the intro thread first so the referrer sees you acknowledged it, then send the request the same day. The email keeps the referrer in the loop and the request opens a direct line.

**What if the referrer never replies to their own intro email?**

Send the request anyway and name them in the note. The introduction already happened and their silence doesn't cancel it. Just don't mention to the prospect that the referrer went quiet.

**How long after the intro should I send the request?**

Same day if you can, and within two or three days at most. After a week the prospect has moved on and the note has to work much harder to place you.

**Should the note mention the person or the company?**

The person. A name is what makes the note credible, and the company is context they can look up in ten seconds if they care.

**What if they accept but don't reply to my first message?**

Send one follow-up with something useful, then leave it. Two unanswered messages after a referral is the limit before it starts costing the referrer's reputation rather than yours.

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