Objection Handling Copy
Answer the objection buyers actually have, at the point in the page where they have it.
Separates stated objections from the real ones behind them, writes a short acknowledging answer for each in buyer language, places it where the doubt occurs, and names the objections copy cannot fix.
Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are a conversion copywriter handling buyer objections.
Context:
- Offer and price: {{offer}}
- Objections you hear, in the words people use: {{stated_objections}}
- Sales call notes, churn reasons or support themes: {{raw_input}}
- Proof, guarantee and policies: {{proof}}
- Where the copy will live, page section or email sequence: {{placement}}
Task: Return:
1. A list of objections split into STATED and UNDERLYING — the polite version and the real one behind it
2. For each objection: its type (price, trust, timing, fit, effort, authority), whether copy can answer it, and how often it likely occurs
3. An answer for each, under 60 words, in the buyer own language, leading with acknowledgement not rebuttal
4. The exact placement for each answer, and the reason the doubt appears there
5. Objections copy cannot fix, with what would fix them instead: pricing, product, proof or targeting
6. Three objections worth pre-empting before they are raised, and three better left unmentioned
Rules:
- Never answer an objection by denying it.
- Do not bundle answers into a generic FAQ, place each where the doubt occurs.
- Where the guarantee is the answer, state it precisely, never vaguely.
- If an objection is legitimate, say the product is not a fit for that buyer.
- Label underlying objections as hypotheses unless supported by explicit buyer evidence.
- Mark frequency and revenue impact unknown when counts or deal values are absent.
- Flag missing proof or policy details as publication blockers; never fill them in.
Finish with: the objection costing the most revenue right now, and the evidence for that.Estimated results
Editor's note
Why this prompt matters
Objection handling is usually done as an FAQ block at the bottom of a page, which is the one place a hesitant reader has already left. It is also usually done from the polite version of the objection rather than the real one: too expensive almost never means the number is wrong, it means the value case has not landed. This prompt splits stated from underlying, places each answer where the doubt actually appears, and — unusually — names the objections that copy cannot solve, so you stop rewriting a page whose real problem is pricing or targeting.
Anatomy
Prompt engineering breakdown
Role
Context
Goal
Constraints
Output format
What you'll get
Expected output
Scenario and supplied evidence
This illustrative example concerns a fixed-fee project-setup workshop for small teams. The buyer receives one facilitated session and a written setup plan; implementation is excluded. The supplied policy allows a full refund before kickoff, but none once kickoff starts.
Illustrative sales notes contain: “That’s a lot for one session,” “We’re already stretched,” “Can we see what we get?” and “We need someone to do the setup.” These are example inputs, not findings from actual customers. No objection counts or lost-deal values were supplied.
Stated versus underlying objections
Underlying interpretations are hypotheses, not hidden motives established as fact.
| Stated objection | Possible underlying objection | Type | Can copy answer it? | |---|---|---|---| | “A lot for one session” | I cannot judge the deliverable’s value. | Price | Partly; needs a sample plan. | | “We’re already stretched” | This creates work we cannot absorb. | Effort | Only if workload is documented. | | “Can we see what we get?” | I cannot assess quality before paying. | Trust | Yes, with representative proof. | | “Do the setup” | We need implementation, not guidance. | Fit | No; the offer excludes it. |
Frequency is unknown for every row. Count distinct buying conversations before assigning prevalence; repeated mentions within one call are not separate buyers.
Answers and exact placements
Price — immediately beside the fee: “It makes sense to question the price of one session. You receive a facilitated workshop and a written setup plan; implementation is separate.” This is where the buyer compares cost with scope.
Effort — beside the participation requirements: “If your team is already stretched, another project may not fit. This workshop gives you a plan; your team still handles implementation.” Add verified preparation and implementation requirements before publishing.
Trust — directly above the booking button: “You want to see what you’re buying. Review a representative setup plan before booking.” Publish this only after adding an approved sample.
Fit — inside the deliverables section: “If you need someone to complete the setup, this workshop is not a fit.” Scope, not persuasion, resolves this doubt.
Pre-empt, omit, and escalate
Pre-empt deliverable scope, implementation responsibility, and refund timing. State: “Full refund before kickoff; no refund once kickoff starts.”
Leave security, procurement approval, and subscription cancellation unmentioned unless buyer evidence raises them.
Implementation demand needs a different service or targeting. Missing samples need proof production.
Revenue priority
Investigate scope mismatch first. Its supporting quote requests an excluded service. Without lost-deal values and objection counts, the highest-revenue objection remains unproven.
Under the hood
Why this prompt works
Acknowledgement before rebuttal is the mechanism that makes short answers work: a reader whose doubt is named will read the next sentence, while a reader whose doubt is denied stops trusting the page. Placement then does the rest, because an answer arriving after the moment of doubt is the same as no answer. The leave-unmentioned list is the part that saves money — raising an objection the reader did not have introduces a doubt you then have to spend copy resolving.
Model fit
Best AI models for this prompt
Claude
Best here. Strongest at surfacing the underlying objection and the most willing to say the product is not a fit.
ChatGPT
Reliable structure and good at mapping answers to page placements.
Gemini
Useful with large volumes of pasted sales call notes or support tickets.
When to use
- After session research reveals hesitation beside pricing or booking.
- Before outlining a sales page or nurture sequence.
- When sales calls repeatedly revisit the same questions.
- When changed terms make existing objection answers inaccurate.
When not to use
- Without buyer quotes or research; interview buyers first.
- When product mismatch requires an offer decision.
- For support documentation requiring complete troubleshooting instructions.
- When refund wording needs legal or policy-owner approval.
- To rank revenue impact without CRM evidence.
Get more from it
Pro tips
- 1
Keep raw buyer phrasing; attach the page section or sales stage where each doubt appeared.
- 2
Treat “too expensive” as ambiguous: test budget limits against uncertainty about value, rather than assuming either.
- 3
Respect the unmentioned list; require buyer evidence before introducing another risk.
- 4
Place answers beside the triggering price, requirement, or commitment—not merely somewhere above the footer.
- 5
Supply exact guarantee exclusions and deadlines; flag missing policy details instead of smoothing them over.
- 6
For a second pass, ask which inferred motives lack evidence and which answers promise more than the supplied proof supports.
Don't ship this
Common mistakes
✗ Answering the polite objection instead of the real one.
Fix — Use the stated-versus-underlying split as the working list.
✗ Burying every answer in a bottom-of-page FAQ.
Fix — Place each answer where the doubt occurs.
✗ Denying a legitimate objection.
Fix — Acknowledge it, and say plainly when the product is not a fit.
People also ask
Frequently asked questions
Q.What is the difference between a stated and an underlying objection?
The stated one is polite; the underlying one is real. Too expensive usually means the value case has not landed, and answering the polite version with a discount solves a problem the buyer did not have.
Q.Why not put all the answers in an FAQ?
Because the reader who has the doubt has usually already left by then. Each answer belongs at the point in the page or sequence where the hesitation appears, which is what the placement output gives you.
Q.What if an objection is genuinely correct?
Say so. The prompt returns objections copy cannot fix along with what would fix them — pricing, product, proof or targeting — and telling a poor-fit buyer that early costs less than a refund later.