What to Say in 300 Characters: The LinkedIn Connection Note
Real LinkedIn connection request examples that use every character with purpose, from building a partner network across two continents.
When I was building the partner agent network across India and Southeast Asia from scratch, LinkedIn connection requests were the first touch for most of it, before an exhibition badge, before a call, before an email. Three hundred characters is not a lot of room, and most people waste it on a greeting and a job title nobody asked for.
Here is what actually fits in 300 characters, and what I stopped doing after the first fifty tries.
The note that gets ignored
What does not work: "Hi [Name], I came across your profile and would love to connect. I work in business development and think we could benefit from being connected." That is 178 characters and says nothing. It could go to anyone on the platform. Acceptance rate on notes like that sits somewhere around 15 to 20 percent in my experience, and the people who do accept rarely reply to the first message after.
What works is one specific fact plus one specific reason, no greeting needed, since your name is already on the request.
Two connection notes that actually worked
Example sent to a travel agency owner in Bengaluru during partner network building:
"Saw [Agency] is expanding outbound packages to the Gulf this year. I build partner networks for a European tour operator entering India and I am mapping agencies with outbound Gulf experience specifically. Would be useful to connect before I am in Bengaluru next month."
That is 271 characters. It names the company, states a specific business fact about them, states exactly who the sender is in one clause, and gives a real, time-bound reason for connecting now rather than someday. Acceptance rate on notes built this way ran closer to 55 to 60 percent across the campaign, and the ones who accepted usually replied to the first real message within a week because the note had already done the work of explaining why.
Second example, sent to a procurement lead at a hospitality group during the same period:
"Your group's new property in Goa caught my eye. I work with hotel groups on distribution partnerships in the Gulf market and wanted to connect ahead of reaching out about your outbound sales channels there."
That is 214 characters, leaving room to spare, which is fine, using all 300 is not the goal, saying only what earns attention is.
Three rules behind every note that converts
Three rules that held up across hundreds of these:
First, name something true about their business before naming yourself. The order matters because the reader decides in the first line whether this is about them or about you, and if it is about you first, most people stop reading before the second sentence.
Second, state your reason for reaching out in one clause, not a paragraph. "I build partner networks for a European tour operator" does the job. Do not explain your whole role, your company history, or your value proposition, there is no room and no one asked yet.
Third, give a reason the timing is now. "Before I am in Bengaluru next month" or "ahead of reaching out about" signals this connection has a near-term purpose, not a someday-maybe networking add. Requests with a time element attached outperformed requests without one by a wide margin, because they read as a real plan rather than a collection habit.
What doesn't belong in a connection note
One thing that does not belong in a connection note: the actual ask. Do not pitch, do not propose a call, do not attach a value proposition. The note's only job is to get accepted and set up the first real message to land in an inbox that already knows why you showed up. Save the ask for the message that follows once they accept, that is a different 300 characters worth of work entirely.
If you are staring at a blank note field, skip the greeting entirely and start with the fact. The greeting is free real estate you are currently paying for with the room a real reason should take.
Say the fact first. Say who you are second. Save the ask for later.
Updated: September 2026
Working on the same problem? Always happy to compare notes.
Let's explore synergies