Checkout Questions and Buyer Information

Collect useful buyer and ticket-holder information without making public checkout longer than it needs to be.

Article guidance

Checkout questions should collect information your team will actually use. SmartGig can collect buyer details, per-ticket holder details, and targeted custom answers, but every extra required field increases the chance that someone stops checkout or enters rushed information.

Buyer details and holder details

Buyer name and email identify the order and receive the secure order link.
Buyer phone can help with support but should not be required unless your event genuinely needs it.
Ticket holder name and email can be captured per ticket when you need individual attendee information.
Holder details are especially useful for workshops, named admission, age-restricted sessions, or customer support after purchase.

Question targeting

Event-level questions apply to the checkout as a whole.
Ticket-type questions apply only when a matching ticket is in the basket.
Schedule questions apply only when a matching session or slot is selected.
Required questions should be limited to information needed before tickets are issued.
Optional questions are better for preferences, notes, or information that helps but should not block purchase.

Good question writing

Write the operational reason first: Know whether the answer is for access, safety, seating, reporting, support, or eligibility.
Use plain wording: Ask the question as a buyer would understand it, not as an internal field name.
Keep answer choices tidy: For select or checkbox questions, use choices the team can report on later.
Preview the public checkout: Check that questions appear only for the intended ticket or schedule choice.