Hall panel
The Hall panel is the host's and manager's workstation inside the till. It opens with the 🗺 button in POS and takes over the whole screen.
Two conditions make that button visible. First, the role: it needs the hall management permission, so a waiter who switched at the till with a PIN will not see it. Second, the Hall panel chip toggle in POS appearance: restaurants and hotels have it on by default, while non-restaurant business types (retail, beauty, pickup point, e-commerce, services, corporate site, blog, widgets) have the panel off by default — switch the toggle on if you need it.
Eight tabs answer eight different questions, but they share one live data set: orders, calls and reservations arrive over a websocket, nothing has to be refreshed by hand.
The floor plan is drawn in Floor plan; the Hall panel displays it and works on top of it.
"Now"
The first tab is a single screen showing the state of the venue this minute, as tiles:
| Tile | What it shows |
|---|---|
| Seats taken | taken / total, and how many tables that is |
| Bookings within the hour | who has to be seated in the next hour |
| Ready, not served | orders waiting for a waiter |
| Calls | active waiter calls |
| Rooms to clean | (hotels) |
| Guest requests | (hotels) |
| Overdue tasks | and how many of them have no assignee |
| Revenue today | the day's total |
Tapping a tile highlights the matching objects right on the floor plan — that is the difference between a dashboard and a list of numbers.
Empty tiles are hidden: a small café with no hotel and no tasks sees a living screen, not a table of zeros. When nothing needs attention, the tab says so.
"Waiting" — the waitlist
The queue of guests for whom there was no free table.
A waitlist entry holds name, phone, party size, the wait time you quoted, and a comment.
Statuses: queued → invited → seated; terminal ones are no-show and cancelled (left on their own). Once invited, a no-show timer starts ticking.
How to invite. There are exactly two channels, and both are real:
- Phone call — a
tel:link right in the row, nothing to configure; - Telegram — the button appears only if the guest already has a conversation with this location's Telegram bot. Telegram does not let a bot message first: until the guest starts the dialogue, the chat simply does not exist. There are no stubs here that look functional.
SMS and WhatsApp are not supported in the waitlist yet.
Seating. When a table frees up, the panel suggests a matching party by itself: among those still queued who fit the table, it picks the one that leaves the fewest empty seats, and on a tie the one who has waited longest. Seating creates an ordinary reservation and hands the table to the till — the same path as seating a reservation from the scheme.
The number of parties waiting is shown on the tab itself.
"Scheme", "Reservations", "Calls"
Scheme — a live floor plan with table statuses: free, occupied, waiting, reserved. Tapping a table opens a card: open the order, seat a reservation, assign a waiter to the table (or change/clear the assignment).
Reservations — the same reservation list as on the floor plan page: create, confirm, assign a table, change status. Unconfirmed reservations show as a number on the tab. More in Table reservations.
Calls — waiter calls sent by guests from the QR menu (see Orders). A row with the table number and reason, an "Acknowledged" button, and a global sound toggle. The same bell is mirrored in the Orders section.
"Day" and "Tasks"
Day — who is on shift right now: today's planned-vs-actual roster grouped into "on shift", "expected", "finished" and "off schedule". Clock-in and clock-out happen from the shared till terminal: an owner or manager can mark anyone without a PIN, everyone else enters their own. In the hotel vertical the tab adds a guest-requests block.
Tasks — a compact version of the shift tasks board: quick add, "open / doing / done" groups, tick to complete. The full kanban with tags and due dates lives on its own page. The number of open tasks is shown on the tab.
"Analytics" — the hall heat map
Which square metres bring in money. The floor plan is coloured by a value — revenue or average check per table — with a table of numbers and a legend underneath.
Two honest limits:
- it covers today only — the tab works from the live 24-hour order cache and has no backend of its own; periods (week, month, revenue per seat) are not supported yet;
- a table with no QR code bound to it means "no data", not "zero revenue": orders are linked to a table through its code, and about a table without a code nothing can be claimed.
Related sections
- POS — where the panel is opened from
- Floor plan — the plan editor and binding table QR codes
- Table reservations — booking, deposits, statuses
- Orders — the waiter call and where it goes
- Shift tasks board — the full board
FAQ
How is the Hall panel different from the "Floor plan" section?
"Floor plan" is the editor: that is where you draw tables and halls and bind QR codes to them. The Hall panel is the work done on top of that plan during a shift: seating, the queue, calls, analytics. The waitlist and the heat map do not exist on the editor page.
Can a guest join the waitlist by themselves?
No, the host adds them. The guest gets a call or a message from the venue when a table frees up.
Why is a table empty in analytics?
It has no QR code bound to it. Orders are linked to a table through its code, so without one there is no data for that table — and the panel honestly shows "no data" rather than zero.
Can I open the panel on a separate tablet at the entrance?
Yes — it is part of the till app, so open POS on the host's tablet and keep the panel expanded.
Are waiter calls duplicated in "Orders"?
Yes, it is the same signal: the bell in the Orders section and the "Calls" tab show the same active calls.