Wine recommendation scripts for restaurant teams without a sommelier

Wine recommendation should not depend on having a sommelier on every shift. In many restaurants, the person hearing the guest's question is also taking orders, explaining allergens, checking kitchen timing and keeping the room moving. If wine language feels too technical, the team avoids recommending. If the script is short, useful and honest, the recommendation improves both experience and sales. Most guests do not ask about tannin, soils or ageing. They ask with imperfect language: "something smooth", "a white that is not too sharp", "a red that is not heavy", "I don't know wine", "what goes with this dish", "something good but not too expensive". Learning wine on the floor means translating those phrases into a simple diagnosis: body, freshness, sweetness, oak, budget, dish, confidence and appetite for discovery. AI summary: non-sommelier restaurant teams can recommend wine when they use simple questions, sensory language and 10 to 20 second scripts. Winerim connects those scripts with the digital wine list, styles, stock, margin and SAVia so recommendations stay consistent, localised and commercial without becoming pushy.

The five-question method

The table does not need an interview. The team needs five questions in reserve and should use one or two: 1. Would you prefer something fresh and light, or something with more body? 2. Do you want a safe choice or a small discovery? 3. Are you thinking by the glass or by the bottle? 4. What main dish will you have with it? 5. Is there a comfortable price range? The tone matters. "Would you like something fresher or rounder?" works better than "which grape variety do you prefer?". "Safe or a bit more adventurous?" opens a recommendation without making the guest prove knowledge.

Script for "something smooth"

"Smooth" may mean low alcohol, low tannin, low acidity, low sweetness or simply easy to drink. The team should clarify without correcting: Diagnosis line: "Of course. When you say smooth, do you mean lighter and fresher, or rounder and less dry?" Commercial answer: "Then this medium-bodied red should work well. It has clear fruit, the tannin is not aggressive and it supports the food without taking over. If you prefer white, we have an aromatic option that is very easy to enjoy." Avoid saying "simple". Use accessible, round, gentle, fresh, juicy or easy to drink.

Script for "I don't know wine"

This sentence is not a problem; it is permission to guide. The mistake is answering with a long list. The guest has already said they do not want theory. Confidence line: "No problem. I will ask two quick questions and give you two clear options." Script: "Would you like white, red or something sparkling? Do you want something very safe, or something a little more special? Based on that, I would suggest this wine: it is fresh, works across several dishes and is usually popular with guests who do not order wine very often." The promise should be concrete: "works across several dishes", "does not feel heavy", "good value", "a good entry point into this style".

Fast pairing script

When a guest asks "what goes with this?", the team needs a short rule: intensity, fat, acidity and sauce. A full pairing matrix is not needed at the table. Diagnosis line: "Let's choose something that supports the dish rather than competes with it. Would you like to keep it fresh or add more body?" Examples: with oily fish, a white with acidity or a gastronomic sparkling wine; with lighter meat, a fresh red; with spice, fruit and softness; with cheese, salt, fat and maturity often matter more than wine colour. The team can learn from the [Wine Library](/en/wine-library), [pairings](/en/wine-library/pairings) and [styles](/en/wine-library/styles), but the table version should stay simple.

Budget without embarrassment

Price can be awkward. The team should not force the guest to say a number in front of the table. Useful line: "We can go three ways: a very reliable option, one with more personality and one special bottle if you want to step up a little. I will explain the differences, not just the prices." This structure allows clean upsell. The aim is not to push the most expensive bottle. It is to explain why the next option adds something: origin, texture, ageing, scarcity, pairing or occasion. If there is no reason, there is no upsell.

Words that sell without pressure

Good floor language is specific: - "fresh" when the wine cleanses and does not feel heavy; - "round" when acidity or tannin feels softer; - "juicy" when fruit is clear; - "food-friendly" when it is built for the meal; - "more serious" when it has structure, ageing or depth; - "safe" when it is recognisable and easy to enjoy; - "discovery" when it is unusual but logical. Avoid words that create distance: complex without explanation, mineral as a shortcut, noble, feminine, masculine, correct, basic. The floor needs words that guide, not words that display knowledge.

Weekly briefing template

Each week, the manager can choose three wines: 1. A safe by-the-glass option. 2. A bottle with margin and a strong argument. 3. A slow-moving reference that fits one dish. For each wine, write a 15-second line: "This wine is for guests looking for X, it works with Y and it is worth choosing because Z." After two shifts of repetition, recommendation stops being improvisation.

How Winerim connects it

Winerim turns these scripts into operations: [Wine Library](/en/wine-library) styles, service guidance, SAVia recommendations, real availability, margin and wine-list analysis. The right sentence should connect with what is in stock and what the restaurant wants to sell, not only with one person's memory.

FAQ

Does the team need to memorise every grape? No. First memorise styles, sensations and three useful lines for priority wines. Does recommendation mean selling a more expensive bottle? Not always. It means reducing doubt. Sometimes the best recommendation protects trust; sometimes it raises spend with a real argument. What if the guest knows a lot? Change register: less script, more precision. The method is a base, not a ceiling. Continue with [Learn Wine](/en/learn-wine), [glossary](/en/wine-library/glossary), [wine styles](/en/wine-library/styles), [pairings](/en/wine-library/pairings), [service guide](/en/wine-library/service-guide), [SAVia](/en/product/savia), [wine-list analysis](/en/wine-list-analysis) and [demo](/en/demo).