Run the day around your queue

Agree who owns the next step

A shared queue works best when the team agrees who opens it, who calls people and who handles the work that follows. Claari's pilot provides a QR join page, a private customer ticket and staff queue controls. Your operating routine connects those pieces to the rest of the business. It does not depend on pretending that a queue ticket replaces a booking, work order or sale.

Before opening: owner and shift lead

The owner or manager checks the location, services and access given to staff. The shift lead decides which services can accept walk-ins with the people actually present. Consult your existing staffing schedule and appointment book; this pilot does not promise shift planning or external-calendar sync. Assign someone to handle customers who need assistance and unresolved visits.

Check the join QR on a phone and make sure signs describe the right service. If using a lobby display, check its ticket-number view. Run a practice join and call before the busy period. Decide where the team will keep a temporary manual list if the app or network cannot be reached, and who will reconcile it afterward. Keep personal information out of public signs and screens.

During arrivals: reception and service staff

Reception confirms the service the customer needs. The person can join by QR without an app or account, or staff can add an assisted walk-in. Explain the private ticket and the manual calling process. Customers without email should keep the ticket page open. Email requires a configured provider and a known outcome; the pilot does not include SMS.

Before using Call next, the caller confirms that someone is ready to receive the customer. The receiving staff member owns the actual work. Use the queue states to record what has happened to that visit, and record the appointment, job, case or payment in the system that already owns it. A finished reception visit does not prove a finished repair, an approved case or a collected payment. The practitioner or adviser records the delivered work in the existing client, job or case record, then tells reception who owns checkout or follow-up. The cashier or administrator confirms payment or the next commitment in the appropriate system and resolves discrepancies with the shift lead. Service staff reset their workstation before declaring capacity for another arrival.

During a rush or a failure: named exception owner

If demand exceeds what the team can accept, decide whether to stop new arrivals and explain that choice to customers. Do not invent a waiting time. When someone misses a call, check with reception and follow the agreed recovery practice before marking a no-show.

If the ticket or board cannot be reached, say what is known and use the manual routine. Avoid creating another visit until staff have checked the original submission. After recovery, reconcile the list with people present before resuming normal calling. Do not promise automatic offline synchronization.

At handover and closing: shift lead

Review people waiting, visits already called and unresolved work with the incoming lead. Name the owner and next action for each exception. Close new arrivals when appropriate and explain the plan to anyone still waiting.

For a simple pilot review, manually note the observation period, how many arrivals you saw, interruptions and people who left. Use consistent definitions; these notes are not automatically calculated Claari reports or a proven improvement. Wider appointments, workplace resources, visitors, memberships, commerce, customization, agents and analytics remain platform direction, with availability and integrated completion varying.

Next step: Start the free pilot with one defined service and one accountable lead. Choose the salon, workshop or public-service guide for a more specific routine. The staff console currently remains in English.