Turn it on
Enable time slots on your event and pick which ticket types need to choose a block. A day ticket with a time slot alongside an evening ticket without one is perfectly fine.
Time slots
Spread your visitors across the day
A gate that clogs up at 10:00, a guided tour with a fixed group size, or a museum day: give visitors a time window instead of one peak moment. You set it up once, after which the platform guards every block separately.
-
Generate your day schedule
Day window, block length and capacity — in one action
-
Visitors pick a block
At checkout, right next to the ticket type
-
At the door
The time slot is on the ticket and in the scanner
The process
How do time slots work?
Set up once per event. After that the platform counts per block.
Generate the blocks
Enter the day window — 10:00 to 17:00, say — plus the block length, an optional gap in between and the capacity per block. The whole series is there in one action. Running it again is safe: existing blocks are skipped.
Sell
Visitors pick their block at checkout. The platform refuses an order that no longer fits — even when two people check out at the exact same moment.
What it is for
When everyone wants in at once
From a busy gate to a guided tour with a fixed group size — anywhere you want to receive visitors in portions instead of one wave.
Busy events
A thousand visitors all standing at the gate at 10:00 makes a queue. Spread arrivals across blocks and the entrance, the cloakroom and the bar stay workable all day.
Guided tours
Every group its own start time, with a hard maximum size per departure. Nobody tags along who does not fit.
Museums & exhibitions
Split the day into windows so the room never gets too busy — and your visitors actually get to see the exhibition.
Open days & free entry
No maximum needed, but you do want to spread arrivals? Leave the capacity per block empty. Visitors pick a window and you know when to expect whom, without shutting anyone out.
Courses, workshops and lessons with enrolments work a little differently — there is a dedicated module for those.
Smartly handled
The details you only miss once they are gone
Built on what actually goes wrong in practice.
Shared or separate
Let several ticket types share the same block — one counter, so adults and children fill the same 25 places together. Or give each type its own stock. You choose per case.
Unlimited is fine too
Leave the capacity empty and the block never fills up. You then only spread arrivals — handy when you want to steer the crowd without imposing a maximum.
Full stays visible
A sold-out block stays in the list but cannot be picked. That way your visitor sees that 14:00 is popular, instead of the block vanishing without a trace. Past blocks do disappear.
It travels along
The time slot is on the PDF ticket, in the confirmation email and in the wallet pass. The box office at the door and a resold ticket hold on to the chosen block too.
Copy a day to another date
Happy with your day schedule? Put it on the other days of your event in a single action. The times stay put and every copy starts back at zero sold.
At the door
Being early is no disaster
A time slot steers your visitors, but never keeps them out.
The inspector sees it, the visitor comes in
Scan a ticket outside its chosen window and the platform still checks the visitor in, while the inspector gets an orange notice with the correct block. Anyone half an hour early does not get left standing in the rain — and you still get to see it.
Works without signal too
The offline scan list carries the time slot of every ticket. If the network drops at the entrance, the notice keeps working and everything syncs up later.
Example
A museum day
Generated once, 350 places neatly spread across the day.
Day window
10:00 – 17:00
Block length
30 minutes
Capacity per block
25 visitors
Number of blocks
14
Places across the day
350
Never more inside at once
25
Good to know
What time slots do not do
Better honest up front than surprised afterwards.
Blocks are named after their time
A block is called "13:00–13:30", not "Afternoon tour". A custom name per block is not possible — if you need the distinction, use separate ticket types.
The waitlist works per ticket type
Once every block is full or past, the ticket type counts as sold out and your visitor can join the waitlist. A waitlist for the 14:00 block alone does not exist.