Close Workflows
Close tickets gracefully with confirmation dialogs, collect a reason, generate transcripts, and trigger feedback — all automatically.
Illustration only — actual interface and behavior may differ
Every Way to Close a Ticket
Different situations call for different close methods. Choose the one that fits.
Confirmation Close
Standard close with a confirmation dialog. Optionally collect a reason. The user and staff both confirm before the ticket is closed.
Scheduled Close
Tickets auto-close after configurable inactivity. Users are warned before closure and can send a message to reset the timer.
Force Close
Staff can immediately close a ticket without confirmation. Used for spam, duplicates, or when immediate cleanup is needed.
Close Confirmation
Customizable confirmation dialog with close reason, feedback trigger, transcript options, and notification settings.
Close Ticket?
Please confirm that you want to close this ticket. This action will generate a transcript.
Messages
24 messages
Duration
2h 15m
Scheduled Close
Set a timer to auto-close a ticket. A warning message is sent before closing, giving users a chance to respond.
Scheduled Closures
ticket-1231
Closing in 4 hours
ticket-1228
Closing in 30 minutes
ticket-1235
Active — timer reset
Auto-close after 48 hours of inactivity
Illustration only — actual interface and behavior may differ
Force Close
Instantly close spam or abusive tickets without confirmation. Optionally skip transcript generation for unwanted tickets. In Modmail, this is called silent close — use /modmail close silent:True to close a thread without notifying the user.
Illustration only — actual interface and behavior may differ
Close Reason Collection
Require or optionally collect a close reason from staff when they close a ticket. Reasons are stored in the transcript, visible in analytics, and help you understand why tickets are being resolved — or not.
Illustration only — actual interface and behavior may differ
Automatic Transcripts
Every closed ticket generates a full HTML transcript automatically. Transcripts include all messages, embeds, attachments, member activity, and metadata. They are delivered to your configured log channel and optionally to the user via DM.
Transcript Contents
Illustration only — actual interface and behavior may differ
Close Workflows at a Glance
Complete control over how and when tickets are closed.
3
Close Methods
Auto
Transcript Generation
Custom
Inactivity Threshold
Optional
Close Reason
Close Methods for Every Situation
Resolved Issues
The standard close flow. Staff or user confirms the issue is resolved, provides a reason, and the ticket closes gracefully with transcript and feedback.
Abandoned Tickets
Users who stop responding get a warning. If they do not reply within the configured window, the ticket closes automatically — keeping your queue clean.
Spam & Duplicates
Force close spam tickets, test tickets, or duplicates immediately. No confirmation needed — just a quick command and the channel is cleaned up.
Frequently Asked Questions
This is configurable. You can allow users to close their own tickets or restrict closing to staff only.
The channel is deleted, a transcript is saved to your log channel, a feedback prompt is sent (if configured), and the user receives a DM notification.
Ready to Transform Your Support?
Set up professional support in minutes. No coding required. Start with a free trial and explore all features.
This offer is only available for selected servers that have never purchased a plan and never used a free trial before. You do not need to enter any payment information to start the trial and the trial automatically expires after 14 days. Servers that have been deleted from SCNX previously are not able to participate.