More Resources
Prompt

Surface every open commitment in your active deals

Built by: Lusha
Time to build: 3 min
Difficulty: Medium
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, Calendar, and Slack connector output, but were not pulled from a live session. Run the prompt with your own data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Deals stall because someone didn’t send the case study, didn’t answer the integration question, or forgot that the prospect committed to looping in the CFO last week. This Claude prompt scans Gmail threads and Google Calendar across every active deal, validates each contact via Lusha, and posts a full commitments log to Slack before the pipeline review. Every open item, every deal, one post.

The prompt

Open in Claude Open in ChatGPT 
<context>
Before my next round of calls or my weekly pipeline review, I want to surface every open commitment across my active deals — things I promised to send, things prospects promised to do, questions that were asked but never answered. I want the list posted to Slack so I can work through it systematically.

My pipeline:
- Active deals: [PASTE DEAL NAME, COMPANY, PRIMARY CONTACT — one per line]
- Slack channel to post to: [CHANNEL NAME — e.g. #my-pipeline or #deal-name]
- Timeframe to check: [e.g. "last 60 days" or specific date range]
</context>

<task>
1. For each deal, search Gmail for the email thread with the primary contact:
   - Any commitment I made but haven't followed through on — "I'll send X", "I'll check on Y", "I'll introduce you to Z"
   - Any question the prospect asked that wasn't fully answered
   - Any commitment the prospect made but hasn't delivered — "I'll loop in our CTO", "I'll get you the budget timeline"
   - Any next step that was agreed on a call but hasn't been actioned

2. Check Google Calendar for any scheduled or recently completed meetings with each deal's contact:
   - Is there a meeting coming up in the next 7 days?
   - Was there a recent meeting where follow-up actions may have been agreed?
   - Flag if no meeting is scheduled and the last touch was more than 14 days ago

3. Use Lusha to validate the primary contact for each deal:
   - Still at the company in the same role?
   - Any title change or account signal since the last email?

4. Build a commitments log per deal:
   DEAL: [name] — [company] — [stage]
   MY OPEN COMMITMENTS: list what I owe the prospect, with approximate date promised
   PROSPECT'S OPEN COMMITMENTS: list what the prospect said they would do
   UNANSWERED QUESTIONS: any question asked by either side that was never resolved
   NEXT MEETING: scheduled date or "none booked — last touch [date]"
   CONTACT STATUS: verified / title changed / flag

5. Post the full commitments log to the specified Slack channel.
   Format for Slack: one block per deal, *bold* key fields, emoji status indicators:
   ✅ no open commitments — clean
   ⚠ open commitments on my side — action needed
   🔴 prospect commitment overdue or contact issue — flag

6. End with a summary line: total deals reviewed, total open commitments on my side, total prospect commitments outstanding.
</task>

<constraints>
- Post to Slack — don't just return the log as text.
- Only flag commitments that are genuinely open — don't surface things that were resolved in a subsequent email.
- If a deal has no open commitments on either side, mark as ✅ and move on — don't pad the output.
- The summary line is for the manager, not just the rep — make it specific enough to use in a pipeline review.
</constraints>

What you'll get back

The situation: An AE runs this before Monday’s pipeline review. Four active deals, last 60 days of Gmail and Calendar checked. Posted to #pipeline-review.

Slack post — #pipeline-review

⚠ Waverly Digital — SDR data layer — Proposal Contact: S.R., VP of Sales ✓ confirmed at Waverly

My open commitments: — HubSpot integration documentation promised 9 days ago — not sent — Intro to solutions engineer promised on the May 14 call — not scheduled

Prospect’s open commitments: — S.R. said she would confirm Q3 budget allocation with her COO — no update received

Unanswered questions: — “Do you have case studies from SaaS companies under 200 people?” — asked May 18, not answered

Next meeting: Discovery call follow-up — booked Thursday May 29, 10am Contact status: ✓ verified, same role, no account signal

⚠ [Collaborative AI workspace] expansion — data quality — Negotiation Contact: D.R., Head of Sales Strategy and Operations ✓ confirmed at [Collaborative AI workspace]

My open commitments: — Case study on enrichment workflow promised 38 days ago — never sent

Prospect’s open commitments: — D.R. said the ops review would wrap “end of April” and the team would revisit — no follow-through

Unanswered questions: — “How does the enrichment handle duplicate records?” — asked in April, no reply sent

Next meeting: None booked — last touch 38 days ago ⚠ Account signal: Sales headcount up 22% in last 60 days — active hiring Contact status: ✓ verified, same role

🔴 [Sales enablement SaaS] new business — RevOps tooling — Proposal Contact: B.N., Sr Director RevOps

My open commitments: None

Prospect’s open commitments: — B.N. said she would loop in the VP of RevOps before the next call — no intro received — call is in 3 days

Unanswered questions: None

Next meeting: Demo call — Thursday May 29, 2pm 🔴 Contact flag: Lusha shows B.N. may have departed — verify before Thursday’s call. Replacement found: J.S., VP of Revenue Operations — j.s@[h***s***].com

✅ [ Sales content SaaS] expansion — $95K — Discovery Contact: M.C., VP RevOps ✓ confirmed No open commitments on either side. Last touch 6 days ago. Next meeting booked June 3.

Summary: 4 deals reviewed · 3 open commitments on my side · 2 prospect commitments outstanding · 1 contact flagged ([Sales enablement SaaS] — verify before Thursday)

Thread structure based on live Gmail and Calendar connector field format. Contacts verified against live Lusha data, May 26, 2026. Names masked to initials.

Why use Lusha in Claude

The [Sales enablement SaaS] flag is the output that matters most in this example — B.N. was supposed to bring the VP of RevOps to Thursday’s call, but Lusha shows B.N. may have left the company. Without this scan, the rep joins a Proposal-stage demo with a departed contact and a buying group introduction that was never made. Gmail caught the open commitment. Lusha caught the contact risk. Calendar surfaced the 3-day window to act. Slack put it in front of the rep on Monday morning, not Thursday at 1:59pm. All four connectors are doing different jobs and none of them is optional here.

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

FAQ

  • How does the prompt know a commitment was made but not followed through on?

    Gmail surfaces the thread. Claude reads the language — “I’ll send X”, “I’ll check on Y”, “we agreed to” — and checks whether any subsequent email in the thread contains what was promised. If the case study was promised on May 18 and the thread shows no email after that containing a case study link, the commitment is flagged as open.

  • What if a commitment was fulfilled on a call rather than by email?

    The prompt can only check what’s in Gmail and Calendar. If the commitment was addressed verbally on a Zoom call with no follow-up email confirming it, the prompt won’t know — it will still flag it as open. The fix is to send a one-line email after every call confirming what was resolved: “Quick note — covered the HubSpot question on the call, sending the doc now.” That gives Gmail the signal it needs.

  • What's the difference between the ⚠ and 🔴 status?

    ⚠ means there are open commitments on the rep’s side — the rep needs to act before the next touch. 🔴 means a prospect commitment is overdue or there’s a contact issue — something outside the rep’s control that needs to be resolved before the deal can progress. In the example, [Sales enablement SaaS] gets 🔴 because B.N. may have left and the buying group intro was never made — two problems that need fixing before Thursday, not after.

  • Can I run this for a single deal rather than the whole pipeline?

    Yes — paste one deal into the “active deals” field. The output is the same commitments log for that one deal. Useful before a high-stakes call where you want to make sure every open item is addressed going in.

  • How is this different from the weekly pipeline review prompt?

    The weekly pipeline review prompt flags deal risk at the pipeline level — stage progression, deal health, forecast accuracy. This prompt goes one level deeper into each deal and surfaces the specific action items that are blocking progression. Use the pipeline review for the manager view, use this prompt for the rep’s pre-call prep.

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