Guests ask fewer wine questions than many restaurants expect. The wording changes, but the job is usually the same: help someone avoid a bottle that feels wrong for the table.
A floor team does not need to recite regions, grapes and production methods before answering. It needs a short, truthful answer, followed by one useful distinction. The best answers name the style, connect it to the food or occasion, and state a limit where one matters.
“Is this dry?”
This is often a request for reassurance, not a technical examination of residual sugar. Guests may be trying to avoid a wine that tastes overtly sweet, heavily fruity, soft, or simply unfamiliar.
Do not answer with a bare yes. Most still table wines on a restaurant list are dry in the technical sense, yet they can feel very different. A direct answer is more useful:
“Yes, it is dry. It has ripe fruit, so it is not severe, but it does not taste sweet.”
Or:
“It is dry and crisp rather than fruity and soft.”
For red wine, the equivalent distinction is often fruit versus sweetness:
“It is dry, with dark-fruit flavour and firm tannin. It is not sweet, but it is more structured than a light red.”
The team should avoid correcting the guest’s language. Saying that all the still wines are dry may be technically defensible and practically useless. Find out what the word means at that table. A quick follow-up works: “Are you looking for something very crisp, or something rounder and more fruity?”
That turns an imprecise question into a usable choice without making the guest feel they asked it badly.
“What goes with this?”
Guests rarely need a grand rule about red with meat and white with fish. They need help with the dish in front of them, including its sauce, spice, richness and cooking method.
A good answer starts with the dominant part of the plate. Grilled fish with a rich butter sauce is not the same pairing problem as raw fish with citrus. Roast chicken with herbs is not the same as chicken in a creamy sauce. A spicy dish needs a different answer from a simply savoury one.
Keep the recommendation specific:
“With the grilled lamb, I would choose the medium-bodied red rather than the fuller one. It has enough structure for the meat but will not dominate the herbs.”
“For the rich sauce, the fresher white will work better than the more aromatic one. Its acidity will keep the dish from feeling heavy.”
“The lighter red is the safer choice if the table is ordering both the mushroom dish and the pork.”
The word “safe” can be useful when used honestly. It tells guests that the wine is designed to work across several dishes, not to be a dramatic match for one plate. When a recommendation involves a trade-off, say so. A delicate white may be excellent with one starter and disappear beside a strongly flavoured main. A bold red may suit one person’s steak and overwhelm another person’s fish.
The practical habit is simple: name the dish, name the relevant feature of the wine, and name the reason. “This has freshness for the sauce” is better than “this is a great pairing.”
“I want a red that isn’t too heavy”
This is one of the most common requests and one of the easiest to mishandle. “Heavy” can mean high alcohol, strong tannin, dense fruit, oak flavour, warmth, or all of them at once. The answer should separate those things rather than pretend they are identical.
A useful first response is:
“Would you prefer something light and fresh, or something with more fruit but softer tannin?”
That question gives the guest two understandable directions. One may lead to a pale, bright, lower-tannin style. The other may lead to a rounder red that is still easy to drink. Neither requires a lecture.
Then answer in plain terms:
“This is lighter in body, with bright fruit and little tannin.”
“This has more weight, but the tannin is soft, so it will not feel drying.”
“This is fresh rather than rich. If you dislike sharp acidity, I would choose the other option.”
That last sentence matters. A server should not treat “light” as a universal virtue. Some guests asking for a lighter red still want a ripe, generous style. Others want tension and freshness. The right answer is not the lightest wine on the list. It is the wine that matches the guest’s version of light.
“Is this one good?”
This question is not asking for an objective verdict. It usually means: is this reliable, is it suitable for what we are eating, and will we regret ordering it?
The weakest response is “They are all good.” It sounds evasive because it is. The wine list may have been assembled with care, but the guest is asking for a judgement between actual options.
Give one. Then make it relevant:
“It is a good choice if you want a fresh, straightforward white for the seafood. It is not the richest option on the list.”
“It is well suited to the steak, especially if you like firmer, drier reds. If you prefer softer fruit, I would point you elsewhere.”
“It is a reliable bottle for the whole table because it is neither very oaky nor very tannic.”
This is also the moment to avoid false certainty. No wine suits every palate, every dish and every mood. A clear limitation makes a recommendation more credible. “Not the richest option” and “better for people who like firmer reds” are useful information, not admissions of weakness.
For a glass recommendation, offer a comparison rather than a verdict: “The first is brighter and lighter; the second is rounder and more textured.” Guests can choose between two clear descriptions far more easily than between a string of grape names.
The floor team’s job is not to prove knowledge. It is to make a defensible recommendation in language the table can use. Keep the answer short, state the trade-off, and give a second option when the first depends on taste.