Topic

Guests book on your booking page (embedded on your site or opened as a link). They never see Settings — only the steps you turned on.

A typical visit

1. Choose what / how many — package, game, party size, or tiles
2. Pick a time — calendar or timeline of free slots
3. Pick a place (optional) — table, room, attraction — or let the system assign one
4. See the price — fixed items, menu picks, or prices from headcount
5. Pay (if you require it)
6. Done — on-screen confirmation; email to the guest and often to your team

That sequence is a procedure: an ordered list of steps. Guests click Next; you build the list in Settings.

What you decide

• Which steps appear, and in which order
• Opening hours and slots (time plans)
• Prices and menus
• Whether payment is required before the booking is saved

Where to go next in the docs

• Copy a full procedure → Examples (start with Classic occupancy)
• Look up one step → API
• Solve a specific twist (weekend prices, holds, …) → How to

Next

• Your day in the app
• Choose your setup