“What do you recommend?” is the question every server gets and almost nobody is trained for. It sounds like small talk and it is actually the highest-leverage moment of the table: handled well it builds trust, sells the right dish and prevents a complaint later. Handled badly it produces a shrug, a default answer, and a guest who orders something they do not enjoy.
Here is how to answer it properly, including what to say when you genuinely have not tasted the dish.
Why the honest default answer fails
Most servers answer with one of three things: “everything is good”, “the salmon is popular”, or their own personal favourite. All three are weak for the same reason. None of them tells the guest anything about themselves.
“Everything is good” is a non-answer that signals you either do not know the menu or do not want to commit. Guests hear it as a brush-off even when it is meant politely.
“The salmon is popular” is better and still generic. Popular with whom? A guest asking for a recommendation is asking to be helped, not to be given a sales statistic.
Your own favourite is fine as a last resort and it assumes the guest shares your taste, which is a coin flip. The dish you love may be the one they find too rich, too spicy, or too unusual.
The question behind the question
When a guest asks what you recommend, they are usually asking one of four different things, and reading which one saves you from answering the wrong question.
They cannot decide between two dishes they already like. Here they want permission and a tiebreaker, not a new suggestion.
They do not know the cuisine. Here they want orientation: what is this place actually good at, and what should a first-timer order.
They are worried about something specific. Portion size, spice level, an ingredient they dislike, a dietary restriction they have not mentioned yet. The recommendation request is a safe way to ask.
Or they are being polite and will order what they already wanted. Here the answer matters less and the interaction still matters.
| What they say | What they usually mean | What to do |
|---|---|---|
| ”What do you recommend?” (menu open, scanning) | Orientation, first visit | Name what the kitchen is known for |
| ”I cannot decide between these two” | Tiebreaker | Compare the two directly |
| ”What is good here?” (menu closed) | Politeness or trust | Two options, one question |
| ”Is the curry very spicy?” | A specific worry | Answer the worry, then recommend |
| ”What would you order?” | Your genuine opinion | Give it, with a reason |
The two-question answer that always works
The reliable pattern takes about ten seconds and works whichever version of the question you got.
Ask one narrowing question. “Are you in the mood for something light or something rich?” or “Do you eat seafood?” or “How hungry are you?” One question, not three, and pick the one that splits your menu most usefully.
Then give two options, not one. A single recommendation is a decision you made for them; two options with a reason each keeps them in control while still narrowing the field.
Then say which one you would pick and why. This is the part servers skip and the part guests remember, because it is the only bit that sounds like a person rather than a script.
The reason clause is where a one-sentence dish description earns its keep. For example: “Light or rich? Light, then I would look at the sea bass or the chicken with the herb salad. The sea bass comes with a lemon butter that is on the lighter side, the chicken is a bigger plate. If it were me I would take the sea bass, because the fish comes in fresh on Fridays.”
What to say about a dish you have never tasted
Every server faces this, especially in the first weeks and at any restaurant with a large menu or frequent specials. Lying is the wrong move and so is a blank stare.
Describe rather than evaluate, which is covered properly in what to say about a dish you have never tasted. You do not need to have eaten a dish to say accurately what is in it, how it is cooked, how large it is and what it comes with. That is information the guest wants and it is entirely honest.
Borrow the kitchen’s opinion, not your own. “The chef put that on this week and the kitchen is pleased with it” is true, useful and does not pretend to a taste you have not had.
Use what other guests say. “It has been going out all week and nobody has sent one back” is a real signal and an honest one.
And be straightforwardly honest when it matters. “I have not tried that one yet, but I can tell you exactly what is in it” costs nothing and buys a lot of trust. Guests forgive inexperience much faster than they forgive being misled.
What you need to know to answer well
Recommendations need a specific kind of menu knowledge, and it is not the same as being able to recite the menu.
For each dish, you want four things: the main ingredient and cooking method, the size relative to other dishes, the flavour direction (rich, light, spicy, sweet, sharp) and what it comes with. Those four let you answer almost any recommendation question honestly.
Add the allergen and dietary flags, because a recommendation that ignores them is worse than no recommendation. The major allergens the FDA requires packaged foods to declare are a sensible list to know cold, and what every server should know about allergens goes further than the label rules do.
Add the kitchen’s view: what the chef is proud of, what is new, what sells out. This is what makes you sound like you work there rather than like you read the menu.
That is a manageable amount of information per dish, which matters because short-term memory holds only a handful of items at once, and it is exactly what a flashcard set can hold. MenuFlashcards lets you build cards from a photo of your menu with those fields on the back, so the recommendation-relevant information is what you drill rather than just the dish names.
| Field to know | Why it matters for recommending |
|---|---|
| Main ingredient and method | The first thing a guest is choosing between |
| Relative size | Answers the hunger question |
| Flavour direction | Answers the mood question |
| What it comes with | Prevents the disappointed side-dish moment |
| Allergens and diet flags | Makes the recommendation safe |
| Kitchen’s opinion | Makes you sound like staff, not a reader |
Recommending in specific situations
A table with children. Recommend by what travels well: something familiar, something that arrives quickly, and mention what can be made plainer. Parents are usually asking about speed and fussiness rather than flavour.
A table sharing. Recommend a shape rather than a dish: two smaller plates and one larger, or a spread. Guests sharing want a plan more than they want a single item.
A table in a hurry. Say which dishes come out fastest, which is genuinely useful information and almost never volunteered.
A regular. Recommend something they have not had, and say so: “You usually take the ribeye. The lamb came in this week if you fancy a change.” Being remembered is worth more than the recommendation itself.
A guest who asks for the most expensive thing. Answer directly and add a reason, since they are usually celebrating and want the occasion acknowledged rather than the price justified.
Practising this before your shift
Take five dishes and, for each, say out loud in one sentence what it is and who it suits. Not the menu description: your sentence, the one you would actually say to a table.
Saying your answer out loud rather than reading it is the whole point, since testing yourself outperforms reviewing by a wide margin. Then pair them. For each of three guest moods, light, hearty, adventurous, name two dishes and which you would pick. That pairing exercise is what makes the ten-second answer available under pressure.
Then rehearse the honest line for a dish you have not tasted, out loud, until it sounds relaxed rather than apologetic.
Ten minutes covers all three, and short rehearsal repeated across days beats one long session, which is the finding behind the spacing effect. It is the difference between a recommendation that lands and a shrug. A menu deck with flavour and size on the back, which is what MenuFlashcards builds from a menu photo, makes the first exercise fast because the information is already in one place.
The mistake that costs the most
Recommending the dish you want to sell rather than the dish that fits. Guests notice, usually not consciously, and it shows up as a table that does not come back rather than as a complaint.
The commercial version of this argument is straightforward: an accurate recommendation produces a guest who enjoyed their meal, tips accordingly and returns. A pushed recommendation produces one larger bill and a worse relationship. Over a section of tables across a month, the first is worth more.
Recommending well is also easier than upselling, because you are answering a question you were asked rather than introducing one nobody wanted.
Recommending drinks, which is harder
Food recommendations have a shortcut: the guest usually knows roughly what they want to eat. Drinks are different, because a lot of guests genuinely do not know what they like beyond a category.
The narrowing question changes. For wine it is not “red or white” but “something light or something with more body”, or the more useful “what are you eating?” For cocktails it is “sweeter or drier”, which sorts nearly the entire list. For beer it is “hoppy or not”, which most drinkers can answer even when they cannot name a style.
Then the same two-option structure applies, and the reason clause matters more, because the guest has less to go on. “The grenache is softer and goes with the lamb, the syrah has more grip” gives them something to choose with.
Price needs handling here in a way it does not with food. Pointing at the list rather than saying a number out loud lets a guest choose a range without discussing money at the table, and it is standard practice for a reason.
The three-second version
Sometimes there is no time for the full pattern: you are double-sat, the kitchen is behind, and a table wants an answer now.
The compressed version is one dish and one reason. “The short rib, it is what the kitchen does best.” That is a complete recommendation and it takes three seconds.
It works because the reason clause is doing the load-bearing work. A dish name alone is a guess; a dish name with a reason is a recommendation. If you only ever remember one thing from this, remember to attach the reason.
Frequently asked questions
What is the best way to answer “what do you recommend?”
Ask one narrowing question, offer two options with a reason each, then say which you would choose and why. That takes ten seconds, keeps the guest in control, and sounds like a person rather than a script. A single recommendation removes their choice, and “everything is good” reads as a brush-off even when meant politely.
What should I say if I have not tried the dish?
Say so, then describe it accurately: what is in it, how it is cooked, how big it is and what it comes with. You can also borrow the kitchen’s view or report that it has been selling well, both of which are honest. Guests forgive inexperience quickly and remember being misled for a long time.
Should I recommend the most expensive dish?
Only when it genuinely fits what the guest asked for. Recommending by margin rather than by fit is noticeable, and it costs return visits rather than producing complaints. An accurate recommendation earns a guest who enjoyed their meal and comes back, which is worth more across a month than one larger bill.
How do I learn a menu well enough to recommend from it?
Learn four things per dish: main ingredient and cooking method, relative size, flavour direction and what it comes with, plus allergens. That is a different set from the menu description and it is what recommendation questions actually need. Drilling those fields as flashcards, which MenuFlashcards builds from a photo of your menu, is faster than re-reading the menu.
What do I do when a guest asks and then orders something else anyway?
Nothing, and it is not a failure. Plenty of guests ask out of politeness or to confirm a decision they had already made. The interaction still did its job if it was warm and informed, and the guest who felt looked after is the one who asks for your section next time.
