> 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/message/faqs.md).
# FAQ's
## 1. How do I open the Message screen in DinePlan from the main dashboard?
To access the internal communication panel from your main screen:
1. Log in to **DinePlan**.
2. From the **"Dashboard"**, select **"Front Desk"**.
3. Select **"Message"**.
**Result:** The **Message** screen opens to display your messages and conversation controls.
## 2. How do I view a list of all incoming messages and active conversations?
To check incoming system notifications or staff messages:
1. Open the **"Front Desk"** module and select **"Message"**.
2. Look at the **"Messages"** list (also known as the **Message List**) on the left panel.
3. Browse the list to see all available messages, notifications, and active conversations.
## 3. How do I review the full message history for a specific conversation?
To read a complete conversation thread:
1. Navigate to **"Front Desk"** → **"Message"**.
2. From the **"Messages"** list, select the required conversation.
3. Review the complete message history displayed in the **Conversation Panel**.
## 4. How do I send a reply to an incoming message in DinePlan?
To respond to a message thread:
1. Open the **"Front Desk"** module and select **"Message"**.
2. From the **"Messages"** list, select the required conversation.
3. Review the existing message history in the **Conversation Panel**.
4. Click inside the **"Reply Here"** text box.
5. Type your response message.
6. Select **Send**.
**Result:** Your reply is sent to the selected conversation, and the thread updates automatically.
## 5. Where do I type my response when replying to a system or user notification?
To locate the text input area:
1. Select the target thread from the **"Messages"** list.
2. Locate the **"Reply Here"** text box located below the conversation view.
3. Type your reply directly into the **"Reply Here"** text field.
4. Select **Send** to transmit your message.
## 6. What happens after I click Send on a message thread?
When you click **Send**:
1. The reply text typed in the **"Reply Here"** text box is sent to the selected conversation.
2. The system updates the conversation record in real time.
3. The **Conversation Panel** refreshes to display your newly sent reply in the message history.
## 7. How do I check active operational details like business type, date, shift number, and user while on the Message screen?
To verify system status and login credentials while viewing messages:
1. Open the **Message** screen via **"Front Desk"** → **"Message"**.
2. Look at the **Status Bar** along the bottom of the screen.
3. Read the **Status Bar** to check:
* **Active Business Type** (e.g., *Restaurant*, *Take Away*, or *Zomato*)
* **Business Date**
* **Shift Number**
* **Logged-in User**
* **Navigation Controls**
## 8. How do I exit the Message screen and return to the Front Desk module?
To exit the messaging interface:
1. Locate the **Close** button on the **Message** screen.
2. Select **Close**.
**Result:** The **Message** screen closes immediately, returning you to the **Front Desk** module.
## 9. What are the main screen elements available on the DinePlan Message interface?
The **Message** screen consists of five primary interface elements:
* **Messages (Message List):** Displays the list of available messages, notifications, or conversations.
* **Conversation Panel:** Displays the complete message history for the selected conversation.
* **Reply Here:** Text box where you enter your response to the selected message.
* **Send:** Button that sends the entered reply to the selected conversation.
* **Close:** Button that closes the Message screen and returns to the Front Desk module.
## 10. Can I reply to internal messages without leaving the DinePlan application?
Yes.
The **Message** screen functions as a centralized communication panel directly inside DinePlan. It enables cashiers, store managers, restaurant owners, and administrators to monitor incoming notifications, review complete message histories, and issue direct replies without exiting or navigating away from the DinePlan software.
---
# 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/message/faqs.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)