Draft the follow-up after a discovery call
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt drafts the post-call follow-up from a Zoom transcript — what they said the problem was, what was agreed, who owns what next. Lusha validates every send-to address before anything goes out. Zoom pulls the transcript automatically. The draft lands in Gmail under 150 words, ready to send while the call is still fresh.
Tools: Claude, Lusha, Zoom, Gmail
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I just finished a call with a prospect. I want to draft the follow-up email from the Zoom transcript, verify everyone's contact details via Lusha, and have it ready to send from Gmail in the next 10 minutes.
My call:
- Company: [COMPANY NAME]
- Meeting type: [DISCOVERY / DEMO / INTRO CALL]
- Who was on the call: [NAMES AND TITLES — or "pull from the Zoom recording"]
- What I need to send: [SUMMARY + NEXT STEPS / SPECIFIC RESOURCE / PROPOSAL REFERENCE]
</context>
<task>
1. Pull the transcript or summary from the most recent Zoom recording for this company.
2. From the transcript, extract:
- The main problem or pain they described — in their words, not a paraphrase
- Any specific thing they asked for (a case study, pricing range, a technical doc)
- Agreed next steps and who owns each one
- Any objection or concern raised that wasn't resolved on the call
- Any competitor or alternative they mentioned
3. Use Lusha to validate the send-to contacts:
- Confirm verified work email for the primary contact
- If any new stakeholder appeared on the call, pull their verified details
- Flag anyone whose email can't be verified
4. Draft the follow-up email:
- Subject: specific to what was discussed — not "Great to connect"
- Opening: one sentence on what was agreed or what they said was the problem
- Body: what I'm sending or doing next, what they're doing next
- If they asked for something specific: include it or confirm when it's coming
- If a competitor was mentioned: one sentence acknowledging it without overselling
- Closing: one specific ask or confirmation from their side
- Under 150 words
5. Return:
- The draft email with verified send-to addresses above it
- Any unresolved concern to track
- Any competitor flag worth noting before the next call
</task>
<constraints>
- Base the email on what the transcript actually says. Don't invent commitments.
- If the Zoom transcript isn't available yet, flag it — don't draft from memory.
- Subject line must reference something specific from the call.
- Under 150 words. If it needs more, the structure is wrong, not the length.
</constraints>What you'll get back
The situation: An AE just finished a 38-minute Zoom discovery call with Waverly Digital. Two people on the call. She runs the prompt 10 minutes after hanging up.
Output: Verified send-to addresses, a 127-word follow-up draft, one unresolved concern, one competitor flag.
Send-to contacts (validated via Lusha)
- S.R., VP of Sales — s.r@[waverly].com ✓ verified
- D.K., Head of Sales Operations — d.k@[waverly].com ✓ verified
Follow-up email draft
To: s.r@[waverly].com CC: d.k@[waverly].com Subject: Data layer for the new SDR ramp — what we discussed
Hi Sofia,
Good call today. You mentioned the biggest issue right now is new SDRs taking 6+ weeks to ramp because they’re building lists manually. That’s exactly where we start.
Next steps:
- I’ll send the SDR onboarding case study from a similar-stage SaaS company by Friday — D.K., you mentioned this would be useful context for the eval
- Sofia, you’ll confirm with your COO whether the Q3 budget has been allocated before we scope a pilot
One question before I send the case study: is this a Q3 decision or are you looking at Q4?
[Name]
127 words.
Unresolved concern to track
D.K. asked whether Lusha integrates with their current CRM (HubSpot). The question wasn’t fully answered on the call — flagged for the next touch. Don’t let this sit without a clear answer before the next meeting.
Competitor flag
Waverly is also evaluating ZoomInfo — mentioned by D.K. when discussing data coverage. Not pressed on it during the call. Worth asking on the next touch: “What’s driving the ZoomInfo evaluation — coverage, price, or something else?”
Transcript pulled from Zoom recording, May 21. Contacts validated via Lusha connector. Details masked for privacy.
Why use Lusha in Claude
A follow-up email written from memory 3 hours after a call is a different email than one written from the transcript 10 minutes after. The transcript version references what they actually said — “new SDRs taking 6+ weeks to ramp because they’re building lists manually” — rather than a paraphrased version of it. The competitor flag and the unresolved concern are the outputs that most reps skip when writing from memory because they’re focused on the positive. They’re also the two things that shape how the next call goes. Lusha validates every send-to address before anything goes out — so the follow-up goes to the right verified email, not a form address that bounces.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if the Zoom transcript isn't ready yet?
Zoom typically processes transcripts within 10–15 minutes of the call ending. The prompt flags if it can’t find a transcript and won’t draft from assumptions. Run it after the transcript is available — 10 minutes post-call is worth the wait for an accurate follow-up.
What if someone was on the call who I can't find in Lusha?
Their email is flagged as unverified. The prompt still drafts the email but marks their address as needing manual verification before sending. Better to send 5 minutes later with a verified address than immediately with one that bounces.
How is this different from the renewal follow-up play?
The renewal brief and follow-up prompt is built for CS/AM renewal calls — it has a pre-call brief and a post-call follow-up phase. This prompt is specifically for AE discovery and demo calls — no pre-call phase, focused on capturing what was said and drafting a specific next-step email fast.
Can I use this for demos, not just discovery calls?
Yes — specify “demo” in the meeting type field. The extraction adjusts: for demos it looks for technical questions asked, features they reacted to, and integration concerns raised. The follow-up draft reflects the demo context.
What if a competitor was mentioned but I don't know how to handle it?
The prompt surfaces the competitor flag and suggests one question to ask on the next call — “What’s driving the ZoomInfo evaluation — coverage, price, or something else?” That question surfaces the real objection without defensiveness.
Ready to build this?
Get started with Lusha and set up this play in minutes.
