> 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/order-creation/checkout/urgency-levels.md).
# Urgency Levels
The POS system allows you to set loyalty **urgency levels** on orders to help staff identify and prioritise time-sensitive or high-priority orders.
## Urgency Levels
Urgency level are used to flag specific orders that require immediate attention. When an urgency level is applied to an order, it it moves to the **top of the queue** and it is **highlighted in red** across all screens to ensure visibility.
* **Remake** — used when an order needs to be redone due to an issue with the original (e.g., wrong product sent, preparation error, etc.)
* **Urgent** — applied to time-sensitive orders that require immediate attention
* **Loyalty Tier** — automatically assigned to high-tier or valued loyalty customers as these orders are given priority handling to reflect their status and maintain service expectations
## Applying an Urgency Level
By default, all orders are set to **Regular** urgency. However, you can apply a higher urgency level directly from the checkout screen when needed.
#### To apply an urgency level:
1. On the Checkout page, click on the **Urgency Level** dropdown.
2. Select appropriate **urgency level** for the order.
3. Click **Send** to finalise the order with the selected urgency.
> Loyalty Tier urgency level is applied automatically to eligible customers based on their loyalty status.
---
# 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://docs.bossithq.com/pos/order-creation/checkout/urgency-levels.md?ask=&goal=
```
`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.