> 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/front-office-module/fo-queries1/fo-queries1-todays-arrival.md).
# Today's Arrival
Steps to view today's arrival report
**Today’s Arrival**
As the name suggests it shows you the list of Expected Arrivals for today. By default it will show the minimum data in the report but there are filters available to extend the report or options to sort the report based on multiple options.
This report will only show on the day arrival(One day only). Next to Date and Display Button it has a Funnel Filter (for sorting) and Options Filter to add on columns of detailed information about the guest or booking.
**Funnel Filter:** If you use this option, you can sort or arrange the sequence of reports based on the options available such as room no and room type etc.
**Options Filter:** This option can be used in to add on multiple columns of information based on the requirement. You can click on any box and it will add a column.
For example the user can add columns to see the info. Of Pax and Mobile and Email
.png?alt=media)
And on the right it shows Summarized no. of Today’s Arrivals.
.png?alt=media)
---
# 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/front-office-module/fo-queries1/fo-queries1-todays-arrival.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.