Queue Kiosk Quantity Configuration: A Sizing & BOQ Guide for Hall Projects

2026-10-15

When a client asks "how many queue kiosks do we need?" the answer cannot come from floor area or counter count alone. The correct queue kiosk quantity configuration affects visitor experience, staff workload, project CAPEX, installation schedule, and long-term service cost. This guide provides a practical sizing framework for brand owners, system integrators, and project contractors planning hall projects—from single sites to multi-site rollouts.

Why Queue Kiosk Quantity Configuration Is a Project Decision, Not a Hardware Guess

In hall projects across banking, government, healthcare, and telecom sectors, under-configuration and over-configuration both carry real project risks. The table below summarizes the consequences that project teams typically encounter:

If Quantity Is Underestimated

  • Ticket-dispensing area becomes the first bottleneck
  • Visitors queue before reaching service counters
  • Staff must issue tickets manually during peaks
  • Client acceptance testing fails under peak load
  • Integrator faces change orders and rework

If Quantity Is Overestimated

  • Project budget and hardware CAPEX increase
  • Lobby space and installation points are wasted
  • More printers, paper, cleaning, and field maintenance
  • ROI becomes harder to justify to brand HQ
  • Future upgrades and layout changes become harder

The kiosk is the entry layer of the queue management system. If ticket issuance is congested, counter capacity, calling displays, and staff scheduling cannot fully compensate. Sizing must protect the entry point first.

Project Inputs: What to Collect Before Sizing

Traffic and Demand Data

  • Daily number of visitors who need a queue ticket
  • Peak-hour ratio, based on ticketing logs, footfall data, appointment records, or on-site observation
  • Seasonal, monthly, or campaign-driven traffic variations
  • Expected growth over the next 2–3 years

Process and Service Data

  • Number of business lines or service categories
  • Whether visitors must select services, verify identity, scan QR codes, enter phone numbers, or print documents
  • Average ticketing time per visitor by workflow type
  • Whether mobile appointment, remote check-in, or virtual queue will divert walk-in traffic
  • Language, accessibility, and assisted-service requirements

Site and Deployment Data

  • Hall layout, entrance position, waiting area, counter zones, and circulation routes
  • Available floor area, power, network, and mounting conditions
  • Number of floors or service zones
  • Brand guidelines, enclosure color, logo placement, and UI requirements
  • Target rollout schedule, pilot site, and total number of locations

Quick Sizing Method: 

Step 1: Estimate Peak-Hour Demand

Multiply daily ticketed visitors by the peak-hour ratio. For example: 800 daily visitors × 15% peak-hour ratio = 120 peak-hour visitors.

Step 2: Define Ticketing Time by Workflow Type

Workflow Type Typical Steps Tüüpiline kestus Hardware Implication
Tier 1: Simple Touch service category → print ticket 8–15 sec Basic touchscreen, thermal printer
Tier 2: Identified QR scan, membership card, or phone-number entry 20–35 sec QR scanner, NFC, keypad
Tier 3: Verified ID read, registration, or document scan 35–60 sec ID reader, camera, secure module bay
Tier 4: Complex Multi-step government or medical registration 60–90 sec Large screen, guided UI, document printer

Step 3: Use the Quantity Reference Table

Peak-Hour Ticket Users Tier 1: Simple Tier 2: Identified Tier 3: Verified Tier 4: Complex
Under 50 1 1 1–2 2
50–100 1 1–2 2–3 3–4
100–200 1–2 2–3 3–5 5–8
200–350 2–3 3–5 5–9 9–14
350–600 3–5 5–8 9–15 15–24
600+ 5+ 8+ 15+ 24+ or multi-zone

Step 4: Adjust for Project Reality

  • Round up to the next whole unit
  • Add N+1 for critical sites or halls where downtime has a high service impact
  • Split by zone or floor if the hall has multiple service areas
  • Add at least one accessible-height unit per public zone
  • Add assisted-service capacity for elderly-heavy or government projects
  • Add spare capacity for expected traffic growth over 2–3 years

Key planning principle: A 15-second simple ticketing flow and a 60-second identity-verification flow require fundamentally different kiosk quantities. The workflow type must be determined before the quantity table is applied. For projects deploying across multiple branches, a standardized Järjekorra haldamise süsteem architecture ensures consistent configuration rules and centralized reporting across all sites.

Workflow-Adjusted Sizing: When Ticketing Time Is a Design Variable

In project planning, ticketing time is not a fixed input—it is a design outcome. Changing the workflow changes the required kiosk quantity. The table below shows how common design decisions affect the calculation:

Design Decision Effect on Ticketing Time Effect on Quantity Project Implication
Add mobile pre-selection (QR-only on site) 30 sec → 5 sec Quantity drops ~60% Invest in appointment system, reduce hardware BOQ
Merge multiple service categories into one menu 10 sec → 25 sec Quantity rises ~40% Fewer kiosks but higher per-user confusion risk
Add ID verification to existing simple flow 12 sec → 45 sec Quantity rises ~3.75× Higher hardware spec, longer queue buffer needed
Deploy a greeter to pre-sort walk-ins Reduces assisted-user share Effective throughput rises Trade labor cost against hardware cost

For integrators preparing client proposals, presenting two scenarios—a "baseline workflow" and a "streamlined workflow"—with the corresponding BOQ difference positions the kiosk quantity not as a hardware decision but as a workflow design outcome. This approach also aligns with the hardware selection criteria covered in this deployment guide, where connectivity choices (wired vs. wireless) affect both installation cost and maintenance planning.

Industry-Specific Case Studies with Country References

United States: Top 5 Retail Bank — Peak-Hour Sizing for High-Volume Branches

Banking Ameerika Ühendriigid

Deployment Context

A top 5 U.S. retail bank deployed Verint Queue Management across its branch network, with a focus on its largest locations. The bank faced lobby congestion from walk-in customers waiting in areas without formal queues, with staff manually tracking wait order and unable to communicate expected wait times.

Sizing Approach

The bank applied a virtual queue model: customers check in via a tablet, QR code, or lobby kiosk. The system captures the reason for the visit and language preference, then assigns the most knowledgeable banker available. The kiosk quantity was sized from peak-hour check-in demand rather than counter count, with additional units in high-traffic branches to absorb arrival surges.

Tulemused

The bank achieved a 51% reduction in customer wait time in select branches and a 38% overall reduction across the network. Customer walkouts decreased by up to 20% in high-volume branches, and average customer service times improved by 10%.1

For bank branch projects, the key sizing lesson is that walk-in check-in demand—not teller counter count—determines kiosk quantity. A branch with 8 counters but low ticketing volume may need only 2 kiosks, while a branch with 4 counters and high transaction complexity may need 3–4. The bank queue kiosk implementation guide covers the full decision chain from ROI modeling to layout design.

United Kingdom: NHS Emergency Department — Verified Workflow at Scale

Tervishoid Ühendkuningriik

Deployment Context

King's College Hospital NHS Foundation Trust in London launched a digital check-in service for patients aged 18 and over at its Emergency Department. Self-service kiosks are installed at the ED entrance, allowing patients to provide key information about their condition, which feeds directly into the electronic patient record system (Epic).2

Sizing Approach

The department sized kiosk quantity based on arrival patterns at the ED entrance, where peak-hour check-in demand can spike unpredictably. The deployment included assisted-service provisions, with Customer Care Officers and volunteers available to help patients using the kiosks.2

Tulemused

The digital check-in service supports the ED team to provide safe, timely, and responsive care, and helps reduce long queues for patients upon arrival. The kiosks enable early identification and prioritization of the sickest patients, improving time to initial assessment and time to treatment.2

Healthcare queue kiosk projects involve a Tier 3 (Verified) workflow, where each user interaction includes patient identification and clinical information entry. This workflow type increases ticketing time and, consequently, the required kiosk quantity. The government service center deployment guide covers similar capacity planning principles, including the use of traffic data rather than assumptions for kiosk sizing.

Germany: Hennigsdorf Bürgerbüro — Tier 2 Workflow with Appointment Integration

Government Saksamaa

Deployment Context

The Bürgerbüro (citizens' office) in Hennigsdorf, Germany, installed a new check-in terminal near the entrance to address long queues at the service counter. More than 11,000 visitors used the office without prior appointment from March 2025 to year-end, with more than 4,600 additional visits handled after online appointment booking. Long lines formed particularly on Tuesdays and Thursdays, the designated walk-in days.3

Sizing Approach

The office deployed a single check-in terminal designed to handle both appointment and walk-in visitors. Users with appointments scan a QR code or enter a booking number; walk-in visitors tap the screen to select their service category anonymously. The terminal supports German and English, with on-screen guidance to waiting areas on other floors.3

Tulemused

The terminal is designed to create more discretion for visitors and reduce the burden on counter staff who previously had to manually direct traffic. The office plans to display queue numbers on large screens in the service area for real-time status visibility.3

For government hall projects, a Tier 2 (Identified) workflow with QR-code and booking-number entry typically yields 20–35 seconds per transaction. A single terminal can handle the volume of a medium-sized office, but larger service centers—such as those processing 2,000+ daily visitors—require 4–8+ kiosks distributed across service zones. The telecom and insurance hall hardware guide provides additional configuration guidance for multi-service environments.

Lithuania: Telia Telecom Stores — Multi-Site Rollout with Accessibility Focus

Telecom Lithuania

Deployment Context

Telia, a leading telecommunications provider in the Baltics, modernized its queue management system across 19 stores in Vilnius, Lithuania. The company selected QMatic software combined with Elo touchscreen hardware following a successful pilot and thorough evaluation.4

Sizing Approach

Telia opted for a 27-inch touchscreen display powered by the Elo Backpack Android compute engine, mounted on a Wallaby Pro self-service stand with printer. The solution was designed to align with Telia's updated store visual identity. The modular Wallaby Pro stand supports floor-stand, countertop, or wall-mount installations, allowing each store to use the configuration best suited to its layout.4

Tulemused

Accessibility was central to the project. Queue management terminals are installed at accessible heights and feature adaptive screen layouts and specialized keyboards for individuals with disabilities. The Wallaby Pro stands ship with an accessory faceplate for integration with ADA-compliant navigation keypads, enabling easier interaction for users with impaired vision, reading difficulties, or limited fine motor skills.4

Telecom store projects typically involve Tier 1–2 workflows (simple selection or QR identification) with daily ticketed visitors in the 300–800 range. A 1–2 kiosk configuration is standard, but accessibility requirements and multi-service routing may require additional units. For retail and telecom environments where branding consistency matters, a kioski riistvara valiku juhend covering cabinet materials and print mechanism durability is a useful reference for BOQ preparation.

Queue Area and Placement: Simple Rules for Hall Projects

  • Allow 8–15 square feet per person in the queue buffer zone
  • Keep a 3–5 meter buffer in front of the kiosk cluster to prevent congestion with the main circulation path
  • Do not block the main entrance or primary circulation route
  • Place kiosks where visitors naturally look for direction after entry
  • Use clear signage, floor markings, and staff guidance to separate walk-in ticketing from appointment check-in
  • Arrange multiple units side by side where possible, with at least one accessible-height unit per public zone
  • Connect the kiosk zone visually and physically to waiting seats, calling displays, and service counters
  • For multi-floor or multi-zone halls, use distributed clusters near service categories rather than concentrating all units at one entrance

Multi-Site Rollout: Standardize Without Ignoring Local Differences

Site Tiering Model

Site Tier Daily Traffic Base Kiosk Quantity Optional Modules Standardization Level
Tier 1: Compact Under 300 1 QR-skanner Fixed
Tier 2: Standard 300–800 1–2 QR NFC Fixed + 1 optional
Tier 3: High-Volume 800–2,000 2–4 ID reader, camera Modulaarne
Tier 4: Flagship 2,000+ 4–8+ Full module set, document printer Modular + site-specific

Standardization Rules for Brand Owners and Integrators

  • Common enclosure platform across all tiers. This reduces spare-part complexity and ensures a consistent brand appearance.
  • Field-replaceable printer module. Front-access design allows maintenance without removing the kiosk from service.
  • Optional module bays. Common enclosure with configurable slots for QR/NFC, ID reader, camera, and payment modules.
  • Standard mounting and cable management. Floor-standing, wall-mounted, and countertop variants share the same internal architecture.
  • Pilot-first deployment protocol. Validate ticketing time, failure modes, user behavior, and software integration at one Tier 2 and one Tier 3 site before mass rollout.
  • Spare-part and service strategy. Define field-replaceable units (FRUs), advance stock policy for Tier 3–4 sites, and remote monitoring for printer status, paper level, and network health.

A scalable kiosk program should consider standardization, field-replaceable modules, peripheral requirements, software ownership, and long-term serviceability—not only the initial unit price. For brand owners planning chain-wide deployments, the queue management system resource hub provides additional guidance on QMS architecture and integration planning.

Tender-Stage Quick Reference by Project Type

Projekti liik Typical Daily Ticketed Visitors Peak Ratio Baseline Kiosks Queue Area (Approx.)
Small bank branch Under 500 12–15% 1–2 80–120 sq ft
Hospital outpatient hall 1,000–3,000 15–20% 4–12 400–1,000 sq ft
Government service center 2,000+ 15–20% 6–14 800–1,500 sq ft
Telecom retail store 300–800 10–15% 1–2 50–80 sq ft
Retail service center 800–2,000 12–18% 2–5 150–350 sq ft

These figures are tender-stage estimates for budget planning. Final quantities require site survey, pilot validation, and actual peak-period measurement.

Common Mistakes in Project Quotations and Rollouts

  • Quoting by counter quantity. Counters reflect service capacity, not ticket-dispensing demand. The two are calculated independently.
  • Using average daily traffic instead of peak-hour traffic. Average-based sizing guarantees under-configuration during real peaks.
  • Treating all ticketing flows as the same. A 15-second simple flow and a 60-second identity-verification flow need different capacity.
  • Forgetting queue buffer space. A kiosk with no physical buffer zone creates congestion even at the correct device count.
  • Ignoring multi-zone layouts. A hall with separate floors or service wings cannot be served by a single entrance cluster.
  • No redundancy or spare-part plan. One printer jam or network issue can disrupt the entire entrance flow.
  • No standardization across sites. Every non-standard configuration adds spare-part complexity, installation time, and training cost.
  • No growth margin. A configuration that exactly matches current peak traffic will feel undersized after 12–18 months.

From Quantity to Specification: Building the Kiosk BOQ

Hardware Configuration

  • Screen size, touch technology, brightness, and enclosure material
  • Freestanding, wall-mounted, or countertop form factor
  • Thermal printer speed, paper capacity, and front-access maintenance design
  • ID card reader, passport scanner, QR/barcode scanner, NFC, camera, keypad, or payment module

Software and Integration

  • Queue management system compatibility
  • Appointment, CRM, visitor management, and analytics integration
  • API/SDK availability for integrators using proprietary software
  • Remote device management, OTA updates, uptime monitoring, and diagnostics

Brand and Project Customization

  • Logo, color, enclosure finish, startup screen, UI direction, packaging, labels, and manuals
  • Private-label or project-specific configuration
  • Sample validation, compatibility testing, aging tests, and mass-production readiness

For OEM/ODM projects, buyers commonly need to define application scenario, user flow, required modules, installation environment, software needs, quantity, and branding plan before requesting an accurate proposal. Qtenboard provides OEM and ODM services covering kiosk structure design, internal component layout, thermal printer integration, cable management, and software compatibility, backed by a daily output of 200 units and 16 production facilities across 330,000㎡ in Shenzhen and Guangzhou.5 Explore the Järjekorda kiosk toote lehekülg for detailed specifications and customization options.

RFP-Ready Sizing Checklist

  • Daily ticketed visitors and peak-hour ratio
  • Peak-hour arrival rate
  • Ticketing workflow type and average ticketing time
  • Required ID, QR, NFC, camera, printer, or payment modules
  • Number of service categories and queue-routing rules
  • Site layout, entrance flow, and waiting-area position
  • Number of floors or service zones
  • Accessibility and multilingual requirements
  • Software platform and integration interfaces
  • Branding, color, logo, packaging, and UI requirements
  • Pilot-site plan and rollout schedule
  • Spare parts, warranty, remote monitoring, and after-sales model
  • Target quantity, budget range, and delivery timeline

Korduma kippuvad küsimused

How many queue kiosks should be configured per service counter?
There is no universal ratio. Calculate kiosks from peak ticket demand and ticketing workflow type. Counters should be sized separately based on service duration and staff capacity. A branch with 8 counters may need only 2 kiosks if ticketing is fast and peak traffic is moderate.
Can one queue kiosk support multiple business types?
Yes. Dynamic menus can route visitors to different queues, but complex flows may increase ticketing time and should be included in the quantity calculation. For government halls with multiple service categories, consider distributed clusters rather than concentrating all kiosks at one entrance.
How long does a customer take to get a queue ticket?
Simple flows may take 8–15 seconds; QR check-in or membership card entry typically takes 20–35 seconds; identity verification or multi-step registration may take 35–60 seconds or longer. Each workflow tier has a different impact on the required kiosk quantity.
Do mobile appointments reduce the required kiosk quantity?
Often yes, because some demand moves off-site. Estimate the mobile penetration rate (e.g., 30–50% for banks, lower for government halls with elderly populations) and reduce the walk-in peak demand accordingly. Retain enough kiosks for walk-ins, appointment changes, and users without smartphones.
How should integrators plan a multi-site rollout?
Use a standard base configuration, classify sites by traffic tier, pilot one representative Tier 2 and one Tier 3 site, then scale with modular hardware and a defined spare-part strategy. Standardize the enclosure platform and field-replaceable modules across all sites.

Need a Queue Kiosk Sizing and BOQ for Your Next Hall Project?

Share your site traffic data, service workflow, and rollout quantity to receive a tailored sizing proposal, layout recommendation, and OEM/ODM quotation.


Qtenboard Queenie Wang

Queenie Wangi

Tegevjuht | Interaktiivne ekraani ja koostöö lahendusekspert

Olen Qtenboardi asutaja, tuues üle 17-aastase praktilise oskusteadmisega puute kuvatööstusesse. Võttes arvesse ülemaailmse juhtimise perspektiivi, mis on saavutatud minu EMBA uuringud ShenZheni ülikoolis, Ma juhin Tootmisvõime jääb tööstuse esirinnas.

Qtenboardi juhina olen spetsialiseerunud kohandatud OEM/ODM-lahenduste pakkumisele interaktiivsetele valgeplaatidele, LCD video seinad, digitaalsed signaalid ja tööstusliku kvaliteediga puuteterminalid. Toetas meie 330.000 m nüüdisaegse tööstuspargi Shenzhenis, säilitame täispuhastuse kontrolli tööstusdisaini, täpsuse tootmise, ja range jõudluse testimine.

Peaaegu kaks aastakümne pikkune projektikogemus kasutatakse Qtenboardi ekraani lahendusi nüüd rohkem kui 120 riigis ja piirkonnas, teenis usaldust üle 15000 ettevõtluskliendi üle maailma. Kui otsite tundlik partner sügava tootmise aluse oma kohandatud touch kuva projekte, Minu meeskonnaga oleme valmis toetama teie nägemust professionaalselt.