Waiting in a line should not require installing an app, creating an account, or giving every visitor a complicated set of instructions. Queue is a focused browser-based product for small businesses, events, desks, and informal situations that need an orderly waiting list. An organizer creates the queue without signing up, receives a private management link, and shares a different public link as a QR code or ordinary URL. Visitors open that public entry point, optionally add a name, and receive their own ticket and private participant link. The result is a clear digital queue with deliberately separate access for the person managing it and the people waiting in it.
A digital queue removes the physical cluster, not the human decision
A paper list can be lost, a shouted order is easy to misunderstand, and a physical line forces people to stay in one narrow place. Queue gives the organizer one ordered list while each visitor keeps an individual ticket. It does not decide who deserves priority or invent rules for the business; the organizer remains responsible for how the queue is used. This makes the product suitable for straightforward waiting scenarios where a shared order is useful but registration, booking, payments, and a large administration system would add more work than value. Queue focuses on joining, waiting, calling, and completing the visit.
Public entry and private management use different links
When a queue is created, the public join link is meant to be displayed and shared. It can be opened from the generated QR code or copied into a message, sign, or screen. The private manage link is different: it gives access to organizer actions and should be kept only by the person responsible for the line. That separation avoids turning a public QR code into an administration key. Visitors do not need an invitation or organizer account, and the organizer does not need to collect email addresses merely to control access. Like any private access link, the manage URL should be stored carefully and not placed in the public QR code.
Visitors join from a QR code or ordinary browser link
A visitor scans the displayed QR code with the camera already available on their phone, or opens the same public destination from a shared link. There is no Queue app to install and no user account to create. A name can be added when it helps the organizer recognise the person, but it is optional rather than a barrier to entry. After joining, the visitor receives a ticket and a private participant link for that ticket. Keeping that link lets the visitor return to the relevant status page without searching for the public entry point again. The link should be treated as personal access to that ticket and shared only when the visitor intends another person to see it.
Each participant gets a focused status page
The participant link opens the visitor's own queue context instead of exposing the organizer's full list. It identifies the ticket and shows its current state, so the visitor has one place to check whether the ticket is still waiting, has been called, or is already finished. The product deliberately avoids promising SMS, push notifications, appointment booking, or a guaranteed waiting time. A digital ticket is most useful when the organizer also communicates how the line works in that location. Visitors should know whether they need to remain nearby, watch a display, listen for a call, or check their status page again. Queue records the order and state; it does not replace clear instructions from the venue.
The organizer controls the flow from one private page
The management page gives the organizer the actions required for a simple working line. They can call the next waiting ticket, mark a visit as served, record a no-show, or remove an entry that should no longer remain. The queue can be paused when new arrivals must stop temporarily, resumed when entry can continue, and closed when the session is finished. These actions are intentionally focused on one organizer workflow. Queue does not claim multi-staff assignment, reservations, automated prioritisation, payments, or customer messaging. Keeping the first version narrow makes the current state easier to understand and reduces the setup needed before the first visitor can join.
No sign-up means fewer identity details by default
Neither side needs a permanent profile for the basic flow. The organizer should choose a queue title that is useful without including confidential information, and visitors should enter only a name they are comfortable displaying in this context. A ticket or private link should not be posted publicly because possession of the link grants access to the corresponding view. The public QR code is intentionally shareable; the management and participant links are intentionally private. This boundary is simple enough to explain at the point of use. It also means the organizer should close a queue when it is no longer active instead of treating an old management link as a permanent business account.
Create the queue before the first person needs it
Open Queue in a modern browser, create a queue, and save the private management link. Display the public QR code where visitors arrive or send the public link through the channel they already use. The first visitor can join immediately, optionally add a name, and keep the participant link attached to the new ticket. From the management page, work through the waiting list with call-next and the final served, no-show, or remove action that matches what happened. Pause entry when necessary, resume it when the line reopens, and close the queue at the end. The whole process stays in the browser and begins without registration.