> For the complete documentation index, see [llms.txt](https://cast-wiki.gitbook.io/cast-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cast-wiki.gitbook.io/cast-wiki/faq/how-do-i-make-a-good-ticket.md). # How do I make a Good Ticket? A good tickets has many factors, if you want your appeal, or billing issue or whatever it may be to get accpect you need to follow the guide below! ## How do I make a Good Ticket? #### Format Be sure your ticket is well formatted to make it easier and quicker for staff to understand. #### Honest Please be honest, wheater it is a staff app or appeal, we love honesty and it will make it more likely for whatever you are making the ticket for to go through. #### Readable Please, make sure your ticket is readable, make sure it has good spelling. Don't swear, make it nice for the staff member on the other side so they reply promptly. #### Professinal Try to keep it professional. Don't say idk, bc, tbh, Try to say "I don't know", "Because", "To be honest", as our staff team comes from all different backgrounds and might not understand these words. ### Examples of a Good & Bad Ticket #### A Good Ticket `BradleyPlayzz = Player` `VaseTheDoodle = Staff` #### A Bad Ticket `BradleyPlayzz = Player` `VaseTheDoodle = Staff` --- # 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://cast-wiki.gitbook.io/cast-wiki/faq/how-do-i-make-a-good-ticket.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.