> 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/dineplan/front-desk/about-front-desk.md).

# About Front Desk

## Overview

The **Front Desk** section provides access to important operational functions used to monitor and manage day-to-day restaurant activities. It brings together features that help users review restaurant information, manage item availability, track till transactions, perform audits, handle reservations, and manage messages.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-af3f8a17d330c5090966ffd4dd5f7b080fe141d3%2Fimage%20(133).png?alt=media" alt=""><figcaption></figcaption></figure>

## Screen Elements

The available options in the Front Desk section are:

| Option                | Description                                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Report**            | Provides access to reports that help users review and monitor restaurant activities and transaction-related information. |
| **Sold Out**          | Allows users to manage items that are unavailable for ordering by marking them as sold out.                              |
| **Till Transactions** | Allows users to view and manage transactions associated with the till, helping track cashier-related activities.         |
| **Audit**             | Provides access to audit-related information for reviewing activities and changes performed in the system.               |
| **Reserve**           | Allows users to manage restaurant reservations and related booking activities.                                           |
| **Message**           | Provides access to messages and communication related to restaurant operations.                                          |

## Accessing the Front Desk

To access the **Front Desk** section:

1. Log in to DinePlan.
2. From the Dashboard, select “Front Desk”.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-fb286d290482e6f243d31c9760ea36cb3e26e032%2Fimage%20(163).png?alt=media" alt=""><figcaption></figcaption></figure>

3. The Front Desk screen opens with the available options.
4. Select the required option to access its respective functionality.

## Front Desk Functions

The Front Desk features support different aspects of restaurant operations:

* [**Report** ](/dineplan/front-desk/report.md)– Review operational and transaction information.
* [**Sold Out**](/dineplan/front-desk/sold-out.md#about-sold-out) – Manage the availability of menu items.
* [**Till Transactions**](/dineplan/front-desk/till-transaction.md) – Track till and cashier transactions.
* **Audit** – Review system activities for monitoring and verification.
* [**Reserve**](/dineplan/front-desk/reserve.md) – Manage customer reservations.
* [**Message**](/dineplan/front-desk/message.md) – Access and manage operational messages.

These options provide users with a centralized location to access frequently required operational, transaction, reservation, and monitoring functions without navigating through the main POS workflow.


---

# 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/dineplan/front-desk/about-front-desk.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.
