The questions a guest asks before arrival are the ones the desk answers at the busiest moment.
When a guest can confirm their details, tell you their arrival time and ask for a cot in advance, the desk spends check-in welcoming people rather than typing. Because the portal writes to the reservation itself, nothing has to be re-entered or forwarded.
What guests can do.
Opened with the reservation reference and the email address on the booking.
- Online check-in
- Guest details and arrival information completed before they reach the desk.
- Manage the booking
- Change dates or cancel under the policy they booked with, seeing the consequence first.
- Pay for a change
- When a change has a cost, it is paid online and recorded against the stay.
- Requests
- Extra towels, a late checkout or a cot, sent to the team as a request it can act on.
- Messages
- A conversation with the hotel attached to the stay, not lost in an inbox.
- Payments and balance
- What has been paid and what remains, clearly separated from anything billed to a company.
- Departure
- Let the hotel know they are leaving and review the stay summary.
- Saved cards
- See and remove a card saved for the booking.
Every portal action is a reservation action.
A request appears in the team’s request queue, a message in the guest conversation, a date change on the board and the folio. Your staff see what the guest did without a separate system to check.
- Requests and messages handled by the team from Ripple
- Date changes and cancellations follow your policies automatically
- Company-billed charges kept apart from the guest’s own balance