What counts as a real trigger for an HR reopen?

A freeze lifting, a new TA lead, a SOC 2 window, a public hiring surge, or a role change. Your internal QBR is not a trigger. Their birthday is not a trigger. A careers-page change they posted this week is. If you have to squint, wait.

Should I reference the old proposal numbers?

No. Prices and packs move. Say you can send what changed. Don't quote a 6-month-old SKU like it's still live. If they want numbers, they'll ask. Stale commercials in a reopen look sloppy and lock you into a discount conversation.

Can I use a new case study as the trigger?

Only if it's in their segment and you can name it without leaking a customer they would recognize as a competitor. Generic we just helped a SaaS company is not a trigger. Specific and safe, or skip it and use their public news instead.

What if they left the company?

Write the new director with a new reason, or write the old director at the new domain if you actually knew them. Don't bounce around until someone bites. Don't BCC both. One honest recipient. LinkedIn is for finding the path, not for pasting the pitch.

How many long-silence reopens can I send a year?

One per real trigger, twice a year at most. More than that and you're a cadence tool. Quality of trigger beats quantity of mail. If two reopens die, put them on a do-not-mail list until they raise a hand. That's the working rule here.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · HR Director · Long Time No Contact

Follow-Up Email After Long Silence with a SaaS HR Director

A long-time-no-contact note to a SaaS HR director is a re-introduction with a reason that belongs to this week. Don't open with it's been a while and paste the old culture pitch. A freeze lifting, a new TA lead, a SOC 2 window, or a public hiring surge is a trigger.

Copy-ready template

Subject

[Trigger] at [Company Name], still a time-to-fill problem?

Body

Hi [First Name],

I'm not restarting last year's people-ops thread. [Trigger: freeze lifting / new TA lead / SOC 2 window / hiring surge] is new. [Your Name] ([Your Company]). We talked last [Month] about [Old Problem: time-to-fill / onboarding / manager tickets].

If that leak still shows up in [Company Name] reviews, I can send a 1-page on what changed in our [Process] since then. If that hiring leak is gone, archive it. Archive or send, both are useful answers.

[Your Name]
[Your Title]

Why this follow-up works

You refuse nostalgia, which is what stale sequences lead with.
The trigger is dated to this week, so it earns the reopen.
One-line identity is enough. They shouldn't have to dig.
Archive is an honorable door, which HR directors actually use.
You offer a page on what changed, not the same deck from Q2.

When should I send this to a SaaS HR Director?

Send when you have a real trigger, not because a cadence tool hit 180 days. After a public freeze lifts, wait two business days so every vendor has already mailed them. After a SOC 2 announcement, wait until that week ends. After an HR director change, write the new person with a new reason, not the old thread. If this reopen dies, don't send a breakup three days later. You already offered archive. Leave it. You can try once more next year with a different trigger. Two empty reopens in a quarter is how domains get filtered.

What this HR Director actually cares about

They may not remember you. That's fine. Fresh start. Don't scold them for the gap. Don't call the email a reconnect. Show a new observation about their world. Keep it short enough to finish between interviews. Two or three short paragraphs, one ask, no attachments on first reopen. If you need more room, offer a one-pager they can refuse. HR directors punish wordiness because every extra sentence costs calendar. They also punish fake intimacy. You are not old friends because you emailed twice last year. Don't joke about culture. Don't treat headcount news as a lead.

How SaaS changes the note

SaaS people orgs change shape every two quarters. The HR director you wrote in March may have a new TA lead, a new ATS, and a new graveyard of tools. Reopening without a trigger is noise. Reopening with a freeze lifting, a certification window, or a hiring surge is work. Time-to-fill still matters, but the story around manager load moves. Don't pretend the old thread is warm. Lead with the trigger, remind them who you are in one line, and make the ask optional. Point tools can still close in two weeks. Platform deals still take a quarter. Your note should ask whether the old leak exists, not assume the old process is still live. Buyers remember vendors who thaw sequences. They also remember vendors who show up with news and an exit. Don't congratulate them on a layoff.

Customization tips

Pick a real trigger: careers-page surge, SOC 2, a new TA post, or a freeze lifting.
If they changed companies, don't write to the old domain and hope.
Don't reference a hallway from 11 months ago unless it was actually memorable.
If your process changed, say the change in one clause, not a launch essay.
Send Tuesday after 10:00. Monday reopens look like a sequence thaw.

Common mistakes

Opening with it's been a while and pasting the old pitch.
Pretending the old thread is still warm.
Citing a layoff they didn't discuss, like a tourist.
Restarting at email four of a sequence they muted.

How this scenario compares

Dimension	For this template
Best send window	When a dated trigger exists, not at day 180
Ideal length	Under 80 words, trigger plus archive door
Primary ask	Does the old hiring leak still exist, or archive?
Unlike a no-response bump	This is a re-introduction, not a 4-day poke
Unlike a breakup	You're opening a door, still easy to ignore

Questions people ask before they hit send

Not if you have a new reason and you don't pretend the old thread is still warm. Lead with the trigger, remind them who you are in one line, and make the ask optional. Nostalgia without news is just another cold email with extra steps they didn't ask for.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1068.