1. Wellness Retreat Management
  2. Features
  3. Reservations and stays
Feature · Reservations and stays

Reservations and stays

Requests, confirmation, check-in and check-out.

OverviewIn-house guests
Wellness Retreat Management · Reservations and stays

In-house guests

Checked out waits for the front desk agent

New
Reservation noGuestUnitDeparture dateGuest count
RN-655PRT-9493UNT-7606927 Oct7
RN-242PRT-2288UNT-9561517 Oct35
RN-303PRT-4475UNT-9225727 Oct14
RN-533PRT-5697UNT-1075807 Oct15
RN-921PRT-7253UNT-7138811 Oct26
6 of 6 records
RN-655Reservations · RSR-15156
GuestPRT-9493
UnitUNT-76069
Departure date27 Oct
Guest count7
Example screen with sample data

What you can do

Hold the room only when the stay can really happen

A reservation is one guest’s stay in one unit: the guest, the unit, the arrival and departure dates, how many people are coming and the nightly rate. It starts as a request. The front desk confirms it only after checking that the dates make sense, that the unit can take that many guests, and that no other confirmed stay holds the unit on any of those nights. When the stay is confirmed, every night from arrival up to departure is reserved at once, so two guests can never end up holding the same room.

From there the stay moves to checked in when the guest arrives, and to checked out when they leave. A requested or confirmed stay can be cancelled, which releases its nights. Each step is a recorded change to the same reservation, so the front desk can always see where a guest is in their stay.

How the work is organized

The front desk agent runs reservations from request to checkout; the retreat manager follows occupancy and the program calendar.

  • Requests first. New bookings come in as requests with the guest, unit, dates, guest count and rate, and wait in the confirmation queue.
  • Confirm once. If the same confirmation is sent twice, the second one returns the first result rather than booking again. A confirmation with different details is rejected so the agent can check what changed.
  • Check in the right guest. Check-in is recorded for the exact guest and unit on the reservation; the unit becomes occupied and the stay’s charges start on the folio.

What to agree during setup

Agree which unit types you sell, their capacities and the nightly rates for each season. Decide who may confirm, cancel and check in stays, and what happens to a stay that is still requested a week before arrival. Agree how group bookings are handled: one reservation per unit with the same guest or party. Prepare examples of a simple stay, a double-booking attempt, a late cancellation and an early departure.

Check the handoff on an actual case

Two enquiries arrive for the same garden suite over the same weekend. The front desk records both as requests. The first is confirmed and its nights are reserved. When the agent tries to confirm the second, the availability check fails and the agent offers the guest another unit or different dates instead of discovering the clash at check-in.

On arrival day the confirmed guest appears in the arrivals list. The agent checks them in, the suite shows as occupied on the turnaround board, and the stay’s charges appear on the folio as drafts ready for posting.

What your team sees

  • Reservation pipeline — Requested, confirmed and checked-in stays by guest and unit.
  • Stays awaiting confirmation — Requests with their dates, unit and rate.
  • Arrivals due — Guests arriving today or overdue.

Follow the work through

Review the implementation plan before importing existing bookings.

What it keeps track of

Data model
Reservations
Guest stays across arrival, occupancy and departure, with rate and status.
Parties
Guests and guest groups booking stays at the retreat.
Units
Accommodation units across the retreat property.

Who uses it

Permissions
Front Desk Agent
, Retreat Manager.
The front desk agent handles requests, confirmation and check-in; the retreat manager follows occupancy.

Set up Wellness Retreat Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started