​
Why This Matters

Guest count is the single most consequential decision in the booking flow. It drives bundle eligibility, capacity checks, admission pricing, and kitchen prep counts for Dinner Show events. Getting the count wrong ripples through every downstream step — pricing recalculates, availability can shift, and fulfillment options may change. Children do not have a separate ticket type. isChildrenAllowed is a content-suitability indicator only. It helps guests understand whether the show content may be suitable for children, but the decision is entirely up to the guest. Every attending guest, including children, uses the same admission price because House of Legends is an intimate theater with limited seats.

​
How It Works

The guest count panel uses an increment/decrement control with six selectable marks: 1 through 6. The starting default is 2. Each tap advances or reduces the count by one. The upper bound is the lesser of the show’s capacity and the self-serve maximum of 6. Once 6 is reached on a show that has remaining capacity, a “Contact us on WhatsApp” option appears rather than allowing further self-serve increases. If the selected show content is marked suitable for children, the panel displays a child-suitability notice. The guest count remains the total number of seats/guests and is not split into adult and child quantities.

​
Key Concepts

​
Total Guest Count

guestCount is the total party size used for offer filtering, capacity checks, fulfillment counts, and admission pricing. It includes every attending guest.

​
Children Suitability

isChildrenAllowed is show metadata used to communicate whether the selected show content may be suitable for children. It does not create age-based tiers, age-based discounts, admission restrictions, or child-specific fulfillment rows.

​
Self-Serve Guest Maximum

The booking flow supports 1-6 guests through the self-serve interface when the selected show has capacity. Parties of 7 or more are routed to WhatsApp for staff-assisted booking.

​
Special Cases

​
5-Guest Upgrade Option (Ticket Only)

When the guest count reaches exactly 5 on a Ticket Only booking, a special upgrade panel appears before advancing. It offers two pathways:
  • 5-Seat À La Carte — each guest pays individually at the standard per-seat rate
  • 6-Seat Table Hold — the party is booked as 6 (the 6th seat is reserved but unpaid), providing table security without extra charge
This is a capacity and pricing optimisation surfaced only at the 5-guest boundary.

​
Large Group WhatsApp Redirect

If the show capacity exceeds maxSelfServeGuestCount, the increment control stops at the self-serve maximum and a WhatsApp link appears for larger groups. Clicking the link opens a pre-filled WhatsApp message to House of Legends staff, skipping the self-serve flow entirely. This ensures that high-touch bookings for parties of 7 or more are handled personally.

​
Technical Details

The booking context stores guestCount as the only guest-count input. The reservation preview request sends guestCount and selected offers; it does not send child ages or separate age-based selections. The ticketCount step object in the selector exposes four boolean flags derived from guestCount, maxCapacity, and SELF_SERVE_MAX_GUEST_COUNT = 6:
  • canDecreaseGuests — guest count is greater than 1
  • canIncreaseGuests — guest count is below min(maxCapacity, 6)
  • canContactForMoreGuests — maxCapacity > 6 AND guestCount >= 6
  • maxSelfServeGuestCount — the lower of show capacity and 6
These flags control the visibility of the increment control and the WhatsApp fallback without exposing raw capacity numbers to the UI. See also: Reservation concept — how guest count flows into the reservation record. Pricing model — admission pricing and formulas.