EYT Experiences · Operator resources
EYT for Concierge Companies

A concierge request is often an evolving brief rather than a ready-to-book service.
- Company
- Concierge Companies
- Creator / Host
- Guest
- Shared Party
Where the operational problem begins
A concierge request is often an evolving brief rather than a ready-to-book service. The client may ask for dining, transport and nightlife in the same conversation. Record each request’s owner and confirmation state before presenting a complete plan.
Turn the evolving brief into owned requests
Split a concierge conversation into individual service requests with an owner. Dinner, a vehicle and a late-night reservation can move at different speeds; describing the whole evening as confirmed hides those differences from the client.
Record the preference that matters to the provider. A quiet dining setting, step-free access or a fixed end time is operationally useful. A long unstructured chat history forces the supplier to infer priorities and can expose unrelated personal information.
When one service changes, review downstream dependencies before updating the Guest. A longer dinner affects pickup, arrival and staffing. Ask the authorized operator which changes are feasible and make the final client instruction consistent across the plan.
Illustrative operating example
Hypothetical example, not an EYT customer case study: A dinner extension moves the vehicle pickup. The concierge confirms the revised transport with the authorized operator before the Host shares a new departure time with Guests.
Review the real handoffs
Walk through a dinner request with two unresolved preferences. The concierge should identify which preference blocks supplier review and which can wait without delaying the whole evening.
Test a transfer change after dining is confirmed. Verify that the vehicle operator acknowledges the revised pickup before the concierge sends the Guest a replacement instruction.
Close the brief by checking whether every requested service has a clear outcome. An unanswered request should not disappear merely because the main experience took place.
An exception worth testing
A restaurant can accept a later finish while the vehicle operator declines a pickup extension. Keep both outcomes visible and ask the client’s authorized contact to choose a workable plan. Do not solve the conflict by silently changing an already confirmed service.
Inspect the dining confirmation and transport acknowledgement together. The release test is whether the departure instruction agrees with both providers’ accepted scope, not whether someone has sent a reassuring message to the Guest.
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
| Stage | Decision | Evidence |
|---|---|---|
| Brief | Concierge identifies the essential preference | Client-approved requirements |
| Service review | Operator confirms each request | Separate dining and transport statuses |
| Revised instruction | Concierge releases coherent update | Provider acknowledgements |
Questions operators ask
Can one service remain pending while another is confirmed?
Yes. Keeping separate request states avoids presenting an incomplete evening as fully confirmed.
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.