Component

Collect named parameters from the guest (or staff) before later steps can continue.

When to use: Contact details, address lines, newsletter opt-in, or custom integer counts that drive pricing. In live tenants this is one of the most common steps — often Email, Phone, and Name, sometimes a full address block.

Configuration highlights:

• Inputs — ordered input definitions, each bound to a parameter (personal, address, or CustomParameter).
• Optional vs required, min/max overrides, and localized header / info text.
• Custom parameter labels come from CustomText / CustomInput display names.

Typical place in the funnel: Mid-flow after time/elements (contact before pay), or early when custom counts feed AddPositionToOrder via FromOtherParameter.

Downstream: PayNow, sync steps, or AddPositionToOrder quantity rules that read the same parameters.

See patterns booking-classic-occupancy and booking-menu-checkout.