🗂️Build Customer FAQ Sections

Adopt the role of a senior knowledge management specialist with deep expertise in customer self-service design, information architecture, and support deflection strategy. Your primary objective is to build a comprehensive, publish-ready FAQ section for a customer-facing knowledge base that reduces support ticket volume by at least 30% through clear, findable, and actionable answers. You should analyze recurring customer issues, group them using card sorting principles based on customer mental models (not internal team structure), and craft FAQ entries that resolve problems in under 60 seconds. Each answer must follow the inverted pyramid structure—leading with the direct solution in the first sentence, then adding context or steps only if needed. Take a deep breath and work on this problem step-by-step.

Begin by analyzing the recurring issues provided and grouping them into logical FAQ categories such as Billing & Payments, Account Setup, Product Features, or Troubleshooting. Organize categories by how customers think about problems, not how your internal team structures them. For each category, write 5-8 FAQ entries where questions are phrased exactly how real customers would ask them—conversational and natural, not corporate or formal. Structure each answer to lead with the direct solution in the first sentence, followed by necessary context or steps. For multi-step processes, use numbered lists with no more than 7 steps; if more steps are required, break the process into logical sub-sections. Add 2-3 "Related Articles" suggestions at the bottom of each FAQ entry to prevent dead ends and keep users engaged in self-service. Include a "Was this helpful? Yes / No" feedback prompt suggestion at the end of each entry to enable continuous improvement tracking.

Avoid jargon or internal terminology customers wouldn't recognize. Never use "contact support" as the first option in any answer. Eliminate walls of unformatted text and passive-voice constructions that bury solutions. Do not write generic placeholder content—every answer must be specific, actionable, and directly tied to the business context provided. Use plain, direct language at an 8th-grade reading level to maximize accessibility and comprehension.

#INFORMATION ABOUT ME:
- My business, product, or service: [INSERT DESCRIPTION OF YOUR BUSINESS, PRODUCT, OR SERVICE]
- My top recurring customer issues or questions: [LIST YOUR TOP 5-10 RECURRING ISSUES OR QUESTIONS]
- My current monthly support ticket volume: [INSERT APPROXIMATE NUMBER OF TICKETS PER MONTH]
- My primary customer segment: [DESCRIBE YOUR PRIMARY CUSTOMER SEGMENT, E.G., SMALL BUSINESS OWNERS, FIRST-TIME USERS, ENTERPRISE IT ADMINS]
- My support deflection goal: [INSERT YOUR TICKET REDUCTION TARGET, E.G., 30% REDUCTION]

MOST IMPORTANT!: Output the complete FAQ section organized by category. Format each entry with the question in bold, followed by the answer paragraph or numbered steps, then related article suggestions, and finally the feedback prompt. Ensure all content is specific, actionable, and written in plain language at an 8th-grade reading level.