> 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/marketplace-owner/support.md).

# Support

### <mark style="color:red;">Support Ticket</mark>

The Support page within the Marketplace Owner's account manages seller inquiries. This page allows for responding tickets, serving as the primary communication platform for sellers. This page is designed for managing and addressing seller inquiries, ensuring seamless communication and issue resolution.

Each instance of seller-Support communication involves the creation of a ticket within the system, displayed on the "Support Ticket" page. 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. Review the list of tickets related to the issue you want to address. Click on the **Subject** or **Reply** button of the ticket that corresponds to your concern to view its details and respond.

   <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F0gyQf4ayxLxXBEdJhCnJ%2Fimage.png?alt=media&amp;token=e45c9dd9-89e4-476c-8203-06f40a0d586d" alt=""><figcaption></figcaption></figure>
5. Within the ticket you can;
   * Assign an Assignee from Seller Center users who can handle the request.
   * Modify the statuses and priorities of requests as needed.
   * Upload visuals or necessary files to provide more context or information.
   * Craft a reply to the message associated with the ticket.
6. After responding to the message, click **Send**.
7. Once the issue is resolved, click **Close Ticket** to mark it as completed.

   <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F0O12PO3tSiCliYM6stcC%2Fimage.png?alt=media&amp;token=04788a70-12ea-4270-9a2a-a5f51fa8a5c0" alt="" width="375"><figcaption></figcaption></figure>


---

# 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/marketplace-owner/support.md?ask=<question>&goal=<user_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.