Sabai: a travel booking platform with one basket for the whole trip

A traveller planning a journey books the stay on one site, the flight or transfer on another, the experiences on a third, a data plan for their phone on a fourth and, for many destinations, an entry visa on a fifth. Each booking has its own confirmation, its own support line and its own idea of who the traveller is. The trip exists only in the traveller's inbox.

Sabai was built to put the whole trip in one basket: stays, transport, experiences, eSIM and eVisa, bought together and held together.

A traveller builds a trip rather than a booking. Stays come from hotels on Opsian's hospitality platform and from connected channels; transport, experiences, an eSIM for the destination and the eVisa application are added to the same basket; and one checkout produces one itinerary, one set of confirmations and one place to change anything.

Because the traveller is one record across every item, the hotel knows who is arriving before they arrive, the identity the eVisa was issued against is the identity the hotel verifies at check-in, and the support conversation about the trip is one conversation rather than five.

Sabai is the traveller-facing end of the same identity and operations substrate Opsian runs for hotels. The guest who books through Sabai, verifies at an ENTRIX kiosk and messages through the property's inbox is one person to every system along the way, which is what makes the journey, and not only the room, something an operator can run.