How HETable works

How HETable works from room setup to live service and review

This page explains the full HETable operating sequence in order, so buyers can understand how room setup, booking controls, live service, and review connect before they open the live reservation directory.

Where this page fits in the reservation cluster

Use the live reservation directory when you want real restaurant pages. Use the support guides below when you want the workflow, launch order, and screen-level context around that same directory to stay one click away.

What teams usually open first

The product is more than a single host screen. Different roles open different parts of HETable depending on what needs to happen before, during, and after service.

ManagerFloor Plan Builder, versions, booking settings, sections, Smart Assign, reports, permissions, locations dashboard, API keys, webhooks, audit log, and security policies.
HostHost Stand, Reservations, Wait Board, Self-Seat Kiosk launch, and table-state visibility tied to the live published plan.
Server and floor teamPocket View plus Station Assignments and section coverage to stay aligned with the current floor and table status.
GuestPublic booking from the restaurant’s own HETable widget link or public location page, reservation confirmation, self-seat, kiosk flow, and concierge support where the restaurant enables those experiences.

1. Set up the room

Everything downstream depends on the room being right. HETable uses the published floor plan as the source for host, reservations, waitlist, kiosk, and self-seat workflows.

Floor Plan Builder Versions & publish Sections Station Assignments Locations Dashboard

2. Prepare the shift

Before the rush, managers and hosts use HETable to shape the service plan instead of waiting to solve everything at the door.

Booking Settings Smart Assign Schedule link/import Staff Ratings

Booking proof before service starts

3. Run live service

Once service starts, HETable keeps reservations, waits, table status, and seat decisions connected to the live room instead of splitting them across disconnected tools.

Host Stand + ReservationsManage arrivals, create or edit reservations, place parties, and work from a live floor-aware seating view.
Waitlist + Wait BoardQuote waits, track queue pressure, review recent seatings, and keep pacing aligned with current capacity.
Self-Seat + KioskLet guests seat themselves where allowed, or use the kiosk flow with suggested tables, waitlist fallback, and concierge chat support.
Pocket ViewKeep the floor team aligned by letting staff update table status from the floor without walking back to the stand.

4. Keep the floor team aligned

HETable is not only for the host stand. It also supports the floor team so hosts, managers, and servers do not work from different versions of the room.

Station maps Pocket View Table moves Section balance

5. Review, control, and improve

After service, managers can use HETable to review what happened and keep the workflow governed over time.

Reports Audit Log Permissions API Keys Webhooks Security Policies

Direct answers for buyers

How do restaurants use HETable before service?

Restaurants usually publish the correct floor plan, confirm booking settings, organize sections and station assignments, and prepare the host workflow before service begins. Many teams also link schedules, review staff ratings, and generate Smart Assign when they want stronger pre-shift structure.

How does HETable work during service?

During service, HETable keeps reservations, waitlist, live table status, and seating decisions in one floor-aware workflow. Restaurants can also run self-seat or kiosk experiences, use concierge support where enabled, and keep servers aligned through Pocket View and station maps.

What do managers review after service?

Managers can review reports, table moves, staffing outcomes, audit activity, permissions, API keys, webhooks, and security policies. That helps the team tune future shifts while keeping the product governed and measurable.