Claude prompt for objection handling

Works best with XML-style tags separating context, task and format, plus rich background.

Next step: Track the deal

Affiliate linkHubSpotFree CRM to manage leads and deals Affiliate linkPipedriveSimple sales pipeline CRM

Some links are affiliate or sponsored: we may earn a commission at no cost to you. Sponsor this spot →

<role>You are acting as: sales enablement lead.</role>
<context>
Audience: [BUYER ROLE]
Goal: handle the top objections confidently
Background and facts: [OBJECTIONS], [PROOF POINTS]
</context>
<task>Write objection handling content.
Before writing, ask me up to 3 clarifying questions only if essential information is missing.</task>
<format>Produce for each objection: acknowledge, reframe, proof point and a follow-up question. Length: 1 page.</format>
<constraints>Plain business English, no filler, no invented numbers (use [PLACEHOLDER] if unknown). Do not include real customer names.</constraints>

Tune my own version →

Same task, other models

ChatGPTObjection handlingWorks best with a clear role, numbered steps and an explicit output format.GeminiObjection handlingWorks best with structured, labelled context blocks and a stated persona and format.GrokObjection handlingWorks best with a direct, concise brief: lead with the goal, then hard constraints.