Skip to main content

Sessions [Beta]

Sessions let you run time-specific offerings like events or classes with capacity control, resource blocking, and per-session rosters and analytics.

Jakob Larsson Stern avatar
Written by Jakob Larsson Stern
Updated today

What are Sessions?

Sessions are a type of service that let you run offerings that happen at specific times — from multi‑track events to recurring group classes — with true capacity, resource blocking, and per‑session attendance. Each customer still gets their own visit for check‑in and messaging, but the occurrence they join is a shared time slot with a set number of spots.

Looking to set things up now? Jump to configuration for events with one or multiple sessions or recurring group classes.

Why use Sessions instead of Standard services

If guests should converge on the same time with limited seats, Sessions fit better than Standard services (where each guest chooses any time during open hours).

  • Sessions: Capacity‑based occurrences at specific times, optional resource assignment and blocking, per‑occurrence analytics.

  • Standard services: Guest‑picked times within availability windows, usually one‑to‑one.

How Sessions work

Think of a Session service as a container. Inside it you create one‑off sessions or recurring schedules. Each occurrence has:

  • A time window

  • A capacity ceiling

  • Optional resources (people, rooms, equipment) that are blocked during the session

When a guest books, a visit is created for that occurrence — enabling check‑in, messaging, and reporting per session.

What Sessions looks like as a customer

For events, guests browse a visual schedule, pick one or more sessions, and receive a single confirmation that includes per‑session QR codes and status pages — all based on your configuration.

For recurring classes, guests choose one or more occurrences from the Sessions tab and get confirmations per occurrence.

What Sessions looks like for staff members

Sessions appear on the Calendar with remaining versus booked spots. Clicking a session opens the roster to add customers, bulk message, bulk serve, or cancel the occurrence. Visits roll up to the session for attendance.

Shared building blocks

There are suggested configuration options when setting up events or recurring group classes. However, you'll notice some core concepts and tasks being used in both setups. Skim this list to understand the common mechanics, then jump into the step‑by‑step guides when you’re ready to configure your specific use case.

  • Creating session occurrences and recurrences

  • Capacity, visibility of remaining spots, and optional waitlists

  • Resource assignment and automatic blocking

  • Check‑in, QR codes, attendance tracking

  • Messaging attendees and cancellations

A few things to keep in mind

  • Try not to mix service types in one booking. Bookings can include either standard services or session services, not both.

  • Remember to assign resources to the sessions. If resources aren’t attached, calendars won’t block and conflicts may occur.

  • Decide whether to allow, disallow, or warn on overlapping session selections and configure this in Service options. Choose what happens if guests try to book multiple sessions that overlap in time:

    • Allow — Guests can book conflicting sessions

    • Disallow — Guests can only book one at a time

    • Warn — Guests see a warning but can still proceed

  • If you want to allow party size bookings in sessions, make sure the following settings are turned on:

Next steps: Configure your setup for events with one or multiple sessions or recurring group classes.

Best‑practice guidance when setting up Sessions

Start by deciding whether you are running an event or a recurring class. Create a dedicated Session service for that purpose, then add the occurrences that match your agenda or weekly cadence. Assign e.g. rooms and instructors as resources so sessions block times in those calendars. Finally, test the guest flow, scan a sample QR at check‑in, and review the session on the Calendar to confirm roster actions work as expected.

  • Events: Consider a dedicated location for the event to avoid configuration conflicts with other services.

  • Recurring classes: A single Session service with one or more recurring schedules is often sufficient; expand capacity or add a second schedule as demand grows.


Have additional questions or need assistance? Reach out to us via chat or at support@waitwhile.com

Did this answer your question?