How can a tourist restaurant serve guests who don't read the menu?
Let them ask about it in their own language. With WaiterPilot, a tourist scans the QR code on the table, asks what a dish is, what's spicy or what comes with it, and gets answers from your menu in the language they wrote in. They confirm the order on their phone and your staff check the first order before the kitchen cooks. Your dish names, prices and printed menu stay as they are.
Updated
What goes wrong at a tourist table today?
Mostly time and guesswork: guests can't read the dishes, servers can't explain them in every language, and the table waits.
- The menu is in a language the table doesn't read. Guests point at a photo, order the one dish they recognise or wait for the one server who speaks some English.
- Every dish needs explaining. "What is it? Is it spicy? Is there pork? What comes with it?" asked at table after table, during the rush.
- Choices get missed. A side, a cooking level or a size is never asked, so the plate that arrives isn't what the guest expected.
- Allergies get lost in translation. A guest tries to explain an allergy with gestures or a translation app, at a noisy table.
- The bill is a puzzle. Visitors don't know your service charge or tipping customs, the group wants to split, and nobody can find a server to ask for the check.
How does WaiterPilot handle each of those?
The chat takes the explaining; your staff keep the decisions. Each line below is what the product does today, with its limit.
| Situation | What WaiterPilot does | The limit |
|---|---|---|
| Guests can't read the menu | The chat answers questions about your dishes in the language the guest writes in, from your menu. Tested in English, Arabic (several dialects) and Spanish; it answers most other languages too | Guest-screen buttons are English or Arabic only |
| Dish names in the local language | Dish names stay as written on your menu; the chat explains them using your descriptions, and a dish name in the chat opens its photo | Explanations are only as good as your descriptions and photos |
| Missed choices | If a dish needs a side, a cooking level or another option, the chat asks before the dish goes in the cart | Only choices you set up on the menu are asked |
| Allergy questions | Gives what the menu says, in the guest's language, and asks the guest to confirm with staff | Staff aren't alerted automatically; a person must go to the table |
| Special requests | "No onions" goes on the ticket as a note | Notes aren't translated; a Japanese note reaches the kitchen in Japanese |
| Arabic-speaking visitors | Replies in the Arabic you choose for your restaurant: Jordanian, Lebanese, Egyptian, Gulf (Emirati), Saudi or Modern Standard Arabic | A visitor from the Gulf hears your chosen dialect, not necessarily their own |
| Getting a server | Guests call a waiter or ask for the check from their phone; it shows on the floor screen within seconds, with cash or card | Someone has to watch the floor screen |
| Bills and tipping customs | The live bill shows tax and any service charge you set, and the group can split it evenly or see each person's share | No payment in the app; guests pay your staff as usual |
What does a visitor's question look like?
A visitor at a Spanish restaurant writes in English about a dish on a Spanish-language menu. The dish keeps its menu name; the chat explains it from the menu's description.
What is pulpo a la gallega? Is it spicy?
Pulpo a la gallega is octopus with boiled potatoes, olive oil, salt and paprika, as the menu describes it. The menu doesn't describe it as spicy. Would you like one?
Yes, one please, and two glasses of water.
One pulpo a la gallega and two waters. Tap Confirm to send it to the staff.
1 × Pulpo a la gallega
2 × Agua
What should you prepare before the season?
A tourist-ready menu and a staff routine for the things the chat hands back to people.
- Describe every dish in plain words. Main ingredients, how it's cooked, whether it's spicy, what comes with it. The chat translates your meaning, so give it something to translate.
- List allergens and diets. Write allergens, pork, alcohol and vegetarian status into descriptions where true. See allergies and dietary questions.
- Add dish photos. A photo answers "what is it?" in every language.
- Set your service charge on the bill. If you add a service charge, set it so visitors see it on the live bill before they pay, instead of guessing at tips.
- Decide who reads foreign-language notes. Keep a translation app on one staff phone at the pass, and check notes when confirming each table's first order.
- Keep the printed menu. Some visitors won't scan, have no data roaming or a flat battery. The printed menu and a server still work.
- Watch which languages your guests use. Owner reports show the languages guests wrote in, and the questions the chat couldn't answer, so you know what to add next.
Who should choose something else?
If your tourists mainly need a translated menu to read, or want to pay on their phone, other tools fit better.
- You need every word on the guest screen in, say, Japanese or Korean. Look for a menu tool that translates the whole interface. Our buttons are English or Arabic.
- Guests want to pay on their phone. WaiterPilot takes no payment. Order-and-pay and pay-at-table tools do.
- Orders must go into your POS or kitchen printer. WaiterPilot has no POS or printer connection; staff ring sales into your till. See works with your POS.
- You mostly serve pre-booked tour groups on set menus. There is little to ask or order; a printed set menu in the group's language does the job.
Questions from tourist restaurants
Which languages can tourists use?
Guests chat in their own language. We have tested English, Arabic (several dialects) and Spanish, and it answers most other languages too. If your visitors often use another language, try it with us during your demo.
Do I need to translate my menu first?
No. The chat answers from your menu as it is, in the guest's language. Clear descriptions make the answers better in every language.
Do tourists need to download an app or sign up?
No. The QR code opens your menu in the phone's browser, with no app and no sign-up. They do need a data connection or your Wi-Fi.
Will the kitchen get orders in Chinese or German?
No. Tickets show dish and option names as on your menu. Only notes appear as the request was taken, not translated.
Can a group split the bill?
Yes. Each phone at the table sees the live bill and can split it evenly or see just its own share. Payment is with your staff.
Does it replace the printed menu or our servers?
No. It works alongside your printed menu, and your servers still serve, handle allergies and take payment.
How much does it cost?
After 30 days free, $200 per location per month, with free setup, 0% commission and no contract. See pricing.
What should you read next?
- Multilingual orderingThe same order in English, Spanish and Arabic.
- Serving tourists who don't speak your languageA 12-point checklist for any restaurant.
- Allergies and dietary questionsWhat the chat answers and what staff decide.
- Hotel restaurantsInternational guests, with no room service.
- From scan to servedThe order flow your staff work with.