EYT Experiences · Operator resources
How to Build a Reusable Guest Network

A reusable Guest Network starts with a permitted relationship, a clear Company context and a reason to invite someone again.
- Verify relationship
- Check permission
- Invite relevant Guests
- Review reuse
The operating decision
A reusable Guest Network starts with a permitted relationship, a clear Company context and a reason to invite someone again. A one-night list alone does not establish that relationship.
A workable process
Define eligibility before importing contacts. Distinguish an attending Guest, a booking contact, an approved relationship and a person who should no longer receive invitations.
Record the purpose and permission for future contact alongside the Company context. Keep suppression decisions effective when a list is copied or a new event is created.
Build a small relevant invitation segment. Review unresolved duplicates manually instead of assuming matching names represent the same person.
Illustrative scenario, not an EYT case study
A hypothetical operator has Guests from two hosted dinners. It first separates booking contacts from attendees, checks which relationships permit follow-up, and invites a relevant segment to a new format. It does not broadcast to every name on both lists.
Keep identity and eligibility separate
A Guest may be a valid person in your records but ineligible for the next invitation. That can reflect a changed contact preference, a different service interest or the end of the original relationship purpose. Give staff a clear way to see the distinction without exposing private notes. When merging apparent duplicates, preserve the stricter contact restriction until an authorized reviewer resolves the conflict.
Test reuse before scaling
Take a small permitted segment and trace every invitation back to the underlying relationship. Check who can see the segment, which Company context applies and how removal requests reach the invitation process. If a Host leaves, their operational access should not remain the only way to understand the Company’s relationship history. This is a governance exercise as much as an invitation exercise.
Build the first segment from a clear purpose
Choose the next experience before choosing the audience. A small hosted dinner, a late-night gathering and a private yacht plan may require different interests, availability and group expectations. Identify the relationships for which that particular invitation is relevant and permitted. Avoid segment labels that imply sensitive characteristics or unsupported assumptions about spending. A useful segment has a reason that a staff member can explain to the Guest. If the only reason is that the contact was easy to export, review the purpose again.
Reconcile records with care
A shared email address, similar name or changed phone number can make identity resolution uncertain. Set a review process for merges and preserve the original Party context until the identity decision is resolved. Do not erase an opt-out when combining records. If two Companies know the same person, the identity may be shared while the relationship permissions remain separate. The practical test is whether a staff member can tell which Company context authorizes a specific invitation without seeing another Company’s private history.
Make network maintenance part of operations
Assign responsibility for correcting stale records, reviewing access and carrying suppression decisions into future invitations. Test what happens when a Host leaves or a Guest asks not to be contacted again. A network should not depend on one employee retaining a private spreadsheet. Review the first invitation cohort for duplicate records, confusing responses and missing permissions before expanding the process. The goal is a more dependable relationship context, not merely a larger count of names available to the team.
Review the invitation outcome
After the first reusable segment is used, check whether the selection logic matched the experience and whether contact preferences were respected. Keep declined invitations and unanswered invitations distinct. A Guest who cannot attend may still value relevant future contact, while a person who withdraws should not remain in the next export. Review the outcome with the Company owner before reusing the segment.
Operating framework
| Decision or measure | Definition / action | Interpretation boundary |
|---|---|---|
| Relationship | Approved Company context | Not ownership of a person |
| Permission | Allowed future contact purpose | Attendance alone is insufficient |
| Suppression | Do not invite again | Must survive list reuse |
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 every past attendee join the reusable network?
No. Verify the Company relationship context, identity and permitted future contact purpose. Attendance alone does not establish permission for another invitation.