How It Works

Jonot is built around three audiences: the business operator who signs up and administers, the venue team running devices on the floor, and the customer joining the queue. Most surfaces run directly in the browser, while kiosk and desk can also be deployed as dedicated Android apps on fixed devices. Here is how they connect.

These are the surfaces the business operator touches personally.

Join — https://join.jonot.io

The self-serve signup wizard — you use it once. New customers use Join to create a Jonot account, name their organisation, choose a plan, and complete checkout — all in one guided four-step flow. The final step is a confirmation screen with a Go to Admin Dashboard button that hands you off to Admin to finish setting up.

Admin — https://admin.jonot.io

The ongoing management console used by org-managers and location-managers. Once Join hands you off, Admin is where you live day-to-day:

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.

Run your venue

These are the physical-space production devices. They authenticate as devices — no personal staff login required.

Kiosk — https://kiosk.jonot.io

A tablet-optimised entrance device that customers tap to join a queue. In production it is typically deployed as a dedicated Android kiosk app on a fixed tablet, though the same kiosk surface can also run in a browser. On Android, the kiosk can print ticket receipts. The kiosk is paired to a specific queue in a location.

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. It can run as a dedicated Android desk app on a fixed counter tablet or in the browser at desk.jonot.io on a PC or tablet. 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.

What customers experience

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.

When a location has multiple queues, the customer sees a queue picker showing all available queues with live waiting counts before choosing which to join. The picker also offers a push notification opt-in so customers can be notified when their number is called, even with the phone screen off.

Data flow — a single customer visit

Here is how the pieces connect end to end:

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.
Ticket created — the ticket enters WAITING state. The customer's phone shows their position. The desk sees the new entry in its waiting list.
Desk calls next — a staff member presses Call Next on the desk. The first WAITING ticket moves to CALLED state.
Display updates — the display immediately shows the called ticket number and the desk name. An audio announcement plays and the screen flashes.
Customer is notified — the customer's phone updates to show that their number has been called. If the customer opted in to push notifications, a system notification is also sent.
Desk completes or skips — the staff member either marks the ticket COMPLETED (service done) or SKIPPED (customer didn't respond, but still recallable). The staff member then presses Call Next to serve the next waiting customer. A SKIPPED customer can be recalled later — the desk presses Recall to queue and the customer's screen updates.

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