FAQ Generator Prompt

What it does

Generates an FAQ section that answers what customers really want to know — including the questions you'd rather avoid. A good FAQ does triple duty: it removes purchase friction (answering the price and risk questions that stall a sale), it deflects support tickets (so people don't email what the page could've answered), and it ranks (FAQ content matches the question-shaped searches people type). This prompt anticipates the real questions, not just the convenient ones, and answers them clearly.

Generate an FAQ for the product/service below.

Include questions across these types:
- Practical (how it works, getting started, what's included).
- Pricing & plans (cost, what's free, billing, cancellation) — don't dodge these.
- Risk & objections (refunds, guarantees, "what if it doesn't work for me," is my data safe).
- Comparison (how this differs from alternatives or doing nothing).
- Logistics (delivery, support, requirements, compatibility).

For each:
- Write the question the way a customer would actually phrase it (natural, not corporate).
- Answer it clearly and honestly in 2-4 sentences. Address the real concern, don't deflect.
- Where it helps, end an answer with a soft next step.

Rules:
- Anticipate the awkward questions; answering them builds trust.
- Plain language, no jargon.
- Be honest — don't oversell or hide limitations.
- Give me 10-15 questions, grouped by type.

Product/service details:
- What it is: [description]
- Who it's for: [audience]
- Price/model: [pricing]
- Common concerns or objections I hear: [list any you know]
- Key differentiator: [what sets it apart]

How to use it

Feed it the objections you already hear — from sales calls, support emails, that one question every prospect asks. Those are your highest-value entries. The output groups questions by type so you can see if you're avoiding a whole category (pricing FAQs are the most commonly, and most damagingly, omitted). Edit the answers to match your real policies exactly; an FAQ that promises a 30-day refund you don't offer creates a worse problem than no FAQ.

For SEO, phrasing questions the way people actually search ("how much does X cost" not "pricing information") helps you match those queries, and the format is eligible for FAQ rich results.

Example output

Pricing: "How much does it cost?" → "Plans start at $12/month, billed monthly or annually (two months free if you pay yearly). There's a free tier for up to 5 invoices a month, so you can try it before paying anything."

Risk: "What if it doesn't work for my business?" → "You can cancel anytime, and we offer a 30-day refund — no forms, just email us. Most people know within the first week whether it fits."

Variations

Support deflection focus: Add "Prioritize the questions that generate the most support tickets, and write answers thorough enough to fully resolve them."

Schema-ready: Add "Format the output as question/answer pairs I can drop into FAQPage schema markup."

Sales-page FAQ: Add "This FAQ sits at the bottom of a sales page. Weight it toward overcoming the final objections before purchase."

Onboarding FAQ: Add "These are for new users after they sign up — getting-started and 'how do I' questions, not pre-sale ones."

Common pitfalls

Dodging price. Omitting the cost question doesn't keep your options open; it frustrates buyers and pushes them away. Answer it.

Corporate phrasing. "What are your service parameters?" isn't how anyone asks. Write questions in the customer's words so they match real searches and feel human.

Answers that don't answer. A non-answer ("contact us for details") wastes the entry. If you can answer it, do; the point is to resolve, not redirect.

Who uses this prompt

Small-business owners building a product or sales page, support teams cutting repetitive tickets, marketers chasing FAQ rich results, and founders who keep answering the same five questions over email. It turns the questions you already get into a page that answers them once.