Founder
Automated Meeting Follow-Up Emails β Sent Before You Leave the Room
Key Takeaway
My AI agent generates and sends meeting follow-up emails with summary, action items, and deadlines within 5 minutes of meeting end β eliminating the most commonly skipped professional habit.
The Problem
Everyone knows you should send a follow-up email after meetings. Summarize decisions, list action items, confirm deadlines, align on next steps. Professional 101.
Almost nobody does it consistently.
The reasons are always the same: you walk out of a 30-minute meeting into a 15-minute gap before the next one. Do you spend that gap typing a follow-up, or prepping for the next call? You prep. The follow-up gets pushed to "after lunch." Then to "end of day." Then to "I'll just cover it in the next meeting."
At PyratzLabs, I was averaging maybe 40% follow-up rate on meetings. The important ones got written β investor calls, board meetings. The routine ones β partner syncs, team reviews, vendor calls β almost never got a follow-up. And those are exactly the meetings where miscommunication festers.
The Solution
When a calendar event ends, Alfrawd automatically generates a follow-up email. It pulls context from the calendar event description, attendee list, any linked documents, and recent email threads with those attendees. The email includes a summary, action items with owners, deadlines, and next steps. For routine meetings, it auto-sends. For important ones, it sends me a draft for approval.
The Process
Step 1: Meeting end detection
yamlShow code
# Cron checks for recently ended meetings every 5 minutes
schedule: "*/5 * * * *"
task: |
Check Google Calendar for events that ended in the last 10 minutes.
For each, generate a follow-up email.
Routine meetings: auto-send.
Important meetings (board, investor, partner): send draft to Telegram.
Step 2: Context gathering
bashShow code
# Agent pulls all available context
gog cal events get <event_id> # Full event details
gog gmail messages list --query "from:{attendee} OR to:{attendee} subject:{topic}" --limit 5
gog drive search "{event_title}" --type doc # Any linked docs
# Agent also checks:
# - Calendar event description (usually contains agenda)
# - Attendee list with names and emails
# - Any notes from the event (if Bilal dictated them during the meeting)
Step 3: Follow-up generation
markdownShow code
# Agent generates structured follow-up:
Subject: Follow-up: {Meeting Title} β {Date}
Hi {attendee_first_names},
Quick summary from today's call:
**Decisions:**
- Agreed to proceed with Option B for the API redesign
- Budget approved for Q2 marketing push (β¬15K)
**Action Items:**
- [ ] Bilal: Send revised timeline by Friday
- [ ] Marc: Share updated financial model by EOD Monday
- [ ] Sarah: Schedule follow-up with legal team this week
**Next Meeting:** Thursday March 19, 2:00 PM CET
Let me know if I missed anything.
Best,
Bilal
Step 4: Send or draft
yamlShow code
# Auto-send rules
auto_send:
- meeting_type: "team_sync"
- meeting_type: "vendor_call"
- meeting_type: "standup"
- recurring: true
draft_for_approval:
- meeting_type: "investor"
- meeting_type: "board"
- meeting_type: "partner"
- attendees_include: "external_domain"
- first_meeting: true # Never met this person before
For draft approvals, the agent sends to Telegram:
View details
π§ Follow-up draft: "Q1 Review with Sequoia"
To: marc@sequoia.com, julie@sequoia.com
[full email preview]
β send | edit | skip
Step 5: Tracking
bashShow code
# Log every follow-up
gog sheets append "Meeting Follow-ups" \
--values "2026-03-12,Q1 Review with Sequoia,marc@sequoia.com,auto,sent,14:05"
The Results
| Metric | Before | After | Change |
|---|---|---|---|
| Follow-up rate | ~40% | 98% | +145% |
| Avg follow-up send time | 4-6 hours (when sent) | 4.2 minutes | -98% |
| Time writing follow-ups/week | 45 min | 3 min (reviewing drafts) | -93% |
| Missed action items | 3-5/month | <1/month | -85% |
| "What did we agree on?" questions | Weekly | Almost never | Eliminated |
The 98% rate (not 100%) accounts for meetings that are purely social or have no actionable content β the agent is smart enough to skip those.
The speed matters more than you think. A follow-up that arrives 4 minutes after the meeting is still fresh. People read it, correct inaccuracies immediately, and confirm action items while the context is in their head. A follow-up 6 hours later gets filed without reading.
Try It Yourself
- Configure
gogCLI with your Google Calendar and Gmail - Set up the meeting-end detection cron (every 5 minutes works well)
- Define your auto-send vs. draft-for-approval rules based on meeting types
- Let the agent run for a week on "draft only" mode β review every follow-up
- Once quality is consistent, enable auto-send for routine meeting categories
The follow-up email is the most high-leverage professional habit that almost nobody maintains. It takes 10-15 minutes per meeting to write manually. The agent does it in seconds. The ROI is absurd β and the professional reputation boost is real.
The follow-up email is where deals close and action items survive. I stopped writing them. They never stopped going out.
Related case studies
Founder
My AI Agent Triages 200+ Emails a Day β I See 5
AI email triage classifies 200+ emails daily into 5 categories so only 5 reach me β eliminating 45 minutes of inbox scanning and all context-switches.
Event Organizer
Event Speaker Outreach β From Luma List to Confirmed Speakers in One Week
AI agent researches target speakers, sends personalized multi-channel outreach, tracks the pipeline in Google Sheets β 3 confirmed speakers for Barcelona meetup in one week, 70% response rate.
Founder
Slack-to-Telegram Bridge β Team Messages Without Opening Another App
An AI agent bridges Slack and Telegram bidirectionally β forwarding only messages that matter to Telegram, posting replies back in Slack β zero Slack checks, 4-min response time.
Want results like these?
Start free with your own AI team. No credit card required.