> For the complete documentation index, see [llms.txt](https://qseller.gitbook.io/yqube-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qseller.gitbook.io/yqube-docs/operations/inquiries.md).

# 문의 관리

쇼핑몰별 고객 문의를 확인하고 QSeller에서 바로 답변합니다.

{% hint style="info" %}
자주 쓰는 답변은 템플릿으로 저장해두면 편리합니다.
{% endhint %}

1. **문의관리** 메뉴로 이동합니다.
2. 쇼핑몰별 고객 문의 목록을 확인합니다.
3. 문의를 선택한 뒤 답변을 작성합니다.
4. **답변 등록**을 클릭하면 해당 쇼핑몰에 자동으로 반영됩니다.


---

# 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://qseller.gitbook.io/yqube-docs/operations/inquiries.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.