> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/options/messages.md).

# Messages

**Messages**

**(1)(2)**

These 2 lines print at the bottom center of every guest check for each revenue center. There can be a maximum of 2 lines of 20 characters each. Examples might be "Thank You!" and/or "Have a Nice Day".

{% hint style="info" %}
NOTE: If you want the server name to display at the bottom of the guest check, there must be something in line 1.
{% endhint %}

**Kitchen**

**Name**

The revenue center name can appear on the tops of the chits that print on shared printers, such as for the bar or the kitchen. The name of the revenue center or any other description that is entered here prints at the top of the chit at all times when servers order items from this revenue center.

**Modes**

The mode can appear on the tops of the chits that print on shared printers, such as for the bar or the kitchen. During each mode a description entered here prints right after the name of the revenue center depending on the time of day.


---

# 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://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/options/messages.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.