What should a restaurant configure first in HETable?

Most restaurants start by building the floor plan, publishing the live room, setting booking rules, and organizing sections or station coverage. Those steps shape what the host stand, waitlist, kiosk, and self-seat flows can do later in service.

How do teams launch HETable for the shift?

Managers usually confirm booking settings, staffing, and assignments first. Hosts then work from Host Stand, Reservations Manager, and Wait Board, while floor teams use station assignments and Pocket View. Guests can use public booking, self-seat, or kiosk flows where the restaurant enables them.

What should operators review after the shift?

After service, operators typically review reports, table moves, reservation outcomes, assignment coverage, permissions, audit activity, integrations, and security policies so the next shift starts from a cleaner operating picture.

Getting started with HETable

How to launch HETable without guessing what to do first

This page explains the safest launch order for HETable, so restaurants can set up the room, prepare the shift, open the right screens, and then send guests into a live reservation path with less guesswork.

See the real screens teams open View the full workflow Use the go-live checklist Browse live restaurant reservations

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.

Current guide: Getting started with HETableUse the launch-order guide for room setup, shift prep, live-service readiness, and the first reservation handoff.

Browse live restaurant reservationsOpen the live HETable reservation directory with crawlable restaurant pages and direct paths into real locations. Restaurant reservation and waitlist softwareSee how direct booking, walk-ins, and pacing support stay connected inside one host-stand workflow. Restaurant reservation management softwareReview booking rules, confirmations, edits, and host-side booking control around the live room. How HETable worksFollow setup, pre-shift, service, and review in one connected operating sequence. What teams open in HETableMap the real manager, host, guest, and floor-team screens behind the reservation workflow.

Start with the room, not the reservation

The floor plan is the foundation for the rest of the product. When the room is current, the stand, reservation tools, waitlist, kiosk, and self-seat experiences all stay tied to the same live operating picture.

Build the room in Floor Plan Builder and keep versions organized.
Publish the live plan the staff should actually use this shift.
Create sections and station coverage before hosts start seating.

Floor Plan Builder Versions & publish Sections Station Assignments

Prepare the shift before guests arrive

Restaurants usually make HETable more effective by finishing a few manager and host checks before opening the door.

Booking rulesConfirm hours, booking intervals, party-size limits, lead time, and any reservation pacing rules.

Staffing inputsLink or import schedules, review roster relationships, and check staff ratings when those workflows are part of the operation.

Assignment planningUse Smart Assign and station maps to shape who covers what on the floor before the rush.

Location oversightGroup operators can review the Locations Dashboard when more than one restaurant is involved.

Open the right screens for service

Different roles use different parts of HETable. The goal is not to put everyone in one screen. The goal is to keep every role working from the same operating picture.

ManagerBooking Settings, Reports, sections, Smart Assign, locations, permissions, audit, API keys, webhooks, and security policies.

HostHost Stand, Reservations Manager, Wait Board, and the live table view tied to the published room.

Server / floor teamStation Assignments and Pocket View to keep follow-through aligned with the host decision.

GuestPublic booking, reservation confirmation or cancellation, self-seat, kiosk, and concierge support where enabled.

Run guest flow from one connected workflow

During service, HETable helps restaurants avoid breaking the guest journey across unrelated tools.

Hosts manage reservations, walk-ins, table status, and seating from the Host Stand and Reservations Manager.
Waitlist and Wait Board support live queue decisions and recent-seating awareness.
Self-seat and guest kiosk flows can be offered where the restaurant wants guest-led arrival options.
Floor teams carry execution forward through station maps and Pocket View.

Host Stand Reservations Manager Wait Board Self-Seat Guest Kiosk Pocket View

Review what happened and tighten control

HETable also gives operators a post-shift review layer so the next service starts cleaner.

Reports and outcomesReview covers, reservation status, assignment counts, and table-move activity.

GovernanceReview permissions, audit activity, API keys, webhooks, and security policies when the operation needs tighter control.

Group visibilityUse the Locations Dashboard for broader oversight when the operation spans more than one restaurant.

What teams open in HETableSee the real screen-level product surface by role. How HETable worksWalk setup, pre-shift, service, and review in order. Front-of-house workflow softwareSee how managers, hosts, servers, and guests fit together. HETable featuresBrowse the feature surface by module. Browse live restaurant reservationsUse the public HETable reservation directory to open live restaurant pages guests and Google can follow. Engineering overviewReview the technical boundary, controls, and launch-readiness summary.