Re-Engagement Outreach
Works with Evergreen, a local-first personal CRM for macOS. Get it on the Mac App Store.
When to Use
- You notice important contacts going stale (3-6+ months since last interaction)
- You want to systematically re-engage your extended network
- A contact's company is in the news and it's a good excuse to reach out
- You're expanding into a new area and want to reconnect with relevant people
How It Works
- Shortlist candidates with
get_relationship_strengths({ grade: "Dormant", limit: 100 }), then repeat with grade: "Weak" (or set a maxScore ceiling) to widen the net. The server scores every contact 0–100 on recency, frequency, depth and variety and returns them sorted strongest-first
- Resolve each candidate to a contact ID with
search_contacts({ query: "<name>" }) — get_relationship_strengths returns name, organization, score and grade, but no contact ID
- Confirm each one is genuinely dormant by reading the
Last Interaction date from get_contact, and pull the history with get_contact_interactions. The score is a candidate filter, not the verdict — a low grade means "probably cold, go check", so the "older than 90 or 180 days" judgment and any day count you state come from that date. search_contacts results report Last Updated, the record's modification time, which an enrichment edit refreshes
- Check their network connections with
get_contact_network for warm re-entry points
- Research recent activity (job changes, company news) for a natural conversation hook
- Draft a low-pressure re-engagement message
- Create a follow-up action with
create_action to track the outreach
Re-Engagement Hooks
| Hook Type |
Example |
When to Use |
| News-based |
"Saw Acme just raised their Series B — congrats!" |
Company milestone or funding |
| Shared memory |
"Been thinking about that project we discussed at..." |
Genuine shared experience |
| Value-first |
"Found this article that reminded me of your work on..." |
Offering something relevant |
| Life event |
"Happy work anniversary! 3 years at Meridian already?" |
LinkedIn milestones |
| Mutual connection |
"Just had coffee with Alex — your name came up" |
Recent interaction with shared contact |
| Seasonal |
"Hope Q1 went well — how's the new product coming?" |
Natural transition points |
Example
Dormant contact:
Contact: Marcus Webb (Founder, DataFlow)
Relationship strength: 38/100 (Weak) — from get_relationship_strengths
Last interaction: Oct 15 (meeting) — "Discussed potential data partnership",
from get_contact
Tags: founder, data, atlanta
Notes: "Building real-time analytics platform. Previously at Google."
Dormant: 173 days since last interaction
Marcus grades Weak rather than Dormant — an earlier run of frequent, substantive
meetings still props up his score — which is why the shortlist covers both bands
and why the 173 days is read from get_contact, not inferred from the grade.
Drafted message:
Hey Marcus,
It's been a while — hope things are going well at DataFlow. I remember
you were heads-down on the real-time analytics engine when we last
caught up.
I've been working on some CRM integrations that touch on similar data
pipeline challenges and it made me think of your approach. Would love
to hear how things have evolved.
Coffee sometime in the next couple weeks?
Post-draft:
create_action({
contactId: marcus_id,
title: "Follow up if Marcus doesn't reply by Apr 19",
dueDate: "2026-04-19",
priority: "low"
})
Principles
| Principle |
Why |
| Low pressure |
Don't make them feel guilty for not being in touch |
| Genuine hook |
Reference something real, not "just checking in" |
| Short |
3-5 sentences max for a re-engagement |
| Easy reply |
Ask one simple question, not a laundry list |
| No ask on first touch |
Reconnect first, then work up to asks over time |
Checklist
Re-Engagement:
- [ ] Candidates shortlisted with `get_relationship_strengths` (Dormant, plus Weak to widen the net)
- [ ] Each candidate resolved to an ID with `search_contacts({ query })`
- [ ] Dormancy confirmed against `get_contact`'s `Last Interaction` date, not a score
- [ ] Prioritized by relationship value and re-engagement potential
- [ ] Natural hook found for each message (not generic)
- [ ] Message is brief and low-pressure
- [ ] Follow-up action created to track response
Learn More
1---2name: re-engaging-evergreen-contacts3description: Identifies dormant contacts in Evergreen CRM and drafts natural re-engagement messages. Use when you want to reconnect with people you haven't spoken to in months, revive stale relationships, or systematically re-engage your extended network.4---56# Re-Engagement Outreach78> Works with [Evergreen](https://heltonlabs.com/evergreen), a local-first personal CRM for macOS. [Get it on the Mac App Store](https://apps.apple.com/us/app/evergreencrm/id6753191506?mt=12).910## When to Use1112- You notice important contacts going stale (3-6+ months since last interaction)13- You want to systematically re-engage your extended network14- A contact's company is in the news and it's a good excuse to reach out15- You're expanding into a new area and want to reconnect with relevant people1617## How It Works18191. Shortlist candidates with `get_relationship_strengths({ grade: "Dormant", limit: 100 })`, then repeat with `grade: "Weak"` (or set a `maxScore` ceiling) to widen the net. The server scores every contact 0–100 on recency, frequency, depth and variety and returns them sorted strongest-first202. Resolve each candidate to a contact ID with `search_contacts({ query: "<name>" })` — `get_relationship_strengths` returns name, organization, score and grade, but no contact ID213. Confirm each one is genuinely dormant by reading the `Last Interaction` date from `get_contact`, and pull the history with `get_contact_interactions`. The score is a candidate filter, not the verdict — a low grade means "probably cold, go check", so the "older than 90 or 180 days" judgment and any day count you state come from that date. `search_contacts` results report `Last Updated`, the record's modification time, which an enrichment edit refreshes224. Check their network connections with `get_contact_network` for warm re-entry points235. Research recent activity (job changes, company news) for a natural conversation hook246. Draft a low-pressure re-engagement message257. Create a follow-up action with `create_action` to track the outreach2627## Re-Engagement Hooks2829| Hook Type | Example | When to Use |30|-----------|---------|-------------|31| News-based | "Saw Acme just raised their Series B — congrats!" | Company milestone or funding |32| Shared memory | "Been thinking about that project we discussed at..." | Genuine shared experience |33| Value-first | "Found this article that reminded me of your work on..." | Offering something relevant |34| Life event | "Happy work anniversary! 3 years at Meridian already?" | LinkedIn milestones |35| Mutual connection | "Just had coffee with Alex — your name came up" | Recent interaction with shared contact |36| Seasonal | "Hope Q1 went well — how's the new product coming?" | Natural transition points |3738## Example3940**Dormant contact:**41```42Contact: Marcus Webb (Founder, DataFlow)43Relationship strength: 38/100 (Weak) — from get_relationship_strengths44Last interaction: Oct 15 (meeting) — "Discussed potential data partnership",45 from get_contact46Tags: founder, data, atlanta47Notes: "Building real-time analytics platform. Previously at Google."48Dormant: 173 days since last interaction49```5051Marcus grades Weak rather than Dormant — an earlier run of frequent, substantive52meetings still props up his score — which is why the shortlist covers both bands53and why the 173 days is read from `get_contact`, not inferred from the grade.5455**Drafted message:**56```57Hey Marcus,5859It's been a while — hope things are going well at DataFlow. I remember60you were heads-down on the real-time analytics engine when we last61caught up.6263I've been working on some CRM integrations that touch on similar data64pipeline challenges and it made me think of your approach. Would love65to hear how things have evolved.6667Coffee sometime in the next couple weeks?68```6970**Post-draft:**71```72create_action({73 contactId: marcus_id,74 title: "Follow up if Marcus doesn't reply by Apr 19",75 dueDate: "2026-04-19",76 priority: "low"77})78```7980## Principles8182| Principle | Why |83|-----------|-----|84| Low pressure | Don't make them feel guilty for not being in touch |85| Genuine hook | Reference something real, not "just checking in" |86| Short | 3-5 sentences max for a re-engagement |87| Easy reply | Ask one simple question, not a laundry list |88| No ask on first touch | Reconnect first, then work up to asks over time |8990## Checklist9192```93Re-Engagement:94- [ ] Candidates shortlisted with `get_relationship_strengths` (Dormant, plus Weak to widen the net)95- [ ] Each candidate resolved to an ID with `search_contacts({ query })`96- [ ] Dormancy confirmed against `get_contact`'s `Last Interaction` date, not a score97- [ ] Prioritized by relationship value and re-engagement potential98- [ ] Natural hook found for each message (not generic)99- [ ] Message is brief and low-pressure100- [ ] Follow-up action created to track response101```102103## Learn More104105- [Evergreen — Local-First Personal CRM](https://heltonlabs.com/evergreen)106- [Vibe Coding a Personal CRM](https://mcginniscommawill.com/posts/2025-09-05-vibe-coding-personal-crm/)107- [Evergreen Gets Even Evergreener](https://mcginniscommawill.com/posts/2026-01-26-evergreen-gets-even-evergreener/)
wdm0006