This page shows sample data in the exact formats your QueueReports engine produces. In production, QueueReports.exe reads the live QMS database (app_tokenrecord: ts = token created, tw = called, te = serving ended, dt = date, ser_id = service, usr_id = operator) and builds these same 10 reports. Waiting = tw − ts (only where tw ≥ ts). Serving = te − tw.
QueueReports.exe on the QMS server PC (port 8007) — it auto-finds db.sqlite3. This website does not access your database.Definitions — Priority Calling: tokens called out of strict token order (call-order analysis). Manual Calls: calls where the operator skipped ≥15 sec / jumped queue (MIN_SKIP_SECONDS = 15 in QueueReports code). SLA: % tokens with waiting ≤ target and serving ≤ target. Change targets in your QueueReports code if needed.
QueueReports.exe (built from standalone_reports.py).http://localhost:8007/ — pick Executive, Service-wise, All, User-wise, Daily Trend, Counter-wise, Peak Hours, SLA, Priority, Manual Calls.Want this demo wired to your real database? Ask Hotsol — we can add a secure, read-only API / export for your dashboard.