The Novus AI Ticket System provides dedicated support conversations for members who need assistance beyond normal Discord chat.
Tickets give each concern its own conversation space where Novus AI can understand the issue, provide AI-assisted support, use your Knowledge Base, maintain conversation context, and work alongside your support staff when human assistance is required.
The goal is not to replace your support team.
Instead, Novus AI can handle repetitive and documented concerns while allowing staff to focus on situations that require investigation, verification, approval, or manual action.
What Is a Support Ticket?
A support ticket is a dedicated Discord conversation created for a member's concern.
Instead of discussing an issue in a busy public channel, the member can receive assistance in a separate support environment.
Tickets are useful for concerns such as:
- General support
- Technical problems
- Account concerns
- Payment or transaction assistance
- Reports
- Applications
- Community programs
- Private concerns
- Issues requiring staff intervention
The exact ticket types available depend on how your Discord server is configured.
How Novus AI Assists Inside Tickets
When AI assistance is enabled for a ticket, Novus AI can participate in the support conversation.
A typical flow may look like:
- A member opens a ticket.
- The member explains the concern.
- Novus AI analyzes the message.
- The appropriate AI Route is identified.
- Relevant Knowledge Base information is used.
- Novus AI provides an answer or troubleshooting steps.
- The member can continue with follow-up questions.
- Human staff can intervene when necessary.
- The concern is resolved.
- The ticket proceeds through the configured closing process.
This creates a support workflow where AI and human staff can work together.
Ticket Profiles
Ticket Profiles allow you to configure different types of ticket experiences.
For example, your server may have separate Ticket Profiles for:
- General Support
- Technical Support
- Payment Support
- Account Support
- Reports
- Guild or Community Programs
Each Ticket Profile can represent a different support purpose and may have its own configuration.
This allows you to control how different types of tickets should behave without forcing every ticket to use exactly the same workflow.
Ticket Profiles and AI Routes
Ticket Profiles and AI Routes are related but serve different purposes.
Ticket Profile
Defines the ticket environment and how that type of ticket should operate.
AI Route
Determines how Novus AI should handle the actual concern expressed during the conversation.
For example, a member may open a General Support ticket but later describe a technical problem.
AI Routing can still identify the technical intent and apply the appropriate support behavior when your configuration allows it.
Knowledge Base Integration
Novus AI can use your Knowledge Base while assisting inside tickets.
For example, if a member reports a launcher problem, the assistant may use documented information about:
- Installation
- Launcher troubleshooting
- Missing files
- Patches
- Connection problems
- Known errors
This allows common concerns to be answered without requiring staff to repeatedly provide the same instructions.
AI Should Not Invent Missing Information
Being inside a ticket does not give Novus AI permission to guess.
If required community-specific information is unavailable, the assistant should follow your configured fallback or escalation behavior.
This is particularly important for information such as:
- Prices
- Payment information
- Account procedures
- Rewards
- Eligibility requirements
- Technical instructions
- Rules
- Administrative decisions
The same Knowledge Base and AI behavior principles continue to apply inside tickets.
Conversation Context
Tickets often involve multiple messages.
For example:
Member:
My launcher closes when I press Start.
Novus AI:
Provides the available troubleshooting steps.
Member:
I already tried the first two steps.
Novus AI can use the ticket conversation context to understand what the member means without requiring the entire problem to be repeated.
This makes longer troubleshooting conversations more natural.
AI and Human Staff
Novus AI is designed to assist your support workflow, not prevent staff from participating.
Human staff may enter a ticket whenever manual assistance is necessary.
For example, staff intervention may be required for:
- Manual verification
- Administrative actions
- Transaction investigation
- Account changes
- Approval decisions
- Complex technical problems
- Concerns outside the available Knowledge Base
The AI can handle the documented portion of the support process while staff handles actions that require human authority.
Staff Intervention
When a staff member begins actively handling a ticket, Novus AI should avoid unnecessarily competing with the staff member.
Your ticket configuration can control how AI assistance behaves during human intervention.
This helps prevent situations where both Novus AI and staff repeatedly answer the same member at the same time.
The goal is one clear support conversation.
Escalation
Novus AI may determine that a concern can no longer be reliably resolved using the available information.
In this situation, the ticket can follow the configured escalation process.
Escalation may be appropriate when:
- Knowledge is unavailable
- Troubleshooting has been exhausted
- Manual verification is required
- Staff approval is required
- A transaction must be investigated
- An administrative action is required
- AI is not authorized to complete the requested action
Escalation provides a clear transition from AI assistance to human support.
Ticket Resolution
A ticket becomes ready for resolution when the member's concern has been successfully addressed.
For example:
Member:
It's working now. Thank you!
This is a strong indication that the original concern has been resolved.
Resolution can also become apparent through the overall conversation even when the member does not use a specific phrase.
AI-Assisted Resolution Detection
When enabled and supported by the Ticket Profile, Novus AI can analyze the conversation to determine whether the concern appears resolved.
The system can consider the conversation context rather than relying only on exact phrases such as:
"resolved"
or:
"fixed."
For example:
"That worked, thanks!"
may indicate that the problem has been solved.
This allows the ticket workflow to react more naturally to real conversations.
Proposed Ticket Closing
Detecting that a concern appears resolved does not necessarily mean the ticket should immediately disappear.
Novus AI can use the configured ticket workflow to propose or suggest closing the ticket when the conversation appears resolved.
This provides a safer transition from active support to closure.
The existing Ticket Profile closing behavior remains responsible for how the ticket is actually closed.
Inactivity
Tickets may also become inactive after the conversation stops.
Depending on your Ticket Profile configuration, inactivity can be considered as part of the closing workflow.
For example, if the conversation appears complete and no new messages arrive for the configured period, the ticket may become eligible for a closure proposal.
Inactivity should not automatically be treated as proof that every concern has been resolved.
The configured closing rules should determine what happens.
Existing Closing Rules Remain Important
AI-assisted resolution should complement your ticket workflow rather than replace it.
If your Ticket Profile already has specific closing behavior, those rules should remain authoritative.
For example, your existing workflow may require:
- A close request
- Member confirmation
- Staff action
- A configured timeout
- Another closing condition
AI resolution detection should work with these rules rather than create a conflicting closing system.
Ticket Closing
Once the appropriate closing conditions are satisfied, the ticket can proceed through the configured closing process.
Closing a ticket helps keep your support area organized and clearly separates active concerns from completed ones.
Your exact closing behavior depends on the Ticket Profile and server configuration.
Knowledge Base Improvement From Tickets
Support tickets can reveal useful information that does not yet exist in your Knowledge Base.
For example:
A member reports a new technical error.
Your staff discovers a verified solution.
The ticket is successfully resolved.
That solution may be useful for future members experiencing the same problem.
Novus AI can use supported Knowledge Base improvement workflows to identify useful new information from resolved tickets.
Knowledge Should Come From Verified Resolutions
Not every message inside a ticket should become Knowledge.
A conversation may contain:
- Incorrect assumptions
- Failed troubleshooting attempts
- Member-specific details
- Private information
- Staff discussion
- Temporary workarounds
- Unverified suggestions
Useful Knowledge should focus on the verified information or solution that can safely be reused for future support.
Knowledge Review and Synchronization
When new reusable information is identified from a resolved ticket, it can be processed according to your configured Knowledge Base workflow.
The goal is to prevent support staff from repeatedly solving the same undocumented problem.
Once appropriate information is added to the Knowledge Base, future Novus AI conversations can benefit from the newly documented solution.
Closing and Knowledge Processing Should Work Together
If your Novus AI configuration performs Knowledge Base processing when a ticket is closed, AI-assisted closing should follow the same Knowledge workflow.
A ticket being proposed for closure by AI should not bypass the existing Knowledge Base processing that normally occurs during ticket closure.
This keeps your ticket and Knowledge workflows consistent.
Ticket Lifecycle
A complete Novus AI ticket may follow this lifecycle:
1. Ticket Created
A member opens a support ticket.
2. Concern Identified
The member explains the issue.
3. AI Assistance
Novus AI uses AI Routing, Route Instructions, and Knowledge Base information.
4. Follow-Up
The member and Novus AI continue the conversation when necessary.
5. Staff Intervention
Human support joins when the concern requires manual assistance.
6. Resolution
The issue is successfully addressed.
7. Resolution Detection
Novus AI or staff recognizes that the concern appears resolved.
8. Closure Proposal
The configured workflow can propose closing the ticket when appropriate.
9. Knowledge Processing
Useful verified information can be reviewed for Knowledge Base improvement when supported.
10. Ticket Closed
The existing closing workflow completes the support process.
This creates a complete path from the first member question to future Knowledge Base improvement.
Benefits of AI-Assisted Tickets
A well-configured ticket system can help:
- Answer common questions faster
- Reduce repetitive staff work
- Provide support using your existing Knowledge Base
- Maintain context during longer conversations
- Escalate complex concerns appropriately
- Keep human staff involved when necessary
- Identify resolved concerns
- Keep active tickets organized
- Discover missing Knowledge Base information
- Improve future AI responses
The goal is a support system where AI handles what it can reliably resolve and staff handles what requires human judgment or action.
Start With a Simple Ticket Flow
You do not need to configure every possible ticket type immediately.
Start with the support areas your community uses most frequently.
For example:
- General Support
- Technical Support
- Payment Support
Test the complete workflow before expanding to additional Ticket Profiles.
Test the Complete Lifecycle
Do not test only whether a ticket can be created.
Test the complete experience:
- Create a ticket.
- Send a realistic concern.
- Verify AI assistance.
- Ask follow-up questions.
- Test Knowledge Base retrieval.
- Test missing information.
- Test escalation.
- Allow staff to intervene.
- Resolve the concern.
- Verify resolution behavior.
- Test the closing process.
- Verify any Knowledge Base processing associated with closure.
This provides a much more accurate test of your ticket system.
Next Step
Now that you understand the complete Ticket System, the next step is configuring the different support experiences your members can use.
Continue to Understanding Ticket Profiles.