Queue

A queue is the service or turn type where people line up. Each queue defines a type of service, and all tickets in that queue share the same numbering.

You can have as many queues as you want in a location. For example:

• A supermarket can have a fruit shop queue, a fish shop queue and a deli queue, all at the same time and separate.
• A corner fruit shop can have just one queue.
• A hospital can have many queues: Emergency, Pediatrics, Information…

Created inside a location

Queues belong to a location. In the dashboard you first select the location and, once selected, you see the menu to create counters, queues, flows, etc.

Queue fields

When creating a queue you define:

Field	Description
Name	What you see in the dashboard (for example, “Fruit shop”).
Prefix	What goes in front of the ticket number (for example, F-001 or C-005).
Max value	Maximum ticket number. When this value is reached, numbering restarts at 1.
Priority	The higher the number, the sooner that queue’s turns are called.
Weight	Ratio between queues with the same priority. With weight 3 vs weight 1, 3 turns of one queue are served for every 1 of the other.
Aging minutes	Every X minutes, a waiting turn rises one priority level. 0 disables aging.
Maximum priority	Maximum number of levels a turn can rise through aging.
Reset time	Time at which the queue resets every day: numbering returns to 1 and pending tickets are canceled. Disabled by default.
Allowed counters	Which counters can call this queue. If you do not select any, the queue cannot be called.
Color	To tell queues apart at a glance.
Description	(Optional) Free text with more context.

In the dashboard you will see each queue as a card with its name, prefix and color.

Daily numbering reset

The reset time is configured on the Rules tab of the queue form. When that time arrives:

• The queue numbering returns to 1.
• Waiting and being served tickets become canceled, and the change is recorded in each ticket’s history.
• The reset runs only once a day.

It is disabled by default: if you do not need it, leave it off.

Counters that can call the queue

The relationship between queues and counters can be configured from either side:

• On the queue, with the Allowed counters list.
• On the counter, with the Allowed queues list (or Queues in the counter form).

The important part:

• If a queue has no allowed counter, it cannot be called.
• If a counter has no allowed queue, it cannot call anyone.
• The relationship must be synced in both directions. If it is not, the system map shows it as an issue.

Priority, weight and aging in detail

These three options fine-tune the order in which turns are called. They are optional: for simple queues you can leave them at 0.

Priority

The higher the priority number, the sooner that queue’s turns are called. For example, an Emergency queue with priority 2 is served before a Consultations queue with priority 1.

Weight

Weight shares turns between queues that have the same priority. With weight 3 on one queue and weight 1 on another, 3 turns of the first are served for every 1 of the second.

It only applies between queues with equal priority: if one queue has higher priority, its turns go first regardless of weight.

Aging

Aging prevents a turn from always ending up last:

• Aging minutes: every X minutes, the turn rises one priority level. 0 disables this option.
• Maximum priority: limits how many levels it can rise. It prevents an old turn from jumping ahead of everyone indefinitely.

For example, with aging every 10 minutes and maximum priority 3, a turn that has been waiting 30 minutes will have risen 3 levels (or the maximum you allow).

Simple queues

Priority, weight and aging are advanced options. For simple queues served as customers arrive, you can ignore these fields completely: tickets are called in order of arrival.