> For the complete documentation index, see [llms.txt](https://help.windmillsoft.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.windmillsoft.kr/simplychat/setup/salesforce-install/omni-channel/queues.md).

# 대기열 (Queues)

## 대기열 생성

* 톱니 바퀴![](/files/cB71S78GJaBSKe3hN3TD) > \[설정(Setup)] > 빠른 찾기 상자(Quick Find)에 '대기열(Queues)' 입력 > \[대기열(Queues)] > \[새로 만들기(New)] 

<figure><img src="/files/DU4wO7JiEDvRGjmUTgiJ" alt=""><figcaption></figcaption></figure>

* 각 항목 입력 > \[저장(Save)]를 클릭하여 대기열을 생성합니다.

<figure><img src="/files/AJ91cxMkRs9y37Um6iqk" alt=""><figcaption></figcaption></figure>

## 대기열 항목

<table><thead><tr><th width="242">항목</th><th>설명</th></tr></thead><tbody><tr><td>Label</td><td><p>대기열의 표시되는 이름입니다. </p><p>'SimplyChat'으로 입력합니다.</p></td></tr><tr><td>Queue Name</td><td><p>대기열의 이름입니다. </p><p>'SimplyChat'으로 입력합니다.</p></td></tr><tr><td>Routing Configuration</td><td><p>연결할 라우팅 구성을 선택합니다. </p><p>'SimplyChat'을 선택합니다.</p></td></tr><tr><td>Supported Objects</td><td><p>해당 대기열이 지원되는 개체를 선택합니다. </p><p>'Chat Session'을 선택합니다.</p></td></tr><tr><td>Queue Members</td><td>해당 대기열에 추가될 사용자를 선택합니다.</td></tr></tbody></table>


---

# 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://help.windmillsoft.kr/simplychat/setup/salesforce-install/omni-channel/queues.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.