Design principle: keep the main line moving
Walk-in counters fail when exceptions are handled in the main queue: disputes, change requests, payment delays, and “which ticket should I buy?” conversations. Your system must route exceptions away from the core flow.
Recommended layout: serpentine queue + token + exception desk
- Serpentine queue: One line feeding multiple counters to balance load.
- Token desk (optional): Issue a printed token when the crowd is large, so guests can wait in a holding zone.
- Exception/help desk: Reschedules, refunds, ID issues, and “QR didn’t arrive” cases.
Token workflow (step-by-step)
- Issue token: Print token number + timestamp + counter group.
- Display and announce: Screen shows “Now serving: T-128”. Announce every call.
- Serve fast: Counter script focuses on ticket type, quantity, and payment only.
- Issue ticket: Print ticket + deliver QR via SMS/WhatsApp/email when possible.
- Route exceptions: Any dispute goes to help desk; counter continues with next token.
Payment handling: reduce counter time variance
Service-time variability is what creates spikes. Standardize the process:
- UPI-first: Prefer UPI to reduce cash counting and change.
- Cash lane only if needed: Split by payment only when cash materially slows the system.
- Receipt discipline: Every payment generates a receipt linked to the issued QR.
QR issuance rules that reduce “I didn’t get it” support
- Show QR on print: Printed ticket includes QR and human-readable ticket ID.
- Digital copy: Send to phone as backup where possible.
- Reprint policy: Allow reprint only with payment proof and ID, logged under staff account.
Counter SOP worksheet
Use this to standardize your walk-in operations and reduce queue time variance.
Must-have controls
- Exception desk with authority.
- Visible token display.
- Receipt linked to ticket ID.
- Reprint policy + audit log.
Need walk-in ticketing + QR gate scanning in one stack?
Talk to Finlo