Core concepts
Core concepts
Five ideas explain most of how the product behaves. The instruction pages assume them, so it is worth twenty minutes here before working out why a wait estimate says what it says.
The concepts
- How Queue Join worksOrganisations, locations, queues and visits — and the two dashboard views.
- Waitlist and bookingsTwo ways in, one system behind them.
- Services and resourcesWhat customers ask for, and what you have to give them.
- Time zones and local daysWhy every location keeps its own clock, and what that changes.
- The visit lifecycleEvery state a visit or booking can be in, and what each one sends.
The whole model in one paragraph
An organisation is your business and owns everything. It has one or more locations, each with its own address, time zone and opening hours. A location has queues that walk-ins join and accepts bookings for a future time. Either way a customer ends up with a visit that moves through a fixed set of states, sending messages as it goes. Services record what the visit is for and how long it should take; resources are the people and places that can do it.