Devices

Jonot has three device types, each with a distinct role in the queue workflow. All devices are paired to a location (and optionally a queue) using a short-lived pairing code that is generated on the device and then entered in admin.

Device types

Kiosk

The tablet placed at the venue entrance. Customers interact with the kiosk to join a queue. In production, Jonot usually runs the kiosk as a dedicated native app on the tablet where available (today: Android). Browser-based kiosk deployments are also possible. On Android, the kiosk can connect to an ESC/POS printer to issue physical ticket receipts. The kiosk is paired to a specific queue.

Surface: dedicated kiosk app where available, or https://kiosk.jonot.io

Display

A TV or monitor in the waiting area showing the live queue status — which ticket numbers are currently called, at which desk, how many customers are waiting, a preview of the next numbers to be called, and a visual history of recent calls. Audio announcements play when a new number is called. Updates in real time via WebSocket.

Surface: https://display.jonot.io

Desk

The staff-facing interface used to call the next customer, complete service, or skip a no-show. It can run as a dedicated native app on a fixed counter tablet where available (today: Android) or in the browser on a PC/tablet. The desk is paired to a specific queue. Staff do not need individual Jonot accounts — the desk session itself is the credential.

Surface: dedicated desk app where available, or https://desk.jonot.io

Pairing model

All three device types use the same pairing handshake:

1. On the physical device, open the pairing screen in the relevant runtime. For kiosk and desk, this is usually the dedicated device app on the tablet; browser-based setups can open https://kiosk.jonot.io/pair/ or https://desk.jonot.io/pair/ instead. Displays currently use https://display.jonot.io/pair/. The device requests a 7-character pairing code (for example, K7M-4PQ) and displays it on screen. The code is valid for 10 minutes.
2. An org-manager or location-manager opens the location in admin, goes to the Devices tab, clicks Pair device, and enters the code shown on the device screen.
3. The server activates the device, creates a DeviceSession, and issues a long-lived device token. The device detects activation and opens its operating screen. A newly paired Android kiosk without a configured printer is redirected to printer setup first.

If the code expires before it is entered in admin, return to the device's pairing screen to request a new code. In browser-based setups, that means going back to the relevant /pair URL. The old code is invalidated automatically.

DeviceSession lifecycle

A DeviceSession is created at pairing time and persists until it is manually revoked in admin or the session expires. It carries:

• Device type (kiosk / display / desk)
• Location assignment
• Optional queue assignment (kiosk, desk, display)
• Optional desk assignment (display — see below)
• Optional display name (e.g. "Desk 1", "Kiosk A")
• Last-seen timestamp
• Online/offline status

To revoke a device session, go to admin → location → Devices, find the device, and click Remove. The device will be locked out at its next request.

Display assignment

A display has two independent assignment axes — which queues it shows, and (optionally) a desk to focus on.

Queue assignment controls the board layout:

• Single queue — one queue assigned; the display uses the single-queue layout leading with the now-serving hero.
• Multi-queue board — 2–5 queues assigned; the display shows them side by side, each column independently live.
• Location view (unassigned) — no queues assigned; the display shows all active calls across the entire location.

Desk linking is an optional overlay on top of any of the above:

• Linked to a desk — set assignedDeskSessionId to a specific desk session. While that desk is online, the display shows only the tickets it calls in a focused single-ticket view. Useful when each desk has its own screen.
• Unlinked — assignedDeskSessionId is null. The display follows its queue assignment as described above.

If a display is linked to a desk and that desk goes offline for more than 2 minutes, the display automatically falls back to the location view. It returns to desk-linked mode when the desk reconnects.

See Pair a Display for the operator-facing walkthrough and Customise the Display for board-layout details.

Offline behaviour

Devices maintain a WebSocket connection to the Jonot API. The server tracks lastSeenAt for each device session. Admin shows a device as Offline when its last-seen timestamp exceeds a threshold. Devices reconnect automatically when the network is restored — no manual intervention is needed.

Desk credential

The desk authenticates using the device token issued at pairing time, not a personal user account. This means any staff member using that device gains desk access without logging in. To restrict access, revoke the device session and re-pair only with authorised devices.