# LinkedIn scripts for mutual connections
> Use a mutual connection to make a LinkedIn request feel less cold. Scripts, examples and a simple process for writing notes people answer on LinkedIn.
- HTML: https://getkinlead.com/scripts-for-mutual-connections
- Markdown: https://getkinlead.com/scripts-for-mutual-connections.md

**Short answer:** Mention the shared contact in the first sentence and explain the real link you have to them. Pick one person the recipient likely knows well, keep the note short, and ask for the connection rather than a meeting.

## Why a shared contact changes the request

When a connection request arrives from a stranger, the recipient looks for risk. They check your photo, your headline and the line that explains why you are in their inbox. A shared contact gives them a name they recognize. It does not guarantee an acceptance, but it gives your request a place to stand.

The common mistake is treating the shared contact as a password. We have mutual connections tells the recipient nothing. They need to know which person you mean and how you know them. A note that says I worked with Priya Shah at Northwind for two years is easy to check. If they know Priya, they can place you in a few seconds.

Use the shared contact to create context, then stop. The note still has to make sense if the recipient does not know that person well. If the only reason you are writing is the shared name, the request feels thin. Add one true detail about their work or a real reason you want to connect.

## Find the right shared contact before you write

Open the profile of the person you want to reach and look at the mutual connections section. If LinkedIn shows a count, open the list. You want names, not a number. The right shared contact is the one with the strongest tie to the recipient, not the one you know best.

Look for a shared employer, overlapping job dates, comments on each other's posts, or a public recommendation. A former teammate of theirs is usually a better name than a conference acquaintance. If you have several shared contacts, pick one and leave the others out.

If you do not know any shared contact well, do not pretend. Use a different opener: a post they wrote, a group you both belong to, or a project you are working on. You can also ask the shared contact for an introduction first. That is slower, but it keeps the trust intact.

- Same company or overlapping dates in their work history.
- Comments, reactions or recommendations between them.
- A shared group, event or school listed on both profiles.
- A public introduction or post that mentions both of them.

## Match the note to how well you know the shared contact

The wording should match the truth. A close colleague, a former teammate and a loose group contact do not deserve the same sentence. If you write with more warmth than the relationship has, the recipient will notice.

Use the table as a starting point. Change the words so they sound like you, and only claim what you can explain if someone asks.

| | Your link to the shared contact | What the note should say | Example line |
| --- | --- | --- | --- |
| Close contact | Say you asked permission, if you did, or that the contact suggested reaching out. | I asked Priya Shah if I could reach out. She said you two worked together on the Northwind rollout. |
| Former colleague | Name the company and the overlap. Keep it factual. | Priya Shah and I worked together at Northwind. I saw your post on pipeline reviews and wanted to connect. |
| Loose community contact | Name the group or event and avoid implying friendship. | I'm in the same B2B Marketers group as Priya Shah. Your post on webinar follow-up was useful, so I wanted to connect. |

## Write the note in four steps

A good note has one job: give the recipient a reason to click accept. It does not need to sell, book a call or explain your whole offer. Keep it to a few sentences.

1. **Name the shared contact first.** Open with the person and the real link. Use their full name once so the recipient does not have to guess.
2. **Add one true detail about the recipient.** Use a post they wrote, a project they shipped or a role they hold. Skip generic praise like I admire your work.
3. **Ask for the connection, not a meeting.** End with a simple line such as I would like to connect or open to connecting. Do not attach a calendar link.
4. **Read it as if you were the recipient.** If you would not know why you received it, rewrite the first sentence. If it sounds like a template, make one detail more specific.

```
Hi [First name], [Shared contact] and I [real link, e.g. worked together at Northwind]. I read your post on [topic] and it matched a question I keep hearing from [role]. I would like to connect and follow your work.
```

## A realistic exchange from request to first question

The note gets the accept. The first message decides whether the conversation continues. The exchange below uses the shared contact as context and then moves to a real question.

- **you:** Hi James, I saw we both know Sarah Chen from the UX meetup. I read your post about accessibility audits and wanted to connect.
- **them:** Hi, yes Sarah is great. Thanks for reaching out.
- **you:** Thanks for accepting. I'm curious how you handle audit handoffs at your agency. Is that something you deal with often?
- **them:** We do. It is usually the messy part.

> The first message after an accept should continue the context, not restart with a pitch.

## Common mistakes to avoid

The biggest mistake is using the shared contact to pitch in the request. The recipient accepts because of the name, then gets a sales message. That feels like bait. They may ignore you, and the shared contact may hear about it.

Other mistakes are easier to fix. Do not claim a close relationship you do not have. Do not list every mutual connection. Do not say a shared contact recommended you unless they did. If you want an introduction, ask the shared contact separately and make it easy to say no.

**Uses the name as bait**

- Hi, Sarah and I are connected. I help companies save money on software. Worth a chat?
- We have a long list of mutual connections. I would like to add you to my network.

**Uses the name as context**

- Hi, Sarah Chen and I worked together at Northwind. I read your post on onboarding and wanted to connect.
- I'm in the same B2B Marketers group as Sarah Chen. Your note on webinar follow-up was useful.

> If the shared contact would be surprised to see their name in your note, do not send it.

## What to do after they accept

Send a short thank you that continues the context. Do not restart with a pitch. The first message should show you remember why you connected.

Ask one question about their work. Use something specific from their profile or a recent post. If they answer, keep the conversation going. If they do not, wait. A second message too soon looks automated.

1. **Reply with context.** Mention the shared contact or the post you used in the request so the thread stays clear.
2. **Ask one question.** Keep it about their work, not your product. A question about how they handle a task is easier to answer than what are your pain points.
3. **Offer something only if it is useful.** Send a link or a short idea that fits the question. Do not attach a deck.
4. **Move to a call when they show interest.** Ask if they want to talk only after they reply with a real problem. Then share a calendar link.

## 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 are not kept. The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads 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.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Outreach runs from your own LinkedIn account through Unipile, a third-party provider. Kinlead never stores your LinkedIn password and 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. Queued messages can be read and edited on the Actions page, and any campaign can be paused.

## Related

- [Connection request checklist](https://getkinlead.com/connection-request-checklist-for-founder-led-sales.md)
- [Requests for CSV imports](https://getkinlead.com/connection-requests-for-leads-from-csv-imports.md)
- [Steal customers agent](https://getkinlead.com/features/steal-customers.md)

## Common questions

**Should I ask the mutual connection for an introduction first?**

Yes, if you know them well enough to make the ask. A direct introduction is stronger than naming them in a request. If you only know them loosely, mention the group or event instead.

**What if I have many mutual connections but know none of them well?**

Do not use them as proof. Pick another reason to reach out, such as a post, a group or a project. A vague shared name is worse than no name.

**How long should I wait before following up after they accept?**

Give them a few hours or wait until the next business day. A follow-up that arrives minutes after the accept feels timed by software.

**Can I mention a shared contact if I have never spoken to them?**

You can mention a group or event you both belong to, but do not imply a friendship. Say how you found them and keep the note factual.

**Should the note include a link to my calendar?**

No. The request is for a connection, not a meeting. Put the calendar link in a later message after they reply with interest.

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