Electronic queue and ticket kiosk for a service center
Employer
Ivan
Project parameters
Type of cooperationOne-time project
SectionWeb development
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 05:25 until Sep 16, 2026
Project description
We run a busy service center where several counters handle different kinds of visits, and the current "take a paper slip and guess" arrangement no longer copes. At peak hours people crowd around the reception, nobody knows whose turn is next, staff waste time calling out names, and complaints about unfair jumping are constant. We need a complete electronic queue and ticketing system built around a self-service kiosk, a calling display, staff workstations and honest wait-time analytics, so that a visitor simply picks a service, receives a numbered ticket and watches for the call in comfort.
The kiosk part should let a person choose the reason for the visit from a clear menu, print a paper ticket with a number and, optionally, receive the same number by phone so they can step outside and return when it is close. A large call display over the counters must show the currently served numbers and the counter each is assigned to, with a short sound signal and, ideally, voice announcement of the called number. Every operator gets a simple dashboard to call the next visitor, redirect a ticket to another service, pause their window and mark a case as finished, so the flow keeps moving without manual shouting.
On top of the live flow we need reporting: average and maximum waiting time, service duration per counter, load by hour and by day of week, and the share of visitors who left without being served. We would also like the queue to connect with pre-booked appointments, so a person with a scheduled slot is placed into the flow at the right moment rather than starting from scratch. Please describe your proposed architecture, the hardware you assume on our side and a realistic timeline.
Key deliverables:
— self-service ticket kiosk with printing and phone ticket option;
— call display with sound and number announcement;
— operator dashboards and a supervisor monitor;
— wait-time and load analytics with exportable reports;
— integration with appointment booking.
The kiosk part should let a person choose the reason for the visit from a clear menu, print a paper ticket with a number and, optionally, receive the same number by phone so they can step outside and return when it is close. A large call display over the counters must show the currently served numbers and the counter each is assigned to, with a short sound signal and, ideally, voice announcement of the called number. Every operator gets a simple dashboard to call the next visitor, redirect a ticket to another service, pause their window and mark a case as finished, so the flow keeps moving without manual shouting.
On top of the live flow we need reporting: average and maximum waiting time, service duration per counter, load by hour and by day of week, and the share of visitors who left without being served. We would also like the queue to connect with pre-booked appointments, so a person with a scheduled slot is placed into the flow at the right moment rather than starting from scratch. Please describe your proposed architecture, the hardware you assume on our side and a realistic timeline.
Key deliverables:
— self-service ticket kiosk with printing and phone ticket option;
— call display with sound and number announcement;
— operator dashboards and a supervisor monitor;
— wait-time and load analytics with exportable reports;
— integration with appointment booking.
