How It Works

Jonot is made up of five surfaces that work together. Each surface is a separate web app serving a specific role. Here is how they connect.

The five surfaces

Admin — https://admin.jonot.io

The management console used by org-managers and location-managers. Admin is where you:

• Create and configure locations and queues
• Pair devices (kiosk, display, desk) to locations
• Invite and manage staff
• Access billing and account settings

Admin requires a Jonot account with an org-manager or location-manager role.

Join — https://join.jonot.io

The self-serve signup wizard. New customers use Join to create a Jonot account, name their organisation, choose a plan, and complete checkout — all in one guided flow. After signup you are redirected to Admin to complete your setup.

Kiosk — https://kiosk.jonot.io

A tablet-optimised interface placed at the venue entrance. Customers tap the kiosk to join a queue. The kiosk prints a ticket receipt with the customer’s ticket number. The kiosk is paired to a specific queue in a location — no staff login is required at the device level.

Display — https://display.jonot.io

A TV or monitor display for the waiting area. It shows which ticket numbers are currently being called, at which desk, and plays an audio announcement when a new ticket is called. The display updates in real time via WebSocket. It can be assigned to a specific desk (shows only that desk’s calls) or left in location view (shows all active calls).

Desk — https://desk.jonot.io

The staff-facing queue management interface at the service counter. Staff use the desk to call the next waiting customer, mark the current customer as completed, or skip a no-show. The desk authenticates as a device (not a personal user account), so staff do not need individual Jonot accounts.

Customer — customer.jonot.io

A mobile-first progressive web app for customers. After joining the queue (via QR code or kiosk), the customer can open their ticket page to see their current position in real time. No app install is required — the join URL opens directly in the phone browser.

Data flow

Here is how the pieces connect end to end:

1. Customer joins — a customer scans the QR code (or uses the kiosk) and joins the queue. Jonot creates a ticket with a sequential number and a unique 22-character hash.
2. Ticket created — the ticket enters WAITING state. The customer’s phone shows their position. The desk sees the new entry in its waiting list.
3. Desk calls next — a staff member presses Call Next on the desk. The first WAITING ticket moves to CALLED state.
4. Display updates — the display immediately shows the called ticket number and the desk name. An audio announcement plays.
5. Customer is notified — the customer’s phone updates to show that their number has been called.
6. Desk completes or skips — the staff member either marks the ticket COMPLETED (service done) or SKIPPED (customer didn’t respond). The staff member then presses Call Next to serve the next waiting customer.

All state updates flow through the Jonot API in real time via WebSocket connections maintained by the display, desk, and customer PWA.