Queue Module Concepts - Documentation Acosys

What This Module Does

A customer queue system for clinics, banks/credit unions, retail cashiers, or any service counter:

A kiosk prints queue numbers (or visitors scan a QR code to follow from their phone).
A waiting-room display shows and announces the number being called and its counter.
A counter screen lets staff call, serve, finish, skip, or transfer numbers.
Reports answer how long people waited, which counter is slow, which hours are busiest, and how many did not show up.

Term	Meaning
Service	A queue line with its own numbering: Dental, Teller, Cashier. The ticket prefix (A, B, C) and numbering rules are set per service.
Counter	Where a customer is served: Counter 1, Consulting Room 2. One counter may serve several services with its own pick order.
Device	A registered kiosk, waiting-room display, or counter desk display with a Device Token. A screen identifies itself by that token, not by a login.
Ticket	One queue number: A-012. Its status moves waiting → called → serving → finished; it can also become no-show, transferred, or cancelled.
Counter session	Staff open the counter when they start and close it when done; meanwhile they are the one calling numbers at that counter.
Priority	A ticket for elderly/disabled visitors taken ahead of normal numbers, when the service allows it.

Make sure the Queue Management feature is on in the licence/package; the menu appears only after that.
Go to the Queue Service form. If the list is empty, press Seed Preset and choose Clinic, Bank/Credit Union, or Retail - sample services and counters are created and can be edited.
Check each Service: ticket prefix, starting number and digits, daily/monthly reset, opening hours, active days, quota, wait and serve targets.
Check each Counter and its Counter Services tab: which services that counter may call, and in what pick order.
Register a Queue Device for each kiosk, waiting-room display, and counter desk display. Note the automatically generated Device Token.
For a printing kiosk: install Acosys Client on the kiosk computer, create a printer profile, and pick a Ticket Design from Print Designer.
Open the Queue Kiosk / Queue Display / Counter Screen page on each device and enter its token once; the token is stored in that device's browser.
Staff log in on the counter screen, press Open Counter, then Call Next.

Every screen asks the server every Poll Interval (default 30 seconds). This path is always correct and always available.
When Hub Address is set (the Acosys Client on the LAN, e.g. ws://192.168.1.10:9999), changes from the counter screen are broadcast instantly to other screens on the same network - without loading the server.
Hub down? Screens stop changing instantly but are correct again within 30 seconds through polling. Do not lengthen the interval "because there is a hub".
Leave Hub Address empty for tenants that only use a browser/PWA - a valid state, just slower.

Tickets are anonymous: not linked to a customer and holding no identity. The public status page uses a random token, not a name.
No offline kiosk mode: when the server is unreachable the kiosk shows "the system is not connected" rather than issuing numbers that could clash.
No server-side printing: tickets are printed by Acosys Client on the kiosk device.