EYT Experiences · Operator resources

EYT for DMCs

EYT for DMCs

A destination management company must translate one client brief into supplier instructions without losing the group context.

  1. Company
  2. DMCs
  3. Creator / Host
  4. Guest
  5. Shared Party
EYT for DMCsEYT · C1 · Operating frameworkCompanyDMCsCreator / HostGuestShared PartyOperating relationships; commercial decisions remain with the authorized Company and provider.
Operating relationships; commercial decisions remain with the authorized Company and provider.

Where the operational problem begins

A destination management company must translate one client brief into supplier instructions without losing the group context. An itinerary describes what should happen; a Party record helps identify who is participating and which handoffs remain unresolved.

Separate the itinerary from the dispatch record

A DMC itinerary tells the client what the program contains. A dispatch record tells the next supplier what has actually been released to them. Keep these purposes separate: a proposed restaurant time is useful for planning but insufficient for sending a vehicle.

Build a change queue around dependency: client approval first, supplier acceptance next, operational instructions last. If transport has acknowledged a change but the restaurant has not, the group does not yet have a coherent replacement plan.

For a multi-day program, reconcile the manifest for each movement. Someone may skip an excursion while remaining part of the main program. Never remove them from every future activity simply because one attendance choice changed.

Illustrative operating example

Hypothetical example, not an EYT customer case study: A dinner relocation changes the transfer destination, Host briefing and Guest meeting point. Updating only the itinerary PDF leaves three teams working from different versions.

Review the real handoffs

Reconcile each transfer manifest against the activity list. The DMC should know whether a missing name reflects a deliberate opt-out, a delayed arrival or a data-entry problem before releasing transport instructions.

Ask a supplier to read back a revised dispatch instruction during evaluation. If the operator cannot identify which version supersedes the original, the workflow still depends on informal memory.

After the program, close supplier exceptions before reusing the client brief. A restaurant capacity issue and an individual dietary request should inform different future decisions.

An exception worth testing

If a delegate misses an excursion departure, first establish whether they opted out or remain in transit. Removing them from the entire program can create incorrect dinner and next-day manifests. Keep the exception attached to the movement concerned.

Test the handoff with two itinerary versions and one amended transfer list. Ask the dispatcher which instruction is current, who approved it and which supplier acknowledged it. If the answers depend on searching informal messages, the dispatch boundary remains unclear.

Company authority and current availability

EYT connects Company, Creator / Host and Guest around a shared Party. Specific capabilities are confirmed in controlled Partner workflows. Keep the tools that already work for you: booking, CRM and payment systems can remain in place without an implied integration. Companies retain client relationships, suppliers, availability, pricing, fulfillment, service approval, payment collection and cancellation or refund authority. Guest Networks describe permissioned relationships, not access to other Companies’ client lists.

Operating framework

StageDecisionEvidence
Client briefClient approves program scopeApproved itinerary version
Supplier dispatchDMC releases confirmed instructionsSupplier acknowledgement
Activity closeoutDMC reconciles movement exceptionsFinal manifest and exception reasons

Questions operators ask

Should the itinerary replace the transfer manifest?

No. An itinerary describes the program; each movement needs an attendance and dispatch record that reflects the actual confirmed group.

Does EYT replace our existing operating systems?

No. Keep your booking, CRM and payment tools where they work. EYT’s Party model addresses the people and coordination around the experience; no technical integration is assumed.

Who controls pricing and supplier confirmation?

The Company and authorized operator retain pricing, availability, service approval, fulfillment, payment collection and cancellation or refund authority under their own terms.

Can our own Hosts or Promoters participate?

The model allows Company-assigned Creators, Hosts or Promoters with appropriate permissions. Confirm the available assignment and visibility controls during Partner onboarding.

Does this page announce live local inventory?

No. Partner fit and workflow availability require review. An invitation, response or shared pass does not guarantee a booking, admission or supplier availability.