# Tickets
## Configure
1. Install Waya on your server by going to [get.waya.one](https://get.waya.one).
2. Run the `/config` command and go to the **Starboard** tab.
3. Set a *#category* channel. ([Need help?](https://lunish.nl/support))
4. Configure anything as you want, when you're unsure what something does, read below.
5. π Done!
Ticket thread example
## Config Options
### π Edit Category
{% hint style="info" %}
**Note:** There is a 500 max channel limit per guild.
{% endhint %}
{% hint style="warning" %}
**Warning:** There is a 50 channel limit per category, please use ticket threads or `no_category` if you exceed this.
{% endhint %}
Change the category or channel where tickets should be created at.
* `#category` - Creates a channel in a category.
* `#channel` - Creates a private threat on any text based channel.
* `no_category` - Creates a channel on top of the channel list.
{% hint style="warning" %}
Require bot permissions in the ticket channel/category:\
`ViewChannel`, `SendMessages`, `ReadMessageHistory`, `SendMessages`, `AttachFiles`, `EmbedLinks`, `AddReactions`, `UseExternalEmojis`, `ManageMessages`
{% endhint %}
### 𧻠Edit Role
Assign a specific staff role that grants access and triggers notifications for new tickets. This role will automatically get the `ManageChannel` permission.
### π« Enable/Disable Open reason
Make it a requirement for members to include a reason when creating a ticket.
### π§Ί Enable/Disable Leave Autoclose
Delete the ticket when the creator leaves the server.
### π Position: To top/bottom
Modify the placement of newly created tickets relative to existing ones, determining whether they appear at the top or bottom of the list.
### π Change Logging Channel
Create a dedicated channel to keep track of ticket closures and let staff members add a reason when closing a ticket.\
### π« Force Reason
Require your staff members to provide a reason when closing a ticket.
### π Save transcript
Generate a `.html` file that captures and preserves all messages exchanged within the ticket. This file is automatically saved and persists even after the ticket is deleted. It is sent to the ticket logs and shared with the ticket creator.\
{% embed url="" %}
Example transcript
{% endembed %}
### π Channel Naming
Chose how new tickets should be named.
* Username: `#ticket-mwlica` (Inappropriate usernames may result in removal from discovery)
* User Id: `#ticket-821472922140803112`
* Random: `#3hvyag`
### π Change (Un)claimd Embed
Customize your whole ticket's message embed for the claimed and unclaimed state! Modify the title, description, thumbnail, image, and even the embed color.\
### πΌ Change Claim/Close Emote
Change the emotes at both the Claim and the Close button. This can be any default Discord emote or a custom emote **from the same server**.\
## Commands
A few useful commands for managing tickets.
### π₯ Add a member to a ticket
{% content-ref url="/pages/YNHWB4PxgABMouddlnpV" %}
[wa add](/text-commands/wa-add.md)
{% endcontent-ref %}
### π€ Remove a member from a ticket
{% content-ref url="/pages/8Mv2C7zaMZKf1L9zvzdb" %}
[wa remove](/text-commands/wa-remove.md)
{% endcontent-ref %}
### π΅ Close/Delete a ticket
{% content-ref url="/pages/E0LX7uJz4nvAN4dWLVCH" %}
[wa close](/text-commands/wa-close.md)
{% endcontent-ref %}
### β Request ticket closure
{% content-ref url="/pages/cKkR9lMLiBJ2LKJbpZzF" %}
[wa closerequest](/text-commands/wa-closerequest.md)
{% endcontent-ref %}
## Conclusion
Maximize your ticket management with Waya Ticketsβa free and highly customizable solution. Unlike other bots, Waya offers extensive customization options, allowing you to tailor your ticketing system to fit your unique needs. Enjoy the freedom to configure categories, channels, and ticket requirements according to your team's preferences. Say goodbye to limitations and costly subscriptions. Choose Waya Tickets for unmatched customization capabilities and elevate your customer support experience.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.waya.one/utilities/tickets.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.