Support Tickets Commands
A full support platform — departments, intake forms, SLA clocks, routing and transcripts. Members open tickets from a panel and work entirely from buttons; /ticket is the staff keyboard surface.
A full support platform — departments, intake forms, SLA clocks, routing and transcripts. Members open tickets from a panel and work entirely from buttons; /ticket is the staff keyboard surface.
Run inside a ticket channel, except /ticket staff. Not one subcommand writes a ticket itself — they all call the same executor the buttons and the dashboard do, so SLA clocks, the event history, metrics, webhooks and automation triggers all apply. Closing is deliberately not gated: the member who opened a ticket may close it, until somebody else replies.
| Command | What it does | Permission |
|---|---|---|
/ticket close [reason] [note]
|
Close this ticket. The reason is autocompleted from your server’s close reasons. | Claim Ticket |
/ticket claim
|
Take ownership. Respects the assignee’s concurrency cap. | Claim Ticket |
/ticket unclaim
|
Return this ticket to the queue. | Claim Ticket |
/ticket assign <member>
|
Assign this ticket to another staff member. | Claim Ticket |
/ticket reply <shortcut>
|
Send a saved reply, rendered with the same {token} vocabulary the automation engine uses. | Claim Ticket |
/ticket staff <availability>
|
Set your own availability. The one subcommand that works outside a ticket channel. | Claim Ticket |
/ticket status <state>
|
Move this ticket to another state. | Change Ticket Status / Priority |
/ticket priority <level>
|
Change this ticket’s priority. | Change Ticket Status / Priority |
/ticket transfer <department>
|
Hand this ticket to another team. | Transfer Ticket |
/ticket note <text>
|
Add a staff-only note. The member never sees it. | Add Internal Note |
/ticket add <member>
|
Add a member to this ticket. | Add / Remove Ticket Members |
/ticket remove <member>
|
Remove a member from this ticket. | Add / Remove Ticket Members |
/ticket rename <name>
|
Rename the ticket channel, following your naming scheme. | Add / Remove Ticket Members |
The rest of the platform is driven by buttons, so members need no commands at all.
| Command | What it does | Permission |
|---|---|---|
Open a ticket
|
The panel button members press — picks a department, runs its intake form and creates the channel. | Everyone |
Close
|
Close with a reason picker. Open to the member who opened the ticket until anybody else replies. | Everyone |
Claim / Unclaim
|
Take or release ownership from the control panel. | Claim Ticket |
Status / Priority / Transfer
|
The same transitions as the commands, from the control panel. | Change Ticket Status / Priority |
⭐ Rating
|
The satisfaction stars on the close DM. One rating per ticket. | Everyone |
Every other part of Azra that adds commands to your server.
Text commands
Every text command is shown with the default ! prefix. Your server can change it
(!prefix <new>, or the dashboard), and @mentioning the bot always works as a prefix
whatever you set — so @Azra help is a reliable way back in if you forget it.
Permissions
Azra does not read Discord's own permissions to decide who may run what — it has its own
Permission Manager, and the server owner and Discord Administrators always hold everything.
A capability is an action, not a command path: denying Ban blocks /mod ban,
!ban and the right-click Quick Ban together, so a restriction cannot be dodged by switching surface.
If a command does not appear in Discord
- Commands register globally and can take a few minutes to show up after the bot joins. Fully restarting your Discord client usually settles it.
- Check the module is switched on for your server, and that your plan covers it — see Plans.
- A command you cannot see may simply not be granted to you.
/permissions viewshows exactly what a member or role holds.