Hotel Marketplace · Documentation

User Journey

The end-to-end path through Hotel Marketplace, from trigger to outcome.

Hotel Marketplace
GUESTlands on heroSEARCHNL · meteredRESULTSrankedDETAILrooms · ratesBOOKINGpay · simulatedCONFIRMED+ ripples out
Live diagram — the Home → Results → Detail → Booking → Confirmation funnel; only NL search is metered and only payment is simulated.
  1. 1

    Guest → booking

    A guest lands on the hero, searches in natural language, scans recommendation-ranked results, opens a property (gallery, 20+ facilities, rooms/rates, reviews, nearby POIs, map), and books a room — applying loyalty or a coupon, paying through the simulated payment surface, and receiving a confirmation. The booking, the payment event, and the notification are all written through the one adapter and emitted on the event bus.

  2. 2

    Booking → the rest of the ecosystem

    That single booking ripples outward through shared entities and events: it accrues loyalty, feeds the recommendation and segmentation engines, appears in the operator booking cockpit and PMS, and rolls into analytics — without any app duplicating the booking. The guest account (trips, saved, profile, loyalty, messages, concierge) is the guest's view of the same data.

User Journey · Hotel Marketplace · Abhishek Saxena