07 Help without explanations
Routine guest requests go straight to the right staff member
Guests can request help, cutlery, napkins, or another venue-specific service with a dedicated button.
The guest journey
The restaurant creates its own request list: bring cutlery, napkins, water, a high chair, or help with an order. The guest selects the right option with one tap.
01
Opens service requests
The guest finds service features on the home screen or in the persistent navigation bar.
02
Chooses a request
The guest taps a clear button instead of typing a message or explaining the request at length.
03
Identifies the table
The device automatically links the request to the guest’s table.
04
Gets confirmation
The guest sees that the request has been received by the restaurant team.
What changes on the floor
Simple requests are not lost in the noise of the dining room and take less time from both the guest and the team.
01
Standardization
Recurring requests become clear event types.
02
Right-person routing
Different requests can be routed to different roles or areas of responsibility.
03
A basis for improvement
Frequent requests show where a process needs to change.
The button set reflects real restaurant processes
Requests, recipients, and confirmations are configured for the venue format, floor areas, and shift roles.
Device
Potok
→
- configurable request directory
- table number and area
- assigned recipient
- acceptance and completion time
→
Restaurant system
iiko / r_keeper / API
See “Service Requests” on a live device
We will show the guest journey and define the integration requirements.