EYT Experiences · Operator resources
Social Guest Invitations

Turn a shared social invitation into a clearer participation handoff without implying a direct Instagram or WhatsApp integration.
- Share link
- Recipient opens
- Required identity steps
- Participation review
Sharing a link does not confirm participation
Turn a shared social invitation into a clearer participation handoff without implying a direct Instagram or WhatsApp integration.
Instagram and WhatsApp can be useful places to share an invitation. The recipient still needs the appropriate identity and participation steps for the applicable workflow. Keep link sharing, account creation, application and approval distinct.
Social Party invitations are described as a platform direction and participation handoff to validate with the Partner team. Existing Creator invitation links do not establish that every Guest invitation journey is Production-accepted. Confirm the supported recipient, identity and approval steps in the relevant workflow before promising a direct path from social sharing to a joined Party.
Write the invitation for the recipient
A shared social message should make clear what the experience is, who is responsible for it and what action the recipient needs to take next. Avoid language suggesting that opening a link reserves a place. If participation requires identity verification, an application or company review, that dependency belongs in the handoff. The recipient should not have to infer their status from the tone of a group chat.
Keep channel activity separate from response state
A message sent in Instagram or WhatsApp is not the same as an accepted participation request. A recipient may forward the link, ask a question or ignore it. Avoid manually converting social engagement into a confirmed Guest count. EYT’s social invitation model concerns a clearer transition from a shared link into the applicable workflow; it does not claim access to private messages or a direct integration with either platform.
Illustrative operating scenario
The following is a hypothetical workflow example, not an EYT customer case study. A Host shares an approved invitation link in a group chat. A recipient follows the link and completes the required participation steps. The Host does not assume that a viewed message is an accepted invitation.
Expect the link to leave the original conversation
A recipient may forward a social invitation to someone the Host does not know. The participation process should still explain who is responsible and what review is required. A broadly shareable message should not carry private Guest information or imply that every person receiving it has been personally approved.
Give questions a responsible destination
A recipient may have a practical question before completing the participation steps. Identify the company or assigned contact that can answer it. Avoid asking a Promoter to improvise a commercial promise in a private message. The invitation should help someone understand the next action without depending on an undocumented conversation.
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 |
|---|---|---|
| Social message | Does the recipient understand the next step? | Approved invitation copy |
| Identity step | What account or verification is required? | Applicable supported journey |
| Participation | Is review or acceptance still outstanding? | Company-approved process |
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.