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.

LLazyPrompt(@lazyprompt)Customer SupportRewriteWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Turn the resolved support conversation below into a help-center article for {{product}}.

Conversation:
{{thread}}

Audience: {{audience}}
Article style: {{style}}

Requirements:
- Remove all personal data, internal notes and blame. Generalise the specific case so it helps anyone with the same problem.
- Write the title the way a customer would search for it (a question or a symptom), plus 2 alternative search phrasings.
- Start with a 1-2 sentence summary of the problem and the fix.
- Give numbered steps. One action per step, using the exact names of buttons and menus mentioned in the thread. If a name isn't in the thread, write [CONFIRM: name] rather than guessing.
- Add a "If this didn't work" section with up to 3 likely causes from the thread, and when to contact support.
- Flag anything in the thread that looks like a product bug or missing documentation in a final "For the docs team" note.

Output the article in Markdown, then the "For the docs team" note.
Example output
# Why is my Gantt view empty? *Also searched as: "Gantt chart shows nothing", "tasks missing from timeline"* If your Gantt view looks blank even though you have tasks, it's almost always because those tasks are missing a start or due date. Gantt only displays tasks that have both. ## Steps to fix it 1. Open the project and switch to **List** view. 2. Select the tasks that don't appear on the timeline. 3. Choose **Bulk edit** and set a start date and a due date. 4. Return to **Gantt** view. Your tasks now appear. ## If this didn't work - Filters may be hiding tasks. Clear all filters on the Gantt toolbar. - Check that the date range at the top includes your task dates. - Still blank? Contact support and include the project name. **For the docs team:** The empty Gantt view gives no hint about the missing dates. An empty-state message would prevent most of these tickets.

Why it works

Forcing [CONFIRM: name] placeholders stops invented UI labels, and the docs-team note turns every ticket into product feedback too. Works best with threads that contain the real resolution, not just the question.

Licensed CC0 (public domain) Version 1 · history