Ticket System

#14-Native Ticket Transcripts, Closing & AI Summary

Learn how Novus handles native ticket transcripts, transcript destinations, ticket-owner copies, closing delays, AI-generated summaries, resolution outcomes, and archive workflows after a ticket reaches the end of its support lifecycle.

Updated 8/28/2026, 11:22:19 PM

Closing a support ticket involves more than simply deleting a Discord channel.

A completed ticket may contain important information such as:

The member's original concern
Form responses
AI troubleshooting
Staff responses
Escalation history
Final resolution
Resolution confirmation
Knowledge Base recommendations

Novus In-House Ticketing is designed so these records can be processed as part of the native closing workflow.

Ticket Closing Lifecycle

A typical native ticket may follow this lifecycle:

Ticket Created

↓

AI or Staff Assistance

↓

Issue Resolved or Support Ends

↓

Closing Process Begins

↓

Transcript Processing

↓

AI Summary Processing

↓

Knowledge Review When Applicable

↓

Final Ticket Closure

↓

Discord Channel Removed After Configured Delay

The exact flow may depend on the Ticket Profile and enabled features.

Resolution Is Not the Same as Closing

A ticket can be resolved before it is actually closed.

For example:

The member says:

“It works now, thank you.”

The issue may now be considered resolved.

However, Novus may still need to:

Generate the transcript
Produce the AI Summary
Check for reusable Knowledge
Send the transcript to its destination
Complete closing metadata

before deleting the channel.

Conceptually:

Active

→ Resolved

→ Closing

→ Closed

Unresolved Tickets Can Also Close

Not every closed ticket is resolved.

A ticket may close because:

The member stopped responding
The member abandoned the concern
Staff manually ended the ticket
No additional action was possible
The ticket was created accidentally
The concern was outside the supported scope

These outcomes should not automatically be marked as successful resolutions.

Why Closing Reason Matters

Consider these two tickets.

Ticket A

Status: Closed
Outcome: Resolved

Ticket B

Status: Closed
Outcome: Inactive

Both are closed, but their support results are very different.

This distinction matters for:

Reports
AI Summary
Knowledge Base analysis
Google Sheets mapping
Support performance statistics

Default Transcript Destination

Novus In-House Ticketing includes a configurable default transcript destination.

For example:

Default Transcript Channel

#ticket-transcripts

The configuration uses an admin-only Discord channel selector so transcript records can be kept away from normal member-facing channels.

Example Transcript Structure

A server might use:

STAFF

#support-team
#ticket-transcripts
#ticket-logs

When a native support ticket closes, the resulting transcript can be sent to the configured transcript channel.

Protect Transcript Channels

Transcript channels may contain information that should not be visible to all server members.

Restrict them to the appropriate staff roles.

For example:

#ticket-transcripts

Visible to:

Administrators
Support Leads
Support Staff

Not visible to:

Normal Members

Global Transcript Destination

Free configurations use a global transcript destination as part of the native ticketing setup.

For example:

All Ticket Categories

→ #ticket-transcripts

This is simple and works well for smaller communities.

Premium Category-Specific Transcripts

Premium native ticketing provides the foundation for per-category transcript destinations.

This allows different ticket categories to archive transcripts in different Discord channels.

Example Per-Category Mapping

General Support

→ #general-transcripts

Technical Support

→ #technical-transcripts

Payment Support

→ #payment-transcripts

Applications

→ #application-transcripts

This is especially useful when different departments should not automatically access each other's records.

Use Global Transcript When No Override Is Needed

You do not need an individual transcript channel for every Ticket Category.

For example:

General Support

→ Use Global Transcript Channel

Technical Support

→ Use Global Transcript Channel

Payment Support

→ #private-payment-transcripts

Only the sensitive Payment category uses an override.

The native configuration supports retaining the global transcript destination as the normal fallback when a category does not require its own destination.

Sending a Transcript to the Ticket Owner

Novus also includes a native configuration foundation for sending a transcript to the ticket owner.

This may be useful when members need a record of:

Technical instructions
Application discussion
Support decisions
Final troubleshooting steps

When Member Transcript Delivery May Not Be Appropriate

Consider disabling ticket-owner transcript delivery for workflows containing:

Internal staff notes
Sensitive administrative discussions
Fraud investigation details
Security-related information
Other staff-only content

Transcript delivery should match the privacy requirements of the ticket category.

Ticket Delete Delay

Novus includes a configurable delay before closed native ticket channels are deleted.

The implementation requires a minimum delay of 5 seconds.

This delay allows closing-related processes to complete.

Why Not Delete Immediately?

Imagine this sequence:

Member selects Close

↓

Discord channel is instantly deleted

↓

Transcript processing begins

If required information depended on the channel still being available, an immediate deletion could cause problems.

Instead:

Member selects Close

↓

Novus starts closing

↓

Transcript and summary processing complete

↓

Configured delay expires

↓

Channel is removed

This is safer.

Example Delete Delay

A community may configure:

Closed Ticket Delete Delay

30 seconds

This gives staff and automated processes a brief period to complete closing operations.

A larger or more complex workflow may choose a longer delay.

AI Ticket Summary

The native ticketing foundation also includes support for Premium AI Summary functionality.

An AI Summary is different from a transcript.

Transcript

Contains the detailed conversation.

AI Summary

Condenses the important outcome into a shorter support record.

Example AI Summary

A Technical Support ticket might produce:

Issue

Member could not launch the client after applying the latest patch.

Troubleshooting

Verified client version, checked missing files, and replaced the affected configuration file.

Resolution

Member confirmed that the client launches normally after replacing the configuration file.

Outcome

Resolved

Escalation

Not required

This is much faster for staff to review than reading the entire transcript.

AI Summary After Staff Takeover

The AI Summary can still be useful even when staff handled the final resolution.

For example:

Issue

Account login failure.

AI Assistance

Basic troubleshooting completed.

Staff Intervention

Required manual account verification.

Final Resolution

Staff corrected the account status.

Member Confirmation

Member confirmed successful login.

This creates one concise record of the entire ticket lifecycle.

Summary Should Reflect the Actual Outcome

Novus should not describe an unresolved ticket as resolved simply because the ticket closed.

For example:

Bad

Resolution: Issue fixed.

when the member never confirmed anything.

Better:

Outcome

Closed due to inactivity.

Last Known Status

Suggested troubleshooting was provided, but the member did not confirm whether it resolved the problem.

Resolution Confirmation

Strong resolution signals may include statements such as:

“It works now.”

“That fixed it.”

“I can login now.”

“Problem solved.”

These indicate an actual support outcome.

Simple responses such as:

“Okay.”

“Thanks.”

“I'll try it.”

do not necessarily confirm that the issue was resolved.

Inactivity Is Separate From Resolution

If a member stops responding, Novus may eventually close the ticket according to configured inactivity behavior.

However:

Inactive ≠ Resolved

This distinction should remain visible in:

Ticket summaries
Reports
Google Sheets data
Knowledge Base analysis

AI Summary and Knowledge Base Review

A resolved ticket may contain a new solution useful for future members.

Novus already supports resolution analysis that checks whether:

Similar verified Knowledge already exists
Related Knowledge exists
No sufficiently similar verified resolution exists

If a new reusable solution is identified, staff can receive the option to:

Add to Knowledge Base

or:

Ignore

Transcript Is Not Automatically Knowledge

A full transcript should not automatically become a Knowledge Base entry.

A transcript may contain:

Failed troubleshooting
Incorrect assumptions
Irrelevant conversation
Member-specific details
Sensitive information
Staff-only discussion

Knowledge should contain the verified reusable solution, not the entire conversation.

Example Transcript vs Knowledge

Transcript

Member:

“My launcher keeps crashing.”

AI:

“Try restarting your PC.”

Member:

“Still doesn't work.”

Staff:

“The installation contains an outdated configuration file. Replace config.dat with the current version.”

Member:

“Working now.”

Knowledge Entry

Issue

Launcher crashes after update.

Cause

Outdated configuration file.

Solution

Replace the outdated configuration file with the current version.

The Knowledge entry removes unnecessary conversation while preserving the reusable solution.

Google Sheets Closing Mapping

When a Google Sheets integration is enabled, closing information can be useful for support tracking.

For example:

Sheet Column	Novus Source
Ticket ID	Native Ticket ID
Category	Ticket Category
Member	Ticket Owner
Created At	Created Date
Closed At	Closed Date
Outcome	Final Outcome
Resolution	AI Resolution Summary
Escalated	Escalation Status
Staff Required	Staff Intervention
Transcript	Archive Reference

This creates a structured index of completed tickets.

Example Closed Ticket Row

A completed Technical Support ticket could become:

Ticket ID	Category	Outcome	AI	Staff
NOVUS-1042	Technical Support	Resolved	Yes	No

An inactive ticket might become:

Ticket ID	Category	Outcome	AI	Staff
NOVUS-1043	General Support	Inactive	Yes	No

They should not be reported as the same outcome.

Google Drive Transcript Archiving

When Google Drive integration is available or enabled, the full transcript can be archived externally.

For example:

Drive Folder

Novus Ticket Archive

↓

Technical Support

↓

2026

↓

08-August

↓

NOVUS-1042-transcript.html

This creates a long-term support archive independent of Discord.

Mapping Different Ticket Categories

A larger organization might configure:

General Support

→ /Novus Archive/General/

Technical Support

→ /Novus Archive/Technical/

Payment Support

→ /Novus Archive/Payment/

Applications

→ /Novus Archive/Applications/

This mirrors the Discord ticket structure.

Combined Closing Workflow

A mature Novus ticket workflow could eventually look like:

Ticket Resolved

↓

AI Summary Generated

↓

Knowledge Analysis

↓

Staff Accepts or Ignores Knowledge Candidate

↓

Discord Transcript Sent

↓

Google Sheets Record Updated

↓

Google Drive Transcript Archived

↓

Delete Delay Expires

↓

Ticket Channel Removed

This provides both operational records and reusable support knowledge without treating every system as the same data store.

Google Sheets vs Google Drive vs Knowledge Base

Use each destination for the purpose it is best suited for.

Google Sheets

Structured reporting and tracking.

Examples:

Ticket ID
Category
Member
Status
Dates
Outcome
Escalation

Google Drive

Full file archive.

Examples:

Transcript
Exported report
Summary document
Attachments

Knowledge Base

Reusable verified support information.

Examples:

Troubleshooting procedure
Known issue
Verified workaround
Policy explanation

This separation helps keep Novus data organized.

Example Payment Ticket Policy

For Payment Support, you might configure:

Discord Transcript

#payment-transcripts

Member Transcript

Disabled

Google Sheets

Store only:

Ticket ID
Member
Transaction reference
Verification result
Final outcome

Google Drive

Restricted payment-support folder

Knowledge Base

Only general payment procedures—not member-specific transaction data.

This provides stronger separation for sensitive support workflows.

Example Bug Report Workflow

For Bug Reports:

Transcript

#bug-transcripts

Google Sheets

Development Bug Tracker

Google Drive

Optional full transcript archive

AI Summary

Enabled

Knowledge Review

Enabled when a verified workaround or solution was discovered

This can create a lightweight support-to-development pipeline.

Example Application Workflow

For Streamer or Guild Applications:

Transcript

#application-transcripts

Google Sheets

Application Tracker

Google Drive

Application archives

Knowledge Base

Normally not needed unless the ticket produced a reusable policy clarification.

Not every category should feed the Knowledge Base equally.

Closing After Staff Takeover

If a staff member takes over the ticket, the native ticket should still continue through its normal closing pipeline.

Staff takeover should not bypass:

Transcript processing
Summary generation
Closing status
Archive handling
Knowledge review where appropriate

The final record should show that staff intervention occurred.

Closing After AI-Only Resolution

If Novus AI completely resolves the issue and the member confirms success, staff intervention may not be required.

For example:

Issue

Member cannot update launcher.

Provides verified update procedure.

Member

Confirms update successful.

The closing workflow can record:

AI Assisted

Yes

Staff Intervention

Outcome

Resolved

This is useful for measuring how much support is being handled without staff intervention.

Avoid Misleading AI Statistics

Do not count a ticket as AI-resolved simply because AI sent the last message.

AI resolution should require evidence that the actual concern was successfully addressed.

Otherwise reports such as:

AI Resolution Rate

can become inaccurate.

Recommended Transcript Setup for Small Communities

A simple configuration could be:

Default Transcript Channel

#ticket-transcripts

Per-Category Overrides

None

Send Transcript to Owner

Enabled

AI Summary

Enabled if available

Delete Delay

30 seconds

This is easy to manage.

Recommended Setup for Larger Communities

A more advanced configuration might use:

General

→ #general-transcripts

Technical

→ #technical-transcripts

Payment

→ #payment-transcripts

Applications

→ #application-transcripts

with:

Google Sheets

Central ticket reporting

Google Drive

Department-specific archives

AI Summary

Enabled

Knowledge Review

Enabled for support categories

This provides better departmental separation.

Closing Checklist

Before launching native ticket closing publicly, verify that:

Default transcript channel is configured.
Staff can access the transcript channel.
Normal members cannot access staff-only transcripts.
Category transcript overrides are correct where used.
Ticket-owner transcript behavior is configured.
Delete delay is appropriate.
Resolved and inactive outcomes remain separate.
AI Summary reflects the actual ticket outcome.
Staff takeover does not bypass closing processing.
AI-only resolution is recorded accurately.
New Knowledge is reviewed before saving.
Duplicate Knowledge is not created unnecessarily.
Sensitive information is excluded from reusable Knowledge.
Google Sheets mappings use the correct ticket status.
Google Drive archives go to the correct folder.
Payment or sensitive categories use stricter access where appropriate.
Transcript processing completes before the channel is removed.

Next Step

Continue to Using Novus with External Ticket Systems.

That one is important because it will clearly document how Novus works with Ticket Tool or other third-party ticket bots, what Novus can control, what remains under the external provider, transcript limitations, AI closing modes, staff review, and recommended migration from External to NOVUS.