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 generated in admin.

Device types

Kiosk

The tablet placed at the venue entrance. Customers interact with the kiosk to join a queue. On Android, the kiosk can connect to an ESC/POS printer to issue physical ticket receipts. The kiosk is paired to a specific queue.

App: 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, and a visual history of recent calls. Audio announcements play when a new number is called. Updates in real time via WebSocket.

App: https://display.jonot.io

Desk

The staff-facing interface used to call the next customer, complete service, or skip a no-show. The desk is paired to a specific queue. Staff do not need individual Jonot accounts — the desk session itself is the credential.

App: https://desk.jonot.io

Pairing model

All three device types use the same pairing handshake:

1. On the physical device, navigate to /pair on the relevant app (kiosk.jonot.io/pair, display.jonot.io/pair, or desk.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 is redirected to its operating screen.

If the code expires before it is entered in admin, go back to the device’s /pair page to request a new code — 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)
• 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 can be configured in one of two modes:

• Assigned to a desk — set assignedDeskSessionId to a specific desk session. The display shows only the tickets called by that desk. Useful when each desk has its own screen.
• Location view (unassigned) — assignedDeskSessionId is null. The display shows all active calls across the entire location.

If a display is assigned 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-assigned mode when the desk reconnects.

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.