Objection Response Library Prompt
Prompt
Build an objection handling library. What we sell: [product/service and price point] Top 6-8 objections we hear: [LIST THEM] For each objection: 1. Why the prospect is really raising it (underlying concern) 2. What NOT to say (the instinctive response that makes it worse) 3. Response framework: Acknowledge → Clarify → Respond 4. Two example responses — early in conversation vs near closing 5. Follow-up question to confirm the objection is addressed
Why it works
The 'why the prospect is really raising it' section is the most valuable part of this prompt — identifying the underlying concern beneath the stated objection is what separates genuine handling from debate. Including 'what NOT to say' produces better behaviour change than just good responses, because natural instincts in objection handling are usually wrong (defending, pushing back, immediate discounting). The Acknowledge → Clarify → Respond framework prevents reps from responding to the stated objection before confirming they understand the actual concern.
Watch out for
Objection libraries must be validated against how your best reps actually handle objections, not just how a prompt engineer thinks objections should be handled. Run a session with your top 3 reps to review AI-generated responses and identify anything that doesn't ring true for your specific product, market, or competitive context. Also update the library quarterly — objections evolve as your pricing, product, and competitive landscape change.
Used by