PlaybookPrompts

Generate a KB article from clustered support tickets

Customer Support kbdocs

If you're answering the same question 10 times a week, write the KB article once. This prompt drafts one from real ticket excerpts.

Prompt
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.
Variables to fill in
  • {{QUESTION}}
  • {{TICKET_EXCERPTS}}
  • {{ANSWER_NOTES}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{QUESTION}}{{TICKET_EXCERPTS}}{{ANSWER_NOTES}}.
  3. Paste it into one of the recommended tools below.
  4. 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.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

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.