Ticket Request Command
Ask a member to open a ticket, and customize the direct message they receive.
/request ticket sends a member a direct message asking them to open a ticket, with a button that opens it on the panel you chose. Use it when a conversation belongs in a ticket and you would rather the member started it themselves, so they answer the panel's form and the ticket is theirs.
Access the Web Dashboard
Open your Tickety Dashboard. Log in using your Discord Account.
Navigate to Ticket Request Command
-
Once logged in, locate and click on the "Configuration" section under Tickets in the sidebar.
-
Select "Ticket Request Command" from the configuration options.
Using the command
Your Tickety admin role, the support roles of the panel you pick, and anyone with Manage Channels can run /request ticket.
| Option | What it does |
|---|---|
user | Required. The member to send the request to |
panel | Required. The ticket panel their ticket opens on. Start typing and your panels are suggested |
reason | Optional. Why you are asking, up to 1024 characters. It is shown to the member in the request |
You get a private Ticket Request Sent confirmation naming the member and the panel.
What the member receives
The member gets a direct message titled Ticket Requested by default, telling them your server has asked them to open a ticket and listing who asked, the panel and the reason. Under it is a Create Ticket button.
Pressing it opens the ticket the same way clicking the panel would, so the panel's blacklist, required roles, blocked roles, open ticket limits, cooldown and form all still apply. When the ticket opens they are told Ticket Created with a link to their new channel.
Nothing about the request expires, so a member can press the button later in the day.
When a request does not go through
| Situation | What you are told |
|---|---|
| You picked a bot | Invalid User, You cannot send a request to a bot. |
| The member has left the server | User Not In This Server |
| Their direct messages are closed | Request Not Delivered, with a link to the opening DMs page you can pass on |
| The command is turned off | Request Command Disabled |
Turning the command off also stops the buttons on requests you already sent. Anyone pressing one after that sees Request Command Disabled.
Command Settings
- Command Enabled - Turns
/request ticketon or off for your whole server.
Ticket Request Embed
The direct message the member receives, with the Create Ticket button under it.
The editor opens with a Message layout choice:
- Embeds - Coloured panels with text and fields. Available on every plan.
- Components 👑 - Text, images and buttons in any order.
In Components layout the Create Ticket button shares the message's room with your own blocks.
Placeholders
The message is written for the member receiving it, so {member.*} is them and the staff member who sent the request has tokens of their own:
{request.reason}- The reason you typed, orNo reason provided.when you left it empty.{request.staff.mention},{request.staff.displayName},{request.staff.username}and{request.staff.id}- Who sent the request.{panel.name},{panel.emoji},{panel.supportRoles}and{panel.openTickets}- The panel their ticket will open on.{member.mention}and the rest of the member tokens,{guild.name}, your{statistics.*}tokens and{currentTime}.
The full catalogue is on the Placeholders page.
Defaults and limits
Command Enabled is on by default.
| Free | Premium | |
|---|---|---|
Reason on /request ticket | 1024 characters | 1024 characters |
| Components message layout | no | yes |
| Embeds on one message | 2 | 5 |
| Fields per embed | 1 | 25 |
This feature requires a Premium Subscription.