Core concepts
How Queue Join works
Queue Joinnests four things: your business, its branches, the lines people wait in, and the individual visits. Almost every question about “why can I not see that?” is answered by knowing which level a thing lives at.
The hierarchy
Organisation
Your business, created when you sign up. It owns your plan, your billing, your team, your customers, your services and your resources. Everybody you invite joins the organisation, not a branch.
Location
One physical place. It has its own address, time zone, opening hours, settings, messages and waitlist. A single-site business has exactly one and can mostly forget the distinction; a chain has many, and this is where they differ from one another.
Queue
A line within a location. Walk-ins join a queue. Most locations need one.
Visit or booking
One customer, one occasion. A walk-in creates a visit on a queue; a booking creates an appointment for a specific time. Both belong to a location, both reference a customer, and both move through a lifecycle.
The two dashboard views
The dashboard has two modes, switched at the top of the screen. They are not a filter — the sidebar itself changes, because the two jobs are different.
Account view
Everything at once: overview, locations, customers, QR codes, analytics, reports, marketing, team and account settings. This is where an owner works.
Location view
One branch: its overview, its waitlist, its appointments, its customers, its marketing and its settings. This is where a manager or a member of staff works all day.
If a page seems to have vanished, check which view you are in. The waitlist only exists in the location view — there is no meaningful combined list of every branch's queue to work through. QR codes only exist in the account view, because the page already lists every code and lets you pick a location.
Staff may only have one view
Somebody restricted to a single branch effectively lives in the location view. That restriction is enforced on the server, not just hidden in the interface — see team and roles.
Customers belong to the business
A customer record belongs to the organisation, not to a branch. Somebody who visits Camden on Monday and Shoreditch on Friday is one person with one history, which is what makes the history useful.
One consequence worth knowing: because a customer is not owned by a branch, restricting a member of staff to one location does not currently restrict which customers they can look up. Their waitlist, appointments and alerts are scoped; the customer directory is organisation-wide.