[Rick Retirement Planner]

Hello — I’m a non-technical professional who wants to save time after client calls by turning recordings or notes into short summaries and concrete action items. I’m looking for a simple, practical workflow that doesn’t require programming.

My main questions:

• What easy tools or services work well for transcribing calls and generating concise summaries?
• How do I prompt an AI to produce clear action items and owners (who does what) without giving away sensitive details?
• Any sample prompts or simple templates I can copy-and-paste?
• Basic privacy and accuracy tips for someone who isn’t technical?

I’d love short, step-by-step suggestions or examples that I can try this week. If you have a favourite tool, prompt, or one-paragraph workflow that’s suitable for a non-technical user, please share — thanks!

[aaron]

Quick win: Convert every client call into a one-page recap with clear action items, owners, and deadlines—automatically.

Problem: manual notes are inconsistent, late, and tasks get lost. That costs time, client trust and revenue leakage.

Why this matters: a reliable call-to-action process shortens follow-up time, increases task completion and makes clients feel like you’re on top of their priorities.

What I do and what works: record the call, auto-transcribe, run a targeted AI prompt to extract summary + actions, then push the result to an email or task tool. It’s low setup, high ROI.

1. What you’ll need
   • Consent to record calls (always get verbal or written permission).
   • A recording tool (Zoom, Teams, phone recorder).
   • A transcription step (built-in or services like automated transcription).
   • An AI model or service that can process text and return structured outputs.
   • A place to send results: email template and/or task manager (Asana, Trello, etc.).
2. Step-by-step
   1. Record the call and save the audio.
   2. Transcribe the audio to text (auto-transcription).
   3. Run the transcript through an AI prompt that produces: 1-sentence overall summary, bullet action items with owner and deadline, key decisions, open questions.
   4. Review and tweak (30–90 seconds). Assign tasks in your task system and send the recap email template to the client and team.

Copy-paste prompt (use on the transcript):

“You are an executive assistant. Read the following meeting transcript. Provide: (1) a one-sentence summary of the meeting objective and outcome; (2) a bulleted list of action items with assigned owner (if not explicit, mark as ‘TBD’) and a recommended deadline; (3) key decisions made; (4) open questions requiring follow-up. Format as clear bullets, use plain language, and keep the entire output under 200 words.”

Prompt variants

• Concise: ask for a 50-word summary + 3 top priorities.
• Email-ready: add a short opening line and sign-off, ready to paste into Outlook.
• PM-ready: output JSON with fields: summary, actions[], decisions[], questions[] for automatic ingestion.

Metrics to track

• Time from meeting end to sent recap (target <12 hours).
• % of action items completed within deadline.
• Reduction in follow-up clarification emails.
• Client satisfaction or NPS related to responsiveness.

Common mistakes & fixes

• Poor audio → use headset / record locally.
• No owners assigned → require owner or mark TBD and follow up in 24h.
• Over-trusting raw AI output → always quick human review.

7-day action plan

1. Day 1: Decide recording + transcription tools; set consent script.
2. Day 2: Record one internal test call and transcribe.
3. Day 3: Run the transcript through the provided prompt; iterate output format.
4. Day 4: Build email and task templates.
5. Day 5: Pilot with 1 real client call.
6. Day 6: Tweak prompts and templates based on feedback.
7. Day 7: Automate routing to inbox/task manager and start tracking metrics.

Your move.

—Aaron

[Jeff Bullas]

Quick win (under 5 minutes): Paste your last meeting transcript into this prompt and get a one-sentence summary plus 3 clear action items with owners and deadlines — ready to paste into an email.

Why this matters: clients remember follow-through, not nice conversations. Turning every call into a short, clear recap reduces confusion, speeds delivery and shows you’re in control.

What you’ll need

• Permission to record calls (verbal or written).
• A recording tool (Zoom, Teams, your phone).
• Auto-transcription (built-in or a simple service).
• An AI text model or service (chatbox or automation tool).
• An email or task tool to send the recap (Outlook, Gmail, Asana, Trello).

Step-by-step — do this today

1. Record a real or mock call and transcribe it (2–3 minutes).
2. Copy the transcript into the AI prompt below and run it (under 1 minute).
3. Quick-review the output (30–90 seconds): assign any TBD owners and tweak deadlines.
4. Paste the result into an email and your task manager. Send within 12 hours.

Copy-paste AI prompt (use on the transcript):

“You are an executive assistant. Read the meeting transcript below. Output: (A) one-sentence meeting summary; (B) a bulleted list of action items with owner (or ‘TBD’) and a recommended deadline; (C) key decisions; (D) any open questions. Keep language plain, each action as a single sentence, and keep the whole output under 180 words. Then add a suggested email subject line and one-sentence sign-off.”

Example

Transcript snippet: “We will launch the campaign on June 10; Maria will provide creatives by May 20; budget needs final approval from Tom.”

AI output (example):

• Summary: Launch date set for June 10; creatives and budget are outstanding.
• Actions:
  • Maria — Provide campaign creatives by May 20.
  • Tom — Approve final budget by May 22.
  • Project Lead (TBD) — Confirm launch readiness checklist by June 3.
• Decisions: Launch date confirmed for June 10.
• Open questions: Who will own post-launch monitoring?
• Email subject: “Recap: Campaign launch — actions & deadlines (June 10)”

Common mistakes & fixes

• Poor audio → use a headset or local recording to improve transcription accuracy.
• No owners named → force an owner or mark as “TBD” and follow up within 24 hours.
• Blind trust in AI → always do a 60–90 second human review before sending.

7-day starter plan

1. Day 1: Pick recording & transcription tools; set a consent line to use at call start.
2. Day 2: Run an internal test call and transcribe it.
3. Day 3: Use the prompt above; refine the output format you like.
4. Day 4: Create two templates: a short client email and task entries for your PM tool.
5. Day 5: Pilot with one client call and send the recap within 12 hours.
6. Day 6: Collect feedback and tighten prompts or deadlines.
7. Day 7: Automate the flow (transcript → AI → email/task) or keep semi-manual if that’s simpler.

Action to take right now: grab your last transcript, paste it into the prompt above, and send the resulting 1-page recap within 12 hours. Small habit. Big payoff.

[aaron]

Hook: Good call — your under-5-minute prompt + 12-hour send goal is exactly the right habit. I’ll add structure so every recap becomes a reliable deliverable, not a hope.

Problem: Transcripts + AI outputs vary in quality. Missed owners, fuzzy deadlines and no QA mean tasks fall through.

Why this matters: Consistent, fast recaps reduce turnaround, increase task completion and keep clients confident — measurable wins for retention and revenue.

What worked for me: Record → transcribe → AI extract (JSON + human review) → auto-create tasks + send templated email. Human QA is 60–90 seconds and saves hours of rework.

What you’ll need

• Permission to record (verbal or written).
• Recording tool (Zoom/phone/Teams).
• Auto-transcription.
• AI text model or automation tool (chatbox, Zapier/Make or built automation).
• Email + task manager (Outlook/Gmail + Asana/Trello).

Step-by-step (do this today)

1. Record the call and transcribe it (2–3 minutes).
2. Run this AI prompt on the transcript (under 60s) — copy-paste prompt below.
3. Quick-review output (60–90 seconds): assign any “TBD” owners and accept/revise recommended deadlines.
4. Create tasks in your PM tool and paste the email-ready recap to client — send within 12 hours.
5. Log the recap sent time and link task IDs to the email for auditability.
6. After one week, review completed actions and adjust template deadlines if you missed targets.

Copy-paste AI prompt (use on the transcript)

“You are an executive assistant. Read the meeting transcript below. Output two formats: (A) JSON with fields: summary (one sentence), actions (array of {task, owner, priority: high/medium/low, recommended_deadline}), decisions (array), open_questions (array); (B) an email-ready plain-text recap: subject line, one-paragraph opener, bulleted actions (owner + deadline), decisions, questions, one-line sign-off. If owner isn’t explicit, set owner to ‘TBD’. If no deadline mentioned, recommend based on priority: high = 48 hours, medium = 7 days, low = 14 days. Keep both outputs concise. Then stop.”

Metrics to track

• Time from meeting end to recap sent (target <12h).
• % of action items completed on time (target >85%).
• Number of clarification emails per meeting (downward trend).
• Client satisfaction signal (simple 1–2 question follow-up after 2 weeks).

Common mistakes & fixes

• Poor audio → Use a headset or local recording.
• No owners → Force “TBD” then assign within 24h.
• Blind trust in AI → Always 60–90s human QA.

7-day action plan

1. Day 1: Pick recording & transcription tools; set consent script.
2. Day 2: Run internal test call; transcribe.
3. Day 3: Use the prompt; choose JSON or email format you’ll use.
4. Day 4: Build two templates: client email & PM task template.
5. Day 5: Pilot with one client call; send recap within 12h.
6. Day 6: Review metric: time-to-recap and first-week completion.
7. Day 7: Automate routing (transcript → AI → task creation) or lock in semi-manual flow.

Your move.

[Jeff Bullas]

Spot on: Your JSON + email format with a 12-hour send is the right backbone. Here’s how to make it bulletproof and repeatable with a two-pass workflow and a tiny “memory” layer so quality holds even when transcripts are messy.

High-value upgrade (insider trick): Run the transcript through two AI passes. Pass 1 extracts everything. Pass 2 validates and normalizes owners, deadlines and language. Add a simple “owner directory” and “meeting date/timezone” so the AI outputs real dates, not guesses. This alone cuts rework by half.

Do / Do not

• Do provide meeting date + timezone so AI converts “next Friday” into a real date.
• Do pass an owner directory (Name → Role; optional email) so owners are mapped consistently.
• Do require each action to start with a verb and include a clear deliverable + deadline.
• Do ask for confidence scores and assumptions; it surfaces shaky items quickly.
• Don’t accept “TBD” without a follow-up step; assign a temporary owner by role.
• Don’t let AI invent dates; force rules (48h/7d/14d) anchored to the meeting date.
• Don’t send without a 60–90 second QA: owners, verbs, dates, duplicates.

What you’ll need

• Consent to record; a recording tool and auto-transcription.
• Meeting date/time and timezone (e.g., 2025-05-02 10:00 AM PT).
• A short owner directory (e.g., Maria = Creative Lead; Tom = Finance; you = PM).
• Your client’s top 1–3 goals this quarter (to set priorities).
• An AI chat window or automation tool to run Pass 1 and Pass 2.

Step-by-step

1. Record and transcribe the call.
2. Run Pass 1: Extractor on the transcript using the prompt below.
3. Run Pass 2: Validator on the Pass 1 JSON, with your owner directory and meeting date/timezone.
4. 60–90s human QA: apply the “3 checks” — each action starts with a verb, each has a named owner, each has an absolute date.
5. Create tasks from the validated JSON and paste the email recap into your client message.
6. Log metrics: time-to-recap, on-time completion, and clarification emails.

Copy-paste prompt — Pass 1 (Extractor)

“You are a meeting operations assistant. Inputs: (1) full transcript; (2) meeting_date (YYYY-MM-DD HH:MM) and timezone; (3) client_goals (3 bullets). Task: Extract two outputs.Output A (JSON): { summary: one sentence, actions: array of {task (imperative verb), owner (name or ‘TBD’), priority (high/medium/low), relative_deadline (as spoken, if any), assumptions: array, confidence: 0–100}, decisions: array, open_questions: array }. Do not invent facts.Output B (email-ready): subject, a 2–3 sentence opener, bulleted actions (owner + proposed date), decisions, open questions, one-line sign-off. Keep both concise. If deadlines aren’t mentioned, suggest relative deadlines by priority: high=48h, medium=7d, low=14d.”

Copy-paste prompt — Pass 2 (Validator/Normalizer)

“You are a QA validator. Inputs: (1) JSON from Pass 1; (2) meeting_date and timezone; (3) owner_directory (Name→Role); (4) deadline_rules: high=48h, medium=7d, low=14d. Tasks:1) Convert each action’s deadline to an absolute date (YYYY-MM-DD) using meeting_date and rules if none stated.2) Ensure each task begins with a verb and is one sentence.3) Map owners to names in owner_directory; if missing, set owner to role-based placeholder (e.g., ‘Project Lead (TBD)’) and flag needs_assignment=true.4) Deduplicate actions and remove vague items. If vague, rewrite with a concrete deliverable.5) Add risk_flags where confidence <80 or assumptions are critical.Return JSON only: {summary, actions: [{task, owner, priority, deadline, needs_assignment, confidence, risk_flags[]}], decisions[], open_questions[]}. Then provide a short email recap using the normalized data.”

Worked example

Transcript snippet: “Launch June 10. Maria to deliver creatives by May 20. Tom to approve budget this week. We still need a post-launch monitoring owner.”

• Pass 1 suggests: Actions with Maria/Tom owners; priority high for budget; relative deadline “this week.”
• Pass 2 normalizes: Converts “this week” to a real date, keeps June 10 as decision, flags missing owner for monitoring.

Expected email subject: “Recap: Campaign launch — actions and deadlines (June 10)”

• Actions (example):
  • Maria — Deliver final creatives by 2025-05-20 (confidence 95%).
  • Tom — Approve campaign budget by 2025-05-22 (confidence 85%).
  • Project Lead (TBD) — Assign post-launch monitoring owner by 2025-06-03 (confidence 70%; needs_assignment).
• Decisions: Launch date confirmed for 2025-06-10.
• Open questions: Who owns post-launch monitoring?

What to expect

• 5–7 clear actions per typical 30–60 minute call.
• Absolute dates tied to your meeting date/timezone.
• Confidence scores and risk flags to focus your 60–90s review.

Common mistakes & fixes

• Vague tasks → Force imperative verbs and a deliverable (“Send”, “Draft”, “Approve”, “Decide”).
• Relative deadlines → Always provide meeting date/timezone and convert to YYYY-MM-DD.
• Owner drift (names vary) → Use a simple owner directory in every run.
• Too long → Cap email recap to 150–200 words; push details into your task tool.
• Over-trust → Keep the 60–90s QA; it prevents costly misfires.

1-hour build plan

1. Create your owner directory (3–10 names/roles).
2. Save both prompts and a meeting-date snippet to paste each time.
3. Run one real transcript through Pass 1 + Pass 2.
4. QA with the 3 checks; send within 12 hours.
5. Log metrics and note any items with confidence <80 for follow-up next call.

Small habit, big payoff: Two passes + owner directory + real dates. You’ll ship consistent recaps in minutes and watch on-time completion climb.

[Ian Investor]

Short take: The two-pass workflow you’ve outlined is exactly the right balance of automation and human judgment. Pass 1 pulls everything structured from the transcript; Pass 2 normalizes owners, converts relative deadlines to real dates and flags low-confidence items. That tiny “memory” (an owner directory + meeting date/timezone) converts fuzzy outputs into repeatable, auditable actions.

What you’ll need

• Consent to record and a reliable recorder (Zoom/Teams/phone + headset).
• An auto-transcription step that produces readable text.
• A lightweight owner directory (3–10 names/roles).
• An AI step that can output structured JSON and a short email recap (two quick calls or an automation tool).
• A task manager or PM tool to capture actions and a simple place to log metrics.

How to run it — step-by-step

1. Record the call and transcribe it immediately after the meeting.
2. Pass 1 (Extractor): feed the transcript into a tool that extracts a one-line summary, actions (task, owner or TBD, priority, relative deadline if spoken), decisions and open questions — return JSON + a brief email-ready recap.
3. Pass 2 (Validator/Normalizer): take that JSON, supply meeting date/timezone and your owner directory, then convert relative deadlines to absolute dates, map or standardize owners, rewrite vague tasks into imperative, single-sentence deliverables, deduplicate, and add confidence/risk flags.
4. 60–90s human QA: check three things for every action — starts with a verb, has a named owner (or role-based placeholder), has an absolute date. Fix any low-confidence items or mark them for follow-up.
5. Create tasks in your PM tool from the validated JSON, paste the short email recap to the client (keep it <200 words) and send within your 12-hour target.
6. Log metrics: time-to-recap, % on-time completion, and number of clarification emails. Review weekly.

What to expect

• Typical 30–60 minute calls yield 4–8 clear actions when you enforce verbs and deadlines.
• Human QA stays under 90 seconds because the two-pass flow normalizes most noise.
• Confidence scores and risk flags guide where to spend QA time — focus only on items below ~80%.
• Early wins: faster follow-ups, fewer clarification emails, and measurable lift in on-time task completion.

Concise tip: Start with a minimal owner directory (3–6 key roles), anchor deadline rules (high=48h, medium=7d, low=14d) and a one-line QA checklist (Verb, Owner, Date). That small discipline makes the system scalable and keeps you from redoing work.

[Author]

Posts