> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recepai.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reservations

> Every booking taken through RecepAI, and what you can do about each one.

**Reservations** is the ledger for bookings your AI staff took directly. It is the operational screen of the Guerrilla Reservation group — the others configure what is on offer; this one is what came of it.

***

## What is on the screen

A list of bookings with a search and a filter bar. You can narrow by **status** — *Active*, *Held*, *No-show*, *Cancelled* — by **date** (booking date, Today, Tomorrow, or a range you pick), by **payment** (including *Prepaid* and *Refunded*), and by the **source** the booking came from.

Each booking carries the state it is in. **Held** is a booking waiting on something rather than settled; **Confirmed**, **Pending payment** and **Paid** describe where the money stands; **No-show** and **Cancelled** are the ends. A cancellation records who did it.

Opening a booking gives you the whole record in sections:

| Section                      |                                                                         |
| ---------------------------- | ----------------------------------------------------------------------- |
| **Stay**                     | Dates, guests, the stay average                                         |
| **Pricing**                  | The total, and what it is made of                                       |
| **Payment**                  | How it is being paid, with **Open in LinkagePay** where money has moved |
| **Channel** and **Campaign** | Where the guest came from                                               |
| **Strategies**               | Which of your strategies applied to this booking                        |
| **Special requests**         | What the guest asked for while booking                                  |
| **Cancellation**             | The terms, and the action if you need it                                |
| **Activity log**             | Everything that has happened to this booking                            |

A booking whose guest has arrived is marked as checked in.

***

## What you do here

<Steps>
  <Step title="Find the booking">
    Search by guest, or filter by date when a guest says "I booked on Tuesday".
  </Step>

  <Step title="Read Strategies alongside Pricing when the price is questioned">
    **Strategies** names which of your rules affected this booking; **Pricing** shows what the total is made of. Read together they are where the answer is — neither is the whole story on its own.
  </Step>

  <Step title="Correct a booking">
    **Edit** changes the booking itself. Use it for a genuine correction — the guest's dates, their party — not to record something that happened.
  </Step>

  <Step title="Chase or check a payment">
    **Payment link** sends the guest a way to pay. **Open in LinkagePay** takes you to the payment itself where one exists.
  </Step>

  <Step title="Cancel when you have to">
    **Cancel reservation** shows the terms before it asks you to confirm, and **Keep reservation** backs out.
  </Step>

  <Step title="Mark a no-show, or put one back">
    **Mark no-show** records that the guest never arrived. **Reinstate** exists for the booking that was ended and should not have been.
  </Step>
</Steps>

<Note>
  **Not every action is on every booking.** Which of them the drawer offers depends on the state the booking is in — a cancelled booking is not edited, and a confirmed one is not reinstated.
</Note>

<Warning>
  **Card details can be revealed once.** Where a booking is held against a card, the drawer offers a one-time view for the situations that need it — a no-show charge, a payment taken by phone. Treat it as exactly that: one look, for a reason you could write down.
</Warning>

***

## What happens next

**Cancelling** releases the room back into what is available and records who did it. Where money has been taken, the cancellation is recorded as needing a refund — issued from your payment tools, not from this screen.

**Marking a no-show** keeps the booking on the record as a sale, because the room was held and not resold.

What all of this adds up to is on [Performance](/front-desk/guerrilla/performance).