Workflow
Accommodation Check-in: A Clear Workflow for Guest Arrivals
A guest's arrival should begin with a clear booking, not a search through scattered notes. Your team needs to confirm the reservation, check whether the accommodation is ready and review payment and deposit details before the stay begins. Kasura brings these steps together in the existing booking, helping staff welcome guests with the information they need in one place.
When this workflow is used
When a guest arrives for a booked stay, staff can open check-in directly from the reservation. If a guest books and checks in at the same time, your team can choose 'Start check-in' during booking creation instead of 'Create booking'. Both options keep the arrival process connected to the guest's booking, whether the stay was reserved in advance or arranged on arrival.
Before check-in
A guest should not be checked into an accommodation unit that is still being cleaned. Kasura allows check-in only on or after the booking's scheduled start date and blocks it while the unit is marked as dirty or being cleaned. This helps your team avoid starting a stay before the accommodation has been marked ready, keeping the guest arrival process aligned with the unit's recorded status.
Guest information
When a guest arrives, your team can access the name and contact details already linked to their booking instead of searching through separate records. Any identity information previously recorded can also be referenced during check-in, helping staff carry out their own checks with the relevant details at hand.
Deposit and payment state
Before a guest takes occupancy, your team can confirm the recorded payment status and document the agreed deposit arrangement. Kasura lets staff record a cash deposit or a passport or ID held at the property instead of cash. The selected arrangement stays connected to the booking, giving your team a clear reference when the guest checks out.
Occupancy start
Confirming check-in marks the booking as an active stay, giving your team a clear record that the guest has arrived. The accommodation's readiness status remains unchanged, so the start of a stay does not automatically change its cleaning status. This keeps the booking's progress separate from the unit's recorded readiness.
Resulting operational state
With check-in completed, the booking reflects an active stay and the accommodation unit is occupied until check-out. Your team can refer back to the guest information, payment status and recorded deposit arrangement within the booking. When the stay ends, the connected check-out workflow provides the next step for closing the booking and updating the unit's status.
How this differs from vehicle pickup
Vehicle pick-up shares the same underlying dialog component but is a functionally different process: it records fuel level, odometer reading and vehicle condition, none of which apply to accommodation check-in, and its outcome is a vehicle leaving the premises rather than a guest occupying a unit that stays on-site.
What this workflow does not mean
- A passport or other identity document is never scanned or read automatically — any document held as a deposit is recorded as a type only.
- Check-in draws only on bookings created directly in Kasura; no OTA or booking channel is synced.
- No channel manager exists in Kasura, at check-in or anywhere else.
- Cleaning tasks and staff assignments are outside this workflow — check-in is not a housekeeping task-management suite.
- Fuel, odometer and vehicle-condition fields belong to vehicle pick-up; none of them appear here.
- Fast Track has no accommodation equivalent — it is a vehicle-return shortcut only.
Frequently asked questions
What happens during accommodation check-in in Kasura?
Staff confirm payment and deposit state as the guest takes occupancy of the unit; no vehicle-specific field is involved.
Is accommodation check-in the same as vehicle pick-up?
No. Check-in has no fuel, odometer or vehicle-condition field, and the unit stays on-site rather than leaving with a customer.