Before you begin
- Have the relevant unit, nightly price/rules, registration details and booking dates available.
- Decide who records guest details and handles check-in, cancellations and filing tasks.
- Verify current provider availability and local obligations outside the prototype before operating a real stay.
The illustrations use fictional demonstration records. Follow your organisation’s review and approval process before issuing changes.
An owner can see current guests, upcoming arrivals and outstanding administration without mixing nightly stays with long-term tenancy assumptions.
What the workflow coordinates
The current workspace connects a direct booking to its daily tenancy, invoice, payment and labelled payment-provider state.
What people review
People verify reservations and guest details, manage turnover and conflicting dates, authorize stay changes and complete any required external filing.
Find the nightly unit and its setup state
Open Short stays → Units & calendar. Review the current unit setup and date availability rather than the older access-control calendar.
The correct nightly unit and its displayed setup state are identified.
The correct nightly unit and its displayed setup state are identified.
Understand what the calendar feed does
The official demo uses direct bookings; the earlier channel/iCal setup illustration is not exposed in the current Short stays navigation. The current Short stays navigation offers Bookings, Units & calendar and Taxes & fees. The earlier channel/iCal configuration is not exposed by this official demo.
Short-stay channel links
The official demo uses direct bookings; the earlier channel/iCal setup illustration is not exposed in the current Short stays navigation.
Confirm current availability before attempting this stage.
Review bookings with their recorded source
The earlier Access/locks prototype is not exposed in the official demo navigation. No hardware or credential action has been verified. Open Bookings and review its status filters, guest, unit, stay dates, nights and total. Direct bookings are confirmed only when the payment provider confirms payment.
Guest access for short stays
The earlier Access/locks prototype is not exposed in the official demo navigation. No hardware or credential action has been verified.
Confirm current availability before attempting this stage.
Check the booking lifecycle and guest context
Open a seeded booking such as BK-000001. Read Stay, Price, Guest and Money together. Its linked daily tenancy, invoice, payment and explicitly simulated online-payment record are distinct records.
The stay state, guest contact, next arrival and intended guest-page route are clear.
The stay state, guest contact, next arrival and intended guest-page route are clear.
Review pass validity and stay changes
The current booking detail does not expose the earlier guest wallet/door-pass sequence. No lock, pass, arrival or cancellation action was submitted during the review.
Pass scope and intended stay-change responsibilities are clear, with simulation limits retained.
Pass scope and intended stay-change responsibilities are clear, with simulation limits retained.
Track declaration tasks and fee information
Open Taxes & fees and read the current settings and scope. A configuration screen is not evidence that a legal filing or external declaration was submitted.
Each filing task has an owner and is distinguished from actual submission evidence.
Each filing task has an owner and is distinguished from actual submission evidence.
Review departures and prepare the next arrival
The earlier Access/locks prototype is not exposed in the official demo navigation. No hardware or credential action has been verified. Use the date calendar and the current housekeeping schedule to plan work around the next booking. The former short-stay cleaner/PIN prototype is not used as a screenshot of this release.
Guest access for short stays
The earlier Access/locks prototype is not exposed in the official demo navigation. No hardware or credential action has been verified.
Confirm current availability before attempting this stage.
What you should have at the end
The current booking, dates, price and linked money records are understood; unexposed guest-access services are kept separate.
Demonstration notes and availability
- Reviewed against the official demo at demo.estatereal.io. Screenshots are native 3× captures in English/light mode. Preset records and enabled functions can change.
- This review followed navigation, record tabs and unsaved forms. It did not submit payments, signatures, invitations, messages or irreversible record changes.
- Current demo limits: The official demo uses direct bookings; the earlier channel/iCal setup illustration is not exposed in the current Short stays navigation. The earlier Access/locks prototype is not exposed in the official demo navigation. No hardware or credential action has been verified.
Useful answers
What does confirmation mean in the current direct-booking workspace?+
The page states that confirmation follows the payment provider’s confirmation, then creates a daily tenancy with an invoice on the rent ledger. A seeded record explicitly labels its simulated payment.
Where are the earlier iCal, wallet and door-pass screens?+
They are not exposed by the current Short stays navigation or the reviewed booking record. Their prototype screenshots are retired rather than presented as current.