> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/reservations-and-operations/reservations.md).

# Reservations

Reservations lists every reservation you ever received, past, present and future, with filters for today's arrivals, departures and stays.

## Reservation list

| Column                 | What it shows                             |
| ---------------------- | ----------------------------------------- |
| Reservation number     | The unique identifier of the booking.     |
| Status                 | The current state of the reservation.     |
| Listing                | The unit or property the guest booked.    |
| Guest name             | The name of the lead booker.              |
| Check-in and check-out | The dates of the stay.                    |
| Outstanding balance    | The amount still owed on the reservation. |

The lists can be sorted by estimated arrival or estimated departure. Search finds reservations by guest name, booking code or phone number. Phone number search also works in the [Unified AI inbox](/inbox-and-messaging/unified-ai-inbox.md).

## Stay status filters

| Filter                | What it shows                                   |
| --------------------- | ----------------------------------------------- |
| **Reservations**      | Every reservation, whatever the date or status. |
| **Arrivals Today**    | The guests who check in today.                  |
| **Departures Today**  | The reservations that check out today.          |
| **Currently Staying** | The guests who are on-site now.                 |

## Guest contact details

<figure><img src="https://content.gitbook.com/content/kBDBFX4VDrFqOnghyBKx/blobs/NsF54aZH6xAYjbCIaJ9i/image.png" alt=""><figcaption></figcaption></figure>

An open reservation shows everyone connected to the booking, not only the lead booker, with each guest's phone numbers and email addresses.

| Element                         | What it does                                                                                                                    |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Star icon (*Mark as primary*)   | Makes a phone number or email address the primary contact detail. Future messages use the primary detail when one is available. |
| Star icon (*Remove as primary*) | Clears the primary contact detail.                                                                                              |

The guest portal link of the reservation is in its right-side panel. See [Guest portal](/guest-experience/guest-portal.md).

## Related

* [Multi-calendar](/reservations-and-operations/multi-calendar.md): all reservations on a timeline.
* [Unified AI inbox](/inbox-and-messaging/unified-ai-inbox.md): the conversations of each reservation.
* [Upsells](/guest-experience/upsells.md): the upsell requests on a reservation.
* [Review center](/reviews-and-analytics/review-center.md): the reviews after check-out.


---

# 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.guestway.io/reservations-and-operations/reservations.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.