RippleA guest whose stay was extended at the desk and whose key stops working at midnight has met the gap exactly.
Software has largely stopped being the boundary inside a property; the boundary is now between the software and the building. The lock knows a card is valid until Thursday. The PMS knows the guest is staying until Friday. Connecting the building to the stay record closes that gap for every system at once.
What the connected hotel covers.
Each connection acts on the stay: when it starts, when it changes and when it ends.
Door locks and access
Coming soonKeys issued against the stay, so extending a booking at the desk extends the key, and a departure ends access without anybody remembering to.
Guest Wi-Fi
Coming soonNetwork access tied to the stay rather than a printed code, ending when the stay ends.
In-room entertainment
Coming soonTelevisions and streaming that greet the guest, know the checkout time and reset for the next arrival.
In-room technology
Coming soonRoom systems that know whether the room is occupied, so a room between stays is not conditioned for a guest who left yesterday.
Parking and vehicle access
Coming soonVehicle entry recognised against the reservation, with charges posted to the folio.
Payment terminals
Coming soonCard hardware at the desk taking payment against the folio directly.
Built on a stay record that is already right.
A lock acting on a wrong date is a worse failure than a screen showing one, so hardware is only as good as the record behind it. Ripple’s single operating record — one reservation, one set of dates, one folio — is what lets each connection act with confidence.