More efficient service in hospitality with getService

Example 1: "First order"

So far

More walking running ways for waiters
Waiter must pay attention to closing the menu to ensure the readiness to order. of the guest. This usually requires additional running ways
Inconsistent quality of service
Some tables are difficult for waiters to see, so that the reaction times or waiting times can be different

with getService

Waiter recognizes order readiness
The guest signals his willingness to order by getService directly to the waiter, regardless of whether the menu is open or closed
Constant service quality
Every guest receives the same quality of service, no matter where the table is standing, or where the guests are sitting
Example 2: "Request menu"

So far

WAITER has 3 running ways
1. way
Sees signs and comes
2. way
Runs off to get card
3. way
Bring card to the table

with getService

WAITER has 1 itinerary
1 Path
Looks wish on his display and brings the card already at the first itinerary to the table
Example 3: "Reorder"

So far

GUEST loses time
look out, give characters, wait for waiter, requests the menu or orders from memory
Less sales
Wish can be overlooked if the waiter is not constantly working with large attention is running around

with getService

GUEST saves time
Scans the table cube and presses the button "Menu" or "Order"
More turnover
All wishes are directly visible, because they are shown on the waiter's display
Example 4: "Guest wants to pay"

So far

WAITER has 3 running ways
1. way
Must ask "together or separately."
2. way
To the receipt/payment system to print invoice
3. way
Back to the table to complete payment

with getService

WAITER has 1 itinerary
1 Path
Waiter sees payment request on his display, prints the invoice and goes to the table with it

Result:

Service is more efficient and guests are more satisfied

Back