> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/bot-commands/createticket.md). # /createticket ## CreateTicket Command ### Overview The `/createticket` command opens a ticket for another member. Use it when staff need to start a ticket for someone. ### Usage ``` /createticket [type] [reason] ``` * **user** *(required user mention)*: The member the ticket is for. * **type** *(optional text)*: A label for the ticket. * **reason** *(optional text)*: A short explanation of why you are opening the ticket. ### Description * **Open for a member**: Staff open a ticket for a member. This helps when the member does not know how to open one. * **Label and reason**: A type and reason help organize the ticket, for example "billing" or "technical". * **Style**: The ticket opens as a text channel or a private thread based on the server's "Manual Ticket Style" setting. ### When to Use It * When a member is not sure how to open a ticket. * When staff need to start a ticket for a member and begin the conversation. ### Permissions * You can use this command if you have Manage Channels or Manage Server, or you are the server owner, or you hold an authorized support role. Administrator also works because it includes those permissions. * The bot needs the permission to create the ticket. For a text-channel ticket it needs `Manage Channels`. For a thread ticket it needs `Create Private Threads`. ### Examples ``` /createticket user:@JohnDoe ``` Opens a ticket for John Doe with no type or reason. ``` /createticket user:@JohnDoe type:"billing" reason:"User requested billing support" ``` Opens a ticket labeled "billing" and records the reason. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://ticketking.xyz/docs/bot-commands/createticket.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.