All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. OTA Channel Manager
  2. Features
  3. Reservations
Feature · Reservations

Reservations

Review requested stays and carry confirmed bookings through departure.

OverviewConfirmed stays
OTA Channel Manager · Reservations

Confirmed stays

Checked in waits for the front desk agent

New
Reservation numberArrival dateDeparture dateGuestUnitStatus
RSR-8049809 Oct16 OctPRT-33727UNT-63541Confirmed
RSR-5463605 Oct13 OctPRT-19151UNT-77623Confirmed
RSR-6189419 Oct23 OctPRT-15521UNT-11745Confirmed
RSR-7290008 Oct12 OctPRT-84827UNT-45882Confirmed
RSR-5000517 Oct22 OctPRT-43716UNT-11435Confirmed
6 of 6 records
PRT-33727Reservations · RSR-80498
Confirmed
Arrival date09 Oct
Departure date16 Oct
UnitUNT-63541
Example screen with sample data

What you can do

Reservations in daily work

A booking party asks for a room for a specific arrival and departure. The Front Desk Agent captures the guest, unit, dates and party size in a reservation. The Property Manager checks the unit capacity and whether another confirmed stay occupies any of the same nights. A Requested record is work to decide; it is not an occupied room or an accepted promise.

The confirmation decision has to use the current reservation revision. If the guest changes dates while the team is reviewing the request, review the changed interval again. A repeated confirmation with the same operation should return the saved decision, while a conflicting change needs attention before anyone promises the room. Cancellation also stays visible as its own status.

The Front Desk Agent should also check what happened to a request that was cancelled or changed before arrival. A cancelled stay remains in the reservation history, while a new request needs its own review against the unit’s current bookings. This keeps the arrival list from mixing accepted stays with work still awaiting a decision. When the guest asks about a change, staff can explain which dates and unit were accepted.

How the work is organized

  • Request. The Front Desk Agent links the booking party and unit, then records the arrival, departure and guest count.
  • Decision. The Property Manager checks capacity and overlapping nights; the Front Desk Agent confirms the current request.
  • Handoff. The confirmed reservation gives the arrival team the guest, unit and dates it must honor.

What to agree during setup

Agree who may change a requested stay after the Property Manager has checked it. The Front Desk Agent needs to repeat the capacity and overlap review when dates, guest count or unit change. Decide how to handle a cancellation while another person is preparing arrival. Rehearse a same-input retry and a changed-input conflict so the desk recognizes both results.

Check the handoff on an actual case

After the first confirmation, have the Front Desk Agent open the accepted stay and compare its dates with the unit’s other confirmed stays. Try to confirm a second request for an overlapping night. The second request should remain unresolved while the first keeps its confirmed state. At check-in, verify that the selected unit is ready before moving the stay forward.

What your team sees

  • Requested reservations — Review guest, dates, unit and party size before the confirmation decision.
  • Confirmed stays — Prepare accepted arrivals and check the selected unit.

Follow the work through

Walk through the related operating process with the team, then use the data model to check the records each step changes.

What it keeps track of

Data model
Reservations
Stay and resource bookings with arrival, departure, party size and nightly rate.
Parties
Guests, groups, companies and other booking parties.
Units
Bookable inventory: rooms, suites, venues, tables, treatment rooms and other resources.

Who uses it

Permissions
Property Manager
, Front Desk Agent, Operations Reviewer.

Set up OTA Channel Manager your way.

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

How to get started