Ability to automatically send the final bill as a PDF attachment by email after checkout, with configuration per property
Problem:
Citybox uses custom-built self-service kiosks for guest check-in and checkout. These kiosks are integrated with the PMS through the API and perform several guest-facing actions without involvement from front office staff.
A key limitation today is that when a guest checks out through our kiosk using the API, the final bill/receipt is not automatically sent to the guest by email.
As a result, guests frequently contact the hotel after checkout to request their receipt. Hosts then need to manually locate the reservation, generate the final bill, and send it by email. Across our properties, this creates unnecessary manual work and reduces the benefit of having a fully automated self-service checkout process.
Requested solution:
We need a way to trigger the sending of the final bill/receipt when checkout is performed through the API.
This could be solved in either of the following ways:
Provide an API endpoint/action that allows our kiosk integration to trigger the final bill/receipt to be sent by email after checkout.
Alternatively, provide a configurable automation in the PMS that automatically sends the final bill when a reservation is checked out, including when the checkout action originates from the API.
The receipt should be sent to the email address registered on the customer/reservation profile once the bill is closed.
Ideally, the functionality should also be configurable per property and booking channel, for example allowing automatic receipts for direct and corporate bookings while excluding OTA bookings where the guest has paid the OTA and a receipt from the hotel could cause confusion.
Business impact:
This would allow our self-service checkout flow to remain fully automated from the guest's perspective, reduce repetitive manual work for hotel staff, and eliminate a significant number of follow-up emails and calls from guests requesting receipts after departure.
Most importantly, it would ensure that checkout performed through our API has the same receipt functionality as checkout performed directly in the PMS.