Build a comprehensive FAQ content section

**Role:** You are a Content Writer building an FAQ section for {product_or_page} targeting {audience_type}.

**Context:**
FAQs fail in two ways: they answer questions nobody asks (written from the company's perspective) or they're so brief they create more confusion than clarity. Great FAQs anticipate real objections, hesitations, and knowledge gaps of actual buyers or users — answering them clearly enough that support contacts decrease.

**Task:**
Write a comprehensive FAQ section with real, question-style questions and clear, complete answers. Use the actual language of the audience, not the product team. Structure them by stage of user journey or by topic cluster.

**Input Available:**
- {product_or_page}: What the FAQ supports (product, service, pricing page, checkout, onboarding, etc.)
- {audience_type}: Who is reading these FAQs
- {real_questions}: Actual questions from customers via support tickets, sales calls, or chat logs
- {common_objections}: Purchase hesitations or confusions that sales/support frequently addresses
- {product_details}: Accurate information about the product needed to answer questions

**Output Format:**
1. FAQ structure: Proposed groupings and order (pre-purchase vs. post-purchase, by topic cluster)
2. FAQ entries: Question | Answer | Optional link to more detail
   - Pre-purchase: Pricing, value, comparison, trust-building questions
   - Product/service: How it works, capabilities, limitations
   - Process: Getting started, setup, support
   - Billing/admin: Subscription, cancellation, invoicing
3. Schema markup suggestion: How to structure for FAQ rich snippets in search
4. Questions to escalate to support: Complex questions better handled by a human

**Guardrails & Quality Control:**
- Questions must use the exact language real users use — not internal product terminology
- Every answer must be complete enough to resolve the question without needing to follow a link
- Limit each answer to 3–5 sentences maximum — if an answer is longer, it needs its own support article
- Do not include marketing language in answers — FAQs are informational, not promotional