Guest Details

​

Why This Matters

Guest Details and Medical collect the information House of Legends staff need to prepare for each guest’s visit. Contact details allow the team to reach the booking party before the event if anything changes. Dietary and medical notes go directly to the kitchen so the culinary team can plan meals safely and appropriately. Personal requests surface to front-of-house staff so they can anticipate special occasions and deliver a more thoughtful experience.

​

Guest Info Fields

The DETAILS section captures the primary contact for the reservation:

• Honorific — optional title (Mr., Mrs., Ms., Miss, Dr., Prof., Mx., Other)
• Full name — the name used on receipts and correspondence
• Email — for confirmation and any pre-event updates
• Phone — for day-of-contact if the team needs to reach the party
• Nationality — a free-text field via a searchable combobox

The nationality field helps the kitchen anticipate cuisine preferences and plan portions across international guests. It is visible to operations staff and is not shared with guests.

​

Dietary & Medical

The MEDICAL section presents two separate text areas, both routed to the kitchen team:

• Food restrictions and allergies — free-text field for dietary needs such as vegetarian, vegan, gluten-free, nut allergies, or shellfish restrictions
• Medical conditions — free-text field for conditions that affect dining or the show experience, such as severe allergies, mobility considerations, or other health-related needs

Both fields are informational rather than clinical. Staff use them to prepare the kitchen and coordinate guest support. Some shows at House of Legends have specific food policies and may restrict outside food or beverages; these are handled operationally by staff rather than enforced through the booking form.

​

Personal Requests

In the current implementation, personal requests live inside Guest Details as an optional free-text note. The older standalone REQUESTS section is not part of the visible booking flow. Examples include anniversary celebrations, seating preferences near the stage or away from speakers, photo opportunities, or greetings for special occasions. Personal requests are visible to front-of-house staff only and are not routed to the kitchen. They are informational — staff make reasonable efforts to accommodate but cannot guarantee specific arrangements.

​

Large Group Exception

Groups that exceed maxSelfServeGuestCount are routed directly to WhatsApp inquiry instead of completing the DETAILS and MEDICAL sections. This is because:

• Large party coordination involves multiple staff members and custom arrangements
• Dietary and medical needs for large groups require direct conversation rather than a form
• The booking team needs to confirm availability and capacity before the party commits

When the guest count exceeds the self-serve maximum, currently 7 or more guests, the booking flow presents a WhatsApp contact link instead of continuing through self-serve details, medical, payment, and confirmation. Parties of 1-6 guests remain self-serve when capacity allows.

​

Key Concepts

• Nationality is operational — it helps the kitchen estimate cuisine preferences across a diverse guest list; it is not shared externally or used for identification
• Medical notes are not clinical records — they inform kitchen prep and staff awareness; House of Legends is not a medical facility and cannot guarantee allergen-free environments
• Requests are best-effort — staff see the notes and attempt to accommodate, but special requests cannot be guaranteed through the booking form

​

Technical Details

The following booking context fields are populated across Guest Details and Medical: The isLargeGroupInquiry flag is set to true when guestCount > maxSelfServeGuestCount. When active, the DETAILS and MEDICAL sections are hidden and the guest is redirected to WhatsApp contact instead. See also: Reservation concept — how guest details are stored in the reservation record.