Draft Follow-Up Message
Works with Evergreen, a local-first personal CRM for macOS. Get it on the Mac App Store.
When to Use
- After a meeting and you need to send a recap or thank-you
- Following up on a promised deliverable or introduction
- Checking in with someone you haven't talked to recently
- Responding to a trigger (job change, funding news, birthday)
How It Works
- Retrieve the contact with
get_contact for full profile
- Pull recent interactions with
get_contact_interactions for conversation history
- Check pending actions with
list_actions for any commitments
- Review the contact's network with
get_contact_network for shared connections context
- Draft a message that references specific shared history and feels personal
- After sending, log the interaction with
log_interaction
- Mark any related actions complete with
mark_action_completed
Message Types
| Type |
Tone |
Key Elements |
| Post-meeting recap |
Professional, warm |
Key takeaways, action items, next steps |
| Thank-you note |
Grateful, specific |
What you're thankful for, why it mattered |
| Check-in |
Casual, genuine |
Reference last conversation, ask about their work |
| Introduction follow-up |
Enthusiastic, brief |
Reference who introduced you, what excited you |
| Congratulations |
Warm, sincere |
Specific achievement, genuine reaction |
| Re-engagement |
Low-pressure, curious |
Shared memory, open-ended question |
Example
Context from Evergreen:
Contact: Sarah Chen (CTO, Meridian Health)
Last interaction: Meeting on Mar 20 — "Discussed API integration possibilities"
Pending action: "Send API documentation" (due Apr 2)
Notes: "Interested in our healthcare data pipeline"
Drafted message:
Subject: API docs + a few thoughts from our chat
Hi Sarah,
Great catching up at the dinner last month. I've been thinking more
about the integration approach we discussed for Meridian's patient
data pipeline.
As promised, here are our API docs: [link]
I flagged the batch processing section specifically — based on what
you described about your throughput needs, that's probably the most
relevant starting point.
Happy to jump on a quick call if any questions come up as your team
reviews. What does your week look like?
Best,
[Name]
Post-send:
1. log_interaction({ contactId: sarah_id, type: "email", description: "Sent API docs follow-up, offered call to discuss" })
2. mark_action_completed({ actionId: api_docs_action_id }) // "Send API documentation"
Writing Principles
| Principle |
Meaning |
| Specific |
Reference real details from your history, not generic pleasantries |
| Brief |
Respect their time — get to the point in 3-5 sentences |
| Action-oriented |
Include a clear next step or question |
| Authentic |
Match the user's natural voice and relationship level |
| Contextual |
Show you remember what matters to them |
Checklist
Follow-Up Draft:
- [ ] Contact history reviewed for relevant context
- [ ] Message references specific shared details
- [ ] Clear call-to-action or next step included
- [ ] Tone matches the relationship level
- [ ] Interaction logged after sending
- [ ] Related actions marked complete
Learn More
1---2name: drafting-evergreen-follow-ups3description: Drafts personalized follow-up emails and messages based on Evergreen CRM contact history, past interactions, and pending actions. Use when you need to write a follow-up email, thank-you note, check-in message, or any outreach to an existing contact.4---56# Draft Follow-Up Message78> 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- After a meeting and you need to send a recap or thank-you13- Following up on a promised deliverable or introduction14- Checking in with someone you haven't talked to recently15- Responding to a trigger (job change, funding news, birthday)1617## How It Works18191. Retrieve the contact with `get_contact` for full profile202. Pull recent interactions with `get_contact_interactions` for conversation history213. Check pending actions with `list_actions` for any commitments224. Review the contact's network with `get_contact_network` for shared connections context235. Draft a message that references specific shared history and feels personal246. After sending, log the interaction with `log_interaction`257. Mark any related actions complete with `mark_action_completed`2627## Message Types2829| Type | Tone | Key Elements |30|------|------|-------------|31| Post-meeting recap | Professional, warm | Key takeaways, action items, next steps |32| Thank-you note | Grateful, specific | What you're thankful for, why it mattered |33| Check-in | Casual, genuine | Reference last conversation, ask about their work |34| Introduction follow-up | Enthusiastic, brief | Reference who introduced you, what excited you |35| Congratulations | Warm, sincere | Specific achievement, genuine reaction |36| Re-engagement | Low-pressure, curious | Shared memory, open-ended question |3738## Example3940**Context from Evergreen:**41```42Contact: Sarah Chen (CTO, Meridian Health)43Last interaction: Meeting on Mar 20 — "Discussed API integration possibilities"44Pending action: "Send API documentation" (due Apr 2)45Notes: "Interested in our healthcare data pipeline"46```4748**Drafted message:**49```50Subject: API docs + a few thoughts from our chat5152Hi Sarah,5354Great catching up at the dinner last month. I've been thinking more55about the integration approach we discussed for Meridian's patient56data pipeline.5758As promised, here are our API docs: [link]5960I flagged the batch processing section specifically — based on what61you described about your throughput needs, that's probably the most62relevant starting point.6364Happy to jump on a quick call if any questions come up as your team65reviews. What does your week look like?6667Best,68[Name]69```7071**Post-send:**72```731. log_interaction({ contactId: sarah_id, type: "email", description: "Sent API docs follow-up, offered call to discuss" })742. mark_action_completed({ actionId: api_docs_action_id }) // "Send API documentation"75```7677## Writing Principles7879| Principle | Meaning |80|-----------|---------|81| Specific | Reference real details from your history, not generic pleasantries |82| Brief | Respect their time — get to the point in 3-5 sentences |83| Action-oriented | Include a clear next step or question |84| Authentic | Match the user's natural voice and relationship level |85| Contextual | Show you remember what matters to them |8687## Checklist8889```90Follow-Up Draft:91- [ ] Contact history reviewed for relevant context92- [ ] Message references specific shared details93- [ ] Clear call-to-action or next step included94- [ ] Tone matches the relationship level95- [ ] Interaction logged after sending96- [ ] Related actions marked complete97```9899## Learn More100101- [Evergreen — Local-First Personal CRM](https://heltonlabs.com/evergreen)102- [Vibe Coding a Personal CRM](https://mcginniscommawill.com/posts/2025-09-05-vibe-coding-personal-crm/)103- [Evergreen Gets Serious](https://mcginniscommawill.com/posts/2025-10-08-evergreen-gets-serious/)
wdm0006