> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/ko/forms.md).

# 양식

- [옵션 질문이란](https://ticketking.xyz/docs/ko/forms/what-option-questions-are.md): 티켓이 열리기 전에 나타나는 팝업 양식으로, 멤버가 입력하는 맥락이 포함됩니다.
- [질문 유형](https://ticketking.xyz/docs/ko/forms/question-types.md): 모든 양식 질문 유형, 각 유형의 정의, 제한값, 그리고 답변 형식.
- [채널 유형별로 채널 선택 필터링](https://ticketking.xyz/docs/ko/forms/filtering-channel-select.md): 채널 선택 질문을 특정 Discord 채널 유형으로 제한합니다.
- [필수 질문과 선택 질문](https://ticketking.xyz/docs/ko/forms/required-vs-optional.md): 질문을 필수로 만들거나, 멤버가 건너뛸 수 있게 하세요.
- [다섯 질문 제한](https://ticketking.xyz/docs/ko/forms/five-question-limit.md): 옵션당 질문 5개 제한과, 우회 방법이 없는 이유.


---

# 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://ticketking.xyz/docs/ko/forms.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.