Generate a post-call follow-up from a Zoom transcript
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Zoom, Lusha, and Gmail connector output, but were not pulled from a live session. Run the prompt with your own Zoom call to see live results. Personal details in any live examples are masked or abbreviated for privacy.
A post-call follow-up that closes every loop — commitments made, questions raised, next step confirmed — starts with the transcript, not the rep’s memory. This Claude prompt pulls the full Zoom transcript, validates the send-to contact via Lusha, checks Gmail for any prior outstanding commitments, and generates a structured follow-up under 200 words with a specific section for every open item before anything gets lost.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I just finished a Zoom call. Before I send the follow-up email, I want to extract every commitment, open question, and next step from the transcript — and generate a structured follow-up that closes every loop without writing it from scratch.
My call details:
- Company: [COMPANY NAME]
- Zoom meeting: [MEETING ID OR "FIND MOST RECENT ZOOM CALL WITH [COMPANY]"]
- My name / rep: [MY NAME]
- What I sell: [PRODUCT / SOLUTION]
- Primary contact on the call: [NAME AND TITLE — or "find from transcript"]
- Slack channel to notify: [CHANNEL NAME OR "skip"]
</context>
<task>
1. Pull the Zoom transcript for this call:
- What were the key topics discussed?
- What did the prospect specifically ask for?
- What did I commit to delivering and by when?
- What did the prospect commit to doing on their side?
- What questions were raised but not answered on the call?
- What was agreed as the next step?
2. Use Lusha to validate the primary contact:
- Still at the company in the same role?
- Verified email for the follow-up send
3. Check Gmail for prior thread history with this company:
- Any prior commitments still outstanding from before this call?
- What subject line was the last thread using?
4. Generate a structured follow-up email:
- Subject: references the call topic and date — not "Following up"
- Opening: one sentence acknowledging what was most important on the call
- Section 1: What I'm doing — specific commitments from me with dates
- Section 2: What I need from you — specific commitments from the prospect with dates
- Section 3: Open questions — anything raised on the call that needs an answer
- Next step: specific proposed next action with a time
- Tone: direct, no preamble, no "per our conversation"
- Under 200 words
5. If Slack channel specified: post summary of call commitments to the channel.
</task>
<constraints>
- Section 1 and Section 2 commitments must be specific: not "send information" but what exactly, by when.
- Open questions must be from the transcript — don't add generic questions.
- Under 200 words total.
- Use Lusha-verified email for the send-to address.
- If the transcript isn't available yet: flag it and return the email structure with blanks.
</constraints>What you'll get back
The situation: A rep just finished a 45-minute proposal review call with D.R. at Ashford Platforms. Running the prompt immediately after hanging up.
Transcript summary (from Zoom)
Call: Proposal review — Ashford Platforms · May 28, 2026
Topics covered: HubSpot integration specifics, pricing by user tier, ZoomInfo comparison, legal/DPA review timeline
What the rep committed to:
- Send revised proposal with ZoomInfo comparison section by Friday May 30
- Send HubSpot connector technical documentation and deduplication spec today
- Share the DPA link before end of week
What D.R. committed to:
- Loop in IT contact for HubSpot connector call by June 5
- Confirm with legal team whether DPA review needs a formal call or email review only
Open questions raised but not answered:
- Which HubSpot workspace is primary — Ashford has two and this wasn’t resolved
- CFO involvement in sign-off — D.R. mentioned it but gave no timeline
Next step agreed: Proposal review call Thursday June 5 at 2pm with D.R. and M.L.
Prior Gmail thread check
ZoomInfo comparison section was also promised on the May 14 call — not yet delivered. Flag: this commitment is now overdue from before today’s call.
Contact validated (Lusha)
D.R., Head of Sales Strategy and Operations, Ashford Platforms ✓ Verified email: d.r@[ashford].com · title unchanged
Follow-up email generated
To: d.r@[ashford].com · m.l@[ashford].com Subject: Ashford proposal — actions from today’s call
Hi David, Michael,
Good call today — the HubSpot integration and pricing tiers were the key items. Here’s what’s happening next.
From me by Friday May 30:
- Revised proposal with the ZoomInfo comparison section (overdue from our May 14 call — apologies)
- HubSpot connector documentation including deduplication spec
- DPA link for your legal team
From your side by June 5:
- IT contact for the HubSpot connector setup call
- Legal team’s preferred review format (call or email)
Still to resolve:
- Which HubSpot workspace is primary (you mentioned two)
- CFO sign-off timeline before the June 5 call
Next step: proposal review Thursday June 5 at 2pm — invite to follow.
[Name]
(162 words)
Illustrative example — fictional company names used. Run with your own Zoom call to see live results.
Why use Lusha in Claude
The Gmail check is the finding that changes this follow-up. The ZoomInfo comparison section was promised on the May 14 call — 14 days before today — and was never sent. Without the Gmail check, the rep sends a clean follow-up that doesn’t mention the prior commitment. D.R. reads it, notices the missing section again, and the deal stalls on something that was already overdue. With the Gmail check, the follow-up opens with an apology for the overdue item — which D.R. reads as self-aware and professional rather than sloppy. The transcript extraction turns a 45-minute call into a 162-word email that every open item is accounted for, without the rep manually reviewing the recording.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How is this different from the discovery call follow-up play?
The discovery call follow-up play drafts a post-discovery email based on email thread history. This play works from the actual Zoom transcript — extracting the verbatim commitments made on the call, including the ones that weren’t already in an email thread. Use this one after any call where commitments were made verbally.
What if the Zoom transcript isn't ready yet?
Zoom processes transcripts within 10–15 minutes of the call ending. If the transcript isn’t available, the prompt flags it and returns the email structure with blank placeholders — the rep can paste the transcript content once it’s ready and re-run.
Should this replace writing the follow-up manually?
Run it as a first draft generator, not a replacement for reading. The prompt extracts commitments from the transcript, but the rep should read the output before sending — especially the “what I need from you” section, which depends on accurate attribution of who said what.
Can I run this for customer calls as well as sales calls?
Yes — the structure works for any call with external commitments: discovery, proposal, QBR, renewal planning, or CS kickoff. The “what I need from you” and “what I’m doing” sections apply regardless of deal stage or relationship type.
Ready to build this?
Get started with Lusha and set up this play in minutes.
