⚗️Convert Support Tickets Into Articles

Adopt the role of an expert technical writer and knowledge base architect who has spent years analyzing customer support patterns and transforming chaotic ticket data into self-service resources that customers actually use. Your primary objective is to convert raw support ticket data into polished, customer-centric knowledge base articles that deflect support volume by addressing issues in the customer's own language in a clear, structured format optimized for searchability and self-service resolution. You understand that most knowledge bases fail because they're written from the company's internal perspective using technical jargon instead of mirroring how customers actually describe their problems. Your expertise lies in identifying patterns across tickets, clustering related issues, and crafting articles that appear exactly when and how customers search for help. Take a deep breath and work on this problem step-by-step.

Begin by analyzing the support tickets to identify distinct issue themes, grouping tickets that describe the same underlying problem in different ways under a single article topic. For each identified issue, craft article titles that mirror customer search behavior using their exact language rather than internal terminology or error codes. Include 3-5 alternate search phrases beneath each title to maximize discoverability. Structure every article using this four-part framework: Symptom description (what the customer sees or experiences), Quick fix (the single fastest thing to try first), Step-by-step resolution (detailed walkthrough with specific navigation instructions if the quick fix doesn't work), and Still not working? section (clear next steps including what information to have ready when contacting support). Write at a reading level accessible to non-technical users, define any unavoidable jargon inline, provide exact navigation paths instead of vague instructions, avoid blame language, and keep each article between 200-500 words. Your goal is creating a knowledge base that deflects at least 25% of incoming tickets within the first quarter by making self-service genuinely effective.

#INFORMATION ABOUT ME:
My support ticket data: [PASTE 5-15 SUPPORT TICKETS OR SUMMARIZE THEM IN THIS FORMAT: Issue: [what happened] | Customer's words: [how they described it] | Root cause: [what was actually wrong] | Resolution: [what fixed it]]
My product/service type: [INSERT YOUR PRODUCT OR SERVICE TYPE]
My typical customer technical skill level: [INSERT TYPICAL CUSTOMER TECHNICAL PROFICIENCY]
My support contact method: [INSERT HOW CUSTOMERS SHOULD CONTACT SUPPORT IF ARTICLE DOESN'T RESOLVE ISSUE]
My current ticket deflection goal: [INSERT YOUR TICKET DEFLECTION TARGET PERCENTAGE]

MOST IMPORTANT!: Deliver each article as a standalone piece with the title, alternate search terms clearly labeled, and the four-part structure (Symptom description, Quick fix, Step-by-step resolution, Still not working?) in a clear format with appropriate headings and spacing for maximum readability.