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 · Las Vegas
A Las Vegas group can move between a convention program, a resort dinner and an evening gathering.
Request Partner PreviewBuilt around local execution
For a bachelor or bachelorette weekend, choose the occasion that matters most before adding another stop. A dinner, performance and club arrival need realistic gaps; a late arrival can change the usefulness of the whole plan.
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 →A Las Vegas group can move between a convention program, a resort dinner and an evening gathering.
A Las Vegas group can move between a convention program, a resort dinner and an evening gathering. The operator’s problem is keeping the handoffs coherent when the attendees, service owners and arrival constraints differ.
Convention participation is not proof of nightlife demand. Define the actual group purpose before recommending another service.
Begin a Vegas operator review by choosing one service transition rather than an entire weekend. A resort dinner followed by another gathering exposes whether the team can confirm the finish, pickup and next arrival as a coherent sequence.
Hypothetical example, not an EYT customer case study: A resort dinner runs later than expected while another operator is preparing a hosted gathering. The Company asks both providers to review the transition, then gives the Host one confirmed departure instruction.
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.
A Guest who leaves the dinner early may no longer be part of the onward movement. The Host should reconcile participation before counting the whole dinner list as expected arrivals at the next gathering. The operator still reviews the revised scope.
Use the confirmed dinner location, named pickup point and receiving operator’s arrival instruction as the evidence set. These records should describe one workable transition rather than three individually plausible but disconnected arrangements.
Ask the local operator to identify the exact entrance used for the group handoff. A resort name alone leaves too much ambiguity for a Host meeting people who are unfamiliar with the property.
Close the review by recording which arrival instructions changed during the evening. Use those observations to improve the next briefing without claiming that one group represents citywide behavior.
| Stage | Decision | Evidence |
|---|---|---|
| Local brief | Company chooses the service transition | Actual locations and group purpose |
| Resort departure | Host confirms release and pickup | Named entrance and ready signal |
| Next arrival | Receiving operator accepts handoff | Current arrival instruction |
No. Agree the actual group entrance or pickup point with the responsible local operator.
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.