Reservations
Know what is arriving. And what has changed.
A reservation is more than a date on a calendar. Keep booking changes, occupancy notes and property instructions together so the next handover starts with the same information.
Discuss this support role ↗
Scope of support
Useful work.
Clear boundaries.
- Check arrival and departure dates against your approved booking records.
- Record occupancy notes and requests in the property management system.
- Flag conflicting calendar information and changes that need a decision.
The working relationship
From your information
to a reviewed handover.
You provide
Your reservation feed, property list and rules for approved changes.
Your assistant prepares
A checked arrival list with differences linked to their source.
You retain
You approve exceptions before records or guest commitments change.
An illustrative working situation
A guest asks to extend a stay
Check the existing reservation and the next arrival. Record the request, flag any turnover conflict and route the proposed change to the person who can approve it. Update the record only after approval.
What you can review
A dated reservation check, a list of unresolved differences and an owner for each proposed change.
This example explains the proposed workflow; it is not a customer result.Clear responsibilities
Remote coordination.
Local confidence.
Your assistant organizes information, communicates within approved guidance and follows up on open tasks. You set coverage, permissions and approval rules.
Cleaning, inspections, repairs and urgent on-site response stay with your local team. Sensitive access details belong in your approved systems, with only the permissions the role needs.
Define the handover together →Before you begin
Can an assistant accept or change bookings?
Only within the permissions and rules you approve. Exceptions, refunds and commercial decisions remain with the authorized property manager.
What should we bring to the first conversation?
A few examples of the recurring work, the systems involved and the people who approve exceptions. Use general descriptions rather than sharing guest records, passwords or access codes.
How do we review the role as it develops?
Agree on a review rhythm and inspect the actual handovers. Check whether records are complete, unresolved items have owners and the assistant is working within the agreed scope.
Your properties. Your way of working.
Let’s make the everyday
easier to manage.
Bring a few examples from your real queue. We will discuss the role, the handovers and the decisions that stay with you.
Talk through your support needs