Getting more from transcripts
A transcript is context you didn't have to write. One meeting gives you the follow-up. A pile of them gives you the pattern: what customers keep objecting to, what investors keep asking, what you keep promising.
Granola and Wispr Flow both produce them. Claude reads them through a connector, or from a file you drop in the folder. The summary is the skim. The questions below go to the transcript.
How to access it
You need a transcript tool that's actually connected. Granola or Wispr Flow, then Customize > Connectors. On Team, an admin adds it first.
The switch people miss: asking the summary. If you say "use my meeting notes" and the notes are the short version, the prices and the names are already gone. Say "use the transcript".
One meeting
Use the transcript of [meeting], not the summary.
GOAL
A follow-up I can send, plus my actions.
CONTEXT
I was in the meeting. The other party was [who]. I'll send this myself.
CONSTRAINTS
Only include commitments that were actually said.
A short email, then a list of actions with owners.
If a deadline wasn't given, write "no date said".
If anything is missing, ask me first. Don't send anything.
Worked example. A sales follow-up after a first call. The summary said the buyer wanted a proposal. The transcript had the two objections (lead time, and who signs off) and a price they floated. The follow-up answered those. A draft from the summary would have attached a generic proposal and ignored both.
At scale
Once the connector can see more than yesterday:
Scan my transcripts from the last [time period].
I'm looking for [theme]: objections, questions, or promises.
Group them. Quote the meeting and the line. Ignore anything that only comes up once.
Don't invent a theme to make the list longer.
Useful versions of [theme]:
- Objections that come up in sales calls
- Questions investors or the board keep asking
- Content ideas customers are already asking for
- Actions I've agreed and not closed
"My last 200 transcripts" only works if your plan still has them. On Granola's free plan, history in the app is short. Check before you build a habit around a search you can't run. See retention on the Granola page.
Into the folder and into a skill
A transcript that stays in the notetaker app helps once. Filed, it helps next time.
- Drop it in the client or project folder, or let the connector read it when that folder is selected.
- If you do the same follow-up every time, turn the prompt into a skill.
/follow-upshould demand the transcript and refuse to invent a promise. - A scheduled task can pull open actions into the morning brief. It should say "nothing" when there aren't any.
Your own session transcript is a follow-up guide. After a Practical AI session, ask:
From this session's transcript, list what I said I'd set up this week.
Split it into: do today, do this week, leave until the tools have been used for a month.
Don't add tasks I didn't agree to.
Pro tips
- Quote the meeting in the answer. If it can't point at a line, it shouldn't state the fact.
- One theme per scan. "Tell me everything interesting" returns noise.
- Say whether you're allowed to record before you build a library. A searchable archive of people who didn't know is not a win. Security, privacy and compliance.
Limits
Transcripts mishear numbers. Check a figure before it goes into a pack or an email.
Connectors see the account you connected. They don't see a colleague's meetings unless those notes were shared with you.
A scan across months uses a lot of context. If you hit a limit, narrow it: one account, one month, one question.
Where to start in 30 minutes
- Connect Granola or Wispr Flow, whichever you actually use.
- Pick the last meeting that still needs a follow-up.
- Run the one-meeting prompt. Send nothing until you've checked the actions against the transcript.
- Save that prompt as a skill if you'll do it again this month.
- If you had a session with us, run the "what did I say I'd set up" prompt on that transcript and keep the list.