As you add more information to Novus AI, your Knowledge Base can quickly grow from a few simple entries into a large collection of guides, rules, FAQs, procedures, and other community information.
A well-organized Knowledge Base is easier to maintain and helps ensure that the information available to your AI assistant remains clear and reliable.
Organize Knowledge by Topic
Create Knowledge Base entries around clear topics instead of storing everything in one large entry.
For example, a community might organize its Knowledge Base into topics such as:
General Information
Account Registration
Download & Installation
Rules & Policies
Frequently Asked Questions
Services
Events
Technical Support
Community Programs
Troubleshooting
Your exact structure should reflect the type of information your community needs.
Keep Each Entry Focused
Each Knowledge Base entry should have a clear purpose.
For example:
Account Registration
Contains information about creating an account.
Password Recovery
Contains information about recovering account access.
Download & Installation
Contains download and installation instructions.
Keeping entries focused makes them easier to update when only one part of your community information changes.
Group Closely Related Information
You do not need to create a separate entry for every small piece of information.
Closely related information can be grouped together when it makes sense.
For example:
Download & Installation
Full Download
Manual Patch
Installation Instructions
System Requirements
Common Installation Problems
These topics are closely related and may be easier to maintain together.
However, something unrelated—such as payment information—should normally have its own entry.
Use Clear Titles
Give each Knowledge Base entry a title that immediately explains what information it contains.
Good examples include:
Account Registration
Server Rules
Payment Methods
Installation Guide
Event Schedule
Account Recovery
Frequently Asked Questions
Avoid titles such as:
Information
Important
Guide
Other
Miscellaneous
New Information
Generic titles become difficult to understand when your Knowledge Base contains many entries.
Use Sections Inside Larger Entries
If an entry contains several related pieces of information, use headings to separate them.
For example:
Account Support
Creating an Account
Registration information.
Password Recovery
Password recovery information.
Account Suspension
Information about suspended accounts.
This keeps related information together while maintaining a clear structure.
Avoid Duplicate Information
Try to maintain one reliable source for each important piece of information.
For example, if your registration URL appears in five different Knowledge Base entries, changing that URL later requires updating all five entries.
If one is missed, conflicting information may remain available to the AI.
Whenever possible, avoid unnecessary duplication.
Watch for Conflicting Information
Conflicting information can cause unreliable responses.
For example:
Event Information A
The event begins at 7:00 PM.
Event Information B
The event begins at 8:00 PM.
If one of these entries is outdated, update or remove it.
When changing important information such as prices, dates, rewards, requirements, or procedures, review related Knowledge Base entries for older versions.
Separate Permanent and Temporary Information
Some information rarely changes, while other information may only be relevant for a short period.
Permanent information may include:
General rules
Registration procedures
Standard services
Common troubleshooting instructions
Temporary information may include:
Special events
Promotions
Temporary maintenance
Limited-time rewards
Announcements
Keeping temporary information easy to identify makes it easier to update or remove when it is no longer valid.
Use Consistent Naming
Use consistent terminology throughout your Knowledge Base.
For example, if your community calls a support system Support Ticket, avoid switching between:
Support Ticket
Help Request
Assistance Form
Customer Ticket
unless these terms actually represent different things.
Consistent naming reduces ambiguity.
Keep Related Rules Together
If several rules apply to the same feature or process, keep them close together.
For example:
Account Transfer
Eligibility
Requirements
Transfer Process
Restrictions
Items That Cannot Be Transferred
This is easier to understand than distributing the rules across unrelated Knowledge Base entries.
Separate Knowledge From AI Behavior
Organization also means placing information in the correct part of Novus AI.
Use the Knowledge Base for factual information.
Use AI Instructions for general assistant behavior.
Use AI Routing for topic-specific handling and instructions.
For example:
Knowledge Base:
Premium subscriptions last for 30 days.
AI Instructions:
Do not invent subscription prices or durations.
AI Route:
Questions about subscription payment problems should follow the subscription support procedure.
Keeping these responsibilities separate makes the entire AI configuration easier to maintain.
Consider How Information Changes
When deciding whether information belongs together, consider how often it changes.
If two pieces of information are related but normally updated independently, separate entries may be easier to maintain.
For example:
General Server Information
and
Current Event Schedule
may be related to the same community, but event schedules may change much more frequently.
Keeping them separate allows you to update events without modifying your permanent server information.
Create a Consistent Structure
For larger Knowledge Bases, using a consistent internal format can make management easier.
For example:
Topic Name
Overview
General information about the topic.
Requirements
Requirements that members must meet.
Procedure
Steps members should follow.
Restrictions
Important limitations or prohibited actions.
Additional Support
Where members should go if additional assistance is required.
Not every entry needs all of these sections. Use only the sections relevant to the topic.
Review Your Knowledge Base Regularly
As your community changes, review your Knowledge Base for:
Outdated information
Duplicate entries
Conflicting information
Broken links
Old schedules
Changed prices
Updated procedures
Missing frequently asked questions
Regular maintenance is especially important for information that Novus AI uses frequently.
Use Member Questions to Improve Organization
Real member questions can reveal where your Knowledge Base needs improvement.
If members frequently ask several questions about the same topic, consider whether those answers should be grouped together.
If one Knowledge Base entry becomes extremely large, consider splitting it into smaller focused entries.
Your Knowledge Base structure can evolve as your community grows.
Example Knowledge Base Structure
A growing community might eventually use a structure similar to:
General Information
About the Community
Frequently Asked Questions
Important Links
Accounts
Account Registration
Account Recovery
Account Rules
Installation & Technical Support
Download
Installation
Common Errors
Troubleshooting
Rules & Policies
Community Rules
Service Policies
Restrictions
Services
Available Services
Packages
Procedures
Events & Programs
Events
Rewards
Community Programs
This is only an example.
Your Knowledge Base should be organized according to the information your own community needs.
Keep It Simple
Do not create unnecessary complexity simply to make your Knowledge Base look organized.
The best structure is one that allows you to quickly answer:
Where should this information be stored?
and:
Where should I update this information when it changes?
If those questions are easy to answer, your Knowledge Base is probably organized effectively.
Next Step
Once your Knowledge Base is properly organized, you will eventually need to update information as your community changes.
Continue to Editing Knowledge.