Check whether a prospect’s issue is tracked in Jira before a call
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 Jira 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.
“We evaluated you before and had a data quality issue.” That sentence can derail a re-engagement call in 30 seconds — unless the rep already knows whether the issue was fixed, when, and whether the prospect was told. This Claude prompt searches Jira for any issue related to a prospect before the call, checks Gmail for whether the resolution was communicated, and validates the contact via Lusha. Walk in knowing the answer before the prospect asks.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
Before a call with a prospect — especially a re-engagement, renewal, or competitive deal — I want to know whether any issue, bug, or feature request related to this company or their stated concern has been logged in our Jira. I don't want to be caught off guard if the prospect brings up a past problem that's either been fixed or is still open.
My call:
- Prospect / customer company: [COMPANY NAME]
- What the prospect has raised or might raise: [SPECIFIC CONCERN / "check all"]
- What I sell: [PRODUCT / SOLUTION]
- Call type: [RE-ENGAGEMENT / RENEWAL / COMPETITIVE DEAL / FIRST CALL]
- Primary contact: [NAME AND TITLE — or "find via Lusha"]
</context>
<task>
1. Search Jira for any issue, ticket, or request that mentions this company or their stated concern:
- Search by company name, domain, or relevant keywords
- Return: ticket number, title, status (open / in progress / resolved), date created, date resolved
- Flag any issue that is still open
2. Use Lusha to validate the primary contact:
- Still at the company in the same role?
- Any account signal in the last 30 days?
3. Search Gmail for any prior thread where this issue was discussed with the company:
- Was it raised by the prospect?
- Was a resolution promised?
- Was the resolution communicated back to the prospect?
4. Build a pre-call issue brief:
COMPANY: [name]
CONTACT: [verified name, title, status]
JIRA FINDINGS: list of relevant tickets with status
OPEN ISSUES: any unresolved tickets the prospect might raise
RESOLVED ISSUES: any tickets fixed — date and what was done
GMAIL CONTEXT: was the prospect informed of the resolution?
RECOMMENDED HANDLING: one specific sentence
5. Flag:
- CLEAN: all issues resolved and prospect informed — no risk on this topic
- OPEN RISK: any issue still open — prepare a response before joining
</task>
<constraints>
- OPEN RISK is the most important flag — surface prominently.
- No Jira record found: return "No issues found" — that's a clean result.
- Recommended handling must be specific to what was found.
- If the prospect was never informed of a resolution: flag it — the call is an opportunity to close that loop.
</constraints>What you'll get back
The situation: An AE is re-engaging Briarwood SaaS — a company that evaluated the product 19 months ago. The Drive check surfaced a prior failed evaluation. Running the Jira check to understand whether any issue was logged before the call.
Pre-call issue brief — Briarwood SaaS
CONTACT P.O., VP of Sales, Briarwood SaaS ✓ — confirmed at company in current role No account signal detected in last 30 days.
JIRA FINDINGS
| Ticket | Title | Status | Created | Resolved |
|---|---|---|---|---|
| PROD-847 | Data coverage gap — EMEA contact verification for mid-market SaaS | ✅ Resolved | Aug 14, 2024 | Nov 3, 2024 |
| PROD-1102 | Batch enrichment timeout on lists >500 rows | ✅ Resolved | Sep 2, 2024 | Jan 17, 2025 |
No open issues found related to Briarwood or the stated concerns.
OPEN ISSUES: None
RESOLVED ISSUES
PROD-847: EMEA coverage gap — resolved November 2024. Fix expanded the verified contact database for EMEA mid-market SaaS companies by 34%. PROD-1102: Batch enrichment timeout — resolved January 2025. Timeout threshold extended; lists up to 2,000 rows now process without interruption.
GMAIL CONTEXT
⚠ Gmail shows the prior evaluation thread from August–October 2024. R.F. (the previous contact, now departed) raised both issues in email. No resolution email was ever sent to Briarway — the tickets were fixed internally but the prospect was never informed.
RECOMMENDED HANDLING
Both issues from the 2024 evaluation have been resolved. Lead with it directly: “We found the two issues that came up in your 2024 evaluation — EMEA coverage and the batch processing limit. Both were fixed. Happy to show you the current numbers before we go any further.”
Flag: CLEAN — but close the loop No open issues. Both concerns were resolved. However, the prospect was never informed — the call is the opportunity to close that loop proactively rather than waiting for the prospect to raise it.
Illustrative example — fictional company names used. Run with your own data to see live results.
Why use Lusha in Claude
Without this check, the re-engagement call to Briarway starts generically — the AE doesn’t know whether the prior evaluation issues were fixed or still open. With the check, the AE leads with: “Both issues from 2024 are resolved — want to see the numbers?” That’s a completely different call. The GMAIL CONTEXT flag is the finding that adds the most value: Jira says the tickets are closed, but Gmail shows the prospect was never told. The call becomes an opportunity to proactively close that loop rather than hoping the prospect doesn’t bring it up. A rep who says “I looked into what happened in 2024 before calling” is different from every other rep re-engaging this account.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if Jira finds no record of any issue?
The brief returns “No Jira issues found for this company” — that’s a clean result. The rep can confidently say there’s no logged issue history without having to check manually. A clean Jira search is a positive signal, not a gap in the output.
What if the issue is still open?
The brief flags OPEN RISK prominently and the recommended handling shifts: “This issue was raised and is still in progress — don’t imply it’s resolved on the call. Acknowledge it directly: ‘I know there’s still an open item here — here’s where it stands and what the timeline looks like.'”
Does this search the rep's own company's Jira or the prospect's?
This searches the rep’s own company’s Jira — where internal bug reports, feature requests, and support tickets are logged. It’s not searching the prospect’s Jira. The question being answered is: “Has our team ever logged anything related to this company or this type of issue?” That’s the check that matters before a re-engagement call.
What if the issue wasn't logged in Jira — just handled informally?
Jira only surfaces what was logged. Informally resolved issues won’t appear. This is a good reason to log all support and bug reports formally — a Jira record is the only way to prove an issue was addressed. If the prompt returns no record but the rep suspects an issue was handled informally, the Drive prior relationship check is worth running alongside this one.
How is this different from the Drive prior relationship check?
The Drive prior relationship check searches for any internal documents, notes, or proposals mentioning the company. This play specifically searches Jira for logged issues — a more targeted check for technical problems, bugs, and support history. Run both for re-engagement calls where the prior relationship is complex.
Ready to build this?
Get started with Lusha and set up this play in minutes.
