Objection Handler

Price Objections

• Surface concern: Cost
• Hidden concern: Value uncertainty, budget priorities, risk aversion
• Response focus: ROI demonstration, payment flexibility, comparative value

Trust Objections

• Surface concern: Credibility
• Hidden concern: Fear of disappointment, past negative experiences
• Response focus: Social proof, guarantees, transparency

Timing Objections

• Surface concern: Schedule
• Hidden concern: Procrastination, uncertainty, competing priorities
• Response focus: Urgency creation, consequence clarity, easy next steps

Technical Objections

• Surface concern: Complexity
• Hidden concern: Fear of failure, tech confidence, support availability
• Response focus: Simplicity proof, onboarding support, success resources

Comparison Objections

• Surface concern: Alternatives
• Hidden concern: Decision paralysis, feature confusion
• Response focus: Differentiation, unique mechanism, specific outcomes

Vietnamese Market Objections

• "Co phai lua dao khong?" (Is this a scam?) — #1 VN objection; address with social proof, video testimonials, business registration proof, and money-back guarantee
• "Sao dat vay?" (Why so expensive?) — Compare to value received and cost of NOT solving the problem, not competitor price
• "De suy nghi them" (Let me think about it) — Create urgency with limited-time bonus or expiring discount for first N buyers

2. Response Framework Overview

Strategic Response Elements

• Acknowledge the concern (validation)
• Uncover hidden objection (clarification)
• Reframe perspective (education)
• Provide evidence (proof)
• Redirect to action (closing)

Multi-Touch Approach

• Preemptive handling (sales page content)
• Direct response (email/message replies)
• FAQ documentation (self-service answers)
• Follow-up sequences (persistent concerns)

3. FAQ Builder Workflow

Research Phase

• Collect actual customer questions from emails, support tickets, comments
• Identify patterns in hesitation points during sales conversations
• Analyze competitor FAQ sections for market-standard concerns
• Review product analytics for drop-off points

Organization Phase

• Group objections by category (price, trust, timing, technical, comparison)
• Prioritize by frequency and impact on conversion
• Sequence from general to specific
• Balance concerns with excitement-building

Writing Phase

• Frame questions in customer language (not company jargon)
• Structure answers with acknowledge-resolve-redirect pattern
• Include proof points (data, testimonials, guarantees)
• End with clear next step or CTA redirect

Optimization Phase

• Test different answer formats (brief vs detailed)
• Monitor which FAQs get most engagement
• Update based on new objections that emerge
• Refresh proof points with current data

Reference Files

Detailed frameworks and templates in /references/:

• objection-classification-framework.md: Objections organized by category with hidden concerns and response directions
• objection-response-library.md: Complete frameworks for handling objections with examples and response templates

Best Practices

Do's

• Address objections preemptively in sales copy
• Use customer language, not marketing speak
• Provide specific proof points, not vague claims
• Make answers scannable with bold key phrases
• Test different response approaches for effectiveness
• Update objection library regularly with new concerns
• Balance concern resolution with enthusiasm building

Don'ts

• Dismiss or minimize legitimate concerns
• Use defensive or argumentative tone
• Rely solely on generic answers
• Ignore emotional drivers behind logical objections
• Create FAQ sections that raise new concerns
• Use company jargon or technical terminology
• Leave objections unresolved without clear next steps

Integration with Other Skills

Works well with:

• copywriting: Integrate objection handling into sales page copy
• content-creation: Build objection-addressing content (blog posts, videos)
• lead-magnet-builder: Create objection-handling email sequences
• market-research: Analyze customer feedback for emerging objections

Output Format

When handling objections, provide:

• Objection category identified
• Hidden concern analysis
• Recommended framework for response
• Complete response with acknowledge-reframe-resolve-redirect structure
• Proof points to include (testimonial suggestions, data points, guarantees)
• Follow-up approach if needed

Success Metrics

Track objection handling effectiveness through:

• FAQ section engagement (time on page, scroll depth)
• Conversion rate before/after FAQ optimization
• Support ticket volume reduction
• Email reply rates to objection-handling messages
• Sales call close rates when frameworks applied
• Customer testimonials mentioning resolved concerns

Notes

Effective objection handling requires:

• Genuine empathy for customer concerns
• Confidence in product value proposition
• Flexibility to adapt frameworks to context
• Continuous learning from customer interactions
• Balance between addressing concerns and maintaining momentum

The goal is not to "overcome" objections but to resolve genuine concerns that prevent customers from getting transformation they need.