These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Guest Feedback & Reviews
- Features
- Reservations
Reservations
Follow each stay from request and unit selection through arrival and departure.
OverviewChecked out stays×
Guest Feedback & Reviews · Reservations
New
Checked out stays
Tickets
| Reservation number | Counterparty | Organization | Resolution due at | Rate per night | Status | |
|---|---|---|---|---|---|---|
| TCK-39160 | CST-46538 | ORG-5147 | 14 Oct | 510 | Checked out | |
| TCK-94413 | CST-34501 | ORG-5710 | 03 Oct | 210 | Checked out | |
| TCK-85236 | CST-43710 | ORG-1516 | 04 Oct | 400 | Checked out | |
| TCK-83934 | CST-34643 | ORG-7098 | 25 Oct | 120 | Checked out | |
| TCK-57130 | CST-60494 | ORG-5305 | 09 Oct | 160 | Checked out |
6 of 6 records
CST-46538Tickets · TCK-39160
Checked outOrganizationORG-5147
Resolution due at14 Oct
Rate per night510
What you can do
Keep the stay as the common record
A reservation links the booking party, the unit, the arrival and departure dates, the guest count and the nightly rate. The Property Manager can see what was requested before the Front Desk Agent confirms it. The same record then anchors the service tasks, outlet bookings, charges and payments that arise during the visit. Use the reservation number when a guest calls so the team does not have to reconcile separate notes about the same stay.
How the work is organized
- Request. Record the party, unit, stay interval, guest count and rate before offering a confirmation.
- Confirmation. Check capacity and overlapping intervals, then authorize the move from Requested to Confirmed.
- Stay. Check in against the confirmed record, link service and outlet work, and close out after financial reconciliation.
What to agree during setup
Decide who chooses the unit and who may confirm a requested stay. Agree how the team checks the dated rate plan and minimum nights before recording the nightly rate on the reservation. The unit’s capacity must cover the party size, and the arrival to departure interval must be clear enough to compare with other reservations. The confirmation step should reject a conflicting stay for the same unit. Keep a cancelled request distinct from a checked out stay so the operating queue remains accurate.
Check the handoff on an actual case
A party asks for a suite from Friday through Monday. The Property Manager checks the unit, capacity and dated rate plan, then records the request. The Front Desk Agent checks the interval before confirming. On arrival, the agent checks in the party and sees the unit marked Occupied. A cleaning task and a restaurant booking can then refer to that same reservation. Before departure, Finance Officer compares posted charges with confirmed payments. Checkout moves the reservation to checked out and the unit to Cleaning. The Property Manager returns the unit to Available after the cleaning inspection passes.
If another stay already covers that interval, confirmation should stop. A repeated confirmation of the same request should return the prior outcome instead of creating another booking. The person handling the call should be able to explain which unit and dates were checked.
What your team sees
- Requested stays — Requests awaiting a unit and interval decision.
- Active stays — Confirmed arrivals and checked-in guests grouped for daily work.
- Stay status board — A compact status view for the full reservation lifecycle.
Follow the work through
Start with stay confirmation, then follow arrival and service and checkout. Review resources and rates when a requested stay needs a different unit.
What it keeps track of
Data model- Tickets
- Stay and resource bookings with arrival, departure, party size and nightly rate.
- Customers
- Guests, groups, companies and other booking parties.
- Organizations
- Bookable inventory: rooms, suites, venues, tables, treatment rooms and other resources.
- Rate plans
- Dated nightly rate plans by unit type with minimum stay rules.
Who uses it
Permissions- Property Manager
- , Front Desk Agent, Finance Officer.
- The Property Manager owns setup and planning; the Front Desk Agent handles the arrival and departure action; Finance Officer checks the linked financial position.
Set up Guest Feedback & Reviews your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.