Meeting Follow-Up
Turn a meeting into a sent follow-up. The AI drives through Extract, Draft, and a send-review checkpoint.
the steps, as stored
- 01Capture
Capture what happened in the meeting before structuring anything.
Record: - Who attended and which company - The purpose of the meeting - What was discussed — paste notes, a transcript, or your recollection - Anything the other side committed to, asked for, or objected to
If the record is thin, ask the operator for the missing pieces — a vague capture produces a vague follow-up.
Save the raw meeting record as a task note with task_notes_add. The next step — Extract — reads this note.
- 02Extract
Read the task notes with task_notes_list — the note from the Capture step contains the raw record. Work from it.
Extract the structure. What good looks like: - Decisions made, stated plainly - Action items, each with an owner and a due date where known - Open questions still to resolve - The agreed next step and who moves first
Pull only what was actually said — do not invent commitments.
Save the extracted decisions, actions, and next steps as a task note with task_notes_add. The Draft Follow-Up step reads this note.
- 03Draft Follow-Up
Read the task notes with task_notes_list — the Extract note holds the decisions, actions, and next steps, and the Capture note holds the attendees and context. Work from them.
Write the follow-up message: - A short, warm opener referencing the meeting - A brief recap of what was discussed and decided - The action items with owners and dates - One clear next step and a proposed time if relevant - A close in the right tone for this relationship
Keep it scannable — the reader should see the next step in seconds.
Save the full follow-up message as a task note with task_notes_add. The Send Review step reads this note.
- 04Send Reviewapproval gate
Read the task notes with task_notes_list — the Draft Follow-Up note holds the message and the Extract note holds what was agreed. Work from them.
Check the follow-up before sending: - The recap matches what was actually discussed and decided - Every action item, owner, and date is correct - Names and company are right - The next step is clear and the tone fits
Ask the operator to approve the message for sending. This is a checkpoint — sending is irreversible, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft Follow-Up.
- 05Completecontext gate
The follow-up is approved and sent. Confirm the final message and the extracted action items are saved as task notes, so the record of what was agreed and sent stays on file, then close out the task.
use it for
- Write a follow-up email from a client call with clear next steps
- Turn raw meeting notes into a recap and an action list
- Send a post-demo follow-up that captures what was agreed
without it, with it
| without | with meeting follow-up |
|---|---|
| The call ends, the day moves on, and the follow-up never gets sent | The AI drives from Capture straight to a sent follow-up while the meeting is still fresh |
| The recap goes out missing the one commitment the client actually cared about | The AI drives an Extract step that pulls every decision, owner, and next step before drafting |
| The send happens before anyone checks the recap matches what was actually agreed | The AI pauses at a send-review checkpoint so you sign off before it reaches the client |
| Weeks later nobody can prove what was agreed in the meeting or what was actually sent | Every step — Capture, Extract, Draft, Send Review — is logged, so the agreement and the follow-up are on the record |