Meeting Follow-Up

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.

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.

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.

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.

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.