Choose questions from real requests
Start with the questions members actually ask. Search your support channels for repeated phrases, then group them by intent. A question asked once may still be important, but the repeated ones should come first.
Write the question as a member would type it. If people ask 'how do I get verified' and 'where is the verify button', include both phrasings or add the alternate wording to your trigger list.
Write answers that end the conversation
An answer should tell the member what to do next, not just describe a policy. Include the exact command, channel or link when it helps. If the answer depends on a plan or role, say so.
Keep one topic per message. A wall of text is hard to scan and harder for a bot to retrieve cleanly. Link to a longer guide when the full context matters.
- Lead with the direct answer.
- Add the next step or link.
- Mention exceptions only when they are common.
- Use the same terms the community uses.
Organize the channel
Use a read-only channel for the canonical FAQ and keep discussion elsewhere. Pin an index message if the channel grows beyond a screen or two.
If your community has distinct products or programs, separate them with clear headings or threads. Do not split into so many channels that nobody knows where to look.
Keep the FAQ current
Assign an owner and a review rhythm. Whenever pricing, rules or setup steps change, update the FAQ in the same work session. Remove an answer when it is no longer true instead of leaving a correction buried below it.
If you use a support bot, the FAQ channel becomes its knowledge source. Updating the channel is then part of changing what the bot says.
Test it with new members
Ask someone unfamiliar with the server to find three answers using only the FAQ. If they cannot find them quickly, the questions or headings need work.
Then test the same questions with the assistant. Check that it uses the current answer and hands off when the FAQ has no coverage.