What repeated support question is ready to become a FAQ?

A workplace documentation question about when repeated private replies should become a reusable FAQ entry.

A repeated support question is not automatically ready for a FAQ. I would first ask whether the answer is stable, whether private account context changes the result, and whether the team can name one owner for review. If those are true, a public or shared FAQ can reduce repeated replies. If not, an internal answer packet may be safer. What signal tells you that a question has crossed the line from “reply case by case” to “write a durable FAQ”?