A public queue people can understand at a glance.
Run service-specific public queues with QR or assisted check-in, numbered tickets, secure staff roles, waiting screens, and reporting.
Direct visitors to the right counter, show only the information needed in public, and give service teams one shared view of demand. Start with a focused branch or office pilot before a wider rollout.
How it works
- Select the required service
- Receive a numbered token
- Wait using the screen or phone
- Go to the service desk when your number is called
Queue management for Banks and public services
Mixed service demand
Separate teller, verification, application, and support queues with clear labels.
Privacy on public screens
Use numbered tickets so displays do not need to show names or phone numbers.
Surge days
Open temporary queues for camps, deadlines, and event days while preserving reporting.
Features
- Assisted and QR check-in
- Separate queues per counter or service
- Number-only waiting screen
- Role-based access
- Integration API
- Daily volume analytics
Frequently asked questions
Do visitors need to install an app?
No. They join from a QR code or link and follow a live ticket in their mobile browser. They can turn on optional browser turn alerts from that ticket.
Can staff add someone without a smartphone?
Yes. An authorised team member can add a walk-in from the staff board and share the ticket number directly.
Can existing software connect to WaitGate?
Yes. Integration endpoints can list your queues, read queue status and add people to a queue. Email hello@waitgate.com to set up an integration token.
Is Aadhaar required?
No. A normal WaitGate queue does not require Aadhaar. Identity checks should stay in the authorised service system.