The walk-in queue: one idea, three businesses

Booked appointments are only half of how service businesses actually run. The other half is the line — the people who show up now. Opraly treats that line as a first-class feature: the walk-in queue with online check-in. The same primitive powers three very different counters.

Salon walk-ins

A customer walks in, or checks in from their phone before they arrive. They join the queue, see a realistic wait, and your team works the list in order — without losing track of the next available stylist. Walk-ins and booked appointments share one calendar, so nobody gets double-promised the same chair.

The restaurant host stand

Same idea, dinner rush. Guests check in online or at the host stand, the waitlist quotes a wait, and the host seats from the queue. When the table is ready, a message goes out — and the visit can carry a tab straight through to payment and tips.

The taxi stand

At a rank or a venue, riders check in to the stand and dispatch assigns the next available driver. The queue keeps the order fair and visible, and the ride flows into the same payment and reporting pipeline as a pre-booked job.

Why one primitive matters

Because it is one feature, everything around it is shared: 2-way messaging to tell people they are up, reporting on wait times and utilization, and a single view of who is here now versus who is booked later. Learn it once, and it works whether you run a chair, a table, or a car.

What a useful queue must answer

A paper list records names. An operational queue has to answer the questions that customers and staff are already asking:

• Who is next? The order should be visible and consistent, including when a booked customer and a walk-in need the same resource.
• How long is the wait? A useful estimate accounts for the work already in progress, not just the number of names on the list.
• Who can take the next job? Availability matters more than raw headcount: the next stylist, table, or driver must actually fit the request.
• How do we reach the customer? A ready notification lets people wait nearby without repeatedly checking the counter.
• What happened afterward? Completed, cancelled, and abandoned entries should feed reporting instead of disappearing from a whiteboard.

That shared model is why the queue can adapt to different businesses without forcing each one into the same workflow.

Design the check-in experience around the wait

Online check-in is most valuable when it sets expectations before arrival. Ask only for the details needed to place someone correctly, show that the quoted time is an estimate, and make the next step obvious. A salon may ask for a service and preferred stylist; a restaurant needs party size; a ride queue needs pickup context. The interface changes, but the promise stays the same: join the right line and know what happens next.

Staff also need a small set of clear actions — check in, assign, notify, start, complete, or remove with a reason. Keeping those states explicit prevents two employees from serving the same person and makes handoffs understandable during a shift change.

Measure whether the queue is helping

Start with three numbers: quoted versus actual wait, the share of people who leave before service, and time from ready notification to service start. Review them by hour and day, because a healthy Tuesday average can hide a broken Saturday rush. If actual waits regularly exceed the quote, adjust capacity or the estimate. If people abandon after being notified, shorten the return window or make the instructions clearer.

The goal is not merely a digital line. It is a calmer arrival experience, better use of staff and resources, and fewer customers lost because nobody could tell them when their turn would come.