Application Request Command
Ask a specific member to apply, and customise the message they receive.
Sometimes you do not want to wait for someone to find your panel. /request application asks one member directly: they get a direct message from Tickety with a Start Application button, and pressing it starts the application there and then.
This page controls whether the command is available and what that direct message says.
Access the Web Dashboard
Open your Tickety Dashboard. Log in using your Discord Account.
Navigate to Application Request Command
-
Once logged in, locate and click on the "Configuration" section in the sidebar under the APPLICATIONS category.
-
Select "Application Request Command" from the configuration options.
Command Settings
- Command Enabled - Turns
/request applicationon or off for your server. On by default. When it is off, running the command repliesRequest Command Disabled, and a button from a request you already sent stops working too.
Using the command
/request application takes three options:
| Option | What it is |
|---|---|
| user | Required. The member you are asking to apply. |
| panel | Required. Start typing an application panel name and pick it from the list. Only enabled panels are offered. |
| reason | Optional. Why you are asking. Up to 1024 characters, and it is shown to the member in their message. |
Anyone in this list can run it:
- The panel's Review Role. This works on its own, without any Discord permission.
- Your Tickety admin role.
- Anyone with the Administrator permission.
- Any role you allowed through Command Permissions.
You get a private confirmation that the member has been asked to apply.
What the member receives
The member gets your Application Request Embed in their direct messages, with a Start Application button under it.
Pressing that button starts the application the same way the panel button does, so the panel's own rules still apply. If the panel uses Discord DMs, the confirmation message appears right there in the same conversation. If it uses Website, they get a private link to fill it out in the browser instead.
A request is an invitation, not an exemption. Required roles, blocked roles, the pending application limit and the panel's cooldown are all still checked when the member presses the button.
Application Request Embed
The direct message itself. It starts as an embed titled Application Requested, telling the member who asked, which application it is for, and the reason you typed.
The editor handles the whole message: several embeds, colours, titles, descriptions, images and footers. The Start Application button always rides along underneath, so a little of the message budget is reserved for it. Premium servers can switch the message to the components layout instead of embeds.
Placeholders you can use
The message is read by the member you asked, so {member.*} is them and the staff member who sent the request is under {request.staff.*}. Mixing those two up is the most common mistake here.
| Placeholder | What it becomes |
|---|---|
{member.mention} | The member being asked to apply |
{member.displayName} | Their display name in your server |
{panel.name} | The application panel you picked |
{request.staff.mention} | The staff member who sent the request |
{request.staff.username} | Their username |
{request.reason} | The reason you typed, or nothing when you left it empty |
{guild.name} | Your server name |
The Placeholders page lists everything Tickety understands, and the editor shows you what is available for this message as you type.
When a request does not go through
| Reply | What happened |
|---|---|
Invalid User | You picked a bot. Requests only go to people. |
User Not In This Server | The member is not in your server, so there is nothing to ask them to apply for. |
Request Not Delivered | Their direct messages are closed. Ask them to open them and try again. |
Application Panel Missing | The panel was deleted or disabled between you picking it and the command running. |
If you hit Request Not Delivered often, point your members at How do I open my DMs?. Nothing can be delivered until they do.
Where to go next
- Application Command: let members start an application themselves with
/apply. - Reviewing Submissions: what happens once the application comes back.
- General Settings: cooldowns, automatic actions and default reasons.
- Making a Basic Application Panel: build the panel you are requesting.