Templates, length and timing rules, and a follow-up sequence that turn LinkedIn connection requests into real conversations.

A LinkedIn connection message strategy is a deliberate plan for how you request connections and follow up after they are accepted, so that more requests turn into real conversations. It covers four decisions: whether to add a note, what that note says, how long it runs, and what you send once someone connects. Treated as a system rather than a one-off message, it lifts both acceptance and reply rates.
Most people obsess over the connection note and ignore the part that actually drives pipeline: the follow-up after the accept. This guide fixes both, with current 2026 limits, copy-paste templates, and a sequence you can run across more than one channel.
A LinkedIn connection message strategy is the repeatable approach you use to (1) decide when a connection request gets a personalized note, (2) write that note around a specific, true reason to connect, (3) keep it short enough to read at a glance, and (4) follow up with value within a day or two of the accept. The goal is not just a higher accept rate; it is starting a relevant conversation with the right person.
The mistake almost everyone makes is treating the connection note as the whole strategy. In practice the note only gets you in the door. What you say next, and how reliably you say it, decides whether you ever talk. A good strategy plans the entire arc from request to first reply, and it tracks the outcome so you can improve it.
It depends on relevance, not on a universal rule. A specific, well-targeted note that names a real reason to connect tends to lift acceptance into the 50 to 65 percent range, and top performers with tightly researched messages report 60 percent and up. A generic note can perform worse than no note at all, because it reads as a pitch before any relationship exists. Some 2026 analyses of large request volumes even found blank requests beating low-effort notes.
The practical takeaway: add a note when you can say something true and specific in one line. Skip the note rather than send a generic one. Either way, plan your real opener for after the accept, since that is where the conversation actually starts.
In 2026 the connection request note limit is 300 characters on Premium, Sales Navigator, and Recruiter accounts, and 200 characters on free accounts, spaces and emojis included. Free members can also add a personalized note to only a small number of invites per month before requests go out without a note; Premium and Sales Navigator do not have that monthly note cap.
The limit is a ceiling, not a target. Notes in the 120 to 180 character range consistently outperform notes that fill the full 300, because the recipient can read the whole thing in the preview without expanding it. Aim for roughly 150 characters: one specific reason, one light reason to accept, no link, no pitch.
| Surface | Free account | Premium / Sales Navigator |
|---|---|---|
| Connection note character limit | 200 | 300 |
| Notes per month | Small monthly allowance | No monthly note cap |
| Recommended note length | ~150 characters | ~150 characters |
| First message (after accept) limit | Standard message limits apply | Standard message limits apply |
Keep the connection note to one or two sentences, around 150 characters. It should fit in the preview and earn nothing more than the accept. Save the substance for your first message after they connect, where you have more room and a warmer audience. Trying to pitch inside the note is the single most common reason requests get ignored.
For the post-accept message, aim for two to four short sentences. Lead with one specific, relevant observation, deliver a small piece of value or insight, and end with a low-pressure question. Avoid links and attachments in the first message; they suppress replies and feel transactional before any rapport exists.
The strongest notes name something true about the recipient and give a light, honest reason to connect. The hook should be relevant to their recent activity, role, or shared context. Below are templates you can adapt; replace every bracket with a real detail, never a mail-merge placeholder you did not check.
Notice none of these pitch a product. The note buys attention; the follow-up earns the conversation.
Follow up within one to two days of the accept, while your name is still fresh, and lead with value rather than a pitch. The accept is interest in you as a contact, not a buying signal. Open with a specific observation tied to their work, share something useful, and ask one easy-to-answer question. Sending an immediate hard pitch is the fastest way to get archived.
A simple, reliable structure is observation, value, question. Keep it human and avoid anything that reads automated. The first message decides the conversation, so give it the same care you gave the note, and more room.
A connection request is the first step of a sequence, not the whole campaign. The strongest results come from planning the note, the post-accept message, and a small number of follow-ups as one flow, then meeting the same person on the channel they actually answer. Many buyers ignore LinkedIn but reply to email, or the reverse, so a single-channel sequence leaves conversations on the table.
This is where running outreach in one place matters. With Klovis, each step of a multi-channel sequence declares its own channel, and messages send from your team's own connected LinkedIn, email, WhatsApp, Instagram, and Telegram accounts. So a LinkedIn connect-and-message flow can hand off to a cold email step without you juggling separate tools or copy-pasting between tabs.
When someone replies on any channel, the reply lands in one unified inbox, attributed to the right person and ready to action, and the prospect is paused so they never get the next scripted step after a human answer.
Track outcomes at the message level, not just the accept. The metrics that matter are acceptance rate, reply rate on the first message, and meetings booked, because a high accept rate with a weak follow-up still produces no pipeline. Reviewing those numbers per template tells you which opener to keep and which to retire.
In Klovis, replies are tracked as campaign reply history and surfaced in a self-updating CRM, so contacts and companies update themselves as conversations progress and replies can be turned into deals. Event-driven workflows can react automatically: when a request goes unanswered, when someone replies, or when a field changes, the workflow can advance the sequence, route the contact, or book a meeting. If you are weighing tools for this, the comparisons page breaks down how Klovis lines up against single-channel LinkedIn and email tools.
Send a note when you can say something true and specific that names a real reason to connect; that typically lifts acceptance to 50 to 65 percent. If your only option is a generic line, a blank request often performs as well or better. Either way, plan a strong post-accept message, since that is where the conversation actually begins.
Keep the connection note to one or two sentences, about 150 characters, so it reads in the preview. The first message after the accept can run two to four short sentences. The 300-character limit (200 on free accounts) is a ceiling, not a target.
Within one to two days, while your name is fresh. Lead with a specific observation and a piece of value, then ask one easy question. Avoid links and hard pitches in that first message.
One or two at most after the first message, spaced a few days apart, and only when you have a genuine reason. Then close gracefully. A unified inbox helps here, because it pauses anyone who replies so they never receive the next scripted step.
Yes. With Klovis you can build a sequence where one step connects and messages on LinkedIn and a later step follows up by email, all from your team's own connected accounts, with every reply landing in one unified inbox and flowing into a self-updating CRM.