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.
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.
- Build or update the floor plan and publish the version the team should actually use.
- Create sections and stations so the stand and floor team work from the same coverage map.
- Open the Locations Dashboard when the group manages more than one restaurant.
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.
- Confirm booking rules such as hours, intervals, party limits, and lead time.
- Copy the restaurant’s public booking widget link or public location page into the restaurant website, button flow, or guest communications when those paths are live.
- Link or import the schedule and generate Smart Assign when the team wants stronger coverage planning.
- Review staff ratings and roster relationships before finalizing the floor.
Booking proof before service starts
- Booking Settings generates the direct public HETable booking widget link managers can copy onto the restaurant’s own site.
- Public location pages can support discovery in the HETable reservation directory when the restaurant wants a crawlable path before the final booking click.
- Confirmation and cancellation links keep guest follow-up tied to the reservation record before hosts work arrivals during service.
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.
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.
- Use Station Assignments to print or share floor coverage maps.
- Use Pocket View so servers can mark tables dirty or available while they are on the floor.
- Review table moves and section balance when the shift needs adjustments.
5. Review, control, and improve
After service, managers can use HETable to review what happened and keep the workflow governed over time.
- Run reports for covers, reservations, assignment counts, and related operating signals.
- Review audit history when permissions, keys, or policy settings change.
- Control access with permissions, user overrides, API keys, webhooks, and 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.