Operations and automation
The day runs without anyone having to remind anyone
A checkout creates a cleaning task. A fault report creates a work order. A laundry request moves through clear steps. Everything is tied to the bed and the guest.
Housekeeping
A bed never returns to sale before approval
Housekeeping staff see their tasks in order on a phone. They start a task, add a photo when required and finish it. A supervisor approves before the bed becomes available.
- Needs cleaning
- Cleaning
- Awaiting inspection
- Clean and available
- An automatic task for every bed after checkout
- Priority for beds with arrivals today
- A checklist per room type
- Tasks reopen if the supervisor does not approve
- Housekeeping never sees guests' personal data
Laundry
Laundry requests follow a clear path from request to delivery
The guest requests from the portal or front desk logs it. Each step has a time and an owner. The guest can see where their request is.
- 01
Requested
By the guest or front desk.
- 02
Picked up
The bag is collected and numbered.
- 03
Washing
In house or with an outside service.
- 04
Ready
The guest is notified in the portal.
- 05
Delivered
Delivery time is recorded.
- The service price is added to the stay folio before closing
- Turn the service off in settings and it disappears from the portal
- Guest notes are kept with the request
- A full history for every request
Maintenance
A fault report becomes a work order
A guest or staff member reports a fault. It becomes a work order with a priority and an owner. If the fault stops anyone sleeping there, the bed comes off sale.
- Report from the portal or the console
- Priority, owner and expected time
- Before and after photos
- The bed returns to sale after closing and cleaning
- Planned maintenance for devices such as battery changes
Tickets
Two separate ticket systems
Guest tickets
Between the guest and your team only.
- Guests raise a request from the portal
- Your team replies from the console
- Every ticket is tied to the reservation and bed
- No outside chat apps
Support tickets
Between your property and the platform team.
- Account, settings and device issues
- Support staff cannot see guest data by default
- Access to your account needs your permission and expires
- Every support action is logged
Automation
Simple rules that run on their own
Each rule has a trigger, a condition and an action. Actions come from a fixed list. No custom code ever runs on your data.
- Every rule is versioned and you can roll back
- Every run is logged with its result
- Automatic retries, then a failure list you can see in the console
- An action never repeats when an event repeats
WhenA guest checks out
ThenCreate a cleaning task for the bed
WhenPayment and details are complete before arrival
ThenPrepare the door code to issue at check-in time
WhenA high-priority fault is reported
ThenTake the bed off sale and alert the supervisor
WhenA temporary hold expires
ThenRelease the bed
WhenA device command stays unknown
ThenRecheck and alert front desk
See Hostelivo on a ready hostel
Properties with rooms, beds and bookings already in. Open one and walk through a day from booking to cleaning.