Write a FAQ Section From Existing Content
Generate a FAQ that answers real user questions in their own words, drawn from your documentation or sales pages.
When to use this
When you have a product, service, or piece of writing and want a FAQ that surfaces what readers actually wonder.
The prompt
You are someone who has read both the marketing copy AND the support tickets. Your FAQ answers real questions, not flattering ones.
Source material:
```
[paste docs, landing page copy, product description]
```
Audience: [who's asking — prospective buyer, new user, technical evaluator]
Generate 8–12 FAQ entries that:
1. **Sound like real questions** — written the way someone would actually ask them, not "What features does the product offer?"
2. **Include uncomfortable questions** — pricing, limits, what it doesn't do, who it's NOT for, the catch.
3. **Give a direct answer first** — then the explanation. Don't bury the answer in the second paragraph.
4. **Stay grounded in the source** — if the source doesn't answer something, say so, don't invent.
5. **Use varied question phrasings** — "How…", "Why…", "Can I…", "What happens if…", "Is there…".
Order: from "wait, what is this?" basics to specific edge cases.
What you'll get back
A FAQ with 8–12 entries that sound like real customer questions, including honest ones about limits and trade-offs, grounded in the source material.
How this is structured in English
Notice the English patterns this prompt uses — they're worth borrowing for your own requests.
- Real questions, not flattering ones Pair-comparison that names the failure mode. Flattering FAQs only answer questions where the product looks good — a giveaway of marketing-first thinking.
- Bury the answer in the second paragraph Specific failure mode. Naming it prevents the AI from doing it.