AI FAQ that answers from your own words
Write a FAQ once, and let the AI answer your members automatically - inline in your help channels and right before a ticket opens. Answers come only from the entries you write, never from outside knowledge.
Illustration only - actual interface and behavior may differ
From a FAQ you write to answers that deflect tickets
Four steps from a blank page to an AI that resolves routine questions on its own - without ever inventing an answer.
Write FAQ entries
Add staff-authored entries in plain Markdown. Each is a question your members ask plus the answer you want used.
The AI indexes them
On save, each entry is split into searchable chunks - usually under 10 seconds - and goes live for the AI to draw from.
Members ask questions
In your chosen help channels, or right as someone tries to open a ticket, the bot picks up the question.
The AI answers or deflects
It replies in your server's voice from your entries - or, if it can't, steps aside and offers a ticket instead.
Dive into every part of AI FAQ
Four focused pages: how the AI answers inline, how it screens tickets before they open, the knowledge it draws on, and what it learns.
Channel Auto-Answer
Let the AI reply to questions inline in the channels you choose, drawing every answer from your FAQ.
Pre-Ticket Gatekeeper
Have the AI try first before a Modmail or Ticket System ticket opens - without ever blocking the member.
Knowledge Base
Write the Markdown FAQ entries the AI answers from - the single, grounded source for every reply.
Insights
See where the AI escalates and why, so you know exactly which FAQ entries to write next.
Auto-answer questions in your channels
Pick one or more help or forum channels and the bot replies inline whenever a member asks something your FAQ covers. It posts a quick "Looking that up..." placeholder, then edits it in place with the real answer - one tidy message, no double-posting.
Illustration only - actual interface and behavior may differ
Deflect questions before a ticket opens
The gatekeeper sits between a member and your ticket flow. Before a ticket actually opens, the bot asks for the question, has the AI answer it, and only opens the ticket if the member still needs help. Members are never blocked - "I still need help" is always one click away.
Illustration only - actual interface and behavior may differ
See exactly what to write next
The Insights dashboard shows where the AI handed questions to your team instead of answering them, and why. Every recurring escalation reason is a gap in your FAQ - and a ready-made to-do list for closing it.
1,284
Total answers
18%
Escalation rate
231
Escalations offered
37
Active entries
Each recurring reason is a question your FAQ doesn't cover yet. Treat the list as a to-do: write or improve an entry and the reason drops off next time.
The AI answers only from your entries - never from outside knowledge
Your FAQ entries are the only thing the AI reads from. If your FAQ doesn't cover a question, the bot says so and offers a ticket instead of guessing at an answer. You stay in full control of every answer your members get.
Grounded answers
Every reply is drawn from entries you wrote. The AI paraphrases in your server's voice and stays grounded in your entries rather than reaching for outside facts, specifics, or steps.
Confidence threshold
Tune cooldowns, minimum question length, and account-age filters so the AI only runs where it can actually add value - keeping spend predictable.
Markdown entries
Write entries in plain Markdown - headings, bullets, links, bold. Answers can run up to 50,000 characters and are auto-chunked at natural breakpoints.
Import from your docs
Drop in a .md or .txt file and it lands straight in the answer field, ready to review and save. No copy-pasting line by line.
Archive vs delete
Archive entries to hide them from the AI while keeping them in your database - free, reversible, and not counted against your 100 active-entry limit.
Credit-based pricing
Pay only for what you use: roughly 1 credit per indexed chunk (~2,000 characters) to save an entry, plus a small per-answer cost that varies by question type.
AI FAQ vs. AI Summaries - what's the difference?
They're two different AI features that work at opposite ends of a ticket's life. Here's how to tell them apart.
AI FAQ
Before a ticket exists
Answers a member's question up front - inline in a channel or right as they try to open a ticket - so routine questions are resolved and no ticket is ever created.
AI Summaries
After a ticket closes
Condenses a finished conversation into a short summary so your team can review what happened at a glance. It works on a closed ticket, not before one.
Where AI FAQ pays off
A few common ways teams put it to work.
High-traffic help channels
Let the AI handle the questions your team answers a dozen times a day, inline and instantly, so staff focus on the cases that actually need them.
Cut ticket volume
Catch the easy questions before they become tickets. The gatekeeper deflects "how do I..." and "where's my..." so your queue stays focused on real issues.
Find the gaps in your docs
Use Insights to see what members asked that the AI couldn't answer - turning every miss into a clear prompt for the next entry to write.
Frequently Asked Questions
It's grounded specifically to reduce that. The AI only works from the FAQ entries you've written and is instructed not to pull in outside knowledge - if nothing matches, it says it couldn't find an answer and offers a ticket instead of guessing. No AI can be guaranteed perfect, but grounding every answer in your own entries is what keeps it tied to what you actually wrote.
AI FAQ uses your server's AI credits. Saving an entry costs about 1 credit per chunk (roughly 1 per 2,000 characters). Each answer costs a little too - around 1 credit for a rejected message, 3 for small talk, and 15 for a real FAQ search on the cheapest AI provider; other providers cost up to 3× more. Each paid plan comes with a monthly credit grant, and you can top up anytime.
Up to 100 active entries per server. Archived entries don't count toward the limit, cost nothing to keep, and can be unarchived anytime. Larger or multi-language knowledge bases can request a custom quota on enterprise plans.
Both, and you choose. Channel mode auto-answers inline in the help channels you select. The pre-ticket gatekeeper intercepts before a Modmail or Ticket System ticket opens, offering the answer first with "That solved it" / "I still need help" buttons. Run one surface or both.
The AI answers in your server's voice based on how your entries are written, and the bot's built-in messages ship with localized defaults. For best results, write your entries using the words your members actually type, including any community-specific terms.
AI FAQ is in beta and rolling out gradually. It is enabled per server as we iterate, so if you don't see it in your dashboard yet your server hasn't been switched on - reach out and we'll get you access. Your SCNX plan is separate and unaffected.
Explore the rest of the Support Bot
AI FAQ works hand in hand with the rest of your support setup.
Ready to Transform Your Support?
Set up professional support in minutes. No coding required. Start with a free trial and explore all features.
This offer is only available for selected servers that have never purchased a plan and never used a free trial before. You do not need to enter any payment information to start the trial and the trial automatically expires after 14 days. Servers that have been deleted from SCNX previously are not able to participate.