> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/seller-center/seller/support.md).
# Support
### Support Ticket
As a seller, your main channel for communication with the Marketplace Owner is through Support, a ticketing system located within Seller Center. This system is specifically designed to address your inquiries and resolve any issues.
The communication process relies on a ticketing system, requiring you, to initiate the process by filing a ticket. Each interaction with the Support results in the creation of a ticket within the system. Every ticket or "case" is assigned a unique 10-digit code, used as a reference for communication between the Seller and Marketplace Owner.
1. Log in to your Seller Center.
2. Click on **Support** located in the bottom left corner of the screen to open the Support Ticket page.
3. On the Support Ticket page, you can filter your tickets based on seller name, start & end dates, priority, and status to streamline your search.
4. Click on the **Subject** of the related ticket to view messages or your message history.
5. If you have a specific issue pertaining to your account, in the page to the top right corner, click on **+ Create Ticket**.
6. Under **New Support Tickets**, write the **Subject** or **Reply** button of the new support case.
7. In the following section, you can also provide any of the following:
* Write your message
* Select priority
* Upload attachments
8. Choose **Send**.
---
# 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://docs.akinon.com/tutorials/seller-center/seller/support.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.
