01Set up the Party
Review request handling, Party setup and Creator / Host assignment. Every assignment depends on review and confirmation; no local Host roster is implied.

Work with EYT · Miami
Miami experience operators work across waterfront departures, neighborhood dining and nightlife.
Request Partner PreviewBuilt around local execution
A marina departure and a late dinner can be separate anchors. Allow room for boarding, changing and the journey between the bay and your evening neighborhood.
One operating picture
Coordinate people, services and status through the existing EYT Company workspace.
01Review request handling, Party setup and Creator / Host assignment. Every assignment depends on review and confirmation; no local Host roster is implied.
02Keep the Guest List, Add-Ons and notifications alongside the provider-confirmed scope. Clarify who owns fulfillment and which details need confirmation.
03Use payment-status coordination, check-in and audit/history. Payment status does not replace provider-direct payment authority or change who is authorized to collect payment.
Assign your own Hosts, Promoters, concierge staff or local coordinators. You do not need EYT to supply a Host or an independent Creator program to begin. Extend distribution through your Hosts: help Guests discover, join and move through the experience, then coordinate arrival and check-in.
Hosts may surface Add-On opportunities; the Partner retains pricing, approval and payment authority. EYT tracks payment status without collecting provider funds. Your team retains local fulfillment, suppliers, venues, transportation, dining and staffing.
EYT can sit alongside the tools you already use. No technical integration or sales increase is promised.
Explore workflow capabilities and practical Partner guides →
Start small, learn together
Include your company, city, service category and a contact person. EYT will review the request before discussing a preview or Pilot scope.
Join the Partner Pilot conversation →Miami experience operators work across waterfront departures, neighborhood dining and nightlife.
Miami experience operators work across waterfront departures, neighborhood dining and nightlife. These formats share a group but have different service owners and confirmation conditions.
A marina departure and a Miami Beach dinner require an explicit transfer plan. A single attractive itinerary does not confirm either supplier.
Choose a Miami transition that crosses service contexts: a waterfront experience followed by neighborhood dining. Ask each operator what constitutes confirmation and when the group can receive final instructions.
Hypothetical example, not an EYT customer case study: A waterfront experience ends before a group dinner in another neighborhood. The operator confirms the actual departure point, and the Company reconciles who is joining the next service before sharing pickup details.
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.
Some Guests may join only the Miami dinner while others leave after the waterfront activity. Building a transfer estimate from the first attendance list can therefore overstate one service and omit another. Ask which transition each person actually joins.
Review the waterfront operator’s confirmed end point and the dinner team’s accepted arrival instructions. The transfer manifest should explain how the participating group connects those two anchors, rather than relying on a general neighborhood description.
Review who updates the Guest if the departure or dining location changes. Separate supplier discussion from the clear current instruction the assigned Host shares with the group.
After the experience, reconcile the final group against each service rather than assuming everyone attended every stage. A Guest may join dinner while deliberately skipping the earlier activity.
| Stage | Decision | Evidence |
|---|---|---|
| Waterfront finish | Operator confirms departure location | Actual end point and time |
| Transfer review | Company reconciles onward participants | Current movement list |
| Dining arrival | Restaurant accepts group handoff | Confirmed arrival instructions |
No. Reconcile each service’s participants and provider-confirmed scope.
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.
The Company and authorized operator retain pricing, availability, service approval, fulfillment, payment collection and cancellation or refund authority under their own terms.
The model allows Company-assigned Creators, Hosts or Promoters with appropriate permissions. Confirm the available assignment and visibility controls during Partner onboarding.
No. Partner fit and workflow availability require review. An invitation, response or shared pass does not guarantee a booking, admission or supplier availability.
External sources provide industry context. They do not establish EYT customer outcomes or platform benchmarks.