Novus AI can handle many common support concerns using your AI Instructions, AI Routes, Ticket Forms, conversation context, and Knowledge Base.
However, not every issue should be handled entirely by AI.
Some situations require human judgment, manual verification, administrative action, approval, or investigation.
Staff Takeover and Ticket Escalation provide a controlled way to transition a ticket from AI-assisted support to your human support team.
What Is Ticket Escalation?
Ticket Escalation occurs when a concern requires human assistance beyond what Novus AI can reliably or safely provide.
For example, escalation may be appropriate when:
- Manual verification is required
- Staff approval is required
- An administrative action must be performed
- A transaction needs investigation
- Documented troubleshooting has been exhausted
- Required information is unavailable
- The concern falls outside the AI's authority
- A staff decision is required
- The issue remains unresolved after available AI assistance
Escalation should occur because human action is necessary, not simply because a ticket exists.
What Is Staff Takeover?
Staff Takeover occurs when a human staff member begins actively handling an AI-assisted ticket.
Before takeover, the conversation may primarily involve:
Member ↔ Novus AI
After staff begins handling the concern, the conversation becomes primarily:
Member ↔ Staff
Novus AI should avoid unnecessarily competing with staff during active human support.
Escalation and Takeover Are Different
These concepts are related but not identical.
Escalation
Indicates that human assistance is required.
Staff Takeover
Indicates that a staff member is now actively handling the conversation.
For example, Novus AI may escalate a ticket and notify the appropriate support team.
The ticket may remain waiting until a staff member becomes available.
Once staff begins actively handling it, the ticket can enter staff takeover behavior.
Why Staff Takeover Matters
Without takeover behavior, Novus AI and staff could respond to the member at the same time.
For example:
Member:
I completed all the troubleshooting but the error is still happening.
Staff:
Let me check this manually.
Then the member says:
Member:
Okay, thank you.
If Novus AI automatically responds again simply because the member sent another message, it can interfere with the staff conversation.
Staff Takeover helps prevent this.
AI Should Handle What It Can First
Escalation should not be the default response to every support question.
If Novus AI has verified information that can resolve the concern, it should generally provide that assistance first.
For example:
Member:
Where can I download the latest patch?
If the download information exists in the Knowledge Base, there is no reason to escalate the ticket.
Similarly:
Member:
What are the requirements for this feature?
If the requirements are documented, Novus AI can answer directly.
Human support should be reserved for concerns that actually require it.
Avoid Premature Escalation
Poor escalation rules can result in staff being notified for questions AI could easily answer.
This can lead to:
- Unnecessary staff workload
- Excessive role mentions
- Slower support for important concerns
- Reduced benefit from AI automation
- Staff ignoring frequent unnecessary alerts
Your Route Instructions should clearly define when escalation is genuinely required.
When Missing Knowledge Requires Escalation
Sometimes Novus AI understands the question but cannot find the required verified information.
For example:
Member:
How much will the upcoming unreleased package cost?
If the information is not available in the Knowledge Base, Novus AI should not invent a price.
Depending on your configured rules, it may explain that the information is currently unavailable or escalate when staff clarification is required.
Missing Knowledge and escalation are not always the same thing.
If staff cannot provide the information either because it has not been announced, escalation may be unnecessary.
When Manual Verification Is Required
Some concerns cannot be resolved through information alone.
For example:
Member:
My payment was completed but the purchase hasn't been credited.
Novus AI may provide documented instructions first.
However, if the transaction must be manually verified by staff, the ticket should transition to the appropriate human support process.
The AI should not claim that the transaction has been verified unless an actual system or staff action confirms it.
When Administrative Action Is Required
Novus AI may explain procedures, but some actions require staff authority.
Examples may include:
- Modifying an account
- Restoring an item
- Reviewing a transaction
- Approving an application
- Changing administrative records
- Performing manual server actions
When the requested outcome requires one of these actions, escalation may be appropriate.
When Troubleshooting Is Exhausted
Technical support is a common example of AI-to-human escalation.
A member may report:
"My launcher won't open."
Novus AI provides the documented troubleshooting steps.
The member tries them but reports:
"Still not working."
Novus AI may provide additional documented troubleshooting if available.
If all verified troubleshooting has been exhausted and the problem remains unresolved, human investigation may be necessary.
This is a better escalation point than immediately notifying staff after the first message.
Route-Specific Escalation
Different AI Routes may require different escalation rules.
For example:
Technical Support
Escalate after documented troubleshooting is exhausted or manual investigation is required.
Payment Support
Escalate when a transaction requires manual verification.
Account Support
Escalate when an administrative account action is required.
General Support
Escalate only when the concern cannot be answered through available Knowledge and genuinely requires staff assistance.
These rules should be defined in the relevant Route Instructions.
Escalating to the Correct Staff
Not every escalated ticket should necessarily notify the same staff group.
Different support concerns may be handled by different teams.
For example:
- Technical Support Team
- Payment Support Team
- Account Support Team
- Community Support Team
Your configuration should direct escalation to the appropriate support destination when available.
This prevents unrelated staff from being notified unnecessarily.
Avoid Repeated Staff Mentions
Once the appropriate staff has already been notified about a concern, Novus AI should avoid repeatedly mentioning them after every member message.
For example, this behavior is undesirable:
Member:
Payment is missing.
AI:
@PaymentStaff assistance required.
Member:
It was yesterday.
AI:
@PaymentStaff assistance required.
Member:
Okay, I'll wait.
AI:
@PaymentStaff assistance required.
One escalation should generally be enough unless your configured workflow explicitly requires another notification.
Preserve the Existing Ticket
When a concern is escalated, the member should generally remain in the same ticket.
Avoid requiring them to:
- Close the current ticket.
- Open another ticket.
- Re-enter their information.
- Explain the concern again.
The existing ticket already contains valuable context.
Escalation should preserve that conversation whenever possible.
Preserve Ticket Form Information
If the member completed a Ticket Form before creating the ticket, staff should be able to use that information during escalation.
For example:
Problem Description:
Launcher closes after pressing Start.
Troubleshooting Attempted:
Reinstalled client and restarted PC.
Staff should not need to ask for the same information again unless clarification is required.
Preserve AI Troubleshooting History
Before escalation, Novus AI may already have provided several troubleshooting steps.
This history is valuable to staff.
Staff can review:
- The original problem
- Form responses
- AI questions
- Member answers
- Troubleshooting attempted
- Results of each step
- The reason escalation occurred
This can significantly reduce repetitive support.
AI Summary for Staff
When AI Summary functionality is enabled for the ticket workflow, Novus AI can provide a concise summary of the conversation to help staff quickly understand the concern.
A useful summary may include:
- The member's main concern
- Important information provided
- Troubleshooting already attempted
- Relevant results
- What remains unresolved
- Why staff assistance is required
The summary should focus on actionable information rather than reproducing the entire conversation.
Summary Does Not Replace the Transcript
An AI Summary provides a quick overview.
The ticket conversation or transcript remains the detailed source when staff needs to review exactly what occurred.
Think of them as:
AI Summary
Quick understanding.
Transcript
Complete conversation record.
Both can serve different purposes.
Bottom-of-Transcript Summary
When your ticket configuration includes an AI Summary at the bottom of the transcript, the generated summary can help staff understand the final outcome of the ticket.
This may include:
- Original concern
- Important troubleshooting
- Staff actions
- Final resolution
- Remaining unresolved information when applicable
This can make completed transcripts easier to review later.
Staff Begins Handling the Ticket
Once a staff member starts actively assisting the member, Novus AI should recognize the human support state according to your configured ticket behavior.
For example:
Staff:
I'm checking your transaction now. Please give me a moment.
At this point, automatic AI responses may no longer be helpful.
Staff Takeover can reduce or disable AI participation while the human support conversation continues.
Preventing AI From Competing With Staff
During active Staff Takeover, Novus AI should generally avoid responding automatically to normal member follow-ups.
For example:
Staff:
Please restart the launcher and tell me what happens.
Member:
Same error.
The response is clearly intended for the staff member.
Novus AI should not unnecessarily insert another troubleshooting answer if staff is actively handling the concern.
Staff Can Still Use AI Assistance
Staff Takeover does not mean AI functionality becomes useless.
Depending on the Novus AI features available to staff, AI-generated information such as summaries or support context may still help staff understand the ticket.
The important distinction is that Novus AI should not automatically compete with the human conversation.
Ticket Holder Access During Escalation
Escalation does not mean the member should lose access to the ticket.
The ticket holder should normally remain able to:
- Read staff responses
- Provide requested information
- Answer questions
- Confirm results
- Continue the support conversation
Ticket access changes should follow your configured closing workflow rather than occurring simply because the ticket was escalated.
Waiting for Staff
There may be a period between escalation and Staff Takeover.
During this time, the ticket is waiting for human assistance.
Novus AI should avoid pretending that a staff member is already reviewing the concern unless that is actually known.
For example, avoid unsupported statements such as:
"An administrator is checking this now."
A safer response is to explain that the concern requires staff assistance according to the configured workflow.
Staff Resolution
Once staff resolves the concern, the ticket can continue through the normal resolution workflow.
For example:
Staff:
The issue has been corrected. Please try again.
Member:
It's working now. Thank you.
The ticket now has a strong resolution signal.
The configured Ticket Profile can determine what happens next.
Staff Takeover Does Not Bypass Closing Rules
A staff member resolving the concern does not necessarily mean the ticket should instantly close.
Existing closing behavior should still apply.
Depending on your configuration, this may include:
- Member confirmation
- Staff closing action
- AI-assisted resolution detection
- Closing proposal
- Knowledge Base review
- Transcript generation
- Other closing rules
Staff Takeover should integrate with the same ticket lifecycle.
Returning From Staff Takeover
Depending on your configuration, a ticket may return to AI-assisted behavior when human handling is no longer active.
For example, staff may complete a manual action and leave the member with a normal informational follow-up.
Whether Novus AI resumes automatic assistance depends on your ticket configuration.
Avoid switching repeatedly between AI and staff in a way that makes the conversation unpredictable.
Escalation and Ticket Rerouting
Sometimes the issue does not require immediate human escalation but does belong to another support category.
For example:
The member opens General Support but reports a transaction problem.
If Payment Support has a different workflow or staff team, ticket rerouting may be more appropriate.
Rerouting changes the support destination.
Escalation indicates that human assistance is required.
The two can also work together when necessary.
Security During Escalation
Human escalation does not change the rules around sensitive information.
Novus AI should still never ask the member to provide:
- Passwords
- OTPs
- Authentication codes
- Recovery codes
- API secrets
- Private credentials
Staff workflows should also use safe verification procedures.
Escalation Should Be Clear to Members
When a concern is escalated, the member should understand why AI can no longer complete the request.
For example:
"This requires manual transaction verification, so a staff member will need to review the ticket."
This is clearer than simply stopping responses without explanation.
Avoid exposing unnecessary internal routing or system information.
Test Successful AI Resolution
When testing escalation, first verify that a concern that AI can resolve does not escalate.
For example:
Ask a documented question.
Confirm that:
- Novus AI finds the appropriate Knowledge.
- It provides the correct response.
- No unnecessary staff notification occurs.
This confirms that your escalation rules are not too aggressive.
Test Manual Escalation Scenarios
Create a ticket that clearly requires human action.
For example:
"My completed transaction needs manual verification."
Verify that:
- The correct AI Route is selected.
- AI provides any required preliminary instructions.
- The correct escalation behavior occurs.
- The appropriate staff destination is used.
- The member remains in the same ticket.
- Existing conversation context is preserved.
Test Exhausted Troubleshooting
Create a Technical Support ticket.
Follow the available troubleshooting until all documented options are exhausted.
Verify that Novus AI does not:
- Repeat the same steps indefinitely
- Invent new unsupported fixes
- Pretend the problem is resolved
Instead, it should follow the configured escalation process.
Test Staff Takeover
After escalation, have a staff member begin responding.
Verify that:
- Staff can access the ticket.
- The member can continue responding.
- Novus AI does not unnecessarily compete with staff.
- Previous AI context remains available.
- Any configured AI Summary is available where expected.
- Staff can complete the support process normally.
Test Repeated Member Messages
After staff has been notified, send several additional messages as the ticket holder.
Verify that Novus AI does not repeatedly notify the same staff group unless your workflow explicitly requires it.
This is especially important in busy support systems.
Test Resolution After Staff Takeover
After staff resolves the concern, have the member confirm:
"It's fixed now, thank you."
Verify that the ticket can continue through:
- Resolution detection
- Closing behavior
- Transcript processing
- Knowledge Base processing when applicable
- Final ticket closure
Staff Takeover should not break the later stages of the ticket lifecycle.
Escalation Testing Checklist
Before relying on your escalation workflow, verify that:
- AI resolves documented concerns without unnecessary escalation.
- Missing Knowledge is handled appropriately.
- Manual actions trigger escalation when required.
- Exhausted troubleshooting can transition to staff.
- The correct staff group is used.
- Staff is not repeatedly mentioned.
- Ticket context is preserved.
- Ticket Form information remains available.
- Previous AI troubleshooting remains visible.
- AI Summary works when configured.
- Staff Takeover prevents competing AI responses.
- Members retain appropriate ticket access.
- AI does not falsely claim staff is already working.
- Resolution still works after staff intervention.
- Closing rules remain intact.
- Knowledge processing still occurs when configured.
Next Step
Once a ticket has been handled by AI, staff, or both, the system needs a reliable way to determine when the member's concern is actually complete.
The next step is configuring how Novus AI recognizes successful resolutions without prematurely closing active support conversations.
Continue to Ticket Resolution Detection & Confirmation.