EYT Experiences · Operator resources

Guest Network Management

Guest Network Management

Understand reusable, permissioned Guest relationships in the EYT platform model and their company-specific context.

  1. Guest context
  2. Company relationship
  3. Permission check
  4. Future invitation
Guest Network ManagementEYT · B1 · Operating frameworkGuest contextCompany relationshipPermission checkFuture invitationGuest context → Company relationship → Permission check → Future invitation. Conceptual operatingsequence; actual workflow availability is confirmed with the Partner.
Guest context → Company relationship → Permission check → Future invitation. Conceptual operating sequence; actual workflow availability is confirmed with the Partner.

A network is a relationship with context, not an exported contact list

Understand reusable, permissioned Guest relationships in the EYT platform model and their company-specific context.

A previous attendance record does not by itself establish permission for every future invitation. Keep the company relationship, source context and appropriate communication choices distinct. Company isolation matters even when a Guest participates in experiences with more than one operator.

Guest Network management is presented here as a platform model, not an announcement of universally available functionality. A reusable relationship requires company context, appropriate access and an understood purpose. Validate the specific Guest Network workflow during Partner review; the existence of private Party participation does not establish that a broader relationship-management capability is Production-accepted.

Preserve the relationship context

A useful Guest relationship records why the company knows the person and what future interaction is appropriate. The operating question is not merely whether an email address exists. A lead client, an invited Guest and someone who applied but was not accepted can have different relationships to the company. Those distinctions should survive the end of a Party if later invitations are to remain understandable and respectful.

Test company isolation with a concrete example

Imagine a Guest who attends experiences with two unrelated operators. Their identity may be consistent, but the commercial relationships and operational information are not automatically shared. Ask how the proposed workflow separates company context, who can access prior participation and what happens when access is removed. Do not treat the idea of a network as permission to pool every operator’s contacts or disclose the source of a private relationship.

Illustrative operating scenario

The following is a hypothetical workflow example, not an EYT customer case study. A Guest who joined one company’s private dinner may be suitable for that company’s future invitation. Their attendance should not become an unrestricted list for unrelated operators.

Separate identity from company permission

Recognizing the same Guest across experiences does not answer which company may contact them or why. Review the relationship in the context of the operator that earned it. If someone asks to stop receiving invitations, the company needs a way to honor that choice in the applicable process. A network model must account for changed preferences as well as growth.

Do not confuse retention with repeated messaging

An ongoing relationship can mean remembering relevant context and offering an appropriate next experience. Sending more invitations is not itself evidence of a stronger relationship. Review relevance, permission and the Guest’s actual participation choices before treating a contact as an active member of a reusable network.

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

CheckpointQuestion to resolveResponsible context
RelationshipWhy does this company know the Guest?Company-specific context
PermissionWhat future contact is appropriate?Applicable Guest choice
IsolationCan another operator access this history?Reviewed company boundary

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.