Skip to main content

​
Transcripts

When a ticket closes, its full conversation is saved automatically — messages, authors, timestamps, embeds and form answers. Nothing to configure.
tickets transcript aliases: transcriptpull, transcriptget, transcriptcase. tickets transcripts alias: mytranscripts. Members can pull their own transcripts without any permission. Staff can pull anyone’s.
Transcripts survive the channel being deleted. That’s the point — you can set an aggressive autodelete to keep the sidebar clean and still have the full record months later.

​
Statistics

Server stats cover ticket volume, how many are open, and how they break down by panel and option. Member stats show how many they’ve opened, how many they’ve claimed, and how many they’ve closed.
Worth checking monthly. Two things usually show up: one staff member handling most of the volume, and one ticket option nobody ever picks. Both are worth acting on.

​
Managing open tickets

Every currently open ticket, who opened it, which option, and whether it’s claimed. The fastest way to spot tickets that have been sitting unclaimed.

​
Closing and deleting

Run inside the ticket, or pass a channel to act on another one. The distinction matters: close is immediate, delete honours the delete delay so there’s a window to reopen. Most staff want close; the delay exists for automated deletion.

​
Claiming

Claiming marks who’s responsible, and — depending on the option’s permission flags — may hide the ticket from other staff or stop them speaking. It can also move the channel to a different category and rename it. unclaim releases it back to the pool.

​
Retention

Ticket channels and transcripts are separate. Transcripts are kept independently of both, so deleting a channel doesn’t lose the record. A reasonable retention shape:

​
Command reference