Not every concern can or should be completely resolved by AI.
A member may ask for information that is unavailable, require manual verification, encounter a problem that cannot be resolved using your Knowledge Base, or need assistance that only a staff member can provide.
Route-specific fallback and escalation rules define what Novus AI should do in these situations.
What Is a Route Fallback?
A Route Fallback defines how Novus AI should respond when the correct route has been identified but the information required to answer the member is unavailable.
For example, a member may correctly reach your Payment Support route but ask about a payment method that is not documented in your Knowledge Base.
Instead of guessing, the route can instruct Novus AI to explain that the information cannot be confirmed and direct the member toward the appropriate support process.
What Is Escalation?
Escalation happens when a concern should be passed to a human staff member or another support process.
This may be necessary when:
- Manual verification is required
- Account-specific information must be reviewed
- A transaction needs investigation
- Available troubleshooting steps have failed
- The requested information is unavailable
- Staff approval is required
- The AI is not authorized to perform the requested action
Escalation allows Novus AI to recognize when AI assistance should stop and human support should continue.
Fallback vs. Escalation
Fallback and escalation are related, but they are not exactly the same.
Fallback means Novus AI cannot confidently provide the requested answer.
Escalation provides the next support path for the member.
For example:
Fallback:
The available information does not confirm the answer.
Escalation:
Please contact the designated support team for further assistance.
A route may use both behaviors together.
General Fallback vs. Route Fallback
Your general AI configuration may already contain a fallback behavior for unknown questions.
Route-specific fallback rules allow you to provide a more appropriate response based on the type of concern.
For example:
General Support
Unknown questions may be directed to the normal support channel.
Technical Support
Unresolved technical problems may be directed to technical staff.
Payment Support
Transaction-specific concerns may be directed to the appropriate private support process.
This allows each route to provide a more useful next step.
When Should a Route Escalate?
Escalation should normally occur when the AI can no longer provide reliable or authorized assistance.
Common examples include:
Missing Information
The member asks for community-specific information that is not available in the Knowledge Base.
Novus AI should not invent the answer.
Manual Verification
The concern requires staff to inspect an account, transaction, application, or other information that the AI cannot verify.
Troubleshooting Has Failed
The member has followed the documented troubleshooting procedure but the problem remains unresolved.
Staff Approval Is Required
Some requests may require approval before they can be processed.
Novus AI can explain the available requirements but should escalate the actual approval process.
Sensitive or Private Concerns
A member may need to provide information that should not be posted in a public Discord channel.
The route can direct the member to the appropriate private support process.
Do Not Escalate Everything
Escalation should not replace normal AI support.
If the member asks a simple question and the answer exists in the Knowledge Base, Novus AI should normally answer it directly.
For example:
Member: How much is Package A?
If the verified price is available, provide it.
There is usually no reason to send the member to staff simply to receive information the AI already has.
Escalation should be used when human intervention is actually necessary.
Avoid Unnecessary Support Tickets
Similarly, do not instruct members to create support tickets for every question.
If Novus AI can answer the question accurately, providing the answer immediately creates a better support experience and reduces unnecessary work for staff.
Use tickets or other staff processes for concerns that require:
- Manual action
- Verification
- Investigation
- Private information
- Approval
- Other human intervention
Route-Specific Escalation
Different routes may have different escalation destinations.
For example:
Technical Support
Unresolved technical problems → Technical Support Team
Payment Support
Transaction verification → Payment Support process
Account Support
Manual account assistance → Account Support Team
Community Programs
Application or eligibility review → Program Staff
Configure each route according to how your Discord community actually handles those concerns.
Using Discord Channels and Roles
Your escalation instructions can include Discord references when appropriate.
For example, you may direct members to:
- A support ticket channel
- A specific support channel
- A staff role
- A designated assistance channel
When using Discord mentions, use the correct channel or role reference.
For example:
<#CHANNEL_ID>
or:
<@&ROLE_ID>
This allows Discord to render the appropriate mention when the response is sent.
Keep these references updated if your server structure changes.
Avoid Mentioning Staff Unnecessarily
If a concern can be answered normally, avoid unnecessarily mentioning staff roles or individual staff members.
Repeated unnecessary mentions can create notification spam.
Route Instructions can specify exactly when a role should be mentioned.
For example:
Mention the Technical Support role only when the documented troubleshooting process cannot resolve the concern.
This keeps escalation intentional.
Example: General Support
A General Support route might use:
Use available Knowledge Base information to answer general member questions.
If the requested community-specific information is unavailable, do not guess or invent an answer.
Use the configured general fallback or direct the member to the appropriate support option when additional assistance is required.
Example: Technical Support
A Technical Support route might use:
Use available troubleshooting information first.
If important details are missing, ask the member for the minimum information necessary to understand the problem.
Do not invent commands, files, download links, or technical procedures.
If the documented troubleshooting steps cannot resolve the issue, direct the member to the designated technical support process.
Example: Payment Support
A Payment Support route may require stricter behavior:
Use only verified payment, package, and service information available in the Knowledge Base.
Do not invent or estimate prices, payment methods, package contents, fees, or transaction information.
Answer simple informational questions directly when verified information is available.
If the concern requires payment verification, transaction investigation, or manual processing, direct the member to the designated payment support process.
Example: Account Support
An Account Support route might use:
Provide general account information and documented account procedures when available.
Do not request passwords, authentication codes, security codes, or other private credentials.
If the concern requires manual account verification or administrative changes, direct the member to the designated account support process.
Handling Unknown Information
A strong route should clearly tell Novus AI what to do when information is unavailable.
For example:
If the requested information is not available in the Knowledge Base or route instructions, do not guess, estimate, or create an answer. Inform the member that the information cannot currently be confirmed and provide the appropriate escalation path when one is configured.
This is especially important for factual community-specific information.
Handling Partially Available Information
Sometimes Novus AI may know part of the answer but not everything.
For example:
A member asks:
How much is the package and when will it be delivered?
The Knowledge Base may contain the package price but no delivery timeframe.
Novus AI should provide the information it can verify while avoiding unsupported details.
For example:
The package price is available, but I don't have verified information about the delivery timeframe.
The route can then provide the appropriate next step if necessary.
The assistant does not need to discard the entire answer simply because one detail is unavailable.
Avoid False Escalation Claims
Do not instruct Novus AI to imply that staff has already received, reviewed, approved, or escalated a concern unless that action has actually occurred.
For example, avoid responses such as:
I have forwarded this to the administrators.
unless your system actually performs that action.
Instead:
Please contact the designated support team so they can review the concern.
AI responses should accurately represent what the system has and has not done.
Keep Escalation Instructions Current
When your Discord support structure changes, review your AI Routes.
Update:
- Channel references
- Role references
- Ticket procedures
- Support responsibilities
- Escalation conditions
- Staff-related instructions
An outdated escalation destination can prevent members from receiving the help they need.
Test Your Escalation Rules
After configuring route fallback and escalation, test different situations.
Test questions where:
- The answer exists and should be provided directly.
- Only part of the answer is available.
- The information is completely unavailable.
- Manual verification is required.
- Staff approval is required.
- Troubleshooting has been exhausted.
- The concern belongs to another route.
Verify that Novus AI escalates only when appropriate.
Don't Confuse Routing With Escalation
Routing determines which AI configuration should handle the concern.
Escalation determines when the AI should stop handling the concern and direct the member elsewhere.
For example:
Member: My launcher crashes.
→ Technical Support Route
Novus AI provides documented troubleshooting.
If the problem remains unresolved:
→ Technical Support Escalation
These are separate stages of the support process.
Recommended Route Flow
A well-designed route generally follows this flow:
1. Identify the concern
Routing Description determines the appropriate route.
2. Answer using available information
Use the relevant Knowledge Base content.
3. Request clarification when necessary
Ask only for information required to continue.
4. Avoid unsupported information
Do not guess missing community-specific facts.
5. Resolve when possible
Provide the answer or documented procedure.
6. Escalate when necessary
Direct the member to the appropriate human support process when AI assistance is no longer sufficient.
This creates a clear path from initial question to resolution.
Next Step
Your routes can now identify member concerns, apply specialized instructions, use relevant Knowledge Base information, and escalate unresolved situations appropriately.
The next step is making sure multiple routes work together without incorrectly competing for the same member questions.
Continue to Managing Overlapping Routes.