A re-warm with no callback is a cold email with your name on it.

The intro request that exposes a cold contact

A former colleague messages on a Tuesday afternoon. They're raising a seed round, and they've noticed you know a partner at a fund they'd love to meet. Could you make the intro?

You say yes before you think about it. Of course you will. You met that partner at a conference last winter, had a real conversation over bad coffee, swapped cards, and haven't spoken since.

Then you open a blank email to the partner and type the only thing that comes to mind: "Hi, hope you've been well. It's been a while! I wanted to reach out because..."

Read it back.

That's the exact email you archive from strangers every week. The partner will read it the same way, because from their side of the inbox, nine months of silence plus a vague greeting plus an incoming ask looks like a cold pitch with your name attached.

The intro breaks before it's written

Most advice about warm introductions focuses on the intro email itself: the forwardable blurb, the double opt-in, the clean subject line. That advice skips the step where intros usually die.

Call it the cold re-warm. Before you can introduce anyone, you have to get back in touch with your contact, and if the relationship has gone quiet, that first message carries the whole intro on its back. A re-warm with no specific reference to your last conversation is structurally the same as a cold email. Same shape, same signal, same likely outcome.

There's a quick way to check which one you've written. Run the callback test: could this message have been sent to anyone else you've ever met? If the answer is yes, it's cold, however friendly the sign-off.

Why "it's been a while" reads as cold

The standard reconnection playbook says to be honest about the gap, keep it short, and lead with value: share an article, congratulate them on a promotion, ask how the quarter is going. Each of those moves is reasonable for a pure catch-up. Each of them fails the callback test.

A congratulations pulled from a job-change notification is something plenty of people sent that same week. An article share shows effort, and it also shows you went looking for a pretext. And "how's the quarter going?" reads as filler once the next message turns out to be a favor.

The double opt-in template has the opposite gap. It's a good protocol (ask your contact before connecting them, so nobody gets ambushed), but it's written as if the relationship is already live. "Would you be open to an intro?" works well between people who talked last month. Sent after nine months of silence, it's a request with no relationship underneath it.

How do you reconnect with a contact before making an introduction?

Search that question and the results split into two piles. One pile is general reconnection advice, written for someone restarting a dormant relationship for its own sake. The other is double opt-in templates, written for a connector whose relationships are already warm.

Neither pile covers the connector's actual position. You've already said yes to a third party. You owe them an intro. And you have to reopen a quiet thread without the ask feeling like the reason for the message (even though it is the reason).

That position has a specific shape. The re-warm and the ask arrive close together, so your contact will connect them. Any pretense of a pure catch-up collapses the moment the ask lands. What survives is evidence that you remembered them as a person, with a detail only someone who was in that conversation could know.

Two re-warms, side by side

Go back to the fund partner. Here's the generic version again: "Hope you've been well! It's been a while. I wanted to reach out because I know someone you should meet."

Now a version that passes the test: "Last winter you told me you were trying to stop taking first meetings on decks alone and wanted to see founders demo live. I've got a founder who'd rather show than pitch. Before I send anything over, would you want the intro?"

The second message spends its opening line on proof. It tells the partner three things the first one can't: that you listened, that you're filtering on what they said they wanted, and that you're asking permission before forwarding anyone. It also makes the ask honest. There's no fake catch-up to unwind.

Now trace that message backward. The sentence that makes it work, the detail about live demos, had to exist somewhere. It came from the original conversation, nine months earlier. If nobody wrote it down then, it isn't available now, and no amount of drafting skill brings it back.

The intro is decided at the original meeting

If the cold re-warm is where intros break, the fix sits months upstream of the ask. The quality of an introduction you make in October gets set by what you captured in January, at a conference table, in the few minutes after the conversation ended.

That changes what being a good connector means. The skill that counts is keeping one usable detail per person: what they're building, what they're stuck on, what they swore they'd never do again. One line is enough. It's the raw material for every future re-warm, and it fades fast. Our piece on the 72-hour memory cliff covers how quickly that kind of context disappears once an event ends.

And when you don't have the detail? Skip the fake catch-up. Send a short, plain message that names the gap, states the ask, and makes saying no easy. A transparent cold ask costs you less than a pretend warm one that turns into a favor two lines later.

Contacts forgive a direct request. They remember being worked.

Where Met fits

Met is built for the minute after the conversation, while the detail still exists. You capture the contact, and the context goes with it: the line about live demos, the project they mentioned, the thing you promised to send. Event Mode keeps the room captured while you keep talking, and everything stays in your own iCloud rather than on someone else's server.

Nine months later, when an intro request arrives, the callback is already on the contact card. The re-warm starts with a sentence your contact will recognize, because they said it.

The intro email is the easy part. Make sure the message before it has something real to say.