Few-Shot Framework: Objection Handling Replies
A few-shot reply framework for handling objections without sounding defensive, robotic, or aggressively salesy.
Use cases
Sales & Outreach, Customer Support
Platforms
Claude, GPT, Gemini, Model-Agnostic
Jump to a section
The resource
Copy and adapt. Do not paste blind.
Task: write a reply to the objection in the same style as the examples.
Principles:
- Acknowledge the concern directly.
- Do not argue with the prospect.
- Reduce friction before adding persuasion.
- Keep the reply short.
Example A
Objection: "This feels too expensive for us right now."
Reply style: Calm, commercial, non-pushy
Reply: That makes sense. If budget is the constraint, the useful question is whether the problem is expensive enough to leave untouched. If helpful, I can outline the lightest version that still gets the result.
Example B
Objection: "We already have a tool for this."
Reply style: Respectful, curious, low-ego
Reply: Completely fair. In that case the useful thing to understand is whether the gap is the tool itself or how the workflow is being run around it. If it helps, I can show where teams usually hit that limit.
Now write the reply for the new objection using the same standard.When to Use This
Use this when you need short written responses to common objections in email, LinkedIn, support-assisted sales, or follow-up messages after calls.
It works best when the objection category is known but the tone still needs to sound measured and human.
Why It Works
Few-shot works well here because tone and pacing matter as much as logic. Showing the model how to acknowledge, reframe, and lower friction is more reliable than describing those ideas abstractly.
The examples are deliberately short. Long objection-handling examples often teach the model to overtalk, which usually makes the reply worse.
How to Customise
Replace the examples with your own winning replies if you already know how your team handles objections well.
You can also create separate variants for pricing, timing, security, and trust objections if you want tighter control.
Limitations
This should not be used for regulated, contractual, or sensitive objections where legal precision matters.
It also will not fix a weak offer. Sometimes the objection is valid and the right answer is not “write a better reply.”
Model Notes
Claude and GPT both handle this format well if the examples are tight.
Gemini benefits from an explicit word limit. Model-agnostic overall, but example quality is everything.
Related Resources
Browse PromptsSystem Prompt: Sales Call Summariser
A structured sales summarisation prompt for extracting pain points, objections, buying signals, next steps, and CRM-ready notes from call transcripts.
Sales & Outreach · Operations & Workflow
Skill: Cold Outreach Composer
A sales-oriented writing skill for concise outbound emails and LinkedIn messages that avoid the usual AI sludge.
Sales & Outreach · Marketing & Growth
Skill: Customer Support Triage
A reusable support triage skill for classifying requests, assessing urgency, gathering missing context, and preparing a safe first reply.
Customer Support · Operations & Workflow