You met her at the end of a panel, talked for six minutes about procurement software, and promised to connect. Two days later you open her profile, click Connect, and stare at the empty note box. A LinkedIn connection request message is about the smallest piece of writing in professional life, and it's surprisingly easy to waste. Most people either skip it or fill it with a line that could have been sent to anyone.
A good connection note does one job: it tells the person who you are to them, in words only you could have written, so the request reads as a continuation and not an interruption.
A connection note isn't a pitch, a cover letter or a place to ask for a meeting. It's a label on a door. The person should be able to read it in two seconds and know why to say yes.
When someone gets a bare request, they do a quick calculation. Do I know this face? Do we share people? Is this a recruiter or a seller? Without a note, you're asking them to do that work, and many won't bother.
A note also does something for you. It forces you to name, in one line, why this person matters to you. Six months from now, when you want to message them, that line is the thread you pick back up, and it's far easier to pick up a thread you once wrote down.
And a specific note signals attention. Anyone can paste their name into a template, so a generic message tells the recipient almost nothing about you. A line that picks up something they said on a panel, or a question they raised in a thread, is proof that you were listening. People are far more generous with someone who listened than with someone who simply found their profile.
This is the easiest case, and the one people most often get wrong by being vague. "Great to meet you at the conference!" tells her nothing. She met two hundred people.
Use the detail you'd remember if the roles were reversed.
Hi Odile, I was the one asking about vendor consolidation after your panel. Your point about pilots that never end has stuck with me. Would be glad to stay connected.
Callum, thanks for the tip on the night bus back from the summit. Good luck with the warehouse launch in March, I'd love to hear how it goes.
Why these work: each one names a moment only the two of you shared. The second one also gives Callum a reason to hear from you again in March, which turns a single meeting into the start of something.
Write the note within a day or two, while you still remember the details. If you capture a quick voice note on the way home, you'll have the specifics ready. We wrote separately about the details worth capturing after you meet someone.
Goodword lets you dictate who you just met and what you talked about on your phone, so the details are there when you write the note. Start your free trial.
When a mutual contact connects you, that person's name is the most valuable thing in the note. Put it first.
Hi Beatriz, Wendell Shaw suggested we talk since we're both rebuilding onboarding at Series B companies. Connecting here so I can follow up properly.
Jon, Ingrid mentioned you spent three years in the Lisbon office. I'm moving there in the spring and would value your take at some point. No rush at all.
Why these work: they borrow trust that already exists and explain the overlap in one clause. The second example names a future ask but defers it, which keeps the request itself low-pressure.
If you haven't yet asked the mutual contact for an introduction, do that first. A note that names someone who hasn't agreed to be named can backfire. Getting that permission is its own small craft, covered in our post on requesting a warm intro.
Cold requests are where notes earn the most and where most people fail. The common mistake is leading with your own goal. Asking a stranger for their time in the very first note is asking for unpaid work.
Lead with what you noticed about them, and be honest about why you're reaching out.
Hi Anders, your write-up on cutting cloud spend at a 40-person company was the clearest thing I've read on it. I'm working on the same problem at a smaller shop and wanted to follow your work.
Soledad, I saw you moved from clinical research into product. I'm early in a similar change and it's encouraging to see someone a few years ahead. Hope it's fine to connect.
Why these work: they're specific enough to prove you didn't send them to fifty people, and they make no demand. Either person can accept without feeling they've signed up for anything.
If a cold connection does turn into a real exchange later, that's when a longer message becomes appropriate. A note's job ends at the yes.
Sometimes you're sending a request to someone you used to know well: a former colleague, a classmate, a client from a past job. The note should acknowledge the gap without making a big deal of it.
Rafael, I realized we never connected here after the Denver project. Still think about that week we rebuilt the forecast in two days. Hope the new team is treating you well.
Why this works: it skips the apology, names a shared memory and leaves the door open. For a fuller approach to rekindling these ties, see the best way to reconnect with old contacts.
A few patterns reliably lower acceptance, or get accepted and then forgotten:
Each of these makes the same error. It treats the note as a way to get something now, when its real value is setting up a relationship for later.
An accepted request is a beginning, not an outcome. Don't follow it with an immediate pitch or a long message. If there's a natural next step, like the March launch or the Lisbon move, make a note of it and come back when the time is right.
Our article on follow-up after networking events covers what to do in the weeks after a first meeting. And if you want reminders built around the moments that matter for each person, Goodword keeps the context attached to the name.
The note itself takes a minute. Spend that minute on the one detail that makes it yours, and the rest of the relationship has somewhere to start.
Goodword helps you remember why you connected with someone long after the request is accepted. Give Goodword a try.
For anyone who might not instantly recognize you, yes. A note makes it far easier for them to place you, and it gives the connection a starting context. For close colleagues who see you every day, a bare request is fine.
Two or three sentences is plenty, and the space for a note is short anyway. One specific detail about how you know them or why you're reaching out is worth more than any amount of background about yourself.
It's usually fine to connect with people you met during the process, especially with a short note thanking them for their time. Avoid using the note to lobby for the job. Keep it to the conversation you had.
Let it go. People leave requests pending for all kinds of reasons, including rarely checking the app. If you have a real reason to reach them later, an email or a mutual contact is a better route than resending the request.
It isn't a disaster. If they accept, send a short message soon after with the detail you would have put in the note, so the connection still starts with context. If the request sits unanswered and the person matters, wait a while and reach them another way, through a mutual contact or email.
