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
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
example · the steps are this template's real steps
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.
The 5 Meeting Follow-Up steps in order, each with the instruction your AI receives there as Meeting Follow-Up stores it.
A sent follow-up that matches what was agreed on the call, with its decisions and action items kept as task notes.
Capture what happened in the meeting before structuring anything.
Record:
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:
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:
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:
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
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.
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
Meeting Follow-Up holds at Send Review until an explicit approval is given, recorded with the account that gave it.
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
reject → back to Draft Follow-Up
gates the engine checks without you
Meeting Follow-Up runs in a ConvOps workspace and attaches to the task type, so new work of that type starts on it. Meeting Follow-Up saves each step's output as a task note in ConvOps, and the next Meeting Follow-Up step reads it back. Meeting Follow-Up needs no repository, so a chat client such as ChatGPT or Claude can run it. Connect a client , then install Meeting Follow-Up from the catalog .
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.
new chat
workflow_step_update · Meeting Follow-Upmore example prompts
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.
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.
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.
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.
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.