utility

Queue Board

Issue queue numbers and call people in order at one to four counters, with a separate display window, history CSV, and printable number tickets.

Local processing
About your filesFiles and content selected in this tool are processed in your browser and are not uploaded to a Browser Kitty backend.
Operation demo See the basic workflow in a short video.

About this tool

Queue Board manages numbered queues for small events, temporary reception desks, and pickup counters. Operate one to four counters from a single browser screen and call the first waiting ticket at each available counter. Existing ticket numbers can also be added manually.

Open the waiting-room display in another window of the same browser and move it to an external monitor. Reception history and settings stay on the device, while ticket printing and history CSV export are available in the same app. This is not a remote-device synchronization or online booking service.

Good for

  • Hand out numbered tickets and call visitors in order at temporary event reception
  • Manage a pickup queue or several counters from one device
  • Show large calling numbers on an external monitor connected to the same computer

What it can do

Key capabilities available in this tool.

How to use

  1. Set the starting number and one to four counters, optionally changing counter names and display settings.
  2. Start reception and use Issue ticket to add sequential numbers. Existing numbers can be added manually.
  3. Choose Call next at a free counter, then use Call again, Complete, or Absent as needed. Absent tickets can return to the end of the queue.
  4. Choose Open display to show numbers in another window of the same browser. Move that window to an external monitor when available.
  5. Review statuses and timelines in History and save CSV when needed. Ending reception shows a summary and stores the completed session locally.
  6. For printed tickets, use the header printer button to set the number range, digits, title, paper, and tickets per page before printing.

Supported

  • Queue management: sequential issue, manual numbers, waiting / called / completed / absent states, and one to four counters on the same screen.
  • Display: another window/tab in the same browser environment, with large numbers, recent calls, optional waiting counts, and a built-in chime.
  • Local storage: active-session autosave and resume, completed-session storage, history status filters, and UTF-8 BOM CSV export.
  • Number tickets: A4 / Letter, 1–6 digits, 1–20 per page, and up to 1000 per print job.
  • Environment: Japanese / English and desktop / smartphone layouts. Chrome / Edge are the primary targets; Fullscreen and Screen Wake Lock depend on browser support.

Limitations and notes

  • Display synchronization stays within the same browser environment. It cannot synchronize a phone's operator screen with a separate computer or tablet.
  • SMS, email notifications, online reservations, cloud sync, customer names/phone numbers, payments, and staff accounts or permissions are not supported.
  • Resuming reception depends on browser storage. Clearing site data, private-browsing restrictions, storage policy, or device failure can prevent recovery.
  • Normal operation is designed around approximately 1000 tickets per session, not a guaranteed capacity. Large history lists may use significant device memory.
  • A print job is limited to 1000 tickets. Actual print margins and scale can vary with the browser, OS, and printer settings.

Frequently asked questions

Can I operate on my phone and display numbers on another computer?

No. In v1.0.0 the display runs in another window/tab of the same browser environment. You can move that window to an external monitor connected to the same computer.

Can I use ticket numbers that have already been handed out?

Yes. In addition to issuing sequential numbers, you can manually add existing ticket numbers to the waiting queue.

Can I continue reception after reloading the page?

Yes, when the active session remains in local browser storage. Storage restrictions or cleared site data can prevent recovery.

Can I print numbered tickets?

Yes. Choose A4 / Letter, 1–6 digits, and 1–20 tickets per page, with up to 1000 tickets per print job.

Is reception state sent to a server?

No. Numbers, queue state, settings, and history are processed in the browser. The hosted app may load its HTML at startup or when opening a display, but reception state is not included in those requests.

Offline version and source code

queue-board.html contains the UI, JavaScript, SVG icon, translations, print CSS, and chime generation in one file. Open the saved HTML directly in a supported browser for offline use. Display synchronization stays within the same browser rather than sending reception state to another device or an external API.

View source on GitHub