faq-objection-crusher（常见问题异议粉碎机）

FAQ Objection Crusher

Purpose

This skill converts buyer doubts and objections into clear, honest FAQ answers, reassurance copy, and sales enablement snippets. Instead of dodging concerns with marketing spin, it builds trust by acknowledging real objections and addressing them with facts, policies, and transparency. Works for product pages, help centers, sales scripts, customer support responses, and checkout trust sections.

Triggers

• "Create an FAQ for my product page"
• "Turn customer objections into FAQ answers"
• "Write reassurance copy for checkout"
• "Build objection-handling copy for sales"
• "Draft trust-building FAQ for this product"
• "Create customer question answers"

Workflow

1. Objection collection — Gather product details, store policies (shipping, returns, warranty, refunds), known customer concerns (from reviews, support tickets, sales calls), and category-specific trust barriers (fit anxiety, quality skepticism, delivery worries).
2. Objection mapping — Group objections by buying stage:

- Consideration objections — "Is this worth the price?", "How does it compare to X?" - Fit/suitability objections — "Will this work for my situation?", "Is it the right size/type?" - Trust objections — "Is this brand legit?", "Are the reviews real?", "What if it breaks?" - Transaction objections — "How's the return policy?", "Is shipping fast?", "Is payment secure?"

1. Answer drafting — For each objection, write an answer that: (a) acknowledges the concern without defensiveness, (b) provides the factual answer, (c) includes proof or policy citation where applicable, (d) adds a caveat if the answer has limitations.
2. Trust cue integration — Where appropriate, weave in trust elements: exact policy language, certification names, warranty terms, shipping timelines with carriers, return windows with conditions.
3. Short snippet creation — Distill each FAQ into a 1–2 sentence "reassurance snippet" suitable for product page badges, checkout sidebars, or sales enablement cards.
4. Escalation notes — Flag objections where the honest answer reveals a product limitation or policy gap that marketing should address at the product or policy level, not just the copy level.

Prompt Templates

1. FAQ Generator (faq_generate)

Purpose: Generate a complete product FAQ from product details and policies.

Input:

• ${product_name} — Product name
• ${category} — Product category
• ${product_details} — Key specs, materials, use cases
• ${policies} — Shipping, returns, warranty, refund terms
• ${known_concerns} — Common customer questions or complaints
• ${faq_count} — Number of FAQ items to generate (default 6–10)

Output: FAQ section with objection-stage labels, honest answers, policy citations, and short snippets.

2. Objection Map Builder (objection_map)

Purpose: Build a structured objection map before writing answers.

Input:

• ${product_name} — Product name
• ${category} — Product category
• ${price_point} — Budget, mid-range, premium
• ${customer_feedback} — (Optional) known concerns from reviews/support
• ${competitive_context} — (Optional) known comparisons shoppers make

Output: Objection matrix grouped by buying stage, with severity scores (how likely to block purchase) and answerability scores (how well can the brand address this?).

3. Reassurance Snippet Generator (reassurance_snippets)

Purpose: Create short trust-building snippets for product page badges and checkout.

Input:

• ${faq_items} — FAQ item list
• ${format} — Badge (1 line), sidebar (1–2 sentences), or sales card (2–3 sentences)
• ${placement} — Product page, checkout, support page, or sales script

Output: Formatted reassurance snippets mapped to placement locations.

4. Policy-to-Copy Translator (policy_to_copy)

Purpose: Translate formal policy language into customer-friendly copy.

Input:

• ${policy_text} — Raw policy text (shipping, returns, warranty)
• ${tone} — Friendly, professional, or minimal

Output: Customer-friendly version preserving all legal terms, with a "policy essentials" summary.

Output Format

## FAQ & Objection Handler: [Product Name]
**Category:** [Category] | **Policies:** [Key policy highlights]

### Objection Map
| Objection | Buying Stage | Severity | Answerability | Status |
|---|---|---|---|---|
| "Is it worth the price?" | Consideration | High | High | Addressable |
| "What if it doesn't fit?" | Fit/Suitability | High | High | Policy-backed |
| "Are reviews real?" | Trust | Medium | Medium | Partial |

### FAQ Section

**Q: "[Objection/Question]"**
*Objection Stage: [Stage]* | *Severity: [1-5]*

**A:** [Honest answer — acknowledge, inform, prove, caveat]

> 🔒 Policy: [Exact policy citation]
> 💬 Reassurance snippet: "[1-2 sentence version]"

---

**Q: "[Next question]"**
...

### Quick Trust Snippets (for product page badges)
- 🚚 "[Shipping reassurance]" — *placement: below Add to Cart*
- 🔄 "[Returns reassurance]" — *placement: product page footer*
- ⭐ "[Quality reassurance]" — *placement: above reviews*

### Escalation Notes
- **Policy gap:** [Objection] is not fully addressable through copy alone — consider [policy/product change]
- **Limitation acknowledged:** [Objection] has an honest limitation — the answer addresses it transparently

Safety Rules

• NEVER hide, minimize, or misrepresent policy limitations (return windows, restocking fees, warranty exclusions)
• NEVER promise outcomes that the product or policy cannot deliver — "fits all sizes" when size chart says otherwise is prohibited
• ALWAYS preserve exact policy language for legally binding terms while making surrounding copy more readable
• ALWAYS flag any FAQ answer that makes a factual claim without backup — "made with organic cotton" needs certification proof
• NEVER create fake customer concerns just to answer them with marketing spin
• ALWAYS include a "when to contact support" escalation path for edge cases

Examples

Example 1: Skincare Product (Premium, First-Time Buyer Concerns)

Input: Product="Vitamin C Brightening Serum", Policies="30-day return on unopened items, free shipping over $50, 12-month shelf life after opening", Known Concerns="Does it cause irritation? How long to see results? Is it worth $45? Can I use it with retinol?"

Output: FAQ addressing each concern honestly: "Some users with sensitive skin may experience mild tingling initially — we recommend patch testing. Visible brightening typically takes 4–8 weeks of consistent use. Our serum uses 15% L-ascorbic acid stabilized with vitamin E and ferulic acid — higher concentration than many drugstore options. Yes, but alternate days when starting." Policy citations for all claims. Reassurance snippet: "Patch-test friendly — 30-day return on unopened items."

Example 2: Kitchen Gadget (Budget, Practical Concerns)

Input: Product="Silicone Baking Mat Set of 3", Policies="Free returns within 60 days, 1-year warranty against defects", Known Concerns="Does food stick? Is it really dishwasher safe? Will it warp in high heat? Is silicone safe?"

Output: FAQ with direct answers: "Food may stick if you use cooking spray (builds up residue) — use as-is or with light oil. Yes, top-rack dishwasher safe, but hand-washing extends life. Rated to 480°F — within normal baking temperatures, no warping. Our mats are food-grade silicone, BPA-free, and FDA-compliant." Reassurance snippet: "Oven-safe to 480°F, dishwasher-friendly, BPA-free."

Related Skills

• listing-bullet-booster — For the listing copy these FAQs support
• marketplace-description-writer — For the product page where FAQs live
• customer-persona-copy-map — For mapping objections to specific buyer personas