Closing, Reopening, & Deleting Tickets

Learn the process for finalizing tickets, generating transcripts, and cleaning up channels.

---

Overview

Closing a ticket in Busybee is a multi-step process that ensures a permanent record of the conversation is saved before the channel is removed from the server.

The Closing Process

1. [Initiate]: Staff can close a ticket via the 🔒 Close button or the /close command.
2. [Scheduled Closure]: Staff can use /closerequest <reason> <time> to schedule a closure.
3. [Confirm]: For immediate closure, a confirmation message is sent.
4. [Transcript Generation]: Busybee scans the channel history and generates a .txt transcript.
5. [Logging]: The transcript and a summary are sent to the Log Channel.
6. [Deletion]: The ticket channel is deleted after a delay (3 seconds for immediate, 10 seconds for automated).

Reopening Tickets

If a ticket has been closed but the channel has not yet been deleted (e.g., during the deletion delay or due to an error), staff can use the /reopen command to restore the ticket's "open" status.

Reference & Configuration Options

State	Behavior
Confirmed	Transcript generated → Logged → Channel deleted.
Cancelled	Confirmation message disappears; ticket remains open.
Reopened	Ticket status reset to 'open'; transcript cleared.

---