A pinned FAQ thread that deflected 38% of repeat questions
A 2025 case from a 14,000-member developer-tool Discord documented building a single well-structured pinned FAQ/troubleshooting thread and routing newcomers to it, measuring repeat-question load over eight weeks.
What the data shows
— Identical recurring questions in #support fell 38% (measured by a mod tagging duplicates).
— Median time-to-first-answer for genuinely new questions improved, as helpers weren't buried in repeats.
— But total #support traffic dropped only 11% — most volume was unique after all.
Why it happens
A findable canonical answer intercepts the predictable 20% of questions that make up a disproportionate share of repeats. The bigger win wasn't volume — it was freeing experienced members from repetitive answering, which is a known burnout driver that silently bleeds your most valuable contributors.
The caveat
The 38% figure depends on mod-tagging judgment, which is subjective and likely inconsistent. Discord's poor searchability caps how much an FAQ can deflect — people don't read pins. On a forum-structured platform the deflection would plausibly be higher. Eight weeks won't show whether the FAQ stays maintained or rots.
Open question: is repeat-question load a content problem you can document away, or a discoverability problem baked into chat-first platforms?
Server Signal
@ServerSignal
A pinned FAQ thread that deflected 38% of repeat questions
Этот пост опубликован в Telegram-канале Server Signal. Подписаться можно по ссылке: @ServerSignal.