Most product FAQs are reverse-engineered from the marketing page and quietly answer questions nobody is asking — meanwhile the same five tickets land in support every day. These prompts force you to mine the actual sources buyers reveal themselves in: 50 recent support tickets, 30 reviews, pre-purchase objection lists, and competitor Q&A pages. Each FAQ entry should preempt the next ticket or the next 3-star review. Includes a pruning audit for FAQ sections that have aged into clutter. Pair with the negative review response prompts — repeat complaints there are FAQ candidates here.
Best for
- Product detail pages
- Help center
- Pre-purchase objection handling
- Onboarding flows
- App Store / Play descriptions
1. Support-ticket → FAQ extractor
Below: 50 recent support tickets. Cluster them and extract the top 15 questions that recur. For each: the exact question, a 60-word answer, and the link to the doc / page that resolves it.
{paste tickets}2. Review-mining FAQ
Below: 30 product reviews. Find questions implied in reviews ("I wish I had known X", "why does it Y") and convert into a 10-Q FAQ. Each answer should preempt the same review next time.
{paste reviews}3. Pre-purchase objection FAQ
For {product at $X}, list the top 10 objections a hesitating buyer has BEFORE clicking buy. For each, write a 50-word FAQ answer that resolves it without overpromising.4. Competitor-comparison FAQ
My buyers compare us to {competitor A, B}. Write 8 FAQ-style answers to "Why you vs {competitor}?", each 60 words, each with 1 honest concession + 2 honest wins.5. Technical-spec FAQ
For {product}, write 12 FAQ entries for technical specs buyers care about (compatibility, dimensions, materials, warranty, certifications). Each ≤50 words, all spec questions in one place.6. Shipping / delivery FAQ
Write 10 FAQ entries for shipping & delivery: domestic / international ETA, carriers, tracking, taxes, returns, lost-package handling, damaged-on-arrival. Each ≤60 words. Specific to {your shipping setup}.7. Returns / refund FAQ
Write 10 FAQ entries for returns & refunds. Cover: window, condition required, who pays return shipping, restocking fees, partial returns, defective items, time to receive refund. ≤60 words each.8. Subscription / billing FAQ
For my subscription product at {price/freq}, write 12 FAQ entries: trial terms, cancellation, pause, upgrade/downgrade, refund policy, taxes, payment failures, multi-user. ≤60 words each.9. App-permissions FAQ
My app asks for {permissions list}. Write 6 FAQ entries explaining why each permission is needed and what we do NOT do with it. Build trust without legalese.10. Size / fit FAQ (apparel / accessories)
For my apparel product, write 8 FAQ entries for size and fit: how it runs, between-sizes advice, body-type guidance, fabric stretch, shrinkage. Include 2 customer-quote snippets where useful.11. FAQ pruning audit
Below is my current FAQ section. For each Q: (a) is this Q ever asked, (b) is the A current, (c) is it answering the right question. Cut anything that no one asks and rewrite answers that have aged.
{paste FAQ}12. Search-intent FAQ for SEO
For {product / category}, generate 10 FAQ entries that match what people actually Google. Use real long-tail queries. Each answer ≤80 words, with a clear definition first then specifics. Mark which qualify for FAQ schema.Common mistakes
- Made-up questions nobody actually asks, while the real top-5 tickets repeat daily
- Answers that recite the marketing page in slightly different words
- No source — FAQ is invented in a vacuum, not tied to tickets / reviews / analytics
- No update cycle — last reviewed 2024, answers reference policies that have since changed
- Hiding shipping / returns / cancellation behind vague answers to avoid commitment
- One generic FAQ across all variants instead of size-specific or region-specific entries
Related
- FAQ writing prompts
- Negative review response prompts
- Product description prompts
- Marketplace listing title prompts
- Landing page section prompts
- AI Product FAQ Generator: Anticipate Buyer Questions Before They Email
Tags: #Prompt #E-commerce #E-commerce #FAQ