EYT Experiences · Operator resources
Capture Add-On Opportunities Around an Experience

An Add-On opportunity should move from a scoped request to authorized supplier confirmation before anyone treats it as booked.
- Scope request
- Provider proposal
- Authorized acceptance
- Confirm service
The operating decision
An Add-On opportunity should move from a scoped request to authorized supplier confirmation before anyone treats it as booked.
A workable process
Capture the requested service, timing, group size and decision deadline. Clarify who asked and who can approve the cost.
Route the request to the responsible Company or provider. Keep proposed scope distinct from confirmed availability and pricing.
Update the Party only after approval and communicate any dependency on the main experience. Retain provider-direct payment and cancellation authority.
Illustrative scenario, not an EYT case study
During a hypothetical yacht outing plan, a Host receives a transport request. The transport operator confirms the vehicle and pickup, while the Company communicates the accepted service. The Host’s suggestion alone creates no booking.
Confirm the decision maker
The Guest who asks about a service may not be the person authorized to accept the cost for the group. Capture both roles and the approval deadline. When a supplier proposes an alternative, route it back to the relevant decision maker before marking the request accepted. Keep quote validity and service availability visible so an old proposal is not mistaken for a current commitment.
Preserve the main experience constraints
An Add-On can change the rest of the plan. A later dinner may affect transport, or a different pickup may affect boarding. Ask which existing commitments the new service depends on and who must approve the resulting change. Keep a declined or expired request distinct from a cancelled confirmed service, because the operational and commercial consequences are different.
Capture the service brief before asking for a price
A provider needs enough context to make a useful proposal: requested service, date, time, group size, pickup or delivery location and any relevant dependency. Clarify what remains uncertain. A broad question about transport is not the same as a scoped vehicle request. Ask who can accept the proposal and when the decision is needed. Keep the Guest’s interest visible without presenting a possible service as available inventory or a guaranteed addition to the experience.
Respect provider confirmation and funds
The authorized operator confirms availability, scope, pricing and payment instructions. A Host can identify a need and coordinate the handoff without receiving authority to collect provider funds. Keep payment reported by a Guest separate from receipt verified by the responsible provider. If the proposal expires or changes, communicate the new terms before treating it as accepted. The applicable Company retains cancellation and refund decisions under its own terms; a shared Party status does not replace those commercial responsibilities.
Review demand without overstating results
Track requests, proposals, accepted services and delivery separately. The difference between stages can reveal where the workflow needs attention, but it does not prove that a platform caused lost or gained revenue. Record known reasons for a request stopping and leave unknown reasons unresolved. Compare similar service types and lead times before changing supplier coverage. A useful Add-On review may lead to clearer brief requirements or faster routing rather than more aggressive selling to Guests.
Keep the Guest’s decision clear
A proposal should make the service, responsible operator, required action and relevant deadline understandable. If the Guest chooses not to proceed, close the opportunity without presenting it as a cancelled booking. If they accept, confirm what still needs provider verification and which payment instructions apply. Avoid bundling an unresolved addition into the main experience as if all services share one commercial agreement. A clear decline or expiry can be a successful coordination outcome because it prevents staff and suppliers from acting on an assumption that the service was confirmed.
Operating framework
| Decision or measure | Definition / action | Interpretation boundary |
|---|---|---|
| Request | Guest need captured | Not inventory |
| Proposal | Provider scope and price | Not acceptance |
| Confirmation | Authorized acceptance | Provider terms govern |
Questions operators ask
Does this require replacing our existing systems?
No. Start with clear ownership and consistent states. EYT can sit alongside booking, CRM and payment systems; no automatic technical integration is implied.
Who controls Guest information and commercial decisions?
The responsible Company sets permitted access and retains commercial authority. Give Hosts and Guests the information relevant to their role; a shared Party is not unrestricted access to Company records.
Can a Host confirm an Add-On or collect provider funds?
Only an authorized operator can confirm the service and relevant commercial terms. Surfacing an opportunity does not itself grant pricing or payment authority.