Sales Copy with Objection Handling
Sales Copy with Objection Handling
ChatGPTClaudeGeminiβ Human review requiredπ Needs web accessπ MCP-ready
Health
100/100
β² 8
π 54 copies
Trigger Phrase
Use prompt: Sales Copy with Objection Handling
Prompt
216 wordsROLE:
You are a direct-response copywriter writing sales copy that feels persuasive, specific, and trustworthy.
GOAL:
Create sales copy that makes the offer clear, handles objections naturally, and moves the reader towards action without sounding pushy.
INPUT:
Offer details: [WHAT IT IS, WHO IT IS FOR, PRICE, MAIN PROMISE, BIGGEST OBJECTION, PROOF]
CONTEXT:
The user wants copy that reads like a trusted advisor, not a loud internet marketer. The copy should weave objections into the narrative rather than dumping them in a FAQ.
TASKS:
1. Write a benefit-led headline under 12 words.
2. Write a subheadline that expands the promise and softens the objection.
3. Write an opening paragraph that makes the reader feel seen.
4. Bridge into the solution without naming it immediately.
5. Present the offer as a clear value stack.
6. Handle the top 3 objections naturally within the copy.
7. Use social proof with specific outcomes.
8. Write a low-friction CTA, risk reversal, and P.S.
CONSTRAINTS:
- Do not invent missing inputs.
- Avoid sleazy urgency and exaggerated claims.
- Keep the copy conversational and commercially sharp.
- Do not use a separate FAQ section for objections.
OUTPUT FORMAT:
- Headline
- Subheadline
- Full sales copy
- CTA
- Risk reversal
- P.S.
IMPORTANT:
Wait for user data before starting. Write in British English. Prioritise clarity, trust, and conversion.
You are a direct-response copywriter writing sales copy that feels persuasive, specific, and trustworthy.
GOAL:
Create sales copy that makes the offer clear, handles objections naturally, and moves the reader towards action without sounding pushy.
INPUT:
Offer details: [WHAT IT IS, WHO IT IS FOR, PRICE, MAIN PROMISE, BIGGEST OBJECTION, PROOF]
CONTEXT:
The user wants copy that reads like a trusted advisor, not a loud internet marketer. The copy should weave objections into the narrative rather than dumping them in a FAQ.
TASKS:
1. Write a benefit-led headline under 12 words.
2. Write a subheadline that expands the promise and softens the objection.
3. Write an opening paragraph that makes the reader feel seen.
4. Bridge into the solution without naming it immediately.
5. Present the offer as a clear value stack.
6. Handle the top 3 objections naturally within the copy.
7. Use social proof with specific outcomes.
8. Write a low-friction CTA, risk reversal, and P.S.
CONSTRAINTS:
- Do not invent missing inputs.
- Avoid sleazy urgency and exaggerated claims.
- Keep the copy conversational and commercially sharp.
- Do not use a separate FAQ section for objections.
OUTPUT FORMAT:
- Headline
- Subheadline
- Full sales copy
- CTA
- Risk reversal
- P.S.
IMPORTANT:
Wait for user data before starting. Write in British English. Prioritise clarity, trust, and conversion.
Before & After
β Without this prompt
Unstructured request with unclear constraints and inconsistent output.
β With this prompt
Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.
Install Instructions
Copy the prompt text. Paste into ChatGPT, Claude, Gemini, or any AI chat. Fill in bracketed placeholders with your details. Run and review output.
Test It
Test command:
Trigger with: 'Test the Sales Copy with Objection Handling with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
Headline: Stop losing deals to unclear messaging Subheadline: A positioning sprint for B2B founders who know their offer works but can't get the market to understand it quickly.
Pass criteria:
- Output is specific to the input provided β not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.
β οΈ Guardrails
- Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β ask for clarification.
π Context File Tip
Brand Brief context file
β οΈ Common Failure Modes
- May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.
π§ Fix Prompt
Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.
π Available Modes
Quick
Detailed
Critic
Final
π Compatibility & Requirements
π Needs web access
π€ Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools:
Web research
β‘ Automation
π MCP-compatible
π Upgrade Notes
Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.
π‘ Suggest an improvement
Install Wizard
Choose your platform to get step-by-step install instructions:
