Meeting Follow-Up AI workflow template: A follow-up out the same day.

The ConvOps Meeting Follow-Up template makes your AI turn a call into a sent follow-up: capture who attended and what was said, extract decisions, action items and the next step, draft the message, then check it against what was agreed. Sending is irreversible, so it stops for your approval. Reject it and it redrafts.

5 steps · 1 approval · 1 loop back

Meeting Follow-Up · example runyour AI client
  1. 01Capture
  2. 02Extract
  3. 03Draft Follow-Up
  4. 04Send Reviewwaits for approval
  5. 05Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Meeting Follow-Up template do?

For sales reps, account managers and founders who take client calls and owe a recap with next steps after each one.

Meeting Follow-Up is stored in ConvOps as five steps, and your AI client receives them one at a time. A Meeting Follow-Up run holds at Send Review until an explicit approval is given.

  • 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
step by step

How does the Meeting Follow-Up workflow run?

The 5 Meeting Follow-Up steps in order, each with the instruction your AI receives there as Meeting Follow-Up stores it.

Capture
Extract
Draft Follow-Up
Send Reviewapproval
Completeclosing note

A sent follow-up that matches what was agreed on the call, with its decisions and action items kept as task notes.

  1. 01

    Capture

    the agent works

    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.

  2. 02

    Extract

    the agent works

    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.

  3. 03

    Draft Follow-Up

    the agent works

    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.

  4. 04

    Send Review

    waits for your approval

    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.

    rejected → back to Draft Follow-Up

  5. 05

    Complete

    closes with a note

    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.

reach for it when

  • You owe someone outside the team a recap after a call.
  • The message carries commitments with owners and dates.
  • A wrong name or date in a sent message would cost you the relationship.

something else fits when

  • The notes are only for your own team: use Meeting Notes.
  • No next step was agreed on the call.
  • The recap changes a contract and has to go through legal.
example · wealth managemententerprise

Recap after a portfolio review

An adviser's call notes become three agreed actions and a date for the next review. Send Review catches a wrong account name, and the adviser approves the corrected recap.

Send Review approval

where approval is required

Where do you approve in Meeting Follow-Up?

Meeting Follow-Up holds at Send Review until an explicit approval is given, recorded with the account that gave it.

step 4

Send Review

Sending is irreversible. The AI checks the recap, every owner and date, and the names against what was agreed, then you approve or send it back to Draft Follow-Up.

what you review

  • 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

reject → back to Draft Follow-Up

gates the engine checks without you

  • Complete closes Meeting Follow-Up only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Meeting Follow-Up?

make it yours

How do you customize Meeting Follow-Up?

Once installed, Meeting Follow-Up is a workflow in your workspace. Ask your AI to change Meeting Follow-Up in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Draft Follow-Up, always propose two meeting times for the next step.
workflow_step_update · Meeting Follow-Up
Done. Meeting Follow-Up in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Draft Follow-Up, always propose two meeting times for the next step."
  • "After sending, add a step that logs the call in our CRM."
  • "Use a more formal tone for enterprise accounts."
the difference

Meeting Follow-Up: without a workflow vs with it

  • The call ends, the day moves on, and the follow-up never gets sent
  • The recap goes out missing the one commitment the client actually cared about
  • The send happens before anyone checks the recap matches what was actually agreed
  • Weeks later nobody can prove what was agreed in the meeting or what was actually sent
  • The Meeting Follow-Up process lives in a prompt, and each run follows it a little differently
  • The AI drives from Capture straight to a sent follow-up while the meeting is still fresh
  • The AI drives an Extract step that pulls every decision, owner, and next step before drafting
  • The AI pauses at a send-review checkpoint so you sign off before it reaches the client
  • Every step (Capture, Extract, Draft, Send Review) is logged, so the agreement and the follow-up are on the record
  • Your AI receives the 5 stored steps one at a time, and the run holds at Send Review until an explicit approval is given
questions

Meeting Follow-Up template FAQ

What is the ConvOps Meeting Follow-Up template?

The ConvOps Meeting Follow-Up template makes your AI turn a call into a sent follow-up: capture who attended and what was said, extract decisions, action items and the next step, draft the message, then check it against what was agreed. Sending is irreversible, so it stops for your approval. Reject it and it redrafts.

Will it invent commitments?

The ConvOps Extract step pulls only what was actually said and does not invent commitments: decisions, action items with owners and dates where known, open questions, and the agreed next step with who moves first. Send Review then checks the recap against the extracted decisions, and that every owner, date, name and company is correct, before the run can be approved.

Does ConvOps send the email?

No. ConvOps holds the run at Send Review until an explicit approval is given, recorded with the account that gave it. Your AI client then sends the final message, or hands it to you, using whatever email or messaging tools it is connected to. ConvOps keeps the process and the record of what was agreed and sent, not your mailbox.

What stays on record?

In ConvOps, the final message and the extracted action items are saved as task notes, so what was agreed and what was sent stay on file for the next person. The Capture note holds who attended, which company and what was discussed, so a later proposal or follow-up can start from those notes instead of someone's memory of the call.

What does the follow-up message include?

The ConvOps Draft Follow-Up step writes 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 with a proposed time if relevant, and a close in the right tone for the relationship. It is kept scannable so the reader sees the next step in seconds.