EYT Experiences · Operator resources
Guest Applications & Approval

Understand applications-open and invite-only participation, company review and Creator recommendations in the EYT model.
- Interest
- Application
- Company review
- Decision
Application, recommendation and acceptance are different states
Understand applications-open and invite-only participation, company review and Creator recommendations in the EYT model.
An application expresses interest. A Creator recommendation adds context. Neither is a substitute for company approval where review is required. Define who reviews, what information is necessary and how an applicant learns the outcome before opening a participation pathway.
Application and approval are operating concepts to validate in a controlled Partner workflow. This page does not announce an application feature enabled for all companies or destinations. Existing private Party participation should not be interpreted as proof of an accepted applications-open capability. Ask to review the actual applicant, reviewer and decision paths before using them.
Specify the decision before collecting information
For an applications-open experience, decide what the company genuinely needs to assess and who reviews it. Ask only for information relevant to the decision and the operating requirements. An application process can create unnecessary friction if it collects broad personal detail without a clear purpose. The applicant should understand that submitting interest is different from receiving an accepted place or a provider-confirmed service.
Resolve recommendations and capacity separately
A Creator may provide useful context about a prospective Guest, but the company still owns the review where approval is required. Capacity, eligibility and provider conditions may change before a decision. Agree how pending applications are communicated and how a decision reaches the applicant. Do not infer acceptance from a recommendation, a shared link or an existing account. Validate the specific application workflow during Partner onboarding.
Illustrative operating scenario
The following is a hypothetical workflow example, not an EYT customer case study. A Host recommends someone for a hosted experience. The company reviews fit and capacity, then communicates a decision; the recommendation alone does not create a confirmed place.
Define a useful pending state
An applicant waiting for review needs to know whether any action is required and whether participation remains unconfirmed. Avoid messages that sound celebratory enough to imply acceptance before a decision. A clear pending state protects both the applicant’s expectations and the company’s ability to review capacity and operating conditions.
Handle a changed decision carefully
If a provider condition changes after approval, the company needs to review the consequences and communicate the new position directly. Do not assume that a previously accepted application overrides later venue or supplier requirements. Keep the original decision context and the reason for the current instruction distinguishable.
Commercial boundary
For this workflow, the Company retains clients, suppliers, availability, pricing, approval, relevant payment collection and fulfillment. Its terms govern cancellation and refunds. Keep the tools that already work for you; no automatic integration or replacement is implied.
Operating framework
| Checkpoint | Question to resolve | Responsible context |
|---|---|---|
| Application | What information is needed to review fit? | Applicant |
| Recommendation | What additional context is being offered? | Creator within assignment |
| Approval | Has the company accepted participation? | Authorized reviewer |
Questions operators ask
Does this replace our existing operating systems?
No automatic replacement or integration is implied. Confirm the proposed workflow alongside the booking, CRM, payment and supplier systems that already work for your company.
Is every described capability available to every Partner?
No. Current availability and permissions depend on the controlled Partner workflow. Platform-model and future-direction descriptions should be confirmed during onboarding.
Who retains commercial authority?
The responsible company retains pricing, supplier approval, fulfillment and the relevant payment and cancellation decisions under its own terms.