> 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/tickets.md).

# 티켓

- [티켓 수명 주기](https://ticketking.xyz/docs/ko/tickets/lifecycle.md): 버튼 클릭부터 닫기까지, 티켓이 거치는 모든 상태.
- [티켓 클레임](https://ticketking.xyz/docs/ko/tickets/claiming-a-ticket.md): 클레임 방식의 작동 원리, 네 가지 모드, 그리고 무엇을 선택할지.
- [티켓 닫기](https://ticketking.xyz/docs/ko/tickets/closing-a-ticket.md): Ticket King의 모든 닫기 동작 설정과 각 기능.
- [스레드 티켓 vs 채널 티켓](https://ticketking.xyz/docs/ko/tickets/thread-vs-channel.md): 텍스트 채널 또는 비공개 스레드, 적합한 티켓 스타일 선택하기.
- [티켓 번호 매기기](https://ticketking.xyz/docs/ko/tickets/ticket-numbering.md): 두 개의 토글이 전체 번호 매기기 방식을 제어합니다.
- [열려 있는 티켓 제한](https://ticketking.xyz/docs/ko/tickets/limits-on-open-tickets.md): 사용자별 및 서버 전체에 적용되는 동시 열린 티켓 제한.
- [비활동 규칙](https://ticketking.xyz/docs/ko/tickets/inactivity-rules.md): 조용해진 티켓을 자동으로 닫는 기능으로, 퇴장 시 닫기(무료)와 시간 제한 비활성(프리미엄)이 있습니다.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ticketking.xyz/docs/ko/tickets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.