EYT Experiences · Operator resources

EYT for Hospitality Operators

EYT for Hospitality Operators

Hospitality teams coordinate experiences around an existing Guest relationship.

  1. Company
  2. Hospitality Operators
  3. Creator / Host
  4. Guest
  5. Shared Party
EYT for Hospitality OperatorsEYT · C7 · Operating frameworkCompanyHospitality OperatorsCreator / HostGuestShared PartyOperating relationships; commercial decisions remain with the authorized Company and provider.
Operating relationships; commercial decisions remain with the authorized Company and provider.

Where the operational problem begins

Hospitality teams coordinate experiences around an existing Guest relationship. A front desk referral, a hosted activity and an external provider confirmation are different events. Keep the hotel’s service context without exposing unrelated reservation or internal Guest information.

Design the referral handoff around service responsibility

A hospitality team needs to know when a referral becomes an accepted provider request. Identify the contact who will handle Guest questions after handoff so the front desk is not left interpreting another company’s terms.

Preserve the minimum service context: the Guest’s requested format, timing constraints and approved contact method. Do not transmit a wider hotel profile simply because an experience operator could find it convenient.

Close the loop on exceptions. If the provider cannot accommodate a request, the hotel needs a clear status and the Guest needs a named next step. Recommending an alternative should remain a reviewed service decision rather than an automatic substitution.

Illustrative operating example

Hypothetical example, not an EYT customer case study: A hotel team refers a Guest to a hosted dinner. The external operator confirms availability and terms; the referral does not itself guarantee a place or authorize access to the hotel’s wider Guest records.

Review the real handoffs

Test the moment a hospitality referral changes hands. The hotel contact should know whether the provider has accepted responsibility for the next response or whether the request remains with the front desk.

Review what the receiving operator actually needs. A timing preference and approved contact method may be relevant; an entire reservation history generally is not. Limit the handoff to its stated service purpose.

After the activity, route a service exception to the responsible provider. The hospitality team may need visibility that a question remains open without receiving every internal commercial detail.

An exception worth testing

A Guest may return to the front desk because the external provider has not replied. The hospitality team needs to know who owns the outstanding response without assuming the referral guaranteed service. Make the escalation route clear before directing the Guest elsewhere.

Review one accepted referral and one unanswered request. Evidence should identify when responsibility changed hands, the contact method the Guest approved and which service status the hotel can appropriately see. Avoid making a full reservation profile the default handoff artifact.

Company authority and current availability

EYT connects Company, Creator / Host and Guest around a shared Party. Specific capabilities are confirmed in controlled Partner workflows. Keep the tools that already work for you: booking, CRM and payment systems can remain in place without an implied integration. Companies retain client relationships, suppliers, availability, pricing, fulfillment, service approval, payment collection and cancellation or refund authority. Guest Networks describe permissioned relationships, not access to other Companies’ client lists.

Operating framework

StageDecisionEvidence
ReferralHotel shares necessary request contextApproved contact and service brief
AcceptanceProvider takes responsibility for next responseNamed owner and accepted handoff
ExceptionResponsible provider addresses service issueOpen question and response status

Questions operators ask

Does a referral require sharing the full hotel Guest profile?

No. Share only the information appropriate to the service purpose and approved handoff.

Does EYT replace our existing operating systems?

No. Keep your booking, CRM and payment tools where they work. EYT’s Party model addresses the people and coordination around the experience; no technical integration is assumed.

Who controls pricing and supplier confirmation?

The Company and authorized operator retain pricing, availability, service approval, fulfillment, payment collection and cancellation or refund authority under their own terms.

Can our own Hosts or Promoters participate?

The model allows Company-assigned Creators, Hosts or Promoters with appropriate permissions. Confirm the available assignment and visibility controls during Partner onboarding.

Does this page announce live local inventory?

No. Partner fit and workflow availability require review. An invitation, response or shared pass does not guarantee a booking, admission or supplier availability.