LinkedIn Connection Requests After Events: What to Write So People Remember You
LinkedIn gives you 300 characters for a connection note. Most people use zero of them, and then wonder why the person they had a genuinely good conversation with on Tuesday accepts the request on Friday and never thinks about them again.
Acceptance was never the goal. Almost everyone accepts requests from people they have plausibly met. The goal is that when your name appears, the person thinks "the scheduling conversation at the expo" instead of "who is this?". A blank request cannot do that. A good note does it in one line.
Send it the same day
Timing does more work than wording. The person you met is having dozens of conversations this week, and you occupy a small, fading slot in their memory. A request that arrives the same evening lands while the conversation is still warm. The same request ten days later arrives from a stranger.
Same day also means you can be light on explanation. "Good talking earlier" needs no setup on Tuesday evening. By the following week you are writing "we met at the conference last Tuesday, I was the one who..." and burning your 300 characters on re-introduction.
What the note needs
One specific reference to the conversation, one human touch if you have one, and no pitch. That is the whole formula.
Here is the same request three ways, for a conversation with an operations director named Marcus about warehouse scheduling:
Blank. No note at all. He accepts it Thursday, between two other requests, and your name enters his network with no memory attached.
Generic. "Hi Marcus, great to connect at the Logistics Show! Would love to add you to my network." This is technically a note, but it contains nothing only you could have written. It reads like the other six requests he got from the same event.
Specific. "Good talking scheduling headaches this morning, Marcus. Enjoyed the debate about whether peak season planning ever survives contact with peak season. Would be glad to stay connected." Twenty seconds to write, and it does something the other two cannot: it replays the conversation in his head.
Notice what the good one leaves out. No product mention, no "I'd love to show you", no link. The note is a memory anchor, not outreach. The selling conversation, if there is one, happens in the follow-up email a day or two later, which we cover in detail in our guide to following up after a conference. Trying to compress a pitch into a connection request usually costs you both.
Keep it between roughly 120 and 180 characters. That is enough for one real detail and it leaves room to breathe. If you are pasting up against the 300 cap, you are explaining too much.
Should you ever send a blank request?
To a stranger you have never met, arguably, since there is nothing genuine to say. To someone you actually spoke with, no. You possess the one asset a note is made of, a shared moment, and leaving it out throws away the only advantage you have over every recruiter and lead-gen bot in their inbox.
Where Heap fits
The reason most event connections go noteless is friction, not ignorance. Finding the right Marcus among forty profiles, on a phone, between sessions, is enough hassle that people defer it, and deferred usually means never.
This is what Heap's LinkedIn feature is for. When you capture a lead by describing the conversation, Heap finds their LinkedIn profile so you are not searching manually, and drafts a connection note from the context you gave it, inside the character limit, referencing what you actually discussed. You read it, adjust a word if you like, and send it yourself.
That last part is deliberate. Heap never sends anything on your behalf and never automates LinkedIn actions. LinkedIn has spent the last few years aggressively restricting accounts that use automation tools, and a restricted account at a networking event is a disaster no time-saving justifies. You stay in control of every send. Heap just removes the searching and the blank-page problem.
Frequently asked questions
Should I add a note to a LinkedIn connection request? If you have met the person, always. The note is what turns an accepted request into a remembered one. Reference the specific conversation, keep it under about 180 characters, and skip the pitch.
How soon after meeting someone should I connect on LinkedIn? The same day, ideally the same evening. Your note can be shorter and warmer while the conversation is fresh, and you avoid the awkward re-introduction a late request needs.
Can I include a link or a pitch in the note? You can, and you should not. The note's job is to anchor the memory of meeting you. Save the substance for a follow-up message after they accept, when you have space and their attention.
What if I cannot find the person on LinkedIn? Common names and sparse profiles make manual search genuinely hard. A tool that matches from your description helps, but when there is real ambiguity, check the company and location on the profile before sending. A connection request to the wrong Marcus helps nobody.
The bottom line
The blank connection request is a wasted asset. You met the person, which is more than almost anyone else in their request queue can claim, and one specific line is all it takes to prove it. Send it the same day, mention the thing you actually talked about, leave the pitch out, and let the follow-up email do the heavy lifting later.
