Interactive Kiosks

Kiosks become part of the platform

Most operations run kiosks as an island: separate vendor, separate software, separate support contract, separate monitoring. The self-order kiosk lives in one system while the menu boards two metres above it live in another, and nobody can see both from the same place. Every new screen type adds another silo.

TelemetryOS treats kiosks as what they are — interactive applications on the same platform as everything else. A self-order kiosk runs on the same console as the menu boards, the queue display, and the promo screens. Kiosk apps are built with the React SDK and deployed git-to-screen, and TelemetryOS enables applications to connect to any REST API, so ordering flows talk to your POS, check-in screens talk to your booking system, and wayfinding pulls from your facilities data.

Interactivity doesn't displace scheduled content; the two run side by side. A kiosk can attract with scheduled promotions until someone touches it, then drop into the ordering flow, then return to the loop. Devices execute applications locally, so the kiosk stays responsive through a network outage and syncs when connectivity returns.

One console for kiosks and everything around them

The case for consolidation shows up in operations. When kiosks join the same fleet as the signage, device health, app versions, and proof-of-play for every screen type sit in one view. A kiosk that's down at one location is a dashboard alert with remote diagnostics behind it, not a phone call routed between vendors who each blame the other.

For integrators, that's the difference between installing kiosks and operating a kiosk business. One platform covers the hardware — Node Mini, Node Pro, or Node Max depending on the workload — one console covers monitoring and content, and one codebase covers the app across every site. Adding a new interaction, a new screen, or a new location is a deployment, not a new vendor relationship.