❓ FAQ
The Community FAQ is built from what members actually ask — the agent scans your server's message history, clusters recurring questions, and drafts answers from your knowledge base. You review, edit, and publish the result, so the FAQ reflects real demand instead of guesswork.
Overview
From the FAQ tab you can:
- Generate an FAQ from member questions over a chosen time window
- Auto-draft answers from the knowledge base, or keep unanswerable questions for manual review
- Edit answers inline, hide or show individual entries, and track what still needs an answer
- Publish immediately or save as a draft
- Restore any earlier version from version history
Configuration
To generate or manage the FAQ:
- Open your project in the Fren One webapp.
- Select the Discord server you want to configure.
- In the sidebar under Agent Configuration, select Knowledge Base, then the FAQ tab.
- Select Generate FAQ (or Regenerate if one already exists).
Generation options
The generate modal controls what goes into the FAQ:
| Option | Description |
|---|---|
| Time window | How far back to scan member questions: Last 30 days, Last 90 days, Last year, or All history. |
| Minimum times a question was asked | Only questions asked at least this many times become FAQ entries. |
| Auto-generate answers | Drafts answers from the knowledge base. If you'd rather answer manually, choose between "Keep questions it can't answer for review" and "Exclude questions it can't answer". |
| When generation completes | Publish immediately, or Save as draft and publish later from version history. |
Generation runs in the background, with live progress as it works — "N messages scanned", then "N question clusters found". You can leave the page and come back.
Reviewing and editing entries
Once generated, each FAQ entry can be worked on directly in the list:
- Edit answers inline — open an entry's answer editor to refine or rewrite what the agent drafted.
- Hide / show — hide entries you don't want published without deleting them.
- Needs answer — a count tracks how many questions still lack an answer, so nothing slips through review.
Version history
Every generation creates a version. The collapsible Version history section lists them, and Restore brings back an earlier version — useful if a regeneration turned out worse than what you had, or to publish a draft you saved earlier.
Saving your changes
Generation is an asynchronous job started from the modal; whether the result goes live right away depends on your "When generation completes" choice — Publish immediately or Save as draft. Edits, hides, and restores are applied per entry as you make them; there is no page-level Save bar.
Best practices
- Raise the minimum ask count in large servers so one-off questions don't clutter the FAQ.
- Start with Save as draft for your first generation, review the entries, then publish.
- Work the Needs answer count down to zero — those are questions members keep asking that the knowledge base can't answer yet, which usually means a missing 📥 source.
- Regenerate periodically with a recent time window so the FAQ tracks what members are asking now.
Troubleshooting
Generation found few or no questions?
- Widen the Time window or lower the Minimum times a question was asked threshold.
Many entries have no answers?
- With auto-generate on, answers are drafted from the knowledge base — if it can't answer, the question is kept or excluded per your setting. Add the missing content in 📥 Sources and regenerate.
A regeneration replaced an FAQ you preferred?
- Open Version history and Restore the earlier version.
Related features
- 📥 Sources - the knowledge the auto-generated answers are drafted from
- 🩺 Curation - see the questions your agent couldn't answer
- 🤖 AI Assistant - answers the same questions live in your server