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.
Do not collect sensitive information just because the form can store it. Only ask for data you need, explain it clearly where needed, and keep retention rules in mind.
Ticketing
Need ticketing and payment tools for your event?
SmartGig helps organisers sell tickets, manage payments, support buyers, scan QR tickets and keep event operations connected in one workspace.
Related articles
Set Up Ticketing on an Event
Create the ticketing workspace from a central event, choose the right setup path, and prepare the public ticket page without opening sales too early.
Ticketing Setup Readiness and Publishing
Use the readiness checklist, preview, visibility settings, buyer policies, support details, and launch checks before opening public checkout.
Ticket Types, Schedules, Capacity, and Passes
Set up the tickets customers can buy, including prices, capacity, sale windows, schedule choices, add-ons, reusable passes, and entry windows.