Opens a ticket for a member on a panel you pick. The member owns the ticket, as if they had opened it from the panel themselves.
The bot first applies the server's Command Access rules for /ticket open and checks that Tickets is enabled ("❌ Tickets is not enabled for this server."). The panel list shows the enabled panels that open a ticket channel or thread, as "<name> · #<number>". An unknown panel answers "That panel was not found. Pick one from the list."; a turned off panel answers "That panel is turned off. Turn it on in the dashboard first."; an application panel answers "That panel takes applications, which have no ticket channel. Pick another panel." Tickets cannot be opened for bots ("Tickets can't be opened for bots.") or for someone who is not in the server ("That person is not a member of this server.").
Who may use it: members with Manage Server, managers on the dashboard's Access page and the staff team of the chosen panel. Anyone else sees "Only server managers and this panel's staff team can open tickets for members."
Because staff decided, the panel's rules on who may open tickets, the blacklist, support hours, the cooldown, the open ticket limits and the panel's form are all skipped. You are added to the ticket so you can talk in it, and the bot posts an embed "Opened by staff" in the ticket: "Opened by @you for @member.", with your reason when you gave one (up to 1000 characters). The embed pings nobody. You get a private "✅ Opened #<ticket> for @member."
Good to know
- The opening is recorded in the ticket's "Activity log", with the reason.
- The ticket always opens in a channel or thread the member is added to. Staff cannot start a ticket by DM for a member: only the member can, by writing to the bot.
- To open a ticket from something a member wrote, use the Start ticket message menu. "Who owns the ticket", under "Tickets from a message" on 1 Opening, can make the message's author the owner of that ticket.