Restaurant work, in detail

Reservations & guest service

Bring the front door, the floor and the guest’s next request into view.

Prepare the published floor, staffing, booking settings and protected guest flow. Enable the intended communication services.

Find the work you need to do.

HETable

Floor plans & builder

Full Platform; also HETable package

Make the floor match the room.

Arrange tables and room objects, edit capacities and labels, save a draft and publish the version the host team should use.

Before you use it: Prepare the physical layout and review the correct published floor and location.

Explore HETable in detail →

HETable

Host staffing & Smart Assign

Full Platform; also HETable package

Prepare the people and sections before seating.

Select the operating date and shift, review eligible servers and build sections. Preview an assignment proposal before an authorized person publishes it.

Before you use it: Map the workforce source and current employees. Publishing a schedule, checking in and granting access are separate actions.

Explore HETable in detail →

HETable

Reservations & waitlist

Full Platform; also HETable package

Bring each arrival into the same host workflow.

Review public bookings, walk-ins, call-ahead parties, quoted waits and reservation changes. Keep the party’s status and communication history together.

Before you use it: Configure booking availability and communication services; public booking and guest texts require their connected services.

Explore HETable in detail →

HETable

Seating & table states

Full Platform; also HETable package

Seat the party and keep the room current.

Seat or move parties, use linked tables where appropriate, and record seated, dirty, clean and available states. Review timers and the assigned server.

Before you use it: Use the correct floor, shift and party. Staff still decide whether the table and section are ready.

Explore HETable in detail →

HETable

Guest kiosk & private links

Full Platform; also HETable package

Give guests the right next step.

Offer configured waitlist or self-seat entry and protected EYS links for the guest’s current party, table and check context.

Before you use it: Enable the intended guest flow. Private links expire or can be revoked and do not grant full app access.

Explore HETable in detail →

HETable

Guest requests & staff response

Full Platform; also HETable package

Let a guest ask and see the response.

A protected guest request reaches the appropriate staff or server board. Authorized staff acknowledge or complete it, and the guest can review the resulting status.

Before you use it: Preserve the same party and check binding, especially when the physical table is reused. A request does not automatically become a POS command.

Explore HETable in detail →

HETable

Reports & protected service history

Full Platform; also HETable package

Review the floor with the right context.

Review available seating, assignment and service history with the applicable date and location. Staff access and private guest context remain scoped.

Before you use it: Choose authorized reviewers. Configuration and integration-management controls are restricted to their permitted roles.

Explore HETable in detail →

Inspect the actual software.

Demo restaurant. Open a capture at full size; its caption identifies the task and any material limitation.

The next handoff

See what carries forward.

Follow the source, the receiving app and the person responsible for the next decision.

Explore the connected journey →

Choose the coverage that fits.

Full Platform; also HETable package.

Compare packages and current availability →
Next step

One restaurant account. The whole operating day.

The Full Platform brings eight base applications and onboarding into one restaurant account. Apply to become a Launch Partner or book a walkthrough of the workflow you want to improve first.

Keep serving through an outage Supported POS and HETable workflows continue on the installed Hybrid Windows computer. Separate tablets and connected services need internet.
Roll out one workflow at a time Start with the clearest operational need, prove it with the team, and expand without creating another account system.
One sign-in for approved apps Each person sees only the restaurants, locations, and HospiEdge apps their account is allowed to open.