Connections drop. The app is built for it: the floor stays on screen, and most of what you do on it is kept on the device and sent the moment the internet is back.
A yellow bar says there's no connection
A few seconds after the connection drops, a yellow bar appears at the top of every screen: No connection. You don't need to do anything — the app keeps checking. Try again checks straight away.
Keep working on the floor
These carry on as normal — each one is kept and sent later:
- seating a reservation, or a party from the waitlist
- closing a table, Mark ready, Mark finishing
- blocking and unblocking a table, No-show
- changing tonight's hours
The bar counts them: 2 changes are waiting to send.
Write these down for later
Some things need the connection, because every device has to agree on them first:
- new reservations, and changes to existing ones
- walk-ins — the table snaps back and the app says it didn't save
- adding to the waitlist, the guest book, and Settings
Put them on paper and enter them when the bar is gone. Moving a party, combining tables and giving out sections need the connection too — wait for it before you do those.
When it's back
The bar says Sending 2 waiting changes…, then disappears. Everyone's floor catches up.
If another stand changed the same table while you were offline — seated someone there first, say — your change can't go through. A red line tells you which one and why. Tap Got it and redo it if you still need to.
Good to know
- Opening the app with no connection shows the floor as it was last time, with the time: This is the floor as it was at 7:42 PM.
- Don't sign out while changes are waiting — they'd be lost. The sign-out button warns you and says how many.
- Two stands changing the same setting at once? The second one is told Someone else just changed these settings and gets the latest to redo their change on. Nothing is overwritten by accident.