> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-1/kot/kot-kitchen-instruction.md).
# KOT Kitchen Instruction
**KOT Kitchen Instruction** is a feature used to define and manage special instructions that are sent to the kitchen along with the Kitchen Order Ticket (KOT).
* These instructions help kitchen staff understand **customer preferences or preparation requirements** clearly.
## Steps to Create KOT Kitchen Instruction
Step 1: Navigate through the menu using the following path:
1. **Point of Sale module→ Masters1 → KOT → KOT Table**
2. The KOT Kitchen Instruction screen will open.
Step 2: On the screen:
1. Click the **New** button.
2. A new entry form will appear.
* This allows the user to add a new kitchen instruction.
Step 3: After opening the form,
1. Enter the **kitchen instruction text** that should be sent to the kitchen.
2. Select or enter the **product group name** to which the instruction belongs.
* This helps categorize instructions based on menu sections.
Step 4: After entering all details:
1. Verify the instruction and group name.
2. Click the **Save** button.
* The system will successfully store the kitchen instruction.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-1/kot/kot-kitchen-instruction.md?ask=&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.
