Electronic waiter for a restaurant

The guest orders.The team keeps up.

Potok removes the wait between menu, order, service and payment right at the restaurant table.

Potok table electronic waiter in a restaurant interior

Revenue growth scenario of 40%

The screen shows the target: the revenue index changes from 100 to 140. This is an example visualization, not a guaranteed forecast.

Target example: +40%. The actual result is compared with the baseline period and control tables during the pilot.

Metric system

Six benefits. Twelve metrics.

In every video the baseline period is set to 100. Pilot values are higher or lower depending on which direction of the metric is beneficial. These are demonstration indexes, not a promise of results.

Less waiting

The guest request is linked to the table at once and reaches the right team member. In the beneficial scenario both time metrics go down.

  • Time to first order100 → 64
  • From bill request to payment100 → 58
Actual intervals are compared on pilot and control tables.
The effect is assessed together with room occupancy, restaurant format and time of day.

Faster table turnover

Fewer pauses between choosing, ordering, billing and completing payment can shorten the visit and free the table sooner.

  • Visit duration100 → 82
  • Seatings per shift100 → 118

Higher average check potential

A drink, a dessert or a modifier is offered in the context of the dish while the guest is still building the order.

  • Impressions and add-ons100 → 132
  • Pilot average check100 → 116
Growth is checked separately for each recommendation scenario and comparable period.
The guest confirms items and modifiers before the order is passed to the restaurant system.

Less routine and fewer manual errors

A clear digital scenario helps reduce re-entry and passes the guest’s exact action to the team faster.

  • Order corrections100 → 61
  • Team reaction time100 → 72

Payment and tips in one scenario

The guest chooses a connected payment method and can leave a tip without waiting for a portable terminal.

  • Share of self-service payments100 → 138
  • Tip frequency and amount100 → 121
The metrics depend on the payment configuration connected by the restaurant.
Scaling starts after a stable pilot and a check of data exchange.

Scaling without changing the POS

The integration layer connects Potok with the POS system, the loyalty program and the content of the restaurant or chain.

  • Exchange stability100 → 112
  • Speed of publishing changes100 → 145

One screen accompanies the whole visit

The path stays clear for the guest, and events are passed to the restaurant system.

01

Chooses

Browses the menu and sees current offers.

02

Orders

Confirms items and modifiers on the screen.

03

Manages the visit

Orders more, calls a staff member and checks the bill.

04

Pays

Finishes the visit in a convenient connected way.

We start with selected tables

We will record the baseline metrics, launch the scenarios and compare the pilot result before scaling.