03 Calm contact with staff

Guests can call a waiter quietly, without gestures or waiting

Guests call a waiter with one tap, without raising a hand, searching for eye contact, or trying to get attention.

The guest calls a waiter with one tap on the Potok device and sees confirmation that a staff member is already on the way
No raised hands or attempts to get attention: the request is sent from a specific table, and the guest sees confirmation right away.

The guest journey

When guests need help, they tap the button on the Potok device. The request is linked to a specific table immediately, and a clear confirmation appears on screen. There is no need to raise a hand, scan the room, or try to catch a staff member’s eye.

01

Taps “Call”

The button is available on the device’s main screen and always in front of the guest.

02

Selects a reason

If needed, the guest chooses help, a menu question, cutlery, the bill, or another restaurant scenario.

03

Sees confirmation

The screen confirms that the request was received and the waiter is already heading to the table.

04

Keeps enjoying the visit

Guests do not have to watch the room, wave, or try to get attention again.

What changes on the floor

The call becomes calm and clear for guests, while the team receives a precise signal without shouting, gestures, or lost requests.

01

No need to raise a hand

The request is sent with one tap, without conspicuous gestures, calling out, or unnecessary attention from others.

02

No need to look for a waiter

The request reaches the team even if a staff member is serving another table or temporarily out of sight.

03

It’s clear the request was received

On-screen confirmation removes uncertainty: guests know they have been noticed and can wait calmly for a staff member.

A table-specific call reaches the team’s work channel

Potok sends the table number, reason for the request, and creation time. Notifications can go to a screen, work app, terminal, or another supported restaurant channel.

Device

Potok

→

  • table number and zone
  • service request type
  • event creation time
  • acknowledgement and completion status

→

Restaurant system

iiko / r_keeper / API

See “Waiter Call” on a live device

We’ll show the guest journey and define the integration requirements.