Queue management or appointment booking: which does your branch need?

What queue management does

A queue management system turns arrivals into an ordered flow. Customers take a ticket for the service they need, wait where they can see their number, and are called to a counter.

With Nexus Queue, customers take a ticket at a self-service kiosk and choose the service, priority and language from those offered. The ticket shows their number, the people ahead and the estimated wait, and the hall board shows where they are called.

What appointment booking does

Appointment booking moves part of the demand ahead of time. Customers choose a day and a time slot before they leave home, so the branch knows who is coming. The branch can then plan staff and rooms around those visits.

In Nexus Queue, where a branch offers booking, customers book online by choosing a branch, a day and a free time slot. They receive a booking reference and a QR code. On the day, they check in at the kiosk and get their ticket.

Which services suit booking, and which suit walk-ins

The answer is usually different for each service. A simple test is how long the service takes and how much has to be prepared before it starts.

• Booking tends to suit longer consultations, services that need documents checked beforehand, and services that only a few specialist staff can provide.
• Short transactions and urgent needs usually stay walk-in, as do customers who cannot plan ahead.

Why one without the other leaves gaps

Booking alone does not organise the people who walk in without a slot. A queue alone gives the branch no view of who is planning to come.

One customer booked a slot last night; another walked in a minute ago. Both expect to be served, and someone has to decide who is called next. The branch also needs to know where demand comes from, and what happens when a customer cancels.

How Nexus Queue runs both

Nexus Queue handles walk-in and booked visits. A branch can switch on online booking while walk-ins continue as usual. Each service is set as walk-in only or open to online booking, and bookings are offered only within branch hours. One service can take both booked visits and walk-ins.

Bookings and walk-ins can have their own number runs, so a booking and a walk-in never share a number. Customers can cancel or reschedule within branch limits.

Who is called next, and what supervisors see

Each calling policy in Nexus Queue serves first come, first served, or follows ordered rules. Booked customers are called according to the priority rules the branch sets, and each call shows staff the rule that decided it.

Supervisors see whether tickets were walk-in or booked. They also see late tickets and uncovered queues earlier, while there is still time to act. Reports include a wait-time distribution and ticket-level history, with CSV, Excel and PDF export.

Early arrivals, late arrivals and no-shows

Any branch that takes bookings needs a rule for customers who come early, come late or do not come at all. Whatever the rule, make it clear, so staff apply it the same way and customers know it before they book.

In Nexus Queue, the branch sets the kiosk check-in window for booked visits. When a called customer does not come to the counter, staff can call again or mark a no-show with a reason, which appears in the ticket history.

Measuring the mix

Once both channels run, managers need to know how demand splits between bookings and walk-ins, and how waiting differs from one service to another. In Nexus Queue, staffing and service targets can be set from measured demand.

Before you choose: a short checklist

• Decide which services need a booked time slot and which stay walk-in only.
• Set how booked customers are called when walk-ins are waiting.
• Agree what happens when a booked customer arrives early or late.
• Check that supervisors can see both kinds of demand in one place.
• List the reports your managers need.