Generate a KB article from clustered support tickets
If you're answering the same question 10 times a week, write the KB article once. This prompt drafts one from real ticket excerpts.
Draft a KB article that resolves this question for future readers.
Recurring question (paraphrased): {{QUESTION}}
Real ticket excerpts showing how customers phrase it:
{{TICKET_EXCERPTS}}
The answer (raw notes from support):
{{ANSWER_NOTES}}
Structure:
- H1 question phrased the way customers actually phrase it (not internal jargon).
- 1-paragraph TL;DR with the answer.
- Step-by-step if applicable.
- 'When this doesn't work' — the 2-3 known edge cases.
- 'Related' — 3 article titles we should also link if they existed.
No marketing fluff. Match the tone of clear technical docs. {{QUESTION}}{{TICKET_EXCERPTS}}{{ANSWER_NOTES}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{QUESTION}}{{TICKET_EXCERPTS}}{{ANSWER_NOTES}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.