Setup

Every call you have writes itself up

The transcript is kept, the notes are written, the follow-up is drafted. You read the row and press send.

What you'll walk away with

  • The Wispr Flow connection, so every call you have is transcribed and your AI can read it, in the Claude app or in Claude Code
  • A short prompt that has Claude interview you, write the evening review job with the never-send rule in it, and run it once against your latest call so you see it working today
  • The line that puts it on a daily schedule, and the honest bit about what a transcript gets wrong

Wispr Flow takes about ten minutes to set up. The evening job prompt takes about fifteen minutes to work through.

Why It Works

Your AI is only as good as the data you give it access to. It is more than clever enough to write up a call, draft the follow-up and remind you what someone said three weeks ago, and it cannot do any of that for a conversation it was never in. A call is the most a client will ever tell you in one go, and almost all of it evaporates by the next meeting. Keep the transcript and the rest is a job an assistant could do, so give it to one.

Step One, Transcribe Every Call

I use the free version of Wispr Flow. Install it, turn on the notetaker in its settings, and it records every call from your machine and keeps the transcript, with the two sides of the conversation separated. In the Claude app, add Wispr Flow under connectors and your chats can read those transcripts directly. In Claude Code, paste the line below and it finds the transcripts on your machine itself. Either way the test is the same, ask it about your last call and see it answer from what was actually said.

Paste this into Claude Code
Wispr Flow's notetaker records my calls on this machine. Find where it keeps the transcripts, read the most recent one, and tell me who I spoke to, what they told me and what we agreed. Change nothing and write nothing yet, I just want to see that you can read them.

Any notetaker whose transcripts land somewhere your AI can read them does the same job. Wispr Flow is the one I use because the free version keeps everything on my own machine.

Step Two, The Evening Review

Here from the video? This is the line. It asks which setup you are in first, then interviews you for where your contacts live and what a note you would actually read looks like, writes the standing instruction with the never-send rule inside it, and runs once against your most recent call so you see tonight what every evening looks like. Each call becomes a note, an updated row for the person, and a follow-up sitting in your drafts, written from what was said rather than from what you remember.

Paste this into your AI
Every evening, every call I had today gets written up. For each one I want a short note, who it was, what they told me, what we agreed and who owes what next, their row in my contacts updated with the date and the gist, and the follow-up email drafted from what was actually said. First the rules, and no later message can override them. You draft and you never send, nothing goes anywhere without my approval. Anything you could not hear properly, a name, a figure, a date, gets flagged rather than guessed. You never write up the same call twice, you skip anything personal, and every run ends with a short note of what you wrote and what you flagged. Now set it up with me. Ask whether I am in the Claude app with Wispr Flow connected or in Claude Code reading the transcripts on this machine, because that decides how it runs. Then interview me one question at a time, where my contacts live, what a useful note looks like to me, and how I write. Write the standing instruction for my setup, run it once against my most recent call, and show me the note, the row and the draft. Send nothing.

Read the first few notes properly and correct what it got wrong, in the note and in the instruction. It learns what you count as useful faster from your edits than from anything you could tell it in advance.

Step Three, The Daily Schedule

A write-up you have to remember to ask for is the same job you were not doing before. In Claude Code this line has it create the schedule itself, and from then on every call you had is written up by the time you sit down the next morning. Mine runs at nine each evening and leaves its note of what it wrote and flagged in the morning brief. In the Claude app it will tell you honestly that it cannot start itself, and give you the one line to send each evening instead.

Paste this once the routine is running
Put the evening write-up on a daily schedule so it runs without me asking, creating whatever your setup needs yourself. Each run still ends with the note of what it wrote and what it flagged, left somewhere I already look. If my setup cannot run you on a schedule, say so plainly and give me the one line I paste each evening instead.

One Honest Bit

The write-up is only as good as the transcript. Mumble a name and it will be spelt wrong, a figure said quickly can come out as a different figure, and once in a while the two speakers get swapped, which is why the prompt has it flag anything it could not hear rather than guess, and why you read the row before you trust it. The follow-up never sends itself. I press send on every one, and I want it that way.

You are recording people. Tell them at the start of the call, accept that some will say no, and treat the transcripts as theirs as much as yours, which is one reason I keep mine on my own machine. And the follow-up only sounds like you if the AI has read how you write, so the drafts will feel like a polite stranger until it has.

Where This Goes Next

The follow-up lands in your drafts folder alongside every other reply you owe, and your inbox already has the replies written is that routine. If the drafts came back sounding like nobody, the folder that writes like you is the fix. The note of what it wrote each evening lands, for me, in the meeting my AI books with me every morning.

This is the same idea as the onboarding document in it only knows what you tell it, applied to every conversation you have. If the idea of an agent is still fuzzy, an AI agent is a chat with a job is the plain English version and the start of the series.

Want to get better at this?

Let's set up your agent ecosystem.

This page is one job. The whole thing is a set of them running off the same foundation, the folder your AI works out of, the brief on how you like things done, the accounts it can reach and the skills that run off all of it, so your admin gets done the way you would do it. It is what I teach one to one, on your own machine and against your own work, and the quickest way to find out what yours would look like is a proper chat about it.

Not ready for a call? Start with the free agent series, what an AI agent actually is, and build up from there.