Home » Argu Products » Queue Management

Queue Management

Argu is a queue management system that gives every waiting person their own live timer, so staff see exactly who has waited too long, in real time.

The differentiator is per person tracking instead of a single aggregate count. Wait time analytics built on individual timers show which specific line is falling behind right now, not an average across the whole facility from an hour ago. A threshold crossing triggers a dispatch alert while the customer is still standing there, not after they have already left. Wait time data sits alongside footfall in the retail video analytics picture of a venue.

Key facts:

Each waiting person gets an individual timer tracked in real time, not a single aggregate headcount.
Runs on existing RTSP or ONVIF Profile S camera streams already covering the service area, at 1080p–4K resolution and 15–30 fps.
A new wait-time threshold rule can be described in plain English and go live in about 30 seconds, per Argu's published agent-creation time.
Per-person wait time data is personal data; GDPR Article 15 governs a customer's right to request what was recorded about them.
Records can be retained on an operator-set 30–90 day window rather than a fixed federal schedule.

Wait time sits alongside footfall in the same occupancy analytics picture used across commercial venues.

Axis	Conventional headcount system	Argu vision-agent approach
What raises the alert	A fixed occupancy count crossing a static number	An individual wait timer crossing an operator-set threshold, per person, in real time
What a human must watch	A single aggregate headcount display	A per-queue view with every timer color-coded by wait length, across every service point at once
Data captured per person	Anonymous headcount only	An individual wait timer tied to that person while in line — personal data subject to GDPR Article 15 access requests
What gets retained	Aggregate counts only	Per-person wait time records retained on an operator-set 30–90 day window
Rule setup	Fixed configuration requiring vendor reconfiguration	A new threshold rule described in plain English, live in about 30 seconds
Integration path	New sensor or beam counter at each queue position	Existing RTSP or ONVIF Profile S streams, IP cameras and NVRs already covering the floor, at 1080p–4K and 15–30 fps

What is Queue Management

Most queue counts show a single number: people in line. This queue management system tracks each person individually, starting a timer the moment they join and updating it continuously while they wait. When a wait crosses a set threshold, the timer changes color and an alert can dispatch staff before that customer reaches the point of walking out. Feeds run at 1080p to 4K resolution, 15–30 fps, over existing RTSP or ONVIF Profile S streams, and per-person wait records can be retained on an operator-set 30–90 day window under GDPR Article 15.

Key Takeaways

These are the core principles that define how Argu approaches every deployment. Our solutions are built to work on your existing infrastructure, require no engineering overhead, and deliver measurable results from day one. Every feature is designed with one goal: giving your team the intelligence to act faster, with more confidence, and without adding complexity.

See it in Action

Each person in line gets their own timer

Timers are color coded by how long someone has waited

A threshold crossing can dispatch staff to that line

How It Works

A person joins the queue

An existing camera covering the service area detects a new person joining the line, using the video feed already in place. over the existing RTSP or ONVIF Profile S stream, at 1080p–4K resolution.

A timer starts for that person

An individual timer begins counting for that specific person, separate from every other timer running in the same queue. This is personal data governed by GDPR Article 15.

The wait is tracked continuously

The timer updates in real time as the person waits, and the color changes as the wait crosses set thresholds. at 15–30 frames per second.

An alert dispatches staff if needed

If the wait crosses the threshold set for that queue, an alert notifies staff to open another line or assist, while the customer is still there. The threshold rule itself can be set in about 30 seconds.

Product Advantages

Frequently Asked Questions

What makes this different from a basic queue management system?

A basic queue management system usually reports a single count of people in line. This one gives each person an individual timer that starts the moment they join and updates continuously, so staff can see exactly who has waited longest rather than just how many people are waiting.

What is wait time analytics used for here?

Wait time analytics built on per person timers show which specific queue is falling behind right now, so staff can be dispatched to that line before customers start to leave, rather than reviewing average wait times after the fact. Per-person wait time data is personal data, and requests to see what was recorded fall under GDPR Article 15.

Can it track more than one queue at once?

Yes. Occupancy analytics cover multiple queues or service points at the same time, so a bottleneck at one counter is visible alongside normal conditions at another, all in one view.

What triggers a staff dispatch alert?

A dispatch alert fires when an individual wait time crosses a threshold set for that queue. The alert reaches staff while the customer is still waiting, aimed at reducing abandonment rather than only measuring it afterward.

Do we need new cameras to add this?

No. The system connects to RTSP streams, IP cameras and NVRs already covering the service area. Argu's technology is designed to run on cameras a site already has installed, rather than requiring new sensors at every queue position. Feeds run at 1080p to 4K resolution, 15–30 fps, over RTSP or ONVIF Profile S.

How is per-person wait time data retained?

Per-person wait records can be retained together on an operator-set 30–90 day window, not a fixed federal schedule, and an on-premise deployment keeps that data on site.

How fast can a new wait-time threshold be configured?

A new threshold rule can be described in plain English and go live in about 30 seconds, per Argu's published agent-creation time, with no dataset collection or model training.

How does AI queue management work with CCTV at retail checkouts and service counters?

Cameras that already cover the queue give each waiting person an individual timer that starts when they join and updates while they wait. When a wait crosses the threshold set for that queue, staff are alerted while the customer is still there. The same view shows occupancy across several queues, so counting and queue timing come from one camera feed, over RTSP or ONVIF Profile S at 1080p to 4K and 15 to 30 fps. Per-person records can be kept on an operator-set 30 to 90 day window.