# How to turn a sales script into LinkedIn connection requests
> Convert formal sales scripts into short, human connection notes under 200 characters. Focus on the trigger instead of the pitch to get more accepts.
- HTML: https://getkinlead.com/connection-request-notes-using-sales-playbooks
- Markdown: https://getkinlead.com/connection-request-notes-using-sales-playbooks.md

**Short answer:** To turn a sales script into a connection request, remove the pitch and formal intros. A connection note should give a reason for the request. Focus on the specific trigger that led you to the person and keep it under 200 characters.

## Why your sales script fails as a connection note

Sales scripts work for emails or calls because you have time to build a case. On LinkedIn, a connection note is just a request to join someone's network. If you lead with a value proposition or a list of features, you look like a spammer before they know who you are.

The goal is to get the request accepted. Closing a deal comes later. When you paste a script into an invite, you ask for their time or attention before you've built any trust. People usually ignore these or mark them as spam.

A connection note has one job: give the person a reason to accept. That reason is usually something you noticed about them, not something you want to sell them. The note can be short because the rest of the conversation happens after they accept.

People read connection requests on their phone, often between other tasks. They give the note a second or two. If the first line sounds like a pitch, they tap decline and move on. You don't get a second chance to explain.

**The script approach**

- We help companies reduce churn using our AI tool. I can show you how we can do the same for you.
- I've been following your company and noticed you're growing. Our platform helps your team work faster and improves productivity for teams like yours.

**The note approach**

- Saw your post about churn rates in SaaS. I'm building a list of people tackling this and wanted to connect.
- Noticed you're hiring for SDRs. I've worked with SDR teams in your niche and wanted to follow your progress.

## The why now framework

A human note needs a trigger. This is a specific, observable fact that explains why you're reaching out today. Without a trigger, your note feels like a mass blast.

The trigger can be small. A recent post they wrote, a job change, a shared group, a comment they left on a competitor's page, or a job posting on their company page. The trigger does not need to be impressive. It needs to be real and recent.

Write the note in two parts. First, name the trigger. Second, say why that trigger made you want to connect. Keep the second part short. You can mention your work if it helps them understand why you're in their notifications, but you don't need to explain your whole company.

A comment they left on a competitor's post is a strong trigger because it shows they already care about the problem. A job change is also strong because it tells you they are in a new role and may be open to new tools. A shared group is weaker on its own, so pair it with something specific they posted.

1. **Identify the trigger.** Find a recent post they wrote, a job change, a shared group, or a comment they left on a competitor's page.
2. **State the connection.** Mention the specific thing you saw. Be precise so they know you actually looked at their profile.
3. **Ask for the connection.** Use a soft request. Avoid words like hoping or pleased and just state your intent to connect.
4. **Check the length.** Read the note out loud. If it takes more than one breath, cut it. Keep it under 200 characters.

```
Saw your [specific post or comment] about [topic]. I'm [short reason you're reaching out]. Wanted to connect.

Example: Saw your comment on the post about AI agency scaling. I'm connecting with people in the space to see how they handle lead gen. Wanted to connect.
```

## Converting scripts to notes

To convert a script, remove all adjectives and claims. If your script says 'full set of tools', change it to a question about the problem those tools solve. If it says 'industry leading', delete it.

Move from what I provide to what I noticed about you. Use the table below to translate common script phrases into notes.

The table is not a set of templates to copy word for word. It shows the shift in thinking. Your note should sound like you typed it on your phone after seeing something they wrote.

If you write the note from a script, you will sound like a script. Start with the trigger and write the note without looking at your sales deck. Then check if you accidentally slipped in a claim or a feature. Cut that part.

| | Category | Script phrase | Connection note |
| --- | --- | --- | --- |
| Value prop | Our platform helps your team work faster and improves productivity. | Saw you're managing a remote team. I'm curious how you're handling the workflow side of things. |
| Targeting | We provide a full set of tools for CFOs in fintech. | Came across your profile while looking for CFOs in fintech. Wanted to connect. |
| Call to action | Can we jump on a 15 minute call to show you our demo. | Saw your comment on the post about tax laws. Wanted to connect and keep up with your insights. |
| Social proof | We work with many companies in your space. | Noticed you're in the same group for SaaS founders. I'm working on lead gen for a few teams in the space and wanted to connect. |

## Common mistakes that get invites ignored

SDRs often use professional language that sounds robotic. Phrases like 'I am impressed by your background' are red flags for buyers because they're usually in automated sequences.

If your note requires scrolling or looks like a wall of text, people decline it. Short notes feel like a quick thought from a real person.

Another mistake is using the same note for everyone. Even if the template is short, the trigger has to change. If you can swap in any name and the note still works, it's too generic.

Asking for a call in the connection note is another common mistake. The note is for the connection. Book the meeting in the message after they accept. The note only needs to get you in the door.

- **you:** Hi Sarah, saw your comment on the post about AI agency scaling. I'm connecting with a few people in the space to see how they're handling lead gen. Would love to connect.
- **them:** Thanks for reaching out! I'm definitely struggling with the lead gen side right now. Happy to connect.

> Avoid using 'I' more than 'you'. If your note lists your company and your goals, you're pitching. Make the note about them.

## How to test and improve your notes

You don't need a big experiment to know if your notes work. Send a small batch of 10 to 20 requests with the same style of trigger. Then read what happens.

Look for qualitative signals. Do people reply with a sentence about the trigger? Do they ask what you do? Do they accept and then view your profile? Those are better signs than a simple accept.

If people accept but don't reply, your note may be too vague. If people ignore the request, your trigger may be weak or your note may sound like a pitch. Change one thing at a time.

Keep a simple record of what you sent and what happened. A spreadsheet with the person, the trigger, the note and the reply is enough. After a few weeks, you will see which triggers get replies and which ones get silence.

1. **Send a small batch.** Pick 10 people with a clear trigger. Use the same note structure but change the trigger for each person.
2. **Read the replies.** Notice which triggers get a response. A comment on a post often works better than a job change because it gives you a topic to discuss.
3. **Adjust one part.** If the note is too long, cut it. If the trigger is weak, find a better one. Don't change everything at once.
4. **Keep a swipe file.** Save notes that get a reply. Copy the structure, not the exact words.

## Doing this with Kinlead

You can automate this by uploading your sales script as a sales playbook in Kinlead. The system uses that playbook to generate AI connection notes under 200 characters.

Each note opens with the reason why that person became a lead, like a specific comment they left on a competitor's post. This puts the 'why now' trigger in automatically.

You can read and edit queued notes on the Actions page before they send. This lets you keep the human feel while using AI for scale. See [automate with playbooks](/automate-linkedin-outreach-with-playbooks).

## Related

- [AI outreach templates](https://getkinlead.com/ai-outreach-templates-for-warm-leads.md)
- [Automate with playbooks](https://getkinlead.com/automate-linkedin-outreach-with-playbooks.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I send a note with every request?**

Send a note when you have a specific trigger to mention. If you have no reason for the request, a blank invite is often better than a generic note.

**What is the best length for a LinkedIn connection note?**

Keep it short. Under 200 characters is a good target because it looks like you typed it on your phone. Long notes get skipped.

**How do I handle people who accept but don't reply?**

Wait a few days after they accept before sending a follow-up. Reference the original trigger from your note to restart the conversation.

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