Three minutes of small talk calls for a different kind of follow-up.
Most conference contacts are quick exchanges, not deep conversations. Following up on those takes a structurally different message with a different job.
The card with nothing on the back
It's Thursday morning after the conference and there's a stack of cards on your desk. You can place maybe a third of them. One has a note scrawled on it: “Q4 vendor review.” Another has nothing. You remember the person was friendly, you remember the coffee line was long, and you remember the conversation ended when the keynote doors opened.
So you open a blank email and type “Great connecting with you at the expo.” Then you stare at it.
The sentence is true in the thinnest possible way. You did connect, for about three minutes. But anything warmer than that is a guess, and the person on the other end will read it as one.
Most of the contacts from a busy event look like this card. Very few look like the long dinner conversation that follow-up advice is written for.
The three-minute contact is its own category
Call it the three-minute contact: someone you met, swapped a card or a QR scan with, and learned one or two facts about. It sits below a worked lead and well below a relationship. A name, a company, maybe a single detail.
A follow-up to that person isn't a weaker version of the deep-conversation follow-up. It's a structurally different message with a different job.
The deep-conversation follow-up bets on their memory. It works because you both spent real time on a shared problem, and your message picks that thread back up.
The three-minute follow-up can't make that bet. There's no thread. Its job is to create a low-friction opening: one concrete reason to talk, and an ask small enough that saying yes costs them nothing.
Why most follow-up advice misfires here
Standard networking advice tells you to reference something specific from your conversation, mention a shared laugh, pick up where you left off. Good advice for the dinner. For the coffee line, it pushes you toward one of two failure modes.
The first is manufactured warmth. You stretch the one detail you have into a paragraph of rapport (“I really enjoyed our chat about the future of logistics”) and the recipient, who doesn't remember the chat either, gets a message that reads like every cold email already in their inbox.
The second is the big ask. Because the deep-conversation playbook ends in a meeting request, the brief-encounter version does too. Thirty minutes on the calendar is a reasonable request from someone who's already earned it. From a near-stranger it's a cost, and people decline costs.
Neither failure means the encounter was wasted. Three minutes is a perfectly good start. It just supports a smaller, sharper message.
Warmth without a shared memory underneath it is just the cold-email tone with better manners.
How to write a follow-up message after a networking event when the conversation was short
The question shows up in Google's People Also Ask results for networking follow-up, and the guides that rank for it tend to share an assumption: that a real conversation happened. Their examples reference a discussion explored at length, a mutual interest, a promise to send something.
That leaves out the contact people tend to collect the most of. A busy expo floor produces a handful of real conversations and a much longer list of quick exchanges at booths, in hallways, and between sessions.
The two follow-ups differ on almost every axis that matters.
Deep-conversation follow-up
Three-minute follow-up
What it bets on
Their memory of a real exchange
A reason to talk that stands on its own
What it references
The thread you both worked on
Where you met, plus the one thing they said
Tone
Picks up where you left off
Plain and specific, no implied rapport
The ask
A next meeting or concrete next step
Something they can say yes to in one line
Length
As long as the thread needs
Short enough to read on a phone between sessions
What kills it
Waiting until the memory fades
Pretending the memory exists
The two follow-up types compared by the job each message has to do. Structure, not wording.
Both types, worked through
Take two contacts from the same hypothetical logistics expo.
Contact one is an operations director you spent over half an hour with at a reception, walking through why their last warehouse-scanning pilot stalled. You promised to send notes on how a similar team staged its rollout. That follow-up builds itself around the promise: name the stalled pilot, send the notes, suggest a call on the one part they pushed back on. It's detailed because the conversation was. And it needs to go out while the reception is still fresh, which is the core argument of our piece on the 72-hour memory cliff.
Contact two is a procurement lead you met in the coffee line on day two. Three minutes. The one useful fact: their team reviews field-service vendors before year end.
A message to this person does three things and stops. It places the encounter in a single clause (coffee line, day two), so they can decide whether they remember you without being asked to. It names the one fact they gave you, because that's the only honest bridge you've got. And it offers something with an easy yes: a short write-up relevant to the vendor review, sent only if they want it.
In practice: “We crossed paths in the coffee line on day two of the expo. You mentioned a vendor review before year end. I have a short write-up on how teams your size scoped theirs. Want me to send it?”
Four sentences. No “great connecting.” No meeting request. If they say yes, the next message has a thread to pull, and the contact starts moving into the other column.
Copy the structure, not the words
The coffee-line message works because every sentence is specific to that one contact. Pasted across a stack of cards, the same wording turns into the cold email it was built to avoid. And if you don't have the one fact, don't invent one: say where you met and ask a genuine question they can answer in a line.
What changes if you take the split seriously
The sorting has to happen at the moment of capture. By Thursday you can't tell which cards were which, and a card with no context defaults to three-minute status. One with no usable fact at all is often better skipped than forced.
The detail you note down matters more than the card itself. For the deep conversation, you'll remember plenty. For the coffee line, that one fact (the vendor review, the hiring push, the office move) is the entire follow-up. Lose it and there's nothing honest left to write.
Silence reads differently too. A three-minute contact who doesn't reply simply didn't opt in. That's information, and it frees your time for the ones who did.
And the smaller ask turns out to be the stronger one. A yes to “want me to send it?” costs them almost nothing, and it starts the thread the deep-conversation follow-up takes for granted.
Keeping the one fact attached to the person
Most card scanners treat every contact the same way: name, title, email, a row in a list. Fine for the deep conversation, where memory fills in the rest. It fails the three-minute contact, because the only thing worth keeping is the sentence you heard in the coffee line, and no card has that printed on it.
Met is built around keeping that sentence with the person. Event Mode keeps capture fast enough to log a card and a line of context while the next conversation is already starting. The follow-up draft works from what you captured, so a brief-encounter message stays brief and honest. Contacts live in your own iCloud, not on someone else's server.
The stack of cards will still be on your desk Thursday morning. What matters is whether each one still has its fact.
Get Met before your next event and keep the one fact that makes the follow-up worth sending.
Met is built for people who meet more contacts than they can remember: Event Mode for fast capture on a crowded floor, a line of context kept with every card, and follow-up drafts built from what you actually captured. No ads, no data sold, and your contacts stay in your own iCloud.
