ResytechResytech Docs
Bookings

Handle Guest Information

How to view and manage individual guest records, demographics, and contact details on a booking in Resytech.

Guest information on a booking represents the individual people who will be participating in the activity. While the booking itself has a primary customer (the person who made the reservation), the guest list tracks each attendee separately with their own contact details and demographic assignment.

Viewing guests

  1. Go to Bookings and open the booking.
  2. Click the Guests tab.

The Guests tab only appears if the booking has guest records. Each guest entry shows:

FieldDescription
Full NameThe guest's name.
EmailThe guest's email address.
PhoneThe guest's phone number.
DemographicThe demographic category this guest belongs to (e.g., "Adult", "Child").
Customer UUIDIf the guest is linked to an existing customer record, the customer's unique ID.

How guests are created

Guest records are typically created during the customer booking flow when guests fill out individual information forms or waivers. They can also be created through integrations and API calls.

The primary customer on the booking is separate from the guest list. The customer is the person who made and is responsible for the reservation. Guests are the people who will attend.

Guests vs. manifest demographics

The guest list and the booking manifest serve related but different purposes:

AspectManifestGuest List
GranularityCounts per demographic category (e.g., 3 Adults, 2 Children)Individual records with names and contact info
PurposeCapacity tracking, scheduling, reportingWaiver tracking, individual identification, communication
Always presentYes (set during booking creation)Only if individual guest info was collected

Using guest information for waivers

If your activity requires waivers, each guest may need to submit their own waiver. The Waivers tab on the booking shows waiver submission status. Guest records help you identify who has and hasn't completed their waiver before the booking date.

Tips

  • Guest records support customer linking. If a guest's email matches an existing customer in your system, the guest record can be linked to that customer profile. This helps build a complete customer history across multiple bookings.
  • The Guests tab is conditional. It only appears in the booking header when guest records exist. If your booking flow does not collect individual guest information, this tab will not be visible.
  • Guest demographics should match the manifest. If you have 3 guest records marked as "Adult" and 2 marked as "Child", your manifest should reflect 3 Adults and 2 Children. Update the manifest if the counts drift apart.
  • Use guest emails for targeted communication. If you need to send waiver reminders or activity instructions to individual attendees (not just the booking holder), guest email addresses are the way to reach them.

On this page