Push Notifications

Jonot sends customers a system notification when their ticket moves to CALLED, even when the browser is in the background or the phone is locked. Notifications are also sent when a skipped ticket is recalled and then called again.

How it works

1. A customer is about to join a queue and sees the queue picker screen.
2. A push opt-in card appears above the queue list — the customer taps Notify me and grants browser permission before joining.
3. Their browser registers a Web Push subscription.
4. The customer joins the queue and receives a ticket. The subscription is linked to the ticket server-side.
5. When a desk calls the ticket, the server sends a push message to all active subscriptions for that ticket.
6. The customer’s device wakes up and shows a system notification with the ticket number, queue name, and location. Tapping the notification opens the ticket screen.
7. Jonot deletes the subscription when the ticket reaches a terminal state (COMPLETED, CANCELED, or NO_SHOW). It also deletes an expired endpoint, such as when the customer unsubscribes or removes browser permission.

Customers who did not opt in on the queue picker can still opt in from the ticket screen — a notification card is shown while the ticket is WAITING or CALLED.

Skipped ticket recall notifications

If a ticket moves to SKIPPED, its push subscription remains active. When staff return the ticket to WAITING and call it again, the customer receives a notification even if the ticket page is closed.

A customer who steps away after turning on notifications does not need to keep the browser open.

Opt-in — customer experience

State	Shown
Prompt (permission not yet requested)	Opt-in CTA card (queue picker + ticket screen)
Permission granted + subscribed	”We’ll notify you — you can close this tab” confirmation
Permission denied	Fallback advice + link to browser settings
Browser unsupported	Nothing (silently skipped)

After the customer subscribes, the browser can deliver notifications when the tab is closed or in the background. The ticket page does not need to remain open.

Reconnecting indicator

If the ticket page loses its connection, for example during a short network outage, a Connection lost — reconnecting… pill appears. It appears only for non-terminal tickets and not during the first page load. The connection returns automatically when the network is available.

iOS — Home Screen required

iOS Safari 16.4+ supports Web Push, but only when the app has been added to the Home Screen (standalone mode). On iOS Safari in the regular browser:

• The queue picker shows an Add Jonot to Home Screen guidance card above the queue list.
• After adding to the Home Screen, the customer reopens Jonot from the Home Screen icon and the standard opt-in CTA appears.

Caution

Customers on iOS must add Jonot to their Home Screen before they can receive push notifications. The app detects iOS automatically and walks the customer through the steps.

Transactional only — no marketing

Each push subscription belongs to one ticket and lasts only for that ticket’s lifecycle. Jonot cannot use it for promotional or bulk messages. Only a ticket moving to CALLED sends a notification.

GDPR / consent basis: the subscription is tied to the ticket the customer just created. The same consent basis (legitimate interest / performance of contract) that covers the ticket itself covers the single notification. No separate consent collection is needed.

Technical reference

• Standards: Web Push with payload encryption per RFC 8291 (AES-128-GCM) and VAPID-authenticated requests per RFC 8292.
• Subscription storage: each subscription is tied to one ticket and is automatically deleted when that ticket reaches a terminal state.