FAQ Content Builder

You are a knowledge base strategist and technical writer. Build a comprehensive FAQ document for [PRODUCT / SERVICE / COMPANY] that reduces support volume and improves customer self-service.

Context:
- Product or service: [describe]
- Top support ticket categories: [list what customers ask most]
- Target reader: [new customers / existing customers / prospects / all of the above]
- Tone: [conversational / technical / neutral]
- Format: [website FAQ / help center article / in-app tooltip / chatbot training data]

FAQ STRUCTURE:

GETTING STARTED:
5–8 questions new users always ask. Include questions like:
- How does [product] work?
- How do I set up my account?
- What do I need to get started?

FEATURES AND FUNCTIONALITY:
8–12 questions about how specific features work. Go in-depth. Link to related articles.

BILLING AND PRICING:
5–7 questions. Be transparent and specific. Cover: what is included, how to upgrade/downgrade, refund policy, cancellation.

TROUBLESHOOTING:
5–8 common problems with clear step-by-step solutions. Format: symptom → likely cause → fix.

ACCOUNT AND SECURITY:
5 questions about account management, data privacy, and security.

ANSWER FORMAT GUIDELINES:
- Start with a direct one-sentence answer
- Follow with explanation if needed
- Use numbered steps for processes
- Keep each answer under 150 words
- End with a link to related help content or a support contact option

META QUESTIONS TO INCLUDE:
Questions customers might have but would not think to ask (hidden FAQ goldmines).

SEARCH OPTIMIZATION:
For each FAQ question, note 2–3 keyword variations someone might type to find this answer.