Skip to content
Search
AppliedPlaybooks

Turn Support Tickets into Knowledge Base Articles

Difficulty
Beginner
Time
30 minutes per article

Before you start

  • Five to twenty solved tickets on one topic, with personal details removed
  • Your current list of help article titles
  • An AI chat assistant your company has approved for support work
  • Someone who can confirm the fix is right (often you)

This playbook turns solved support tickets into knowledge base articles, and finds the questions your help center doesn't answer yet. Each solved ticket already holds a tested answer. Writing it up once means the next customer can help themselves, and the next reply can be grounded in an approved article.

Step 1: Pick the tickets and strip personal data

Use the AI assistant your company has approved for this kind of work, and follow your company's AI policy. If you don't know which tool is approved, ask before you paste anything. Export or copy a handful of solved tickets on the same problem. Remove names, emails, phone numbers, addresses, order and account numbers and anything else that identifies a customer. The article only needs the problem and the fix.

Step 2: Write the article

Below are solved support tickets about the same problem. Write one help
center article from them.

- Title: the question as a customer would type it.
- Symptom: what the customer sees, in their words.
- Cause: why it happens, only if the tickets say so. Otherwise leave
  this section out.
- Fix: numbered steps, one action each.
- When to contact support: the cases the fix doesn't cover.

Use only what the tickets show worked. If tickets disagree on the fix,
list both and mark them [CONFIRM]. No marketing language.

Tickets:
[paste]

Step 3: Test the fix yourself

Follow the numbered steps exactly as written, in the product, as a customer would. If a step is missing, unclear or wrong, fix the article. Resolve every [CONFIRM] with whoever owns that part of the product. Don't publish an article whose steps you haven't followed.

Step 4: Find what's missing

Now look for gaps across a wider set of tickets, for example a week's worth with personal data removed, and your current article titles.

Below are recent support tickets and the titles of our current help
articles. Group the tickets by the question the customer was asking.
For each group, give: the question in the customer's words, how many
tickets asked it, and the article title that answers it, or NO ARTICLE.
Sort by count, highest first. Do not invent tickets or articles.

Tickets:
[paste]

Article titles:
[paste]

Spot-check the counts by searching your help desk for two or three of the groups. AI tools are unreliable at exact counting, so treat the numbers as a rough order, not a report.

What to do next

Publish the article through your help center's normal review. Work through the NO ARTICLE list from the top. New articles also make drafting replies from your help docs safer, because the AI has an approved source to work from.

Rather have someone set it up for you?

That's a fair call. LTFI, the agentic business operating system from Kief Studio, can set up the work these guides describe and run it with you. No website yet? Kief Studio will build you one for free.

Go further on kief.studio