## TL;DR

Support threads are a list of what your users actually want to know, written in their words.
A question asked five times is a blog post waiting to happen.
Applies to any product with a support inbox, forum, or issue tracker.

## The query

```text
how to build a content backlog from support threads
```

## Use this when

- Support answers the same questions repeatedly.
- You want content ideas grounded in real user demand.
- You have a support inbox, forum, or issue tracker to mine.

## Not for

- You have almost no support volume yet (write from user interviews instead).
- The threads are mostly bug reports with no reusable lesson (fix the bugs, skip the content).
- You want thought-leadership pieces (those come from a different process).

## Steps

1. Export the last 90 days of support threads: titles, bodies, and reply counts.
   Expected output: A corpus of real user questions in their own words.
2. Cluster by topic and count frequency; rank the clusters.
   Expected output: A ranked list of the questions users ask most.
3. For the top 10, write one content brief each: the question, the answer, and the format.
   Expected output: Ten briefs, each traceable to real support demand.
4. Publish in rank order and link the new content from future support replies.
   Expected output: A backlog that shrinks support load as it ships.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_YXP5jaF9pjapO60xnNHvHw