The Three Questions Every Server Should Be Able to Answer Cold

The first one is the most important. What's in this dish that someone might be allergic to?

I'm not talking about a rehearsed disclaimer. I'm not talking about "I can check with the kitchen." I'm talking about a server who, when table four asks about the spicy tuna roll or the pasta alla norma, can look that guest in the eye and say with confidence: this has soy, this has gluten, this was made on shared equipment with tree nuts. Real information, delivered in real time.

At Black Barrel Tavern we added a walnut romesco to the burger menu last spring. Good sauce. Really good. But walnuts don't announce themselves. A guest sees "burger with romesco" and doesn't think tree nut, because most people don't know what romesco is. If your server doesn't flag that, and the wrong guest orders that burger, you're not just looking at a bad Yelp review. You're looking at a hospital visit. The liability aside, you've failed someone who trusted you with their health.

This one has to be drilled until it's automatic. Not memorized-and-forgotten from a one-time pre-shift, but actually automatic. The same way a server knows the table numbers, they need to know the allergens on every plate. That's non-negotiable.

The second question is one most training programs don't even bother with. What wine goes with this?

I know, I know. Not every restaurant is a fine dining operation. But whether you're running a 400-cover Italian spot or a burger-and-beer joint, your guests are going to order drinks with their food. If your server can't even offer a suggestion, you're leaving real money on the table. That's not an opinion. That's math.

A server who can say "that braise goes really well with our Malbec, it's got enough body to stand up to the richness" is not being a sommelier. They're being helpful. That's a $14 glass add-on that happens because the server had one specific, confident, well-placed sentence. Multiply that by six tables a night, five nights a week, 50 servers over the life of your business, and you start to understand why wine knowledge isn't a luxury skill. It's a revenue skill.

At Fat Tommy's the most consistent upsell we have isn't a dessert and it isn't a premium cut. It's a specific beer pairing one of our servers started doing two summers ago. She'd recommend a local wheat beer with the fish sandwich, every time, with a one-line reason. Started doing it on her own because she genuinely thought they went together. Her check average was 15 percent higher than the rest of the floor all summer. The other servers noticed. We made it part of training.

That's the thing about pairing knowledge. It doesn't have to be fancy. It just has to be specific and genuine. Guests can feel the difference between a server who's saying words and a server who actually believes what they're recommending.

Third question. What's the upsell on this item?

Every dish on your menu has a natural next step. An obvious add, a better version, a companion item that makes it more complete. A soup that goes with the sandwich. A premium protein substitute. A side that turns a light lunch into a real meal. Your servers need to know what those are and, more importantly, when to mention them.

This is where a lot of operators get it wrong. They think upselling means training servers to be pushy. It doesn't. It means training servers to know the menu well enough to make one good, well-timed suggestion. There's a massive difference between a server who blurts "do you want to add shrimp for five dollars?" and a server who says "a lot of people add the crispy shrimp to that one, it's worth it." One feels like a script. The other feels like advice.

If your server can't tell you what the natural upsell is on a dish, they don't know the menu. And if they don't know the menu, they're not an asset to that table. They're furniture.

Here's the hard truth. Most restaurants train on the "what" and skip the "why" and the "what else." They get staff through a menu rundown, maybe a tasting, maybe a test on the ingredients. And then they call it done. The allergen question, the pairing question, the upsell question get answered in the first week and then never revisited. New sauces get added. Seasonal items rotate. A walnut romesco shows up on the menu and nobody briefs the floor.

That's the gap I've been trying to close since I started building the platform I built, because I watched it happen for 30 years in my own restaurants. The knowledge needs refreshing, constantly, because menus aren't static. And the refresh has to happen faster than a quarterly all-hands meeting.

Three questions. Every menu item. Every server. If your people can answer those cold, you've got a floor that's safe, effective, and actually selling. If they can't, you know exactly where to start.

Have a great day! — Terry
Your AI Restaurant Guy