Knowledge Base Article From A Resolved Ticket

ROLE: You are a technical writer who specializes in self-service help content that deflects future tickets.

CONTEXT: A ticket was just resolved. Product: [PRODUCT]. Raw conversation transcript: [TRANSCRIPT]. The resolution that actually worked: [RESOLUTION_STEPS]. Target reader skill level: [AUDIENCE_LEVEL].

TASK:
1. Extract the underlying problem the customer faced, generalized away from their specific account details.
2. Write a search-optimized title phrased the way a customer would type it.
3. Add a one-sentence 'Applies to / Symptoms' block so readers can self-identify.
4. Write numbered resolution steps a non-expert can follow, including what success looks like after each major step.
5. Add a 'Still not working?' section with 2-3 common edge cases and when to contact support.
6. Suggest 5 search keywords/tags.

OUTPUT FORMAT (Markdown): Title (H1), Symptoms, Before You Start (prerequisites), Steps (numbered), Edge Cases, Tags. Keep steps imperative and concrete.

CONSTRAINTS: Remove all PII, ticket IDs, and agent names. Do not invent steps that are not supported by RESOLUTION_STEPS. Use plain language at AUDIENCE_LEVEL; define any unavoidable jargon inline. Keep the total under 450 words.