Group Ticket Orders: How to Collect Information From Every Guest, Not Just the Buyer

Here's the honest answer: Most ticketing tools think in orders. One buyer, one form, one set of answers. To welcome every guest equally, you need ticketing that works per ticket, so each person in a group gets their own ticket and answers their own questions, even when someone else paid.

This piece comes from Kelsey's conversation with Rachel Gillman Rischall and Jeana Anderson Cohen on The Connection Code, "From Gathering to Belonging." Watch on YouTube or listen on Apple Podcasts.

The person who didn't buy the ticket

Picture three friends going to a dinner. One of them buys all three seats. The host now knows that friend's name, email, and dietary needs. The other two? They're a quantity field.

Then one of them shows up with a shellfish allergy nobody asked about. Or a name tag is missing. Or the host greets the buyer warmly and the other two get a nod.

When Rachel and Jeana asked me about the small online touches that make guests feel cared for, this was the first thing I talked about:

"Most ticketing tools think about information on a per-order basis. We set Eventually up to be per ticket. If all three of us are going to an event and I buy the tickets, it's still really easy for me to gather information about Rachel and you, so that we can all be welcomed in equally as guests."

Why per-order ticketing became the default

This isn't anyone being careless. Commerce systems are built around orders because orders are what get paid for. That works for t-shirts. It works less well for people.

For a calendar-centric business, the thing you're selling is a seat that a specific human will sit in. If the system only knows the buyer, the host spends the days before the event chasing emails, building spreadsheets, and guessing.

Common workarounds, and where they break:

Ask the buyer for everyone's details

What works: It's quick to set up. What breaks: The buyer often doesn't know their friends' sizes or allergies, so you get blanks, guesses, or "I'll ask them."

A follow-up form after purchase

What works: You can ask anything. What breaks: Response rates drop, and you're now matching form submissions to orders by hand.

Collect it at the door

What works: It's accurate. What breaks: It's too late for anything you needed to prepare, and it slows the line.

What it costs

The real cost isn't the spreadsheet. It's the guest who feels like an afterthought at a moment that's supposed to feel personal. And it's the follow-up you can't send, because you never had their email.

"For so long hosts see orders as a monolith, and they don't get the chance to really engage with all of the people that are going to be there in person."

What good looks like

  • One ticket per guest, each with its own name and email.

  • Tickets delivered to each guest individually, so nobody waits on the buyer to forward a PDF.

  • Questions that match the ticket type, so the workshop seat and the VIP add-on ask different things.

  • Answers that travel with the ticket, visible at check-in.

  • Every guest reachable afterward, not just the person who paid.

How Eventually handles it

Eventually is a native extension for Squarespace, built per ticket from day one. When someone buys for a group, they can add each guest's email and Eventually sends each person their own ticket. Hosts can attach questions to specific ticket types (food allergies, t-shirt sizes, personal interests, preferences) and each guest's answers show up on their ticket. For larger events, there's a QR code to scan at the door.

"No matter who's buying the tickets, we've made it really easy for hosts to learn about each and every guest."

Payments run through Squarespace Payments, so the money lands where the rest of your Squarespace Commerce does.

What to do right now

If you run dinners or tastings: Make dietary needs a per-guest question, not a buyer question. It's the one you can't fix at the door.

If you run workshops with materials: Ask for sizes or skill level per seat so you can prep the right kits.

If you host members and their guests: Collect a name and email for every guest so you can welcome them by name and invite them back.

If you're stuck on a per-order tool: Send a short pre-event form with a deadline, and keep the questions to what you'll actually use.

The bottom line

Every person who walks through your door is a guest, regardless of whose card was on file. Hospitality means knowing them before they arrive.

That's why we built Eventually per ticket. The friend who got invited along deserves the same welcome as the friend who bought the seats, and they're often the one who comes back next.

Keep reading

Welcome every guest by name

Set up per-guest questions on your first event at eventuallyticketing.com.

WOTW

Websites on Squarespace, calendars on Eventually and stores on Shopify, custom built by your dedicated WOTW team.

https://www.weekofthewebsite.com
Previous
Previous

Press Release: Squarespace event ticketing is now in the Extensions marketplace

Next
Next

How to Get Guests to Come Back to Your Events