> 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/tickets.md).

# Tickets

## **Overview** <a href="#about-sold-out" id="about-sold-out"></a>

The Tickets screen is an operational screen available from the DinePlan Dashboard that provides a centralized view of ticket records generated during restaurant operations.

Users can use the screen to view, filter, search, and manage ticket records based on a specific date range and ticket type. The ticket list displays key details such as the invoice number, ticket number, member, table, customer, reference number, department, terminal, payment, total amount, and user name. The screen also provides actions such as Refresh, Push, Pull, Excel, Call, and Close for managing and working with the displayed tickets.

## **Open the Tickets** <a href="#open-the-tickets" id="open-the-tickets"></a>

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

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

3. The “Tickets” screen opens.

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

## **Ticket Types** <a href="#ticket-types" id="ticket-types"></a>

The Ticket Type filter provides different categories that allow users to narrow down the ticket list and locate the required records more efficiently. Each option represents a specific type, status, or classification of ticket available in the system.

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

**Available options include:**

* **All Tickets** – Displays all available tickets within the selected date range. This option provides a complete view of the ticket records without applying a specific ticket type filter.
* **Only Open Tickets** – Displays tickets that are currently open and have not yet been closed. This can be used to identify tickets that are still active and may require further processing.
* **Only Closed Tickets** – Displays tickets that have already been closed. This option can be used to review completed ticket transactions.
* **Ticket No** – Allows users to locate tickets based on their ticket number. This is useful when the specific ticket number is known and the user needs to retrieve that particular ticket.
* **Ticket Note** – Displays or filters tickets based on ticket notes. This can help users locate tickets containing relevant notes or additional information.
* **Credit** – Displays credit-related tickets. This option can be used when users need to review tickets associated with credit transactions.
* **Invoice** – Displays invoice-related tickets. This allows users to locate tickets that are associated with invoice transactions.

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

* **Terminal** – Displays tickets related to a terminal. This can be used to review tickets based on the terminal from which they were generated or processed.
* **Edine Tickets** – Displays tickets associated with Edine transactions.
* **NonRevenue** – Displays tickets classified as non-revenue. These tickets are handled separately from regular revenue-generating transactions.
* **ExternalNotSynced** – Displays tickets that have not been synchronized with an external system. This can help users identify tickets that may require synchronization or further attention.
* **NotSynced** – Displays tickets that have not yet been synchronized. This allows users to identify tickets that are pending synchronization, and PUSH them for syncing.
* **PAX** – Displays tickets associated with PAX-related transactions.
* **Hold** – Displays tickets that are currently on hold. This allows users to identify tickets that have been temporarily held and may require further action.
* **Member** – Displays tickets associated with members. This option can be used to locate transactions linked to member records.
* **Table** – Displays tickets associated with tables. This can help users locate tickets based on the table involved in the transaction.
* **Customer** – Displays tickets associated with customers. This allows users to locate tickets linked to a particular customer record.

## **Ticket Fields** <a href="#ticket-fields" id="ticket-fields"></a>

The ticket list displays the following information for each ticket:

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

| **Ticket Field**  | **Description**                                                         |
| ----------------- | ----------------------------------------------------------------------- |
| **I.No**          | Displays the invoice number associated with the ticket.                 |
| **T.No**          | Displays the ticket number.                                             |
| **Q.No**          | Displays the queue number associated with the ticket, where applicable. |
| **Member**        | Displays the member associated with the ticket, where applicable.       |
| **Table**         | Displays the table associated with the ticket.                          |
| **Customer**      | Displays the customer associated with the ticket, where applicable.     |
| **Reference No.** | Displays the reference number associated with the ticket.               |
| **Alternate ID**  | Displays the alternate ID associated with the ticket, where applicable. |
| **Department**    | Displays the department associated with the ticket.                     |
| **Date**          | Displays the date associated with the ticket.                           |
| **Terminal**      | Displays the terminal from which the ticket was generated.              |
| **Open-Close**    | Displays the opening and closing time of the ticket.                    |
| **Payment**       | Displays the payment information associated with the ticket.            |
| **Total**         | Displays the total amount of the ticket.                                |
| **Note**          | Displays any note associated with the ticket.                           |
| **User Name**     | Displays the name of the user associated with the ticket.               |

## **Screen Elements** <a href="#screen-elements" id="screen-elements"></a>

The Tickets screen consists of the following screen elements:

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

| **Screen Element** | **Description**                                                                          |
| ------------------ | ---------------------------------------------------------------------------------------- |
| **From**           | Select the starting date for the ticket search.                                          |
| **To**             | Select the ending date for the ticket search.                                            |
| **Calendar Icon**  | Opens the date picker to select the required date.                                       |
| **Ticket Type**    | Allows users to select the required ticket type for filtering the ticket list.           |
| **Previous**       | Moves to the previous set of ticket records.                                             |
| **Next**           | Moves to the next set of ticket records.                                                 |
| **Refresh**        | Reloads the ticket list using the selected filters.                                      |
| **Push**           | Pushes the selected ticket information where applicable.                                 |
| **Pull**           | Retrieves ticket information where applicable.                                           |
| **Excel**          | Exports the ticket information to an Excel file.                                         |
| **Call**           | Performs the call action for the selected ticket where applicable.                       |
| **Close**          | Closes the Tickets screen.                                                               |
| **Search**         | Allows users to search for a specific ticket or ticket-related information.              |
| **Ticket List**    | Displays the tickets matching the selected date range, ticket type, and search criteria. |
| **Tickets Count**  | Displays the total number of tickets in the current result.                              |
| **Total**          | Displays the combined total amount of the tickets shown in the current result.           |

## **Working with Tickets** <a href="#working-with-tickets" id="working-with-tickets"></a>

Use the options available on the Tickets screen to view, search, navigate, export, and perform applicable actions on ticket records.

### **View and Filter Tickets** <a href="#view-and-filter-tickets" id="view-and-filter-tickets"></a>

To view tickets based on a specific date range or ticket type:

1. Open the “Tickets” screen from the Dashboard.

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

2. In the “From” and “To” fields, select the required date range.

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

3. Select the required “Ticket Type”.

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

4. Click “Refresh”.

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

5. Review the tickets displayed in the ticket list.

**Note:** The ticket list is updated based on the selected criteria.

The Ticket Type filter can be used to display specific ticket statuses. For example:

* **Only Open Tickets** – Displays tickets that are currently open.
* **Only Closed Tickets** – Displays tickets that have been closed.

**Note:** Use **Refresh** whenever you change the date range or **Ticket Type** to reload the ticket list based on the selected criteria.

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

### **Search for a Ticket** <a href="#search-for-a-ticket" id="search-for-a-ticket"></a>

Use the Search field to quickly locate a specific ticket using any relevant information available in the ticket list.

1. Enter the relevant ticket information in the Search field, such as I.No, T.No, Q.No, Member, Table, Customer, Reference No., Alternate ID, Department, Date, Terminal, Payment, or User Name.
2. Review the matching ticket records displayed in the ticket list.
3. Select the required ticket to perform an applicable action.

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

### **Navigate Through Ticket Records** <a href="#navigate-through-ticket-records" id="navigate-through-ticket-records"></a>

When multiple ticket records are available, use the **Previous** and **Next** buttons to navigate through the results.

* **Previous** – Moves to the previous set of ticket records.

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

* **Next** – Moves to the next set of ticket records.

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

### **Export Ticket Information to Excel** <a href="#export-ticket-information-to-excel" id="export-ticket-information-to-excel"></a>

After displaying the required tickets, click **Excel** to export the ticket information displayed on the screen to an Excel file.

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

### **Push and Pull Ticket Information** <a href="#push-and-pull-ticket-information" id="push-and-pull-ticket-information"></a>

The Push and Pull options are available for applicable ticket operations.

* **Push** – Pushes the selected tickets for syncing.

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

* **Pull** – Retrieves ticket information where applicable.

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

**Note:** The Push option is enabled only when NonSynced tickets are selected. This allows users to push non-synchronized tickets for synchronization. The availability or behavior of these actions may depend on the ticket and system configuration.

### **Call a Ticket** <a href="#call-a-ticket" id="call-a-ticket"></a>

Use the Call option to retrieve an order received through a connected online ordering gateway and bring it into the Tickets screen for processing.

1. Click “Call”.

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

2. The available order is retrieved from the connected gateway and added to the ticket list.

For example, an online order received through Foodpanda can be called into the Tickets screen immediately for further processing.

### **Close the Tickets Screen** <a href="#close-the-tickets-screen" id="close-the-tickets-screen"></a>

* Click "Close" to exit the Tickets screen and return to the previous screen.

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

## **Use Cases** <a href="#use-cases" id="use-cases"></a>

* View tickets generated within a specific date range.
* Filter tickets by Ticket Type, such as open or closed tickets.
* Search for specific tickets using available ticket information.
* Review ticket and transaction details for operational reference.
* Navigate through multiple ticket records using Previous and Next.
* Export ticket information to Excel for reporting or record keeping.
* Push Non Synced ticket information or Pull ticket information where applicable.
* Call online orders from connected gateways, such as Food panda, into the Tickets screen for immediate processing.


---

# 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/tickets.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.