The short answer
Follow up while the conversation is still easy to remember. Remind the person where you met, mention one specific thing you discussed, and offer one useful next step. If you promised a resource or introduction, start there. A thoughtful message does not need to be long.
1. Save the details that will help you reconnect
Before the names and conversations blur together, make a short note for each person you want to stay in touch with. A business card gives you contact details. Your note should preserve the reason to use them.
- Where you met and what you talked about
- One detail they would recognize from the conversation
- Anything you offered to send, answer, or introduce
- The next step you actually agreed on, if there was one
For example: “Met at the design meetup. Comparing ways to onboard volunteers. I offered our checklist. Send it Friday.” Keep notes relevant and respectful. Do not collect sensitive details just because they came up in conversation.
2. Choose a useful time and channel
If you agreed on a date, use it. Otherwise, the next day or two can be a practical starting point while the event is fresh. This is a working habit, not a rule: a useful message sent later is better than a rushed message that says nothing.
Use the channel they offered or the one where you already connected. Exchanging a card is an opening for a relevant follow-up, not permission to add someone to a mailing list. Avoid sending the same message through several channels at once.
Already a week late? Acknowledge the gap briefly if it matters, then return to the conversation. You do not need a long apology.
3. Write a message with one clear next step
A useful follow-up has three parts: a reminder, a reason, and an easy response. Identify the event, bring back a concrete topic, then deliver what you promised or make a small invitation.
“Great meeting you” can be a warm opening, but it is not enough on its own. Add the detail that makes the message recognizably theirs. If you are asking for time, explain what you would like to discuss. If there is no natural request, sending the resource you mentioned is enough.
Before sending, check the name, links, and any commitment you are making. Keep the note short enough that the next step is obvious.
4. Three follow-up messages to adapt
These are fictional examples. Replace the details with what actually happened; do not imply a promise or interest the other person did not express.
You promised a resource
Subject: Volunteer onboarding checklist
Hi Alex, it was good talking at the design meetup yesterday. Here is the volunteer onboarding checklist I mentioned: [link]. The first-week section is the part we discussed. Hope it is useful for your next intake.
You want to continue the conversation
Subject: Continuing our conversation about community events
Hi Alex, I enjoyed hearing how you approach smaller community events at Thursday’s meetup. I am working through a similar question about welcoming first-time attendees. Would you be open to a short call next week to compare notes? No pressure if your schedule is full.
You are reaching out later than planned
Subject: The checklist from last week’s meetup
Hi Alex, I meant to send this sooner. We spoke at last week’s meetup about volunteer onboarding, and I offered to share our checklist: [link]. I hope the first-week section is still useful. It was lovely meeting you.
5. Leave room for no reply
People miss messages, get busy, or decide not to continue a conversation. A quiet inbox does not tell you which. If there is a genuine reason to reconnect, one brief follow-up after a reasonable gap can make sense. Add useful context rather than just asking whether they saw your message.
If there is still no response, let it rest. Respect a decline or request not to be contacted. A reminder should help you keep a promise, not turn a new connection into a sequence they never asked for.
For the relationships that do continue, save the new context and the next agreed step. That is the habit: remember, follow through, and make the next conversation easier.