> For the complete documentation index, see [llms.txt](https://guides.privatesolution.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.privatesolution.org/payments-and-support/how-a-ticket-works.md). # How a Ticket Works Every Private Solutions order starts and ends with a real person on Discord. Here is how to make it fast. ## Opening a ticket 1. Join our Discord — the invite is on [privatesolution.org](https://privatesolution.org). 2. Click **Open a ticket**. 3. Tell us: what you want to buy, your parts (PC model, motherboard, or what you already own), and what game you play. ## What we do with your ticket * **Before you pay** — we check your parts and confirm the right product. You never buy the wrong thing. * **During setup** — we walk you through it step by step, in your language, at your speed. * **After setup** — your ticket stays open. If anything changes (a game update, a new PC), just ask in the same ticket. ## Making the ticket useful * **Send a screenshot** of the thing you are stuck on. One screenshot saves ten messages. * **Tell us your motherboard model** for XMA — it is the one thing we need. * **One topic per ticket** keeps things clear, but you can have as many tickets as you need. ## What support is NOT * We do not play the game for you or give game advice. * Setup help is included; so is patience. Ask as many questions as you need. {% hint style="success" %} Real person, real answers, no bots between you and us. That is the whole promise. {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guides.privatesolution.org/payments-and-support/how-a-ticket-works.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.