--- id: post-meeting-followup-engine title: Post-meeting follow-up engine enabled: true owner: goal:sales-weapon-ae-copilot mode: task schedule: kind: daily timezone: America/New_York time: 18:00:00 delivery: - chat_id: ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b metadata: predicted_connector_permissions: - connector: gmail method: users.messages.send originating_chat_context_json: '{"chat_id":"ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b","origin_provider":"main","chat_kind":"direct","event_kind":"message","require_mention":false,"device_id":"11d6f508-35e2-48ec-9e92-39b4972d1a29"}' presentation_locale: en-US --- Post-meeting follow-up engine for Sean Mattsson. After every customer meeting, automatically: summarize the transcript in Notion, send the follow-up email, create to-do items, and run ongoing nurture. Sean's standing order (2026-10-06): "Do this for all meetings. Optimize anyway you need to." AUTO-SEND: follow-up emails SEND directly (blanket send permission 2026-10-06). Quality gates still apply. EACH RUN (daily, 6pm ET): 1. Query the Notion Meetings database (via notion-cli) for meetings with Stage=Done (or meeting date = today) AND Follow-up Sent=NO. 2. For each such meeting, find the transcript/notes: - Check the Notion Voicenotes page for a transcript matching the account name and date. - Check the meeting page content for pasted notes. - If no transcript or notes exist, SKIP the email (do not fabricate) but create a to-do: "[SEAN] Debrief — no transcript found, add notes." 3. If transcript/notes found: a. Summarize in Notion: append a "## Post-Meeting Summary — " section to the meeting page with: attendees, duration, key outcomes, referrals (with permission notes), action items split by owner (Sean vs. contact), and next step. b. Send the follow-up email: warm and friendly, thank them for the meeting, recap key points in their words, action items clearly split (For me / For you), no placeholders, full Stratix signature, title Account Relationship Manager, zero em-dashes. CC any additional attendees from the meeting page. c. Create to-do items in the Notion To Do List DB (3e1a4fa9-4a8a-80ab-aac8-d2d4fdb7f92e): prefix [SEAN] for items needing his voice/presence/judgment, [MUSE] for research/drafting. Include any referrals as separate to-dos with the permission context. d. Set Follow-up Sent=YES on the meeting page. e. Log to ~/memory/YYYY-MM-DD.md. 4. NURTURE: for meetings with Follow-up Sent=YES and no reply within 7 days, the opp-followup-campaign handles ongoing touches per the never-stop-pivot rule. Do not duplicate. 5. NEVER fabricate meeting content. If the transcript is ambiguous about who said what or what was agreed, note the uncertainty in Notion rather than guessing. To add a meeting to this flow: set its Stage to Done in Notion. The engine picks it up on the next run.