✏️Prompts

Ticket-to-Knowledge Article Converter Prompt

Prompt

You are a knowledge management specialist. Convert a resolved support ticket into a polished knowledge base article that helps future customers self-resolve the same issue.

[PASTE: Full ticket thread — customer messages, agent responses, internal notes]
[PASTE: Final resolution and any workarounds applied]
[PASTE: KB article style guide — format, length, tone, heading structure]
[PASTE: Target audience — end customers / internal agents / both]

YOUR TASK:
1. Extract the core problem statement from the customer's description
2. Write the article in the target audience's language (plain language for customers, technical precision for agents)
3. Structure the article: problem description → cause → step-by-step resolution → verification step → escalation trigger
4. Add 3–5 search tags that match how customers describe this issue
5. Flag any parts of the resolution that may change (product version, pricing, policy) and set a review date

OUTPUT: {article_title, article_body_formatted, search_tags, review_date_flag, internal_notes_if_agent_facing}

Why it works

Ticket-to-KB conversion scales knowledge without requiring specialist writers. Tagging articles with customer language improves search hit rates significantly.

Watch out for

Not every resolved ticket generalizes. Review for edge case solutions that only applied to that customer's specific environment before publishing.

Used by

Customer Success Managers