> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/pos/waiting-room.md).

# Waiting Room

The Waiting Room is a holding area for orders before they reach the kitchen displays. Orders placed in the waiting room will not be cooked or prepared until explicitly released to the kitchen.

If a venue has the Waiting Room enabled, each service can be configured to **use or skip** the Waiting Room.

{% hint style="info" %}
To set the service(s) that use the Waiting Room, please contact support.
{% endhint %}

## Configuration

The Waiting Room can be **enabled** or **disabled** for a venue.

1. In the POS, go to **Settings**.
2. Click **Venue config**.
3. Toggle **Waiting room** on or off to enable or disable.
4. Click **Save**.

When enabled, the Waiting Room icon will be available and new orders for service types that use the Waiting Room will appear in the Waiting Room screen, instead of being sent directly to the kitchen.&#x20;

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2Fxf7U4h4KBASKfRwFMgJb%2Fimage.png?alt=media&amp;token=b44d76a4-5d2e-4c96-a7c4-762e383e0dc1" alt=""><figcaption></figcaption></figure>


---

# 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://docs.bossithq.com/pos/waiting-room.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.
