Reservations and the front desk for hotels and resorts
Rooms, tables, tickets and activities booked against one availability position, and a guest folio that is current from check-in through check-out. Bought once and owned outright.
- One availability position
- Rooms, tables, tickets and activities, across every channel.
- The folio is current
- Not assembled at check-out.
- One guest record
- A returning guest is recognised across properties.
- Owned outright
- Run in the operator's own environment.
From the booking to check-out
Four features on one system, for reservations, the front desk, the outlets and the group.
A day at a resort on asasii stay
From the first booking of the morning to the day's figures at close.
- 07:30
A booking from a partner
It lands on the same availability position the front desk and the website book against, so no system holds its own version of what is free.
- 10:00
A table for tonight
Booked at the desk against the same availability position as the rooms, and read by the restaurant.
- 11:30
A guest checks out
The folio has carried every charge as it happened, so nothing is assembled at departure. The payment posts against the folio.
- 12:30
Lunch on the folio
A staying guest's lunch is rung up on asasii pos at the restaurant and posts to the guest folio as it happens.
- 14:00
A returning guest checks in
Recognised from one guest record across the group's properties, not treated as new. The deposit goes on the folio as it is taken.
- 16:00
A day visitor at the gift shop
Not staying, so the sale settles directly at the counter on asasii pos.
- 21:00
A question at the desk
A guest asks what is owed so far. The folio is current, so the desk answers while the guest is standing there.
- Day close
Figures to the group
Occupancy and room takings go to asasii ledger and consolidate across every property, so group finance reads the month while it runs.
Who it's for
Four groups of people, working from the same records of the stay.
A licence, not one more system to reconcile
The operator buys a standard product configured to its own structure, and keeps every record it produces. idataraya is paid to customise, install and maintain it.
| Topic | A system at each counter | asasii stay |
|---|---|---|
| Who owns the software | Each system's vendor | The operator, outright |
| Where the guest records live | Spread across the systems | The operator's own environment |
| What is free | A copy in each system, synced on a schedule | One availability position for every booking |
| What a guest owes | Assembled at departure | Current on the folio as charges land |
| A returning guest | Treated as new at each property | Recognised across properties |
Security and Malaysian compliance
The questions owners, group finance and audit ask, answered in the system.
Security and data overview- PDPA 2010
- Guest data stays in the operator's own environment.
- Roles
- Each role is scoped by property and function.
- Single sign-on and MFA
- On every console, with the operator's own identity provider.
- Audit trail
- Every action recorded with the previous value and kept for seven years.
- The operator's records
- Bookings, folios and guest records are held in the operator's own environment.
- Card data
- Card payments go through the operator's own acquirer, and card data stays with it.
Installed and maintained by idataraya
asasii stay runs in the operator's own cloud account or data centre. idataraya installs it and keeps it current, and the operator's team holds the keys, the backups and the data.
- Response times by severity, measured monthly
- Monitoring from within the operator's environment
- A cutover planned for the shoulder season
- Support staffed when the property is full
Questions hotels and resorts ask
About bookings, the folio, moving across and the agreement.
Can the desk, the website and partners all book at once?
Yes. Rooms, tables, tickets and activities are booked against one availability position, whether the booking comes from the front desk, the website or a partner. No system holds its own version of what is free, so overbooking stops being a reconciliation problem between systems.
Do we have to change the booking channels we sell through?
No. The booking channels, payment providers and accounting packages already in use stay where they are. idataraya integrates asasii stay with them, rather than asking the group to change how it sells in order to change how it records.
Is a returning guest recognised at our other properties?
Yes. One record for the guest carries stay history, spend and entitlements across the group's properties. A returning guest is recognised rather than treated as new at each one.
How does outlet spend reach the guest folio?
The restaurants, bars, cafes, gift shops and ticket counters run on asasii pos. Where the guest is staying, the charge posts to the guest folio as it happens; where the guest is not, the sale settles at the counter. Room charges, deposits and adjustments post as they happen too, so what a guest owes is current at the desk rather than assembled at departure.
How long does the front desk take to learn?
It is designed to be learned in a shift, because seasonal hiring means it is taught again every intake. Where a task is complex, the system carries the complexity rather than the training material, and staff are trained against the real counter.
When would we move across?
In the shoulder season, on the operator's own calendar. asasii stay runs at one front desk before the group commits every property to it, and the previous system stays available until the new one is trusted. Nobody replaces a property management system the week before a long weekend.
Where does it run, and can our other systems talk to it?
In the operator's own cloud account or data centre. idataraya installs it, hardens it and keeps it current, and the operator's team holds the keys, the backups and the data. It works beside asasii pos, asasii commerce, asasii procure and asasii ledger, and a documented API is open to the operator's other systems.
What does the yearly agreement cover?
Software updates and patches, the customisations made for you, monitoring, incident response, severity-based response and restoration targets, and the changes needed as the operator opens outlets and adds properties. Hosting stays with you. It is a fee, not a subscription.