Short answer: A good LinkedIn connection request message gives one honest reason to connect, mentions something specific about the person, and asks for nothing. Keep it under 200 characters, which LinkedIn's Help Center gives as the note limit. Leave out pitches, links and meeting requests; those belong in a later message, after they accept.
The connection request message has one job: get a stranger to click Accept. It is not a sales email, and it is not the place to explain your product. This guide covers the character budget, when to skip the note entirely, examples for five common situations, the mistakes that get requests ignored, and how to test your wording without burning through your weekly invitations.
What should a LinkedIn connection request message say?
It should answer the question the recipient silently asks: "why me, and why you?" One specific detail about them plus one plain reason for connecting is enough.
A reliable structure has three parts:
- The detail: something they posted, said, built or attended that you actually noticed.
- The reason: how you relate to it, such as the same role, the same market, or a shared problem.
- A light close: "glad to connect" or "would be good to stay in touch." No question that demands a reply.
Notice what is missing: your offer. LinkedIn's Professional Community Policies tell members not to use the invitation feature "to send promotional messages to people you don't know." A note that reads like an ad breaks the spirit of that rule and is the quickest route to "I don't know this person."
How long can a LinkedIn connection request message be?
Up to 200 characters, according to LinkedIn's main Help page on personalizing invitations. An older LinkedIn Help page still mentions 300 characters for Premium members, so write to 200 and you are safe on every account.
200 characters is about two short sentences. A useful budget:
| Part | Characters | Example |
|---|---|---|
| Greeting | about 10 | Hi Dana, |
| Specific detail | 70 to 90 | your post on pricing pages for usage-based plans was the clearest I've read |
| Reason | 50 to 70 | I work on billing for B2B SaaS teams |
| Close | 20 to 30 | Glad to connect. |
Count characters with spaces and with personalization fields filled in. A long company name in {CURRENT_COMPANY} can push a 190-character template over the limit, and some tools cut the note off or skip it when that happens.
Should you send a connection request without a note?
Often, yes, especially on a free account. LinkedIn's Help Center says non-Premium members can add a personalized note to only three connection requests a month (another of its pages says five), while Premium members can add one to every request.
A blank request works well when the context is already obvious: you both commented on the same thread, you are in the same niche with mutual connections, or they recently viewed your profile. It works poorly for senior people who get many requests, or when nothing links you. A good middle path is to visit their profile or like a recent post a day or two before inviting, so your name is familiar when the blank request arrives.
LinkedIn connection request message examples
These examples each fit in 200 characters with normal-length names filled in. Adapt the detail; never send a detail you did not actually check.
Name-drop a mutual contact only with their permission. For longer messages that follow acceptance, see our LinkedIn cold message templates.
What mistakes get connection requests ignored?
Pitching, vagueness and fake familiarity. Each makes the request look like it was sent to hundreds of people, which it often was.
| Mistake | Weak | Stronger |
|---|---|---|
| Pitch in the note | We help companies like yours grow pipeline. Open to a quick call? | Saw you're hiring three AEs this quarter. I work with sales leaders scaling teams. Glad to connect. |
| Generic opener | I'd like to add you to my professional network. | Your talk on churn signals at the CS summit was useful. I work in retention analytics too. |
| Empty flattery | Impressive profile! Let's connect. | Building a 40-person support team without a ticket backlog is rare. Would like to follow your work. |
| Fake familiarity | Great to reconnect! Hope all is well. | We haven't met, but we share a few customers in logistics software. |
| Link or calendar | Here's my Calendly if you'd like to chat. | Save it for the second or third message, after a reply. |
Also avoid broken personalization. "Hi {FIRST_NAME}" sent literally, or "Hi DANA" in capitals pulled from a messy list, undoes any effort elsewhere in the note.
How do you personalize connection request messages at scale?
Use structured fields for the basics and real research, human or AI, for the specific detail. Templates alone produce notes that all sound the same.
- Fields: {FIRST_NAME}, {CURRENT_COMPANY} and {TITLE} are safe when your list is clean. Set a fallback, such as "there," for blank first names.
- Segments: write one note per tight segment (for example, "heads of RevOps at 50 to 200 person SaaS companies") so the reason line is true for everyone who receives it.
- Research: the specific detail must come from the person's profile or recent posts. That is the slow part.
Quicklead's AI personalization handles the research step by reading each prospect's profile and posts and drafting an opener, then generating five distinct variants and rotating them across leads so no two batches read identically. Review a sample before launching; AI can misread a profile just as a rushed human can. Because free accounts get so few notes, plan notes for Premium accounts and pair blank invites on free accounts with a profile visit or post like beforehand.
How do you test which connection note works?
Change one thing at a time, split the same audience evenly, and judge on acceptance rate after enough time for late accepts to arrive.
- 1
Pick one variable
The detail type (post versus company news), the length, or note versus no note. Not all three.
- 2
Split one list
Alternate variants within the same segment so differences come from the note, not the audience.
- 3
Send enough to learn
Aim for at least 100 invites per variant. With a weekly invitation ceiling, that can take a few weeks; the connection request limit explainer shows how to budget invites.
- 4
Wait two weeks, then compare
Many people accept days later. Compare acceptance and, more importantly, replies to your first message.
Acceptance is only the first step. What you send next decides whether the connection becomes a conversation; our guide to the LinkedIn follow-up message picks up from there.
Frequently asked questions
- What is the character limit for a LinkedIn connection request message? LinkedIn's main Help page says each note can be up to 200 characters. Another Help page mentions 300 for Premium members, but writing to 200 works on every account.
- How many personalized connection notes can a free LinkedIn account send? LinkedIn's Help Center says three a month on its personalization page and five on another page. Premium members can add notes to all requests, within the overall invitation limit.
- Should I mention my product in a connection request? No. LinkedIn asks members not to use invitations for promotional messages to people they don't know, and a pitch lowers acceptance. Introduce what you do in a later message, once there is a reason to.
- Is it better to send a LinkedIn connection request with or without a note? With a note when you have a specific, true reason and the person is senior or unfamiliar with you. Without one when shared context is obvious or you are on a free account with few notes left.
- Can I edit a connection request after sending it? No. You can withdraw it, but a withdrawn invite blocks a fresh one to that member for up to three weeks, so proofread placeholders before sending.
Sources
- LinkedIn Help: Personalize invitations to connect
- LinkedIn Help: Differences between InMail messages and personalized invitations
- LinkedIn Help: Connecting with other members, best practices
- LinkedIn Professional Community Policies