The guest list most places have is an export. It is a snapshot of one event, it is stale the day after it is made, and it cannot answer the only questions worth asking: is this person new, how often do they come, what did they book last time, and have they already failed to turn up twice. A record built out of the bookings themselves answers all four without anybody maintaining it.
What one record holds
None of this is typed in. It is what the bookings already say, gathered against the person who made them.
- Every visit: booked, completed, cancelled, did not turn up, and what is still to come
- What they have spent with you altogether, and what they have run up on site
- When they first came, when they last came, and when they are next expected
- Your own tags and notes: the quiet table, the nut allergy, the one who always brings eight
- Whatever you asked at booking: pick-up point, licence number, dietary needs, shoe size
- Whether they have asked not to be marketed to, which is honoured where it matters
The person at the desk knows all this already. The point is that whoever is on the next shift does too.
Regulars, without relying on somebody's memory
Small operations run on recognition. Somebody walks in, the owner knows them, and the whole visit is better for it. That stops working the day the owner is not on shift, or the day the business outgrows one person's memory.
The counts are rolled up in the background rather than recalculated on every page load, and the screen tells you when they were last built instead of implying they are accurate to the second. Corrections stay corrected, too: if the same person once booked with a phone number and once with an email, merging them is permanent, and a later rebuild will not pull them apart again.
Asking the list a question
A segment is a question you save rather than a list you copy. It tells you how many match before you do anything with it.
- People who came once and never came back
- Everybody with something booked in the next fortnight
- Your biggest spenders, or everyone who has ever failed to turn up
- Anyone who booked a particular thing, for the season it runs again
They are your guests
Records belong to your organisation rather than to a pool shared across the platform, and any segment exports as a CSV whenever you want it, which is the honest test of whether a business owns its own customer list. Marketing preferences travel with the record: somebody who opts out is left out of the lists that are for marketing, and still gets the confirmation, the reminder and the change of plan for something they have actually booked, because those are not marketing.
Common questions
Where do the records come from?
The bookings. A record is created and kept current from what people actually book, so there is nothing to import and nothing to maintain by hand. Walk-ins taken at the counter build records the same way, which is usually where the biggest gap in a guest list is.
What if the same person appears twice?
It happens: once with a phone number, once with an email, once with their name spelled differently. You can merge them, and the merge is recorded against their identity rather than against the visible record, so a later rebuild of the statistics does not undo it.
Can we ask our own questions at booking?
Yes, per thing, so a dive can ask for a certification level and an airport transfer can ask for a flight number without either asking the other's question. The answers sit on the booking, on the guest's record and on the day's roster, which is where whoever is running the shift actually needs them.
What gets sent to guests automatically?
A confirmation when they book, a reminder before they come, and a message if something changes or is cancelled. You can also send one guest a templated email with your own note on it, or re-send their code if it went missing. The venue itself can be notified by email and SMS when a booking lands, which matters when the person who needs to know is not the person watching a dashboard.
Can we get our guest list out?
Any time, as a CSV, for the whole list or for any segment of it. The records are scoped to your organisation and are not shared across the platform.
The rest of what we do
On-site operations
The gate, the counter and the guest tab, on one code and one ledger.
Read more
Box office
Quicket POS at the counter: walk-up sales from the same inventory as your web store, with printed tickets.
Read more
Coming soonQuicket Studio
The organizer app for your phone: build events, run the door and follow the sales.
Read moreTell us about the event
Tell us what you need to know about a guest before they arrive, and what you wish you had asked at booking. Those two questions usually design the whole thing.
Prefer email? support@quicket.me