Validate everyone on a call before you start talking
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 runs a 90-second pre-call check before any meeting. Google Calendar pulls the attendee list. Lusha validates every title and scans the account for signals. Returns who’s in the room, what changed, and one specific thing to lead with — while you’re waiting for everyone to join.
Tools: Claude, Lusha, Google Calendar
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I'm about to join a call. Before I start talking, I want to validate everyone in the meeting — who they are, whether their title has changed, and whether anything has shifted at the account that I should know. I have about 90 seconds.
My meeting:
- Company: [COMPANY NAME]
- Meeting type: [DISCOVERY / DEMO / RENEWAL / NEGOTIATION / OTHER]
- Who I expect to be there: [NAMES AND TITLES — or "pull from the calendar invite"]
- What I sell: [PRODUCT / SOLUTION]
</context>
<task>
1. Pull the meeting from Google Calendar and get the external attendee list.
2. For each external attendee, use Lusha to validate in real time:
- Current verified title — does it match what I expect?
- Still at the company?
- Tenure in current role
- Seniority: decision-maker / influencer / end user
3. Use Lusha's signals layer for a 30-second account check:
- Any structural change in the last 30 days: exec departure, M&A, funding, headcount shift
- Any change that would affect what I say on this call
4. Return a 90-second pre-call brief:
WHO'S IN THE ROOM
- Each attendee: verified name, current title, seniority read, one flag if anything changed
ACCOUNT CHECK
- Clean or flagged — with the specific signal and what it means for this call
ONE THING TO LEAD WITH
- Specific to who's in the room and what's happening at the account
5. If anyone can't be verified: flag them — "confirm who this is when you join."
</task>
<constraints>
- This is a 90-second brief. One screen, no headers, just the facts.
- ONE THING TO LEAD WITH must be specific — not "ask about their goals."
- If the account has a live signal, it changes the one thing to lead with.
- If no attendees can be pulled from Calendar, ask me to name them and run the check anyway.
</constraints>What you'll get back
The situation: An AE is joining a demo call in 2 minutes. Two external attendees on the calendar invite. She runs the prompt while the meeting loads.
Output: One validated, one flagged, one live signal, one specific opening.
Pre-call brief — Waverly Digital demo
WHO’S IN THE ROOM
- S.R., VP of Sales ✓ — 22 days in role. Decision-maker. First VP Sales hire at a previously founder-led company.
- D.K., Head of Sales Operations ✓ — 14 months in role. Influencer — knows the existing setup better than anyone.
- ⚠ Unknown attendee: a.smith@[waverly].com — not found in Lusha. Confirm who this is when you join.
ACCOUNT CHECK
Flagged: Sales team has grown 34% in the last quarter — 8 new AE and SDR roles currently posted. No M&A, no exec changes outside S.R.’s hire.
ONE THING TO LEAD WITH
S.R. is 22 days in and hasn’t formed opinions on the stack yet. D.K. has been managing the current setup for 14 months. Open by asking D.K. what’s working and what isn’t — get the institutional knowledge on the record before S.R. has to rely on memory they don’t have yet.
Attendees validated via Lusha connector. Calendar pulled from live session. Details masked for privacy.
Why use Lusha in Claude
The 90 seconds while a call loads is the last moment to know something before you have to perform. Lusha in Claude uses that window to answer the three questions that actually matter: is everyone who I think they are, has anything changed at the account, and what’s the one thing that should shape how I open. The unknown attendee flag is the output that saves the most awkward moments — someone’s on the call who wasn’t on the invite, and knowing before you start talking is better than discovering mid-demo. Works with Zoom, Google Meet, Teams — whatever platform the meeting is on.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Does this work with Zoom, Google Meet, or Teams?
Yes — the attendee list comes from Google Calendar, not the video platform. As long as the meeting was booked through Calendar, the prompt pulls the attendees regardless of whether you’re using Zoom, Meet, or Teams.
What if the meeting hasn't started yet and I don't have the full attendee list?
Name the attendees manually in the “who I expect to be there” field. The Lusha validation runs the same way — Calendar is the convenient trigger, not the only input.
What if Calendar shows an email I don't recognize?
The prompt flags it as unverified with a note to confirm when you join. You know there’s an unknown attendee before the meeting starts, not after you’ve been talking for 10 minutes without knowing who they are.
How is this different from the signing call validation play?
The signing call play is a deep pre-close check — it validates signing authority, checks contract re-routing risk, and returns a GO / HOLD decision. This prompt is a 90-second quick check for any meeting — lighter, faster, designed for the moment the call loads rather than an hour before a contract call.
What's ONE THING TO LEAD WITH based on?
It’s built from two inputs: who’s in the room (seniority, tenure, role) and what’s happening at the account (signals). A new VP 22 days in the role gets a different opener than a CFO who’s been there 4 years. A company with a live funding round gets a different opener than a clean account. The combination of both inputs is what makes it specific.
Ready to build this?
Get started with Lusha and set up this play in minutes.
