30 Claude Prompts for Objection Handling

You are a senior account executive who specializes in closing deals that stall on timing. <context> A prospect told me now is not the right time to buy, and I want a script that surfaces the real reason behind the delay without pressuring them. </context> <inputs> - Stated reason for the delay: [STATED REASON] - Original timeline the prospect gave us: [ORIGINAL TIMELINE] - Event or deadline they are waiting on: [WAITING ON EVENT] - Relationship length with this prospect: [RELATIONSHIP LENGTH] </inputs> <task> Write a short spoken script of three lines that acknowledges the delay, then asks one question that uncovers whether timing is the real objection. </task> <constraints> Do not sound pushy or imply the prospect is making excuses. Keep each line under twenty words. Avoid the phrase just checking in. </constraints> <format> Return as a labeled script with ACKNOWLEDGE, then ASK, then a short note on what answer would confirm timing is genuine. </format>

You are a business case writer who helps sales teams quantify delay. <context> My prospect wants to revisit this next quarter, and I need to reframe the conversation around what waiting actually costs them so the delay decision is made with full information. </context> <inputs> - Problem currently costing them money or time: [CURRENT PROBLEM] - Estimated monthly cost of the problem: [MONTHLY COST] - Number of months until next quarter: [MONTHS OF DELAY] - Prospect's job title: [PROSPECT TITLE] </inputs> <task> Write a short reframe, delivered as three sentences, that calculates the total cost of waiting and presents it as a neutral fact rather than a pressure tactic. </task> <constraints> Use only the numbers given, show the multiplication plainly. Do not use urgency language like act now or limited time. Keep it factual and calm. </constraints> <format> Return as three sentences under a heading called THE COST OF WAITING. </format>

You are a customer success manager who has seen what happens to accounts that delay adoption. <context> I want to share a real pattern from past customers who waited to start, so my current prospect understands the tradeoff of delaying without me sounding like I am fear mongering. </context> <inputs> - What typically happens when customers delay: [DELAY OUTCOME PATTERN] - Example customer who delayed then later regretted it: [EXAMPLE CUSTOMER] - What that customer ended up losing: [WHAT WAS LOST] - Current prospect's situation: [PROSPECT SITUATION] </inputs> <task> Write a two sentence proof point the rep can say naturally in conversation, referencing the pattern without naming confidential details if none are given. </task> <constraints> Keep the tone matter of fact, not dramatic. Do not fabricate a name if none is given, use a generic descriptor like a similar company instead. Two sentences maximum. </constraints> <format> Return as a single quoted line the rep could say verbatim, followed by one line explaining when to use it. </format>

You are a sales strategist who trains reps to handle deprioritized deals. <context> A deal that was moving well suddenly went quiet after the prospect said other priorities came up, and I need discovery questions for a check in call to understand what changed. </context> <inputs> - Last known deal stage: [LAST DEAL STAGE] - Date of last real engagement: [LAST ENGAGEMENT DATE] - New priority they mentioned, if known: [NEW PRIORITY] - Internal champion's name or role: [CHAMPION ROLE] </inputs> <task> Write four discovery questions for a check in call that respectfully find out whether the deal is truly deprioritized, stuck internally, or lost to a competitor. </task> <constraints> Keep the tone warm, not accusatory. Avoid asking are you still interested directly. Four questions maximum. </constraints> <format> Return as a numbered list of four questions with a one line opener to use before asking them. </format>

You are an implementation lead who explains rollout timing to prospects. <context> My prospect thinks it is safer to wait for a quieter period before starting implementation, and I want a clear comparison of starting now versus waiting so they can decide with real information. </context> <inputs> - Typical implementation length: [IMPLEMENTATION LENGTH] - Reason they want to wait: [REASON TO WAIT] - Upcoming busy period they are avoiding: [BUSY PERIOD] - Benefit they would miss during the delay: [BENEFIT MISSED] </inputs> <task> Create a short two column comparison of starting implementation now versus after the busy period, covering timeline, effort required, and when they would see value. </task> <constraints> Be honest about tradeoffs on both sides, do not only favor starting now. Keep under 180 words. No pressure language. </constraints> <format> Return as a two column comparison labeled START NOW and START LATER, with three rows: TIMELINE, EFFORT REQUIRED, WHEN VALUE APPEARS. </format>

You are a competitive sales specialist who wins deals from entrenched incumbents. <context> A prospect told me they already use a competing tool and are happy with it, and I need a script that opens a real conversation instead of arguing against a tool they like. </context> <inputs> - Competitor they currently use: [CURRENT COMPETITOR] - How long they have used it: [TIME USING COMPETITOR] - Known gap or complaint we have heard about that competitor: [KNOWN GAP] - Our differentiator relevant to that gap: [OUR DIFFERENTIATOR] </inputs> <task> Write a three line script that validates their choice, then introduces the known gap as a question rather than an accusation. </task> <constraints> Do not badmouth the competitor by name. Frame the gap as a question, not a claim. Keep each line short and conversational. </constraints> <format> Return as a labeled script with VALIDATE, then ASK, then a note on what response signals real interest. </format>

You are a business case analyst who compares switching costs against the cost of staying put. <context> My prospect is worried about the effort of switching away from their current tool, and I want to reframe the decision around the ongoing cost of staying with a solution that has known limitations. </context> <inputs> - Current tool's known limitation costing them: [KNOWN LIMITATION] - Estimated monthly impact of that limitation: [MONTHLY IMPACT] - Estimated one time switching effort: [SWITCHING EFFORT] - Time to break even on the switch: [BREAK EVEN TIME] </inputs> <task> Write a short reframe of four sentences that compares the one time cost of switching to the ongoing cost of staying, ending with the break even point. </task> <constraints> Use only the figures provided. Keep the tone respectful of their current choice, not dismissive. Four sentences maximum. </constraints> <format> Return as four sentences under a heading called SWITCHING COST VERSUS STAYING COST. </format>

You are a customer marketing manager who curates switch stories for the sales team. <context> I want a proof point built from a customer who switched from the same competitor my prospect currently uses, so the prospect can see a peer's experience rather than just our claims. </context> <inputs> - Customer who switched: [CUSTOMER NAME] - Competitor they switched from: [COMPETITOR SWITCHED FROM] - Specific result after switching: [RESULT AFTER SWITCHING] - How long the switch took: [SWITCH DURATION] </inputs> <task> Write a two sentence proof point referencing the switch story, including the specific result and the time it took. </task> <constraints> Only use the details provided, do not add unverified claims. Keep it factual, not promotional. Two sentences maximum. </constraints> <format> Return as one quoted sentence the rep can say aloud, followed by one line on the best moment in a call to use it. </format>

You are a discovery specialist who trains reps to probe past a surface level yes. <context> A prospect said they are satisfied with their current vendor, and I want discovery questions that go past the polite answer to find any real friction they have not mentioned yet. </context> <inputs> - Current vendor: [CURRENT VENDOR] - How they described their satisfaction: [SATISFACTION DESCRIPTION] - Contract renewal date if known: [RENEWAL DATE] - Team size using the current vendor: [TEAM SIZE] </inputs> <task> Write four discovery questions that respectfully explore whether satisfaction with the incumbent is complete or whether there are unaddressed frustrations. </task> <constraints> Avoid leading questions that assume dissatisfaction. Keep a genuinely curious, non confrontational tone. Four questions maximum. </constraints> <format> Return as a numbered list of four questions, each with a short note on what a hesitant answer would reveal. </format>

You are a value engineering consultant who compares new solutions against doing nothing. <context> My prospect is comparing us not to a competitor but to simply keeping their current manual process, and I need a comparison that makes the tradeoffs of the status quo explicit. </context> <inputs> - Current manual process: [CURRENT PROCESS] - Time it takes per week: [TIME PER WEEK] - Error rate or quality issue with the manual process: [ERROR OR QUALITY ISSUE] - What our solution automates: [WHAT WE AUTOMATE] </inputs> <task> Create a short comparison covering time spent, error rate, and scalability between the current manual process and our solution. </task> <constraints> Be fair about effort required to adopt the new solution, do not overstate ease. Keep under 180 words. No hype language. </constraints> <format> Return as a two column comparison labeled CURRENT PROCESS and WITH [PRODUCT NAME], with three rows: TIME PER WEEK, ERROR RATE, ABILITY TO SCALE. </format>

You are a brand credibility specialist who helps reps at lesser known companies build trust fast. <context> A prospect said they have never heard of our company and seem hesitant to trust an unfamiliar vendor, so I need a script that builds credibility without sounding defensive about our size. </context> <inputs> - Years in business: [YEARS IN BUSINESS] - Notable customer or certification we can reference: [NOTABLE PROOF POINT] - Prospect's industry: [PROSPECT INDUSTRY] - What they are most worried about: [MAIN WORRY] </inputs> <task> Write a three line script that acknowledges being less known, then offers one concrete credibility point relevant to their industry. </task> <constraints> Do not overclaim size or scale we do not have. Keep the tone confident but honest. Three lines maximum. </constraints> <format> Return as a labeled script with ACKNOWLEDGE, then CREDIBILITY POINT, then a suggested next step to reduce their risk. </format>

You are a deal desk manager who structures risk reducing terms for cautious buyers. <context> My prospect is worried about committing to a new vendor and I want to reframe the conversation around the safety nets we can offer instead of just repeating our pitch. </context> <inputs> - Trial period or pilot option available: [TRIAL OR PILOT OPTION] - Cancellation or refund terms: [CANCELLATION TERMS] - Support level included: [SUPPORT LEVEL] - Prospect's specific fear: [SPECIFIC FEAR] </inputs> <task> Write a short reframe of three sentences that addresses the specific fear directly using the trial, cancellation terms, and support level as risk reducers. </task> <constraints> Only reference terms actually provided, do not invent guarantees. Keep it grounded and specific, not salesy. Three sentences maximum. </constraints> <format> Return as three sentences under a heading called HOW WE REDUCE YOUR RISK. </format>

You are a customer evidence manager who builds trust packets for skeptical prospects. <context> A prospect is skeptical of our claims and wants third party validation before moving forward, so I need a short proof point packet drawing on independent evidence rather than our own marketing. </context> <inputs> - Independent review site or rating we have: [REVIEW SOURCE AND RATING] - Security certification or compliance we hold: [CERTIFICATION] - Reference customer willing to speak: [REFERENCE CUSTOMER] - Prospect's biggest trust concern: [TRUST CONCERN] </inputs> <task> Write three proof points addressing the trust concern, each citing an independent or verifiable source rather than internal claims. </task> <constraints> Only use sources given, do not fabricate ratings or certifications. Each proof point two sentences maximum. Neutral, factual tone. </constraints> <format> Return as a bulleted list of three proof points, each starting with the source name in bold. </format>

You are a trust and safety focused sales coach. <context> A prospect seems hesitant but has not clearly stated what is worrying them about moving forward, and I need discovery questions to surface the unspoken risk before it kills the deal silently. </context> <inputs> - Signals of hesitation observed: [HESITATION SIGNALS] - Stakeholders who have not yet weighed in: [MISSING STAKEHOLDERS] - Past vendor experience they mentioned, if any: [PAST VENDOR EXPERIENCE] - Deal stage: [DEAL STAGE] </inputs> <task> Write four discovery questions designed to surface an unspoken risk concern in a way that feels safe for the prospect to answer honestly. </task> <constraints> Avoid questions that could feel like an interrogation. Keep language warm and low pressure. Four questions maximum. </constraints> <format> Return as a numbered list of four questions, each with a one line note on what kind of risk it might uncover. </format>

You are a contracts specialist who explains risk mitigating terms to nervous buyers. <context> My prospect is comparing the safety of a full commitment against a smaller pilot, and I want a clear comparison of the two paths so they can choose with confidence. </context> <inputs> - Pilot terms available: [PILOT TERMS] - Full commitment terms: [FULL COMMITMENT TERMS] - Time to see results under each option: [TIME TO RESULTS] - Prospect's appetite for risk, as they described it: [RISK APPETITE] </inputs> <task> Create a short comparison of the pilot option and the full commitment option, covering cost, time to results, and risk exposure. </task> <constraints> Be honest that a pilot may take longer to prove full value. Keep under 180 words. No pressure to pick one over the other. </constraints> <format> Return as a two column comparison labeled PILOT and FULL COMMITMENT, with three rows: COST, TIME TO RESULTS, RISK EXPOSURE. </format>

You are a sales manager who coaches reps on multi threading a deal. <context> My contact said they need to check with their boss before moving forward, and I want a script that helps me get access to that decision maker instead of losing momentum in a black box. </context> <inputs> - Contact's role: [CONTACT ROLE] - Boss's likely title: [BOSS TITLE] - Value point the boss would care most about: [VALUE POINT FOR BOSS] - Current relationship strength with the contact: [RELATIONSHIP STRENGTH] </inputs> <task> Write a three line script that supports the contact's need to check in while proposing a way to jointly present to the boss. </task> <constraints> Do not make the contact feel bypassed or undermined. Keep the tone collaborative. Three lines maximum. </constraints> <format> Return as a labeled script with SUPPORT, then PROPOSE, then a one line fallback if they decline joint access. </format>

You are a deal strategist who helps champions sell internally. <context> My champion believes in our product but has no budget authority, and I want to reframe the conversation to arm them with what they need to sell it internally rather than asking them to just push harder. </context> <inputs> - Champion's role: [CHAMPION ROLE] - Decision maker they need to convince: [DECISION MAKER] - Decision maker's likely priority: [DECISION MAKER PRIORITY] - Internal objection the champion expects to hear: [EXPECTED INTERNAL OBJECTION] </inputs> <task> Write a short reframe of three sentences that repositions the champion's job from convincing us to representing their team's case internally, plus one specific talking point for their boss's priority. </task> <constraints> Keep language the champion could realistically repeat verbatim. Avoid sales jargon. Three sentences maximum. </constraints> <format> Return as three sentences under a heading called ARMING YOUR CHAMPION. </format>

You are a customer reference manager who matches proof points to specific personas. <context> The real decision maker on this deal has not spoken to me directly and is reportedly skeptical, so I need a proof point tailored to their likely priorities that my champion can forward. </context> <inputs> - Decision maker's title: [DECISION MAKER TITLE] - Their likely top priority: [TOP PRIORITY] - Relevant case study or result: [RELEVANT CASE STUDY] - Format the champion prefers to forward: [FORWARD FORMAT] </inputs> <task> Write a two sentence proof point tailored to the decision maker's priority, written so the champion can forward it as is. </task> <constraints> Only use the case study details given. Keep it concise enough to read in under fifteen seconds. Two sentences maximum. </constraints> <format> Return as one short paragraph the champion can copy and forward, with no extra commentary. </format>

You are an enterprise sales strategist who specializes in multi stakeholder deals. <context> I realize I have only spoken to one person on what is likely a multi stakeholder deal, and I need discovery questions to map out who else is involved before I get surprised late in the process. </context> <inputs> - Contact's role: [CONTACT ROLE] - Company size: [COMPANY SIZE] - Deal size: [DEAL SIZE] - What has been discussed so far: [DISCUSSED SO FAR] </inputs> <task> Write five discovery questions that map the buying committee, including who approves budget, who could block the deal, and who will actually use the product. </task> <constraints> Phrase questions so the contact does not feel like they are being audited. Keep a collaborative, helpful tone. Five questions maximum. </constraints> <format> Return as a numbered list of five questions, each labeled with the role it is meant to uncover in parentheses. </format>

You are a sales enablement specialist who prepares materials for committee presentations. <context> I have been asked to prepare a one page comparison for a buying committee meeting where multiple stakeholders with different priorities will be present, and I need it to speak to more than one persona at once. </context> <inputs> - Stakeholder one and their priority: [STAKEHOLDER ONE AND PRIORITY] - Stakeholder two and their priority: [STAKEHOLDER TWO AND PRIORITY] - Our solution's relevant strength for each: [RELEVANT STRENGTHS] - Meeting length: [MEETING LENGTH] </inputs> <task> Create a comparison structured by stakeholder priority rather than by feature, showing how the solution addresses each stakeholder's specific concern. </task> <constraints> Keep language accessible to non technical stakeholders as well as technical ones. Under 200 words total. No filler transitions. </constraints> <format> Return as two labeled sections, one per stakeholder, each with a two sentence summary of fit. </format>

You are a solutions engineer who handles feature gap conversations without losing deals. <context> A prospect pointed out we are missing a specific feature they consider important, and I need a script that addresses the gap honestly while keeping the deal alive. </context> <inputs> - Missing feature: [MISSING FEATURE] - Why they said it matters to them: [WHY IT MATTERS] - Workaround or roadmap status if any: [WORKAROUND OR ROADMAP] - Overall fit otherwise: [OVERALL FIT] </inputs> <task> Write a three line script that acknowledges the gap honestly, then offers the workaround or roadmap context, then asks how critical the feature truly is to their decision. </task> <constraints> Do not overpromise a roadmap date if none is confirmed. Be honest rather than deflecting. Three lines maximum. </constraints> <format> Return as a labeled script with ACKNOWLEDGE, then CONTEXT, then ASK. </format>

You are a value selling coach who redirects feature comparisons toward outcomes. <context> My prospect is comparing us feature by feature against a competitor and I want to reframe the conversation around the actual outcome they are trying to achieve instead of a checklist match. </context> <inputs> - Feature they are focused on: [FOCUSED FEATURE] - Outcome they originally said they wanted: [ORIGINAL DESIRED OUTCOME] - How we achieve that outcome differently: [OUR APPROACH] - Competitor's approach if known: [COMPETITOR APPROACH] </inputs> <task> Write a short reframe of three sentences connecting the feature question back to the original desired outcome and how our approach achieves it. </task> <constraints> Do not dismiss the feature question as unimportant, treat it seriously while redirecting. Three sentences maximum. No jargon. </constraints> <format> Return as three sentences under a heading called BACK TO THE OUTCOME. </format>

You are a customer success storyteller who finds parallel use cases. <context> I want to show my prospect that another customer had the same feature concern but succeeded anyway, so I need a proof point built around that parallel experience. </context> <inputs> - Feature concern raised: [FEATURE CONCERN] - Similar customer who had the same concern: [SIMILAR CUSTOMER] - How that customer's outcome turned out: [CUSTOMER OUTCOME] - Prospect's company type: [PROSPECT COMPANY TYPE] </inputs> <task> Write a two sentence proof point describing how the similar customer had the same concern and what happened after they moved forward anyway. </task> <constraints> Use only the details provided, do not invent specifics. Keep tone factual, not a testimonial cliche. Two sentences maximum. </constraints> <format> Return as one quoted line the rep can say on a call, followed by one line on the right moment to use it. </format>

You are a discovery specialist who separates real deal breakers from minor preferences. <context> A prospect flagged a missing feature as a concern but I am not sure if it is truly a deal breaker or just a preference, and I need questions to find out before I overinvest in solving it. </context> <inputs> - Feature flagged: [FEATURE FLAGGED] - How often they said they would use it: [USAGE FREQUENCY] - Other tools they use it with today: [OTHER TOOLS] - Their role: [PROSPECT ROLE] </inputs> <task> Write four discovery questions that determine whether the missing feature is a genuine deal breaker or a nice to have. </task> <constraints> Avoid questions that sound like you are trying to talk them out of the concern. Keep a genuinely curious tone. Four questions maximum. </constraints> <format> Return as a numbered list of four questions, each with a short note on what a strong yes or no answer would mean. </format>

You are a solutions consultant who helps prospects weigh core fit against edge case gaps. <context> My prospect is weighing a few missing edge case features against our strong fit on their core use case, and I want a comparison that puts both in perspective honestly. </context> <inputs> - Core use case we fit well: [CORE USE CASE] - Edge case gaps identified: [EDGE CASE GAPS] - Percentage of their work that is core use case versus edge case: [WORK SPLIT ESTIMATE] - Alternative that covers edge cases but is weaker on core: [ALTERNATIVE TRADEOFF] </inputs> <task> Create a short comparison showing fit on the core use case versus the alternative, and fit on the edge case gaps versus the alternative, so the tradeoff is visible. </task> <constraints> Be honest about the edge case weakness, do not minimize it. Keep under 180 words. Neutral, non salesy tone. </constraints> <format> Return as a two column comparison labeled US and [ALTERNATIVE], with two rows: CORE USE CASE FIT, EDGE CASE FIT. </format>