← Back to blog

Offline kiosk mode: keep self check-in running without internet

7 November 2026· 12 min read

Watercolor ribbons framing the article title

Offline kiosk mode is a managed device state in which a locked-down kiosk app keeps doing its job when the network or the management server is unavailable. It does this by holding a small, bounded set of policy, content and business rules locally, and by queuing what guests do until the connection returns. It is not the same as pinning an app to a screen. This guide explains the difference, how to configure it, what to store, and what your staff should do during an outage.

Riddlio
Keep Escape Room Bookings Together
Riddlio brings bookings, availability, payments and customer communications into one place for escape room operators.
Explore Riddlio

TL;DR

  • Kiosk mode locks a device to one app. Offline kiosk mode adds a design for what that app does when the internet and the management server are gone.
  • Preload what the kiosk needs while you have a reliable connection, and set a maximum age for cached data.
  • Never store card numbers on the device. Queue encrypted payment records or use a payment terminal built for offline use, and treat every offline decision as provisional until the server confirms it.
  • Give guests a clear message and a staff fallback, so nobody stares at a loading screen.
  • Test the outage before you rely on it: remote commands, updates and monitoring all need connectivity.

Table of Contents

What offline kiosk mode actually is

A kiosk is a device restricted to one purpose. On ChromeOS, for example, kiosk mode runs one administrator-chosen app at a time, locked in full screen without a user login. That is different from a normal session where a guest can open a browser or other apps.

Offline is a second layer. It means the kiosk has been designed to keep certain functions working without a live connection. The decisions sit in the policy, the credentials, the cached content and the business rules. A production Android kiosk, according to one embedded-systems guide, should define how old cached data may be and show a clear, non-escapable service state when the data is too stale to trust.

For an escape room venue, the practical question is simple. When the Wi-Fi drops at 6 pm on a Saturday, what can a arriving group still do at your lobby screen, and what must a staff member take over?

What offline kiosk mode actually is

Managed kiosk versus a pinned app

Many searches for this topic come from people who have pinned an app and assume the job is done. On Android, screen pinning is user-controlled. A pinned app without Device Owner status is, in the words of the same guide, mainly a user convenience and not equivalent to a managed kiosk. A managed kiosk uses Device Owner and a device policy controller, and lock task mode limits the user to allowlisted apps.

Why this matters offline: a pinned guest-facing tablet can usually be escaped by someone who knows the gesture, and if it is not enrolled in management, nobody can fix its settings remotely. If you are buying hardware for the lobby, look for a dual OS touch screen kiosk that you can lock to a single app under administrator control, rather than a consumer tablet on a stand.

Pinned app Managed kiosk Managed kiosk with offline design
Who controls the lock The user The administrator The administrator
Remote policy changes No Yes, when online Yes, when online; last policy cached
Guest sees during outage Often a loading or error screen App may stall Defined offline state with supported actions
Data on device Whatever the app keeps Whatever the app keeps Minimum needed, with an age limit

How to configure a kiosk to keep working offline

The steps are the same whatever hardware you use.

  1. Preload while online. Configuring a kiosk for offline work means loading essential content, apps and configuration during a period of reliable connectivity so they are stored on the device. For a venue that means room names, game descriptions, waiver text, and the day’s booking list.
  2. Choose what is allowed offline. Kiosk best practice is to preload items such as menus, schedules or forms and to queue actions like form submissions or payment confirmations locally, then sync in batches when the connection returns. Decide which of your guest actions fit that pattern.
  3. Build the cache the right way. If you build or commission a web-based kiosk app on ChromeOS, Google’s documentation says offline content can be stored with service workers and storage such as the Cache API and IndexedDB, and application state can be persisted with the Workbox library.
  4. Set the switch. Some point-of-sale kiosks have a built-in setting. One vendor’s help page describes Auto, On and Off options for Offline Mode, confirmed with a manager code, where Auto enters offline mode on an internet loss and exits on reconnection. Whatever your system, know where that switch is and who may use it.
  5. Add a second connection. For time-sensitive kiosks, Ethernet as primary with cellular as backup is the recommended hybrid. A cheap cellular router in the office often does more for uptime than any software setting.
  6. Test with the cable pulled. Remote management commands, updates and monitoring all require connectivity, so test the offline state before opening day and again after every update.

What the guest sees during an outage

The worst outcome is a spinner. Good kiosk design presents supported offline workflows or a clear notice instead of leaving users on a loading screen. Write the offline messages in advance and keep them short.

Useful wording for a lobby screen:

  • “Self check-in is paused. Please see our host at the desk.”
  • “Your booking is saved. We will confirm it as soon as we are back online.”
  • “Payments are unavailable on this screen. Our host can take payment at the desk.”

The screen must not offer an action it cannot complete. If a function needs live data, such as selling a slot for a time that may already be taken, hide it in offline state.

What a kiosk can store locally, and how to protect it

Store the minimum. A useful test: if the device were stolen from the lobby, what would the thief learn?

Safe to cache, with limits: today’s slot list with group names and player counts, game descriptions, the waiver template, the staff exit PIN rule. Set a maximum age and clear it when it expires.

Never store: card numbers. The Kiosk Industry Association’s U.S. report states that PCI DSS requires kiosks that accept cards to never store card numbers locally, to use a secure network connection, to be physically protected and tamper resistant, and to run a locked-down operating system. It also notes that point-to-point encryption makes compliance easier.

Protect what you do store:

Taking payments when the connection drops

Payments are where offline design needs the most care. Two patterns exist.

Store and forward on a certified terminal. One restaurant-POS article explains that when the internet drops, the terminal captures card data, encrypts it with DUKPT-derived AES-128 keys and holds it in secure local memory, then sends it to the acquirer in an encrypted batch once the connection is back. The same source says accumulated transactions are sent in a single encrypted payload, typically within two to five minutes for restaurant volumes, and that offline receipts carry a unique reference number linking them to the sync queue. Your volumes are far smaller than a restaurant’s, but the pattern is the one to look for.

Decline payment at the kiosk. For many venues the simplest rule is that the kiosk takes no payment offline and the host collects it at the desk. This avoids the risk that an offline-approved card is later declined. Remember that offline mode may not trigger at all when the internet is up but payments cannot be processed; one vendor states that new orders cannot then be captured. Have a plan for that case too.

When payments fail after reconnection, follow a recovery routine. Our payment failure recovery playbook sets out how venue managers contact guests and rebook. If cards use extra authentication, see 3D Secure bookings for escape room owners.

Taking payments when the connection drops

Avoiding double bookings and oversold slots

Offline is where overselling happens, because two devices can each believe the same slot is free. The fixes are procedural as much as technical.

  • One source of truth. The server decides. Kiosks only hold a provisional copy, and offline check-ins are reconciled when the connection returns.
  • Limit what offline can change. Allow check-in of existing bookings offline. Do not allow new sales of slots that could be taken elsewhere.
  • Split by device if you must. Festival ticketing offers a model: each scanner downloads the full ticket list before gates open and validates against the local cache. When several gates are offline, organisers reduce cross-gate duplicates through periodic syncing, segmenting tickets by gate and staff communication, then reconcile all scans afterwards. For a venue, the equivalent is one kiosk and one host tablet that never both sell the same room.
  • Expect retries. Reconnecting devices can flood a backend, so well-built systems retry with exponential backoff and discard duplicate packets. Ask your software provider how theirs behaves.

If you run many rooms, the multi-room scheduling plan helps you structure slots so a single failure affects fewer bookings.

A staff checklist for the first ten minutes of an outage

Print this and keep it at the desk.

  1. Confirm the outage is the internet and not the kiosk: check the router, then the cellular backup.
  2. Switch the kiosk to its offline state, or confirm it switched itself.
  3. Put a sign on the kiosk: “Please check in with our host.”
  4. Open the printed or cached list of today’s bookings. Tick off arrivals on paper if needed, with time and group size.
  5. Take payments only by a method your terminal supports offline, and note each reference number.
  6. Do not sell last-minute slots unless one person holds the master list.
  7. When the connection returns, check that every offline check-in and payment synced, and look for duplicates before the next session.

Restoring normal operation, and exiting kiosk mode safely

Staff sometimes need to leave kiosk mode, for updates or repairs. Use a controlled exit, not a hidden gesture. Management tools can switch a device in or out of kiosk mode remotely, and one Windows kiosk product describes a configurable exit PIN that lets staff leave temporarily and returns the device to its locked state on a timer or sign-out. Scheduled lock and unlock can also open the device to staff at set hours.

After an outage, restore in this order: reconnect, let the sync finish, review the exceptions, then clear stale cached data. Only then hand the screen back to guests.

Our perspective

Most outages at a venue are short, and most of the damage is done in the first ten minutes by confusion, not by the lost connection. A kiosk that tells guests plainly what to do next, and a host who knows exactly which list to open, turn an outage into a minor delay.

That is why we build around the real workflow of an escape room: player numbers, room availability and group bookings in one place, with reminders, waivers and a self check-in kiosk as part of the same system. When the booking record, payment and communications live together, reconciliation after a disruption is a short review rather than a hunt across tools.

Our advice to operators is to decide what the lobby screen may do offline before you need it, write the guest messages, and rehearse the staff checklist once a quarter.

Iosif Beraru

Where Riddlio fits

Riddlio is a booking and management platform for escape room venues, bringing bookings, availability, payments, SMS and email reminders, waivers, analytics and a self check-in kiosk together. Plans start at $29 per month (Starter), with Pro at $79 per month and Unlimited at $199 per month; Enterprise has no published price. See the Riddlio pricing page for what each plan includes.

Riddlio

If you are planning your lobby set-up, read about escape room booking software and our self-service POS integration options, or browse the full feature list.

FAQ

What is offline kiosk mode?

It is a managed kiosk state where the app keeps working when the network or management server is down. It relies on a small cache of policy, content and rules, with an age limit. When data gets too old, the kiosk shows a clear service message.

Is offline kiosk mode the same as screen pinning?

No. Pinning is user-controlled and, on Android without Device Owner, is mainly a convenience. A managed kiosk is set by an administrator and can limit the device to allowlisted apps. Offline design is then layered on top.

Can guests pay at a kiosk when the internet is down?

Only if the terminal supports it. Certified terminals can capture and encrypt card data for later batch sending. Kiosks must never store card numbers locally, so many venues simply route payment to the host desk during an outage.

How do I leave kiosk mode for maintenance?

Use a managed exit, such as a staff PIN or a remote switch from your device management console. The device should return to its locked state on a timer or sign-out.

What happens to offline activity when the connection returns?

The kiosk sends queued actions to the server, which stays the source of truth. Staff should then check for duplicates and failed payments before the next session.

Sources

← Back to all posts