> 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/customization-and-branding.md).

# 사용자 지정 및 브랜딩

- [서버 임베드 색상](https://ticketking.xyz/docs/ko/customization-and-branding/server-embed-color.md): 서버의 모든 Ticket King 임베드에 사용되는 강조 색상.
- [봇 개인화](https://ticketking.xyz/docs/ko/customization-and-branding/bot-personalizer.md): 서버에서 Ticket King의 이름, 아바타, 배너, 소개를 사용자 지정하세요.
- [커스텀 환영 임베드 및 메시지](https://ticketking.xyz/docs/ko/customization-and-branding/custom-welcome-embeds.md): 멤버가 새 티켓 안에서 보게 되는 시작 임베드입니다. 티켓 옵션별로 설정하세요.
- [사용자 지정 티켓 이름 형식](https://ticketking.xyz/docs/ko/customization-and-branding/ticket-name-format.md): 새 티켓 채널의 이름 지정 방식. 변수, 문자 제한, Steam 인식 이름 지정까지 포함합니다.
- [임베드 푸터](https://ticketking.xyz/docs/ko/customization-and-branding/embed-footers.md): "Powered by Ticket King" 바닥글과 임베드별 바닥글 텍스트.


---

# 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/customization-and-branding.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.