After creating your AI Routes, Routing Descriptions, Route Instructions, Knowledge Base content, and escalation behavior, you should test the complete routing system.
Testing helps confirm that Novus AI correctly understands member intent and applies the appropriate instructions for each type of concern.
Why Test AI Routing?
A route may look correctly configured but still overlap with another route when real members begin asking questions.
Testing can help identify:
- Incorrect route selection
- Overlapping routes
- Routing Descriptions that are too broad
- Routing Descriptions that are too narrow
- Incorrect Route Instructions
- Missing Knowledge Base information
- Incorrect escalation behavior
- Problems with short or informal questions
- Problems with multilingual messages
- Problems with follow-up questions
Testing should focus on realistic member conversations rather than only perfectly written examples.
Start With Clear Questions
Begin by testing questions that clearly belong to each route.
For example, suppose you have:
- General Support
- Technical Support
- Account Support
- Payment Support
You can test each route individually.
General Support
"What are the community rules?"
Technical Support
"My launcher won't open."
Account Support
"I forgot my password. How can I recover my account?"
Payment Support
"What payment methods are available?"
Each question should be handled using the expected route.
Test Multiple Questions Per Route
Do not assume a route works correctly after testing only one question.
Members can describe the same concern in many different ways.
For example, test Technical Support with:
- "My launcher won't open."
- "The client keeps crashing."
- "I'm missing a required file."
- "The game won't start after updating."
- "I can't connect to the server."
- "I'm getting an error after patching."
All of these may belong to the same Technical Support route even though the wording is different.
Test Short Messages
Discord members often send very short messages.
For example:
- "launcher error"
- "payment pending"
- "forgot password"
- "where register"
- "client crash"
- "missing purchase"
Test these messages to make sure Novus AI can still identify the intended route when enough context is available.
Test Informal Messages
Real conversations are rarely written like documentation.
Members may use:
- Informal language
- Abbreviations
- Slang
- Incomplete sentences
- Minor spelling mistakes
- Mixed capitalization
For example:
"bro my launcher keeps closing"
should still be understood as a technical concern.
Routing should focus primarily on the meaning of the message rather than perfect grammar.
Test Different Ways of Asking the Same Question
Create several variations of the same concern.
For example:
Payment Support
"What payment methods are available?"
"How can I pay?"
"Where do I send payment?"
"Can I purchase using another payment method?"
"How do I buy this package?"
These questions may use different wording but can represent related payment or purchase intent.
Test Ambiguous Questions
Some messages may reasonably appear to belong to more than one route.
These are especially important to test.
For example:
"I paid for Premium but it isn't active on my account."
This involves both a payment and an account.
If your Payment Support route is responsible for purchased services that have not been delivered or activated, the message should follow that route.
Another example:
"I can't log in after installing the latest patch."
This involves login and a technical change.
If the actual problem is caused by the client or patch, Technical Support may be the appropriate route.
Your routing structure should define which route owns these situations.
Test Route Boundaries
You should also test questions that are close to a route's topic but should belong somewhere else.
For example:
"How much does Premium cost?"
may belong to Payment Support.
But:
"What benefits does Premium provide?"
may be a general informational question depending on how your routes are configured.
There is no universal correct routing structure.
What matters is that your routes have clearly defined responsibilities and behave consistently.
Test Questions That Should Use General Support
If you have a General Support route, make sure it does not compete unnecessarily with specialized routes.
Test normal informational questions such as:
- "What are the server rules?"
- "When is the next event?"
- "Where can I find the guide?"
- "What features are available?"
- "Where is the download page?"
Then test specialized questions and verify that General Support does not incorrectly take them.
Test Unknown Questions
Ask questions that do not clearly belong to any configured specialized route.
For example:
"Do you know when a feature that hasn't been announced will be released?"
Your configuration should handle the question according to your general fallback behavior rather than forcing it into an unrelated specialized route.
Test Missing Knowledge
Routing can be correct even when the answer is unavailable.
For example:
A question may correctly reach Payment Support, but the requested package price may not exist in your Knowledge Base.
In this situation, verify that Novus AI:
- Selects the correct route.
- Recognizes that the required information is unavailable.
- Does not invent the missing information.
- Uses the appropriate fallback or escalation behavior.
Do not mistake missing Knowledge for a routing failure.
Test Route Instructions
Correct route selection is only the first part of the test.
After the route is selected, verify that Novus AI follows the appropriate Route Instructions.
Check whether it:
- Uses available Knowledge Base information
- Follows route-specific procedures
- Respects restrictions
- Avoids unsupported information
- Requests clarification only when necessary
- Escalates when required
- Avoids unnecessary escalation
A route that is selected correctly but behaves incorrectly may need changes to its Route Instructions rather than its Routing Description.
Test Escalation
Create scenarios where human assistance should be required.
For example:
Technical Support
The member has completed all documented troubleshooting steps but the issue remains unresolved.
Payment Support
The member needs a specific transaction manually verified.
Account Support
The member requires an administrative account change.
Verify that Novus AI directs the member to the appropriate support process.
Also verify that simple questions do not trigger unnecessary escalation.
Test Follow-Up Questions
Routing should also work naturally during conversations.
For example:
Member:
"I paid for Premium but it hasn't activated."
Member:
"How long should I wait?"
Member:
"What if it's still missing tomorrow?"
The member should not need to repeat the original payment concern in every message when the conversation context is available.
Test short follow-ups such as:
- "how much?"
- "where?"
- "what about this one?"
- "still not working"
- "and if it fails?"
- "can I use another one?"
These are common in real support conversations.
Test Topic Changes
Members may also change topics during a conversation.
For example:
Member:
"My launcher won't open."
After receiving technical assistance:
Member:
"Also, what payment methods do you accept?"
The new question should be handled according to its new intent rather than remaining permanently attached to the previous Technical Support topic.
This is important for longer support conversations.
Test Multilingual Routing
If your community uses multiple languages, test each route using the languages commonly used by your members.
For example, the same technical concern may be asked in different languages.
The route should still identify the underlying intent.
Also test:
- Mixed-language messages
- Informal translations
- Common local terminology
- Short multilingual questions
Multilingual routing performance may depend partly on the capabilities of your selected AI model.
Test Similar Routes Together
If two routes are closely related, test them against each other.
For example, if you have Account Support and Technical Support, create a test set containing questions from both categories.
Do the same for:
- Payment Support vs. Account Support
- General Support vs. Technical Support
- General Support vs. Payment Support
- Any other routes with similar boundaries
This can reveal overlap that may not appear when routes are tested individually.
Create a Routing Test Set
For larger configurations, maintain a simple collection of test questions.
For each question, define the expected route.
For example:
Question:
"My launcher crashes after updating."
Expected Route:
Technical Support
Question:
"I forgot my password."
Expected Route:
Account Support
Question:
"My payment is still pending."
Expected Route:
Payment Support
Question:
"What are the community rules?"
Expected Route:
General Support
You can reuse this test set whenever you make major changes to your routes.
Diagnose Routing Problems Correctly
When a test fails, determine which part of the configuration caused the problem.
Wrong route selected?
Review the Routing Description.
Two routes frequently compete?
Review route boundaries and overlap.
Correct route but wrong response behavior?
Review Route Instructions.
Correct route but incorrect factual answer?
Review the Knowledge Base.
Correct route but information is unavailable?
Add or update Knowledge if the information should exist.
AI invents missing information?
Review fallback and no-guessing instructions.
Incorrect human escalation?
Review route-specific escalation rules.
Changing the correct configuration prevents unnecessary complexity.
Change One Thing at a Time
When troubleshooting routing, avoid changing several routes simultaneously.
Instead:
- Identify the failing test.
- Determine which routes are involved.
- Compare their descriptions.
- Make one targeted change.
- Save the configuration.
- Run the same test again.
- Test nearby scenarios to make sure the change did not create another conflict.
This makes routing improvements easier to evaluate.
Retest After Adding a New Route
Whenever you add a new AI Route, do not test only the new route.
Also retest existing routes that are closely related.
A new route can introduce overlap with routes that previously worked correctly.
For example, adding Account Support may require retesting Technical Support and General Support.
Test With Real Community Questions
After your initial testing, use actual support questions from your community as additional test cases.
Real member questions can reveal:
- Unexpected wording
- New terminology
- Common abbreviations
- Frequently confused topics
- Missing Knowledge
- New support categories
- Unclear route boundaries
Use these patterns to improve your routing configuration over time.
AI Routing Testing Checklist
Before considering your routing setup ready, verify that:
- Clear questions reach the correct route.
- Different wording still reaches the expected route.
- Short messages are handled appropriately.
- Similar routes have clear boundaries.
- Ambiguous questions follow the intended route.
- General Support does not override specialized routes.
- Route Instructions are applied correctly.
- Knowledge Base information is used correctly.
- Missing information is not invented.
- Escalation occurs only when necessary.
- Follow-up questions retain useful context.
- Topic changes can move to the appropriate route.
- Multilingual messages route appropriately.
- New routes do not break existing routing behavior.
Continue Testing Over Time
AI Routing should not be treated as a one-time configuration.
As your community grows, members may introduce new questions and support situations that were not considered during the initial setup.
Review routing behavior periodically and improve your routes when recurring problems appear.
The goal is not to create a route for every possible question.
The goal is to maintain a small, understandable routing system that consistently applies the correct support behavior.
AI Routing Setup Complete
You have now completed the core AI Routing setup.
You understand how to:
- Create AI Routes
- Write effective Routing Descriptions
- Create Route Instructions
- Use Knowledge with routes
- Configure fallback and escalation
- Manage overlapping routes
- Test the complete routing system
Your routing system can now help Novus AI identify different types of member concerns and apply the appropriate support behavior.
Next Step
With your AI behavior, Knowledge Base, and AI Routing configured, the next major step is controlling where Novus AI can operate inside your Discord server.
Continue to the Channel Configuration documentation.