The six-month-old warm intro is a capture problem wearing a follow-up costume.

Six months later, the thread is still open

The intro email is still sitting in your inbox. A former colleague wrote it in March: two short paragraphs, a line about why the two of you should talk, and a cc. You replied within the hour. The first call went well. Then a reorg on their side, a quarter-end on yours, and the thread stopped.

Now it's September and you want back in. You open the email to write the follow-up and hit a wall. What did the connector actually say the fit was? What was the other person trying to fix? Did you promise to send them something?

The inbox has the intro. It doesn't have the conversation.

So you write the email everyone writes in this spot. And it goes nowhere.

The real problem is context debt

Call it context debt. Every warm intro creates a small pile of specifics: the connector's framing, the other person's live problem, the next step somebody named out loud. Those specifics are what make the intro warm. Strip them out and you've got a cold email with a mutual friend's name on it.

The debt builds quietly. On the day of the call, you could have told anyone the three things that mattered. A week later, maybe two of them. Six months on, you're holding a name, a company, and a faint sense that it went well.

Most re-engagement advice treats this as a writing problem. Find the right words, the right tone, the right excuse for the gap. But phrasing isn't the bottleneck. The material you'd build the email from is gone, and no amount of rewording brings it back.

Why 'reference your last conversation' falls apart

Guides to reviving a stalled introduction tend to land on the same instruction: reference your last conversation. It's correct advice. It's also written for someone who remembers the last conversation.

That assumption holds up the whole method. When the context is fresh, you barely need a guide. When it's stale, the guide tells you to use the one thing you're missing, so people fill the gap with whatever they can reconstruct. A company name. A title pulled from LinkedIn. A guess at what the call covered.

The guess is where revivals go wrong. It produces three recognizable emails, and each one fails for a different reason.

Three ways a dead-intro revival fails

Faux-familiarity. The email acts like no time has passed. 'Great to reconnect! Still thinking about what you said about your pipeline.' If the recipient can't place what they said about their pipeline, and you can't either, the warmth reads like a mail merge. Enthusiasm with no specifics under it is easy to spot.

The context-free check-in. 'Just checking in to see if the timing is better now.' Polite, short, easy to ignore, because it asks the recipient to do the remembering. You're handing them the job of reconstructing why this intro mattered. Most people won't take it.

Over-explaining the silence. Three sentences about the busy quarter, the travel, the reorg. It's an apology for a gap the other person barely registered, and it buries the one useful line at the bottom. Six months of quiet between two busy people is ordinary. Treating it as a breach turns it into one.

Underneath, all three are the same email. Each is what you write when the specifics are missing.

What the revival looks like with the context intact

Walk one through. A consultant gets introduced by a former client to the head of operations at a regional distributor. The connector's framing: the distributor is moving carrier scheduling off spreadsheets and keeps getting burned by vendors who sell software instead of process. The first call goes well. The ops lead says to follow up after their Q2 system cutover. Then six months of nothing.

Working from memory, the consultant sends the check-in. Working from a record, the email is four sentences. Your cutover should be behind you now. Our mutual contact mentioned the vendors selling software instead of process, and that's the gap I work in. Here's a one-page note on what tends to break in the first months after a scheduling migration. Worth 20 minutes?

No apology. No borrowed enthusiasm. Every line proves the sender was listening in March.

Then close the loop with the connector. A one-line note saying you've picked the thread back up costs nothing, and it tells the person who vouched for you that the intro was worth making.

Re-engagement starts the day of the intro

If context debt is the real problem, the fix moves upstream. The September email gets written, in effect, on the day of the first call, when the specifics are still sharp enough to note in a few lines.

The trigger is the line people skip, and it matters most. It's what tells you when silence stops being a stall and becomes an opening. 'After the cutover' or 'once the board meets' is a date you can act on, even if nobody put it on a calendar.

This changes how to read the stall itself. A warm intro that goes quiet usually hasn't failed. It's waiting on something one side named and both sides forgot. Keep the name, and a six-month revival is just a promise kept late.

Keeping the context attached to the person

Met is built around that day-one moment. You capture the person, and the context goes with them: where you met, who made the introduction, what they're working on, what you said you'd do. It lives on the contact, so six months later the revival starts from what was actually said, not from a guess. Your contacts stay in your own iCloud, not on someone else's server.

When the trigger finally fires, the specifics are already sitting there. The email that follows sounds like someone who was paying attention, because the record shows you were.

A warm intro is the highest-stakes version of a broader problem. Our piece on the 72-hour memory cliff covers how fast meeting context slips in general, and why capture has to happen before the week is out.