When should you use it?
- You leave a client call, sales visit or site walk with details in your head and no notes
- Typing a recap on your phone feels like a second job, so the write-up keeps slipping
- You want the follow-up email drafted while the commitments are still fresh
Not for: Meetings that were recorded and transcribed already; work from the transcript instead; Anything that needs a verbatim record, such as legal or HR conversations; Sending messages to clients without reading them first
What do you need, and what do you get?
You need
- An agent or assistant app with a live voice conversation mode
- Five minutes right after the meeting ends
- Who attended and what the meeting was for, said out loud at the start
You get
- A written list of decisions made and commitments given, with who owns each
- Due dates mentioned in the meeting and questions still open
- A draft follow-up message waiting for your review
How does it work, step by step?
- Open a voice conversationIn Grok Bot, pick a single Bot's chat, keep the text field blank and press the voice chat button. Other assistants with a voice mode work the same way.
- Say the prompt and talkUse Fenech's opening line, then describe the meeting in any order. Let the agent ask about anything unclear.
- Hang up and read the transcriptThe conversation stays in the chat, so open the written summary and compare it with what you remember.
- Fix names, numbers and datesCorrect anything misheard, especially amounts, client names and due dates, before you rely on the list.
- Send the follow-up yourselfEdit the draft, then send it from your own email once it says exactly what was agreed.
The prompt
The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, ChatGPT, Claude and others. Values in lime are placeholders.
Original prompt by Michael Fenech (@Michael_Fenech_)
I’ve just finished a meeting. Help me debrief. Pull out decisions, promises, deadlines and open questions. Draft the follow-up for me to review.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: five moments to use a voice conversation with your Bot, with what to say.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
I just came out of a {meeting_type} with {attendees} about {topic}. I am going to talk it through; let me finish before you respond. Then list, in writing: what was decided, what each person committed to and by when, and what is still unresolved. Ask me about anything that sounds like a commitment but has no owner or date. Finally, draft a short follow-up message to {recipient} that confirms only what we agreed. Do not add prices, dates or promises I did not say, and do not send it.
What can go wrong?
- Speech recognition mishears names and figures. Check every amount, date and spelling in the written version before acting.
- Waiting until the evening. The point is to capture details in the first few minutes, before they fade.
- Treating your own recap as the full record. The other side may remember a commitment differently, so keep the follow-up factual.
- Letting the agent send the follow-up. Keep the draft as a draft until you have read it.
Our take
Most meeting follow-up fails for a boring reason: nobody writes it down while it is fresh, and by evening the promise to send a quote on Thursday has turned into a vague memory. Fenech's suggestion fits that gap neatly. Talking is faster than typing on a phone, and a live conversation lets the agent ask what you forgot to mention, which a voice memo never does. The prompt itself is short but asks for the right four things, and the phrase about a draft for you to review keeps the sending decision with you. His closing rule is the one we would underline: speak to work out your thinking, then review the written version before you act on it, above all names, figures and anything going to a client. We would add a habit of saying who attended and what the meeting was for in your first sentence, because that context improves the follow-up a lot. In our dry run on a fictional plumbing contractor's site visit recap, the debrief separated two firm commitments from one maybe, flagged a missing due date and produced a follow-up draft without inventing a price.
Where the time goes back: A five-minute spoken recap replaces the half hour of typing notes later, and the follow-up draft is ready before you reach your next appointment.
FAQ
What are the other four situations in the post?
Is voice mode the same as dictation?
Can I start it quickly on a phone?
Source and credit
The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X post: five moments to use a voice conversation with your Bot, with what to say
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Nov 13, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Grok Bot
- AI dry run
- Nov 14, 2026: passed. Dry-run tested by our AI test agent on sample input. Commitments separated from maybes, missing date flagged, no invented price, draft left for review.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 14, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.