When should a repeated chat answer become a FAQ instead of another reply?

A concrete team-ops question about the threshold for turning repeated Slack or support replies into reusable FAQ entries.

A repeated chat answer is convenient in the moment, but it disappears quickly. If the same question comes up every week, I think the team should ask whether the answer path is stable enough to publish as a FAQ. The tricky part is boundary. Some questions repeat because the answer is universal. Others repeat because the intake is confusing, but the final decision still depends on private context. In that case, maybe the public artifact should be an intake checklist rather than the answer itself. What threshold do you use before turning a repeated reply into a FAQ?