Tickets

A member presses the button on the panel; the bot opens a channel that only they and the staff can see, under a Discord category it manages, one open ticket per member. On close the bot writes a transcript, attaches it as a text file to the log and to the member’s DM, and removes the channel.

On means the panel’s button opens tickets. Off leaves the panel where it is but answers “switched off” to a press, and no channel is created.

Every closed ticket lands here with who opened it, who closed it, how many messages it held, and the transcript. When the Logs page has its own ticket-logs channel switched on, that one is used instead.

A category is a kind of ticket with its own staff roles: “Support” for the moderators, “Partnerships” for the owners. With more than one, the member picks one when opening a ticket; with one, the ticket opens straight away. The free plan has one category; Pro as many as you need.

The roles that see every ticket; the blueprint’s moderator and host roles are preselected. The Discord category is where ticket channels are created; when it holds 47 open tickets the bot opens the next one, “Tickets-2”, and a category is removed again when its last ticket closes.

The message with the button, in the channel you pick (the blueprint’s 🎫┃support channel). Design the embed, set the button label (“open a ticket” by default), and Post the panel; posting again edits it in place. Moving it to another channel deletes the old one first, so no orphaned button keeps opening tickets.

What the member reads the moment their channel opens: how to describe the problem, when to expect an answer. {user}, {number}, {category}, {server} and {bot} are filled in.