SOURCE 01Hotel host
BOOKABLE HOSPITALITY · ONE JOURNEY
One itinerary. Many providers. One beautiful handoff.
Build custom experiences and packages across internal teams and outside providers. Journey coordinates availability, options, checkout, fulfillment, and partner settlement.
Deepens the stay Member outcome Partner outcome Source-aware context
SOURCE 02Local expert
SOURCE 03Dining
SOURCE 04Wellness
ExperiencesSINGLE UNDERSTANDING
USEFUL OUTCOMEOne guest link
USEFUL OUTCOMEChoices + timing
USEFUL OUTCOMEOne checkout
USEFUL OUTCOMETraceable settlement
Illustrative product behavior. Source availability and permitted actions depend on configured integrations, data rights, consent, and access.
THE PROBLEM THIS PIECE SOLVES
The moments guests remember are often scattered across vendors, links, messages, deposits, spreadsheets, and folio conversations.
Deepens the stay.
From a private breakfast to a multi-day itinerary—booked as one considered experience. Every action begins with the same governed relationship and creates context the next moment can use.
A better moment, not more machinery.
A richer stay arrives as one considered itinerary—even when several independent providers help create it.
A stronger relationship, not another silo.
Compose, sell, fulfill, and reconcile experiences while the host shares in the value created during the verified stay.
HOW IT CREATES VALUE
Powerful underneath. Calm in the moment.
Curate the moment
Combine internal inventory and qualified partners into packages, options, timing, notes, and capacity.
Make booking feel singular
Give the guest one beautiful handoff, one set of choices, and one understandable payment path.
Keep every provider accountable
Track confirmation, fulfillment, exceptions, host participation, and settlement from the same itinerary.
PRODUCT IN MOTION · ILLUSTRATIVE
From a private breakfast to a multi-day itinerary—booked as one considered experience.
The scene below shows the hospitality moment this capability is designed to make clearer. Example data is synthetic; connected availability and actions depend on configuration and permission.
Sunrise paddlePrivate guide
Breakfast at the waterVegetarian table
Horses at golden hourTwo guests
3 experiences · 2 providers
TRUST IS A PRODUCT FEATURE
Useful context, with boundaries.
Sources stay visible
Useful values retain lineage, freshness, aliases, confidence, and scope.
Access remains scoped
Organizations, brands, venues, permissions, and consent govern what can be seen and used.
Important decisions stay reviewable
AI can synthesize and recommend without hiding rules, evidence, or human control.
PART OF ONE JOURNEY
Context should compound—not disappear at the next door.
Experiences resolves the same guest, member, program, stay, scope, and permission context as the rest of HXP.
AvailabilityProvider networkJourney PayPMS folioMessagingConciergeOS
CONTINUE THROUGH THE RELATIONSHIP
The next useful piece of One Journey.
BUILD WITH EXPERIENCES
From a private breakfast to a multi-day itinerary—booked as one considered experience.
Start with your brand and operating model. Journey will research the opportunity, ask the questions that materially change it, and craft an editable concept before commercial activation.
Applications are curated. Connected features, providers, commercial terms, and activation timing depend on the executed agreement and completed readiness checks.