More Resources
Prompt

Book the follow-up meeting directly from Claude

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude ▪ Gmail ▪ Google Calendar ▪ Lusha

Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Gmail, and Google Calendar connector output, but were not pulled from a live session. Run the prompt with your own thread data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A prospect replies: “Tuesday 3pm works.” The rep opens Calendar, creates the event, copies in the email address, adds the Meet link, and sends a confirmation email — five steps that take 3–4 minutes every time. This Claude prompt does all of it in one pass — Gmail finds the confirmed time, Google Calendar creates the event and adds a Meet link, Lusha confirms the verified attendee email, and the confirmation email is ready to send.

The prompt

Open in Claude Open in ChatGPT 
<context>
A prospect just replied to my email confirming a meeting time. Instead of opening Google Calendar, creating the event manually, copying in attendees, and then sending a confirmation — I want to do it all from here. Find the reply, create the calendar event, and draft the confirmation email.

My meeting:
- Prospect name and company: [NAME, COMPANY]
- Thread to check: [GMAIL THREAD SUBJECT OR "CHECK GMAIL FOR MOST RECENT THREAD WITH [COMPANY]"]
- What I sell: [PRODUCT / SOLUTION]
- Meeting type: [DISCOVERY / DEMO / FOLLOW-UP / PROPOSAL REVIEW / OTHER]
- My calendar: [MY EMAIL ADDRESS]
</context>

<task>
1. Search Gmail for the most recent thread with this prospect:
   - Find the email where a specific meeting time was confirmed
   - Extract: the agreed date, time, and timezone
   - Note who confirmed the time and whether any agenda was discussed

2. Use Lusha to validate the prospect:
   - Confirm current title and that the prospect is still at the company
   - Pull the verified work email — use this as the attendee address for the invite

3. Create the calendar event via Google Calendar:
   - Title: [Meeting type] — [Company name]
   - Date and time: as confirmed in the Gmail thread
   - Duration: 30 minutes (default) unless a different length was specified in the thread
   - Attendees: the prospect's verified Lusha email + my email address
   - Description: one sentence on what the meeting is for, based on what was discussed in the thread
   - Add a Google Meet link

4. Draft a brief confirmation email to the prospect:
   - Subject: Confirmed — [Meeting type] [Date] [Time]
   - Body: confirms the meeting is in both calendars, states the agenda in one line, includes the Google Meet link
   - Under 60 words

5. Return:
   - Confirmation that the calendar event was created
   - The meeting details: date, time, attendees, Meet link
   - Draft confirmation email ready to send
</task>

<constraints>
- Use the Lusha-verified email as the attendee address — not the email address from the Gmail thread header, which may be a personal address.
- If no confirmed time is found in the Gmail thread: flag it — don't create an event without a confirmed time.
- Default duration is 30 minutes unless the thread specifies otherwise.
- The confirmation email must include the Google Meet link — the prospect needs it to join.
</constraints>

What you'll get back

The situation: D.R. at Ashford Platforms replied to an email: “Thursday June 5 at 2pm works for me — can you send a calendar invite?” The rep runs the prompt.

Gmail thread found

Thread: “RE: Data layer for the SDR ramp — Ashford” Confirmed time: Thursday June 5, 2:00pm — 2:30pm (D.R. specified 30 minutes) Confirmed by: D.R. Agenda discussed: “Proposal review — specifically the HubSpot integration section”

Contact validated (Lusha)

D.R., Head of Sales Strategy and Operations, Ashford Platforms ✓ Verified work email: d.r@[ashford].com ✓

Note: D.R. replied from a Gmail personal address ([email protected]) — using Lusha-verified work email for the invite instead.

Calendar event created

✅ Event created in Google Calendar

Title: Proposal Review — Ashford Platforms Date: Thursday, June 5, 2026 Time: 2:00pm – 2:30pm Attendees: d.r@[ashford].com · rep@[company].com Description: Proposal review — HubSpot integration section and pricing questions Google Meet link: meet.google.com/xxx-xxxx-xxx (generated on live run)

Draft confirmation email

To: d.r@[ashford].com Subject: Confirmed — Proposal Review Thursday June 5, 2pm

Hi David,

Calendar invite sent — we’re booked for Thursday June 5 at 2pm to walk through the proposal, specifically the HubSpot integration section. Google Meet link is in the invite.

Looking forward to it.

[Name]

44 words.

Illustrative example — fictional company names used. Run with your own thread data to see live results.

Why use Lusha in Claude

The Lusha email validation is the detail that justifies running this as a prompt rather than just creating the Calendar event manually. D.R. replied from a personal Gmail address — a common pattern when a prospect checks email on a mobile device. Without the Lusha check, the Calendar invite goes to a personal address that may not show the prospect’s work calendar. The Lusha-verified work email goes to the right place. The five-step manual workflow — open Calendar, create event, add attendees, add Meet link, send confirmation — becomes one prompt run. For a rep who books 8–10 meetings a week, that’s 20–30 minutes recovered.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • What if the prospect said "Thursday works" without specifying a time?

    The prompt flags it — “no specific time confirmed in the thread, can’t create the event.” The rep needs to reply asking for a specific time before the event can be created. The prompt never creates an event from an ambiguous time reference.

  • What if the prospect is in a different timezone?

    The prompt extracts the timezone from the thread if specified. If no timezone is mentioned, it uses the rep’s local timezone by default and flags it in the output — “timezone not specified in thread, defaulting to your local timezone — confirm with prospect if international.” For cross-timezone meetings, explicitly state the timezone when confirming the time in the email.

  • Can I add additional attendees — an SE or manager?

    Yes — add the additional email address in the “my calendar” field: “[email protected], [email protected].” All addresses listed are added as attendees on the invite.

  • What if the thread has multiple time suggestions that were rejected before a final one was agreed?

    The prompt reads the full thread and finds the most recently confirmed time — not the first one proposed. If the thread is ambiguous about which time was finally agreed, the prompt flags the ambiguity and returns both options for the rep to confirm before creating the event.

  • How is this different from just creating a Calendar event manually?

    Three differences: the Lusha email validation ensures the invite goes to the verified work address rather than whatever email replied to the thread. The thread-based description means the event description reflects the actual agenda discussed rather than a blank or generic note. The confirmation email is drafted alongside the event creation rather than as a separate step.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Start for free Read the Docs