Your 90-day reminder can't tell you what to say.

The reminder fires, and there's nothing there

The reminder fires at 9:40 on a Tuesday: “Check in with Priya.” You set it in March, right after a logistics conference, on the advice that every good contact deserves a touch once a quarter. It's now June.

You open a blank message. Priya ran... something. Operations? At a freight company, or maybe a freight software company. You talked for twenty minutes near the coffee station and it went well, you're pretty sure. That's all you have.

So you type “Hope you're doing well! Just checking in.” And you delete it, because you'd ignore that message too. Then you snooze the reminder for two weeks.

The schedule did its job. It fired on time.

It just had nothing to hand you.

Context beats cadence

Scheduling check-ins is a workaround for not having anything to say. That's the whole problem in one line, and it's why the calendar-first approach to keeping relationships warm keeps producing messages nobody wants to answer.

People who hold genuinely warm networks tend to work the other way around. They reach out when something happens: a promotion, a funding announcement, a talk the contact gave, a product that finally shipped. The outreach has a reason, and the reason is about the other person.

Call it the trigger test. Before you send, can you name the event that prompted this message? If you can, it'll read as specific and timely. If you can't, it's a check-in, however nicely it's worded.

But a trigger only counts if you recognize it. A contact's company opening a Denver office means nothing unless you remember they told you, six months ago, that they were trying to get out of Chicago winters. The trigger lives in the world. The relevance lives in what you wrote down at the first meeting.

A reminder can tell you when. It can't tell you what.

The cadence number, and what the research says instead

Search for how often to reach out to keep professional relationships warm and most answers land on a number. Every 90 days. Once a quarter. The number is appealing because it's actionable, and because it turns a vague social anxiety into a task you can check off.

But a cadence treats a relationship like an oil change: service it on the interval and it'll keep running. Relationships go cold when the last exchange stops being relevant to anyone's actual life, and a scheduled ping doesn't restore relevance.

The research points the same direction. Mark Granovetter's 1973 paper "The Strength of Weak Ties" argued that acquaintances, more than close friends, carry new information into your life, which is why the conference contact you barely know is worth keeping at all.

Later work looked at reconnection directly. In a 2011 Organization Science study, Daniel Levin, Jorge Walter and J. Keith Murnighan had executives reach out to contacts they'd been out of touch with for years, and found those dormant ties often delivered more novel, useful input than their active ones. A long gap wasn't the liability people assume.

Research by Peggy Liu and colleagues in the Journal of Personality and Social Psychology points the same way. People tend to underestimate how much a brief, unprompted reach-out is appreciated.

None of this argues for a tighter schedule. It says silence is recoverable, and that an unexpected, specific message beats a predictable one. A reminder still has a fair use: for contacts you'd otherwise never think of, it's better than nothing. The trouble starts when the reminder becomes the whole system.

Which triggers are worth a message?

Not every event is a reason to write. The useful line is whether the trigger connects to something the contact told you, or only to something the whole internet can see.

High-signal triggers let you reference the original conversation. Low-signal triggers are real events with no thread back to you, so your message becomes one of dozens in their inbox that morning. A promotion announcement gets a wall of congratulations. A promotion into the exact role they said they wanted gets remembered.

The same contact, two ways

Back to that conference in March. Say that during the twenty minutes by the coffee station, you'd captured three lines before the next session: runs ops at a freight software company; rebuilding customer onboarding, stuck on the handoff from sales to implementation; needs a data lead, can't find one who knows logistics.

In June, the calendar version still fires. You still have nothing, so you send “just checking in,” get no reply, and the relationship is a little colder than before you wrote.

The trigger version doesn't wait for June. In August, the company posts that its new onboarding is live. That note turns a press release into a reason: “Saw the new onboarding shipped. When we talked in March, the sales-to-implementation handoff was the sticking point. Did the fix hold?”

Two sentences. Only someone who was listening could send them.

Then in October, a former colleague mentions they're leaving a logistics analytics role. That's a trigger too, and a better one, because now you're bringing something instead of asking for attention.

What changes if you run on triggers

The work moves. In a cadence system, the effort goes into the reminders: setting them, snoozing them, dreading them. In a trigger system, the effort goes into the first meeting, and the two minutes afterward when you write down what the person is trying to do, what's in their way, and what they'd want to hear about.

You'll send fewer messages. Each one will be about them.

Keep a floor if you want one. A yearly nudge for contacts who never make news is reasonable, as long as it prompts you to go look for a reason rather than to send nothing in particular. But if your system can't tell you what to say, it isn't a relationship system. It's an alarm clock.

Where capture fits

No alert knows which headline matters to which person you met, because only you heard what they said they were working on. That recognition stays yours. What software can do is make capture fast enough that it actually happens: in the hallway, between sessions, before the next conversation overwrites the last one. We've written about how fast that window closes in [The 72-Hour Memory Cliff](/articles/72-hour-memory-cliff/).

Met is built around that moment. Event Mode keeps the room captured while you keep talking, the note about the onboarding project sits with the contact instead of on the back of a card, and it all stays in your iCloud rather than on someone else's server. So when the announcement lands in August, the context you need to recognize it is already there.