Hospitality · Integrations
The guest sees one hotel. The systems see a handoff.
Valet and front desk were bought separately, staffed separately, and measured separately. The guest still expects an early arrival, room charge, and late checkout to move between them without explanation.
The operating truth
An integration is useful only when both teams can see whether the handoff completed.
Sending a folio charge is not the same as knowing it posted. Receiving a checkout time is not the same as knowing the guest is ready. The seam needs status, ownership, and recovery.
The shared moments
Where the two operations become one
Four handoffs worth designing
Arrival
Room not ready
Valet knows the vehicle; front desk knows the stay. The guest should not have to reconnect them later.
Billing
Post to folio
Valet submits the charge and receives an accepted, rejected, or unresolved result.
Change
Stay extended
A checkout change should prevent a premature retrieval assumption without exposing excess guest data.
Departure
Guest is ready
Checkout intent becomes useful only when the curb can sequence the vehicle and luggage.
The acknowledgment loop
→“We sent it” is a transport fact. Hospitality needs a business result.
Share the minimum useful context
A valet does not need the guest's whole stay history to post parking. The front desk does not need key-board detail to answer whether a car is ready. Map the smallest identity and state needed for each handoff, then log who can see it.
That restraint improves privacy and operations at once: fewer fields to mismatch, fewer stale copies, and a clearer owner for the authoritative record.
The guest test
Can either team answer without calling the other?
If the front desk can see the valet charge result and the stand can see the relevant departure state, the integration has removed a seam. If staff still trade radio calls to confirm every event, two systems are merely connected, not coordinated.
Test failure before launch. Disconnect the hotel interface, submit the same folio charge twice, move a guest to another room, reverse a checkout, and restore the connection. The expected result is not that nothing ever fails. It is that duplicates are prevented, unresolved work is visible, staff know what to tell the guest, and reconciliation can prove which system eventually accepted the event.
Agree on support ownership before the first unresolved folio. Front desk should know whether to correct the stay, valet should know whether to retry the charge, and accounting should know which report settles the difference. A shared queue with named aging is more hospitable than three departments forwarding screenshots.
