Help-center article from a support thread
Convert a resolved ticket conversation into a clear, searchable help-center article with steps, troubleshooting and a good title.
Build a customer-ready FAQ from your docs, with questions phrased the way customers ask and answers grounded only in the source.
Create an FAQ for {{product}} using only the source material below.
Source material:
{{docs}}
Audience: {{audience}}
Number of questions: {{count}}
Tone: {{tone}}
Instructions:
- Pick the questions customers are most likely to ask, ordered from most to least common. Phrase each in the customer's own words, not product jargon.
- Group them under 3-5 short category headings.
- Each answer: direct answer in the first sentence, then at most 2 sentences of detail. Include steps only if the doc has them.
- Use only facts from the source. Never fill gaps with assumptions. If a likely question cannot be answered from the source, list it under "Gaps in the documentation" at the end.
- Where answers depend on plan, region or version, say so explicitly.
Output in Markdown.Restricting answers to the source text prevents confident but wrong FAQs, and the gaps list tells you what documentation to write next. Run it on one product area at a time for better coverage.
Licensed CC0 (public domain) Version 1 · history
Convert a resolved ticket conversation into a clear, searchable help-center article with steps, troubleshooting and a good title.
Condense a long, messy ticket history into a crisp escalation note with impact, timeline, what has been tried and what you need.
Turn a furious customer message into a reply that acknowledges the problem, takes ownership and offers a clear next step without grovelling.
Say no to a refund or policy-exception request clearly and kindly, explain the reason, and offer real alternatives so the customer feels respected.
Analyze a batch of tickets to find top issue themes, root causes, deflection opportunities and product or documentation fixes worth making.
Reply to a customer in their own language with natural phrasing, the right level of formality and a back-translation so you can check it.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.