Follow up within 24 hours, reference one specific thing from the conversation, and make the ask small or make no ask at all. The timing matters less than the specificity — a message that could have been sent to anyone in the room reads as a template, because it is one.
TL;DR
- Send within 24 hours. Not because of urgency, but because that's while you still remember something worth referencing.
- One specific detail from the conversation is the entire message. Without it you're sending a form letter.
- Make the ask small, or skip the ask. "Good to meet you, here's the thing I mentioned" outperforms a meeting request you haven't earned.
- Most follow-ups fail before they're written — the detail worth referencing was never captured.
- I have no response rate to give you, and neither does anyone else publishing one on this topic.
When should I send the follow-up?
Within 24 hours, and the reason isn't etiquette.
- Same night
- What you can still reference: The actual conversation, in their words
- How it reads: Keen, and occasionally too keen
- Next morning
- What you can still reference: The specific thing they said
- How it reads: Right. This is the window
- Within 48 hours
- What you can still reference: The gist, roughly
- How it reads: Fine, slightly generic
- Within a week
- What you can still reference: The event, your job titles
- How it reads: A form letter with their name on it
- After a month
- What you can still reference: That you met
- How it reads: An apology wrapped around a request
The decay is in what you can say, not in what they'll tolerate. Nobody minds receiving a message four days later. The problem is that by day four you've lost the detail that would have made the message worth reading, so what you send is structurally identical to what everyone else in the room sent.
That's why "follow up faster" is slightly the wrong advice. The real instruction is: capture faster, so that following up later still has something in it. More on that in what to do with all those business cards you collect.
What should the message actually say?
Four parts. The whole thing should fit on a phone screen without scrolling.
Where you met, in six words. Not "it was great connecting at the event." Name the thing: the fintech evening in Bangsar, the panel on supply chains, the queue for coffee.
One specific thing they said. This is the message. Everything else is packaging. If you can't produce a specific detail, you don't have a follow-up — you have a contact request, and you should send something much shorter and stop pretending.
What you're giving, if anything. The article you mentioned, the intro you offered, the name of the supplier they were looking for. Deliver it in this message rather than promising it.
The smallest possible ask, or none. A follow-up that asks for a call after one conversation is asking a stranger for an hour. If you have no reason for a meeting, don't request one — say you'll be in touch, and be.
Here's the shape:
``` Subject: [Event name] — the [specific thing] we discussed
Hi [name],
Good to meet you at [event] on [day]. You mentioned [the specific thing they said] — [the relevant thing you're giving: a link, a name, an introduction].
[If there's a real reason: one sentence proposing it. If there isn't: "No need to reply — just wanted to send this over."]
[Your name] ```
That's a template for the structure, not a script. Sending it verbatim produces exactly the problem it's designed to avoid, because the whole value sits in the two bracketed specifics and those can only come from you.
What makes a follow-up get ignored?
Four things, in rough order of frequency.
Nothing specific in it. "Great to connect, let's keep in touch" is indistinguishable from every other message they received that week. It isn't rude and it isn't wrong. It's just empty, and empty messages get archived without malice.
An ask that's too large for the relationship. One conversation at an event buys you a reply. It doesn't buy you a 30-minute call, a referral, or an introduction to their boss. Requests that outrun the relationship put the recipient in the awkward position of either overcommitting or declining a near-stranger, and most people choose the third option, which is silence.
A promise not kept. If you said you'd send something, the follow-up is the sending. A follow-up that references the promise without fulfilling it is worse than no message.
Length. They met forty people too. A message that requires scrolling is a message that gets read later, which means never.
What response rate should I expect?
I don't know, and I'm not going to invent a number.
This is worth saying because every other article on this topic seems to have one. You'll see confident figures for networking follow-up response rates, usually round, usually uncited, usually followed by a claim that some specific technique doubles them. As far as I can tell, those numbers come from nowhere. There's no obvious body of research on how often people reply to a message from someone they met once at an industry event, and there couldn't easily be — the population is unmeasurable and the variables are enormous.
What I can tell you is what the variables actually are, because they're not mysterious. Whether you referenced something specific. Whether you delivered a thing or requested a thing. How long you left it. Whether they were expecting your message. How senior they are and how much unsolicited mail they get. Any of those swings the outcome more than phrasing does.
If you want a real number, measure your own. Send twenty follow-ups, log which got a reply, and you'll have better data about your own network than any published figure could give you. I intend to do exactly that and publish it, and until I have, this section stays empty rather than being filled with something plausible.
What if you've already left it too long?
Send it anyway, shorter, and don't apologise at length.
The instinct is to open with a paragraph explaining the delay, which doubles the length of the message and makes the delay the subject. One clause is enough — "meant to write sooner" — and then straight to the reason you're writing.
The bigger question is whether you have a reason. A late follow-up with a specific purpose is completely fine; people receive those constantly and think nothing of it. A late follow-up with no purpose beyond re-establishing contact is hard to write because there's nothing to write, and that difficulty is information. If you can't find a reason, the honest options are to wait until you have one, or to send something genuinely useful with no ask attached.
What doesn't work is a message whose entire content is that time has passed.
The reason this situation is so common is that the follow-up isn't really where things break. It breaks weeks earlier, at the point where the conversation should have been written down and wasn't. By the time you're staring at a card wondering what to say, the material that would have made the message easy is gone.
That's the gap I built Habitus Mind to close. Every person gets one record, and each later encounter merges into the same dated history rather than starting a second entry. You set a follow-up date yourself while you still remember why — and when it comes due, opening the dashboard shows you that person along with the notes you wrote, in your words. It doesn't interpret anyone or decide who matters. It extracts what's there and files it.
Habitus Mind is invite-only and admin-approved. There's no public signup. Request access.
How do you follow up with someone when you don't have a reason?
Most of the people worth staying in touch with fall into this category, which is why it deserves its own answer.
The move is to lower the stakes of the message rather than manufacture a pretext. Send something useful and close the door on a reply: an article that connects to what they were working on, a name they were looking for, a note that something they mentioned came up again. Then explicitly say no reply is needed. Removing the obligation is what makes these messages welcome rather than taxing.
The version that fails is the invented pretext — the "just checking in" that both parties know is a placeholder, or a manufactured question you don't need answered. People can tell, and it costs a little credibility each time.
The other honest option is patience. Some relationships have no next step for eighteen months and then suddenly have an obvious one. The only requirement is that when the reason appears, you can still remember who the person was and what you talked about, which is a storage problem rather than a communication problem.
FAQ
How should I follow up after a networking event?
Send within 24 hours, name where you met in a few words, reference one specific thing they said, and either deliver something useful or make no ask at all. The specific detail is the whole message — without it, you've sent a form letter.
How long should I wait before following up?
Within 24 hours is ideal, and 48 is fine. The limit isn't their patience, it's your memory: after a few days you can no longer reference anything specific, so what you send becomes generic regardless of how carefully you write it.
What should a networking follow-up email say?
Where you met, one specific thing from the conversation, whatever you're giving them, and the smallest possible ask or none. Keep it to a phone screen without scrolling. They met a lot of people that week too.
Is it too late to follow up after a month?
No, but shorten it and skip the long apology. One clause about the delay, then the reason you're writing. If you can't find a reason beyond re-establishing contact, wait until you have one or send something useful with no reply expected.
What response rate should I expect from networking follow-ups?
Unknown. Published figures on this exist but appear to be invented — there's no clear research base for how often people reply to a near-stranger from an event. Measure your own across twenty messages and you'll have better data than any article can give you.